Managing Backup Success with CBT Failure: Full VM Data Resend in Vembu-VMBackup

Title: Backup Success with CBT Failure: Handling Full Resend of VM Data in BDRShield

KB ID: 105070
Summary:
This knowledge base article addresses the scenario where a backup operation is reported as completed successfully, but Change Block Tracking (CBT) fails for a specific VM in BDRShield. This situation arises due to multiple configurations of the same source VM for backup or replication jobs, leading to CBT tracking failure.
Cause:
The mentioned remarks, "Backup Completed Successfully but CBT failed for this VM," occur when a VMWare backup or replication job finishes with this outcome. This arises from configuring the same source VM multiple times for backup or replication tasks, resulting in CBT tracking failure.
Solution:
To address this issue, follow these steps:
1. Handling CBT Failure:
  1. When a VM encounters CBT failure, the subsequent incremental backup or replication will automatically be treated as a full backup/replication for that specific VM.
  2. The CBT Driver will initiate tracking changes from a particular timestamp, ensuring accurate synchronization.
Note: This solution is provided to address the situation where backup operations show success but encounter CBT failure for a specific VM in BDRShield. By allowing subsequent incremental as full backups and resetting CBT tracking, the issue can be resolved to ensure proper data synchronization.