Mandatory and Full Consistency Checks

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

The consistency check is a technique that provides avoiding data losses. By finding any discrepancies, a user is notified if some backup objects are missing in backup storage or there is a mismatch between object sizes or modification dates.

Once a consistency check is run, the request goes to 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 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.

Mandatory Consistency Check

In the new backup format, the mandatory consistency check is a current-generation check. The light consistency check is mandatory for all plans and is executed before any Backup Plan run.

Full Consistency Check

Full consistency check implies all backup plan generation checks except the current generation. Once the full consistency check succeeds, a user can be sure that backed up data is ready for restore.