Backup Consistency Checks

When backing up data, a user assumes that it is possible to restore data, but this is not always the case if backup data is corrupted. This issue can have many causes, ranging from technical problems with the cloud provider’s service to industrial sabotage.

The consistency check is a technique that helps avoid data loss. If any discrepancies are found, the user is notified that some backup objects are missing in backup storage or that there is a mismatch between object sizes or modification dates.

Once a consistency check is run, the request goes to the backup storage. A file list is requested along with metadata.

In all cases, the user is notified about backup damage. If something happened, MSP360 Backup runs a full backup automatically. Possible damage to previous generations is also monitored.

Once a consistency check is executed, the user is aware of any possible mismatches and is able to plan further actions to solve possible issues.

A consistency check can be created as a separate plan using the command line interface or in the Management Console.

Mandatory Consistency Check

In the new backup format, the mandatory consistency check is the current generation check. The current generation consistency check is mandatory for all plans and is executed before starting any backup plan.

Full Consistency Check

The full consistency check performs backup plan generation checks with the exception of the current generation check, which is the subject of a mandatory consistency check. After a successful full consistency check, the user can be sure that backed-up data is ready to be restored.