Hybrid/Non-Hybrid Errors (codes 1524, 1525, 1526, 1527, 2600, 2601)

Situations

A backup plan terminates with one or more errors with the following codes: 1524, 1525, 1526, 1527, 2600, 2601

For complete error descriptions see the error list at the bottom of this article

Causes

The occurrence of these errors means that there is some data interference on backup storage due to non-hybrid (local or cloud) and hybrid backup simultaneous usage.

Avoid using non-hybrid (local or cloud) and hybrid backup plans with the same or similar backup dataset!

Solutions

First, make a decision which backup type you are going to use in the future: hybrid or non-hybrid (local or cloud). Then, follow the instructions below. They are divided into different backup types.

To Continue Using Non-Hybrid Backup Plans

  • Delete or suspend hybrid backup plans with the same or similar set of volumes
  • Disable synthetic full backup for the backup plan that produced one of the errors listed above, force full backup, then enable synthetic full again. To do this, proceed as follows:
  1. Edit the backup plan that produced one of the errors listed above.
  2. Proceed to the Advanced Options step of the backup wizard.
  3. Unselect the Use synthetic full backup check box.

  1. Finish the backup wizard to save the configuration.
  2. Run full backup for this backup plan.
  3. Edit the backup plan again.
  4. Proceed to the Advanced Options step of the backup wizard.
  5. Select the Use synthetic full backup check box.
  6. Finish the backup wizard to save the configuration.
  7. Run the backup plan again.

To Continue Using Hybrid Backup Plans

  • Delete or suspend the non-hybrid backup plans with the same or overlapping set of chosen volumes.
  • Clean-up the cloud storage from the mixed-up hybrid and non-hybrid data, then continue using the hybrid backup plan. To do this, proceed as follows:
  1. Log into your storage provider management console or access the storage directly by other means, such as the MSP360 Explorer application.
  2. Navigate to the bucket (storage container) containing the problematic backup data.
  3. Find the backup prefix folder corresponding to the name of the machine that created the problematic backup data (name pattern: CBB_MACHINENAME).

OR, if you are MSP:

Find the MBS user ID folder (name pattern: MBS-XXXXX-XXXX-XXXX-XXXX-XXXXX) corresponding to the ID of the user with problematic backup, then locate the backup prefix folder inside it (name pattern: CBB_MACHINENAME).

  1. Find the directory corresponding to the backup plan type (see the list of plan types and directory names below) and delete it. Below is an example from the MSP360 Explorer application:
  • Image-based plan -> CBB_DiskImage
  • VMware plan -> CBB_VM
  • Hyper-V plan -> CBB_HV
  • MS SQL plan -> CBB_Database
  • MS Exchange plan -> CBB_Exchange

  1. Synchronize the repository database on the machine, so that the Backup software properly recognizes the actions made directly on the storage.

To synchronize the repository:

  1. Open the Backup application on the machine.
  2. In the Tools menu, select Options.
  3. Switch to Repository tab, then click Synchronize Repository.

OR, if you are an MSP:

  1. Access the machine's options through the Computers page:

  1. Locate and use the "Synchronize Repository" option:

  1. Run the full hybrid backup again.

Error List

The following errors may occur:

  • Non-hybrid and hybrid backups conflict. Non-hybrid and hybrid backup plans with similar backup datasets cannot be used. To continue using a non-hybrid plan, delete hybrid backup plans with a similar dataset, disable synthetic full backup (if applicable), then force a full backup. For more information, contact our technical support team (codes 1524, 1525, 1526, 1527)
  • Hybrid and non-hybrid backups conflict. Hybrid and non-hybrid backup plans with similar backup datasets cannot be used. To continue using a hybrid plan, contact our technical support team (codes 2600, 2601)
https://git.cloudberrylab.com/egor.m/doc-help-kb.git