

The latter is established by performing a new hash calculation of each data block in the backup and comparing it against the hash that was originally calculated and recorded in the backup when the backup was first created. All it does is confirm that the backup is completely readable and that it has not been altered since its original creation. The verification operation, even the auto-verify option that runs immediately after a backup, does NOT recheck the data in the backup against the original source data.

Click to expand.There are arguments both ways, but it's important to understand one thing that seems to surprise users.
