Resolving Backup Failure Caused by Altered Source Disk Order

Backup Failure Due to Altered Source Disk Order

KB ID: 103005
Details:
BDRSuite utilizes its proprietary image backup driver to track block-level changes in the disk designated for backup. When taking incremental backups, a "Backup failed as the source disk order is altered" error may occur if the BDRSuite proprietary driver cannot track block-level changes due to changes in the order of disks configured for the backup.
Causes:
There are two possible reasons for this error:
  1. The order of disks in the target machine configured for backup is changed during an incremental backup.
  2. The external storage device(s) attached to the target machine during the backup configuration is disconnected or removed.
Solutions:
In both cases, it is necessary to restore the disk order to its original state. Follow the appropriate steps below to find the original disk order:
If the backup job is configured from the Vembu BDR Backup Server:
Step 1: Open the target machine and navigate to the Vembu Integration Service installation location. By default, it is installed on the OS drive (C-drive on most machines).
Step 2: Open the proxy.log file located at <installation location>\Program Files\Vembu\VembuIntegrationService\log\<backup server ID>\<backup job name>\proxy.log.
Step 3: Search for the lines "Configured Disk No :: X, Current Disk No :: Y."
            X: Disk number received during the initial full backup schedule.
            Y: Disk number received for the recent incremental schedule.
Step 4: Change the disk order of the target machine to its original state and rerun the backup job.
If the backup job is configured using BDRSuite Client:
Step 1: Open the target machine and navigate to the BDRSuite Client installation location. By default, it is installed on the OS drive (C-drive on most machines).
Step 2: Open the backup.log file located at <installation location>\Program Files\Vembu\VembuImageBackup\log\<backup job name>\backup.log.
Step 3: Search for the lines "Configured Disk No :: X, Current Disk No :: Y."
            X: Disk number received during the initial full backup schedule.
            Y: Disk number received for the recent incremental schedule.
Step 4: Change the disk order of the target machine to its original state and rerun the backup job.



    • Related Articles

    • Source Might Be Altered

      KB ID: 64 Cause: The Image backup job may fail with the error message "Source might be altered. Please check if the source disk order is correct." This error occurs when the GUID of a volume has been changed after configuring the disk image backup. ...

    • Source Disk Order / Volume GUID Change Causing Incremental Backup Failure in BDRSuite Disk image Image backups

      KB ID: 103002 Cause: Incremental backup schedules may fail for Disk image backups in BDRSuite when the source disk order or Volume GUID has been altered between incremental backups. This can occur under the following scenarios: Dual booting multiple ...

    • Configuring Windows Disk Image Backup

      You can follow the below steps to configure the Windows Disk-Image Backup; Step 1: Adding Basic Job Details Get started by creating a backup job by choosing Job Create Option, choose to Create Job without using a template if you want to create a ...

    • VMware Backup Failure: Unable to Retrieve queryChangedDiskAreas

      KB ID: 105017 Issue: During VMware backups, encountering the error message "Unable to retrieve queryChangedDiskAreas even after CBT query retry" indicates a failure to track Changed Blocks of a virtual machine (VM) within BDRSuite. Cause: The error ...

    • Troubleshooting: Backup Failure Due to Invalid VM State During Backup

      KB ID: 104075 Issue: Backup attempts fail with an error indicating that the virtual machine's state was not valid during the backup process. Cause: This issue arises due to the following reasons: 1. Offline Cluster Disk: The Cluster Disk containing ...