Consistency Check Warnings (code 2500, 2501, 2502)

Situation

A backup plan terminates with one of the following warnings:

  • Consistency Check detected an issue. One or more data parts are missing on backup storage for restore point: (restore point date). This restore point and all the following restore points may not be restored properly. A full backup was executed instead of the planned incremental backup and a new generation was created

  • Consistency Check detected an issue. Data part sizes on backup storage do not match the original values for restore point: (restore point date). This restore point and all the following restore points may not be restored properly. A full backup has been executed instead of incremental backup and a new generation was created

  • Consistency Check detected an issue. Data part modification date on backup storage does not match its original values for restore point: (restore point date). It may happen for objective reasons. The current generation was continued

Cause

These warnings inform you about some discrepancies detected by the consistency check that is executed before each backup plan run. All of them are related to peculiarities of the new backup format.

To read more about the new backup format, refer to the New Backup Format section at help.msp360.com

The new backup format implies a signature for data parts comparison for a current restore point, which is based on hash sums. Thus:

  • The warning 2500 means consistency check detected that one or more data parts are missing on backup storage. This situation may lead to an invalid restore from the current restore point. To avoid this, a full backup is forced to run instead of an incremental
  • The warning 2501 means that one or data part sizes on backup storage are distinct by their size. Taking in attention that data parts are added sequentially, this may lead to an invalid restore from the current restore point. To avoid this, a full backup is forced to run instead of an incremental
  • The warning 2502 means that data part dates are distinct. This discrepancy is not critical since it can occur in case of a storage class change due to lifecycle policy settings. In this case, no action is taken and the current generation is continued along with a scheduled incremental backup.

To read more about consistency checks, refer to the Consistency Checks (coming soon) chapter at help.msp360.com