1528 - Types of Integrity Checks

Integrity Checks are a feature of the Storage Platform Console that allow you to check that the data in a backup account is complete and uncorrupted. You can run an Integrity Check on an account at any time by following the steps in Article 1103.

There are three types of Integrity Checks.

• Quick Integrity Check

During a Quick Integrity Check, our system reads all the indexes on the StorageServer to check that these are not corrupted and to determine which backed-up files need to be present. At the same time, the system scans through all the backed-up files to ensure that all files referenced in the indexes are in fact present. If the files match what is in their index, the check passes.

• Standard Integrity Check

A Standard Integrity Check entails a Quick Integrity Check as well as decryption of the backed-up files to scan them for disk errors or any form of corruption. Note that this process may be time-consuming. For a more convenient alternative, consider data verification.

• Full Integrity Check

A Standard Integrity Check entails a Quick Integrity Check as well as decompression of all backed-up files into memory, calculating their hashes and checking these against the source files. For files that have been modified, we apply their patch chains to check that these function correctly and without errors, i.e. that all updates that have been made to the backed-up file match the updates made to the source file. Note that this process requires significantly more overhead on the StorageServer than a Quick or Standard Integrity Check. A Full Integrity Check should not be necessary if a Standard Integrity Check has passed.

Applying fixes

When running any of the Integrity Checks, you have the option to apply fixes. If you do not select this option, our system will simply read all the files and warn you about any errors. If you enable fixes, the data index will be rebuilt from scratch, and the StorageServer will be allowed to make changes to the data in order to address any errors that are found. For example, if a file is missing, the StorageServer will attempt to retrieve it from the MirrorServer.