Using accelerators with CDP
CDP for VMware exclusively supports accelerator-based backup. So, CDP needs accelerator-compliant storage units based on MSDP or OST-based storage.
Force rescan enhances safety, and establishes a baseline for the next accelerator backup. This feature protects against any potential damage like failure of checksum verification on the data in the staging area.
When you use accelerator-based forced rescan, it clears the data on the CDP gateway staging area. So, any corrupted data is replaced with fresh data synced from the ESXi server. Note that the first backup job triggered by forced rescan may not have all data needed for a recoverable image. As data becomes available, the subsequent backups are triggered automatically, making the images recoverable.
Recommendations for using forced rescan:
Do not trigger force rescan for the VMs which are turned off.
If the staging location memory is full, you can see a notification in the UI. Initiate the force rescan only when sufficient memory is available at the staging location.
To manually trigger the backup with force rescan run the following command in the command prompt or the Linux terminal:
bpbackup -i -p policyname -s <schedulename>
NetBackup creates a schedule named ForcedRescan for every protected VM.