Scenarios when NetBackup overrides object change tracking
In some cases, NetBackup may detect that object change tracking is insufficient to generate a list of changed objects due to system errors or manual disruptions. When this occurs, NetBackup switches to object scanning to identify changes since the last backup.
NetBackup stores a reference context for each backup in the log bucket to track the last backup. If this context is missing - due to deletion, pruning errors, or system issues - NetBackup cannot reliably identify changed objects. In such cases, NetBckup performs a full object scan.
If you modify the object change tracking configuration, NetBackup verifies the updated settings. If the configuration is incompatible, the next backup fails. If the modified configuration is compatible, NetBackup performs a full bucket scan during the next backup to detect object changes. The subsequent backups use object change tracking.
If you disable the option, and then re-enable it in the policy, NetBackup performs the next backup by ignoring object change tracking, and directly scanning the entire bucket to identify the changed objects. The subsequent backups are taken using object change tracking.