Consistency Check Warnings (codes 2503, 2504, 2505)

Situation

A backup plan terminates with one of the following warnings:

  • Consistency Check detected an issue. An excess restore point was found and marked as forbidden

  • Consistency Check detected an issue. Latest restore point is marked as 'forbidden' and will not be used. A full backup was forced

  • Consistency Check detected an issue. Generation number collision due to simultaneous backups from cloned instances

Cause

All these warnings (codes 2503, 2504, and 2505) have a common cause. In some cases, two or more backup plans with the cloned instances in their backup source can run simultaneously and back up different copies of the same content. This leads to a situation when backup plan settings, deduplication database, and current generation on backup storage are identical.

This may invoke restore point conflicts because of similar restore points are created for different machines. Thus, one of the restore points is marked as 'forbidden', and a full backup is forced to start a new generation on backup storage. Once a 'forbidden' restore point is detected, this will also force a full backup for the other cloned machine.

Since it is not possible to determine unambiguously which instance created the generation on backup storage, generations must be separated.

To learn more about the generations, restore points, and new backup format in general, refer to the New Backup format section of the help documenation

Solution

The easiest solution for these warnings is a backup plan cloning.

To Clone a Backup Plan

  1. Switch to the Backup Plans tab.
  2. Find the plan that produced this warning on consistency check.
  3. In the bottom menu, click Clone Plan.

  1. In the Clone Plan dialog box, specify a new name for the cloned backup plan for easier distinction.

  1. Run both backup plans.

Clone Backup Plan Using CLI

using CLI applies for Hyper-V backups only

To clone a backup plan using CLI, run the following command:

cbb addHyperVPlan -cloneplan {newname}

where {newname} is the name for the cloned backup plan.