Skip to main content

Backup (made with Update 1) validates on one PC, fails as corrupt on another.

Thread needs solution

First time this has happened. It may be a conincidence, but I upgraded to Update 1 this week.

PC "A" does full backup of files (not image) to PC "B" but validation failed "the file is corrupt".

I ran validation locally on PC "B" and it passed.

Tried running validation again from PC "A" but again it fails.

Any ideas?! Other backups are running and validating fine. There is no network problem.

0 Users found this helpful

Hello Jon,

Thank you for posting. I will do my best to assist you.

Does this happen only with that specific backup or with all backups created on PC A on a regular basis?

Can you transfer that backup to the PC A, store it locally and run validation one more time. Does it pass?

Please let me know if you have additional questions.

Thank you.

Anton, I believe this was true for all backups made originally with build 0.5. At least I had two such backups - one made on PC "A", backed up to "B" and one made on "B", backed up to "A". Both failed validation the first time they backed up after update 1, yet the backup would validate on the PC it was stored. Of course, in each case that PC did not have any "history", it was just being asked to validate a standalone backup file.

Unfortunately I cannot do any further testing as I created a new backup task on each PC, performed new backups with that task and then deleted the old ones. These backups are now working fine, including validation.

Hello Jon,

Thank you for the follow-up.

Just in case I sent this case to our testing lab and in case we will be able to reproduce this issue, I will let you know.

If you need additional help, please let me know.

Thank you.