Skip to main content

Validation within seconds - Trustable?

Thread needs solution

Validation within seconds - Trustable?

I just upgraded to b6569. In the column of enumeration of my backups there are backups which have been validated before. After the upgrade to b6569 the formerly existing checkmark of validation no longer existed. Therfore I did a validation run on one of these backups.

To my surprise this run finished within seconds. So I ran the Log Viewer Utility from this forum: it took only 9 seconds (Validation_log.png). The backup is - contrary to the folder name - on an ordinary Seagate ST2000DM001 (properties.png).

Now my question:
Is it trustable that the validation of a 72 GB file finished within 9 seconds?

Wolf

 

Attachment Size
validation_log.png 35.29 KB
properties.png 19.3 KB
0 Users found this helpful

Wolf,

Thanks for using the log viewer & posting the results...Version 2 of the log viewer has been released and can be downloaded at:

https://forum.acronis.com/forum/115626

9 seconds is impossible and must be investigated further.

One of the fastest SSDs has a read speed of 504MBs/second.  So, by my rough calculation, just reading the 72 GB file would take almost 144 seconds...and that assumes you have the fastest SSD in your computer.

So, I recommend you perform at least one more validation.

FtrPilot

I was under the impression if a backup has already been validated, it stores that information in the database, so it might make sense that a previously validated backup would go so quickly.  However, if it was then modified with another INC or DIF after that, it would revalidate the entire chain again since it had been modified.  If this is a "static" (non changing backup).  I would possibly delete the backup settings (not the entire backup files though) withing Acronis and then add it back and validate it again and see if it still goes as quickly or not.

Typcially, I don't validate anymore - just don't trust it 100% (that's me personally though because I only believe a true validation can be done by attempting a restore).  In most cases, if I can double click a .tib and Windows can navigate it without issue, that's validation enough for me.  Alternatively, mounting the .tib successfully is basically the same verification.