Forced rescan schedules
For virtualization technologies, such as VMware and Hyper-V, forced rescan schedules work differently than for files and folder backup. With files and folders, NetBackup maintains a track log to manage the change detection. However, with virtualization workloads, it is usually the virtualization vendor technology that provides the change detection.
Forced rescan mode in files and folder verifies information on the client file system with the information stored in the track log. For VMware backups, there is no track log, so there is no verification as such. Instead, forced rescan with virtualization workloads requests all blocks, regardless of any detected changes. This method ensures that all blocks are protected by that backup, which results in a full backup. The duration of the forced rescan backup takes longer and is similar to a non-Accelerator full backup.
For stable customer environments with proven technology stack, forced rescan schedules are not required for virtualization workloads. They can be used for troubleshooting and problem-solving purposes. For additional information on forced rescan for VMware, refer to the NetBackup fo VMware Adminstrator's Guide