New
#841
Although I have never found a bad image, i have set the default verify to on and I always verify every image upon creation.
I have also created a second backup definition file without the auto verification, which I run only for quick incrementals, as replacement of Windows Restore point and for which I don't really care if they go bad. Nothing really important to lose, as I can always restore the corresponding full or differential image. Even in that case, I have never encountered a bad image.
I have neverhad a backup fail due to verification for many years. That was needed in the days of writing to dvds as backup medium but modern hard drives just do not cause it. I have turned verification off.
Sure. I am taking a teensy weeny risk but that is my choice.
So question guys and gals, have any of you ever had a verification failure in a long time?
Happened to me couple of times. backup would finish but would not pass verification. Once it was due to not 100% good backup disk and once because of overclocked RAM. Since then I set auto verification. Only 100% good and verified backup is real backup.
Had one fail a month ago. Re-verified and it passed. Being suspicious, I ran another backup and verification was fine. The destination drive was a USB 3 enclosure newly formatted as RAID 0 with windows storage spaces so I deleted it and set it up again. Since then no verification fails. The data isn’t super important so I’m not too concerned.
For me verifying backups is like wearing a seat belt. I haven't been in car accident where I need it but I still wear it.
I just don't know when I'll need it.
New updates v7.2.4884