What is the best technique to ensure that a backup is always 100% ok?
I've been surprised a few times when trying to restore a backup and get the warning that the backup had some kind of flaw.
And this even after validation say that the backup is ok.
Currently, with every backup I make (daily, incremental), I force ATI 2018 to do a full validation after the backup is finalized (which consumes HOURS, but I still think it's worth it).
Within the ATI 2018 environment, what would be the best way to ensure that a backup is 100% available for recovery?


- Log in to post comments

Espartano,
A good way to check if a backup is good is to open a tib file Wndows File Explorer by double clicking on the file name.
Doing so effectively mounts the file as a drive so that it can be navigated. Although this is not a guarantee that a restore of the file will work it is as close as you can get without actually restoring it.
Personally, I do this all the time and I have never had a tib file I could mount not work when recovered.
- Log in to post comments