Log messages about the Use Change Journal option and Accelerator
The Accelerator uses the NTFS or ReFS change journal to help identify data changes on the Windows client. The following table describes the change journal messages that may appear in the NetBackup job details log in the Activity Monitor. The left column lists the messages.
For Accelerator backups, these messages indicate various impediments to the use of the Windows change journal. In general, they indicate either of the following:
That the Accelerator cannot use the change journal for the backup. To use the change journal, you may need to reconfigure the policy.
That the Accelerator cannot exclusively use the change journal to detect changes in the file system. NetBackup examines the file system metadata for each file, to detect which files have changed. It also uses the change journal to help detect which files have changed.
Note:
In the following messages, the variable <%%s> represents the items in your backup selections list.
The change journal messages often appear in pairs. The first message indicates why the change journal cannot be used. For example:
not using change journal data for <%%s>: forced rescan requested
The second message indicates that the Accelerator nevertheless can use the change journal to detect changed files:
not using change journal data for enumeration for <%%s> but will use it for change detection
Table: Accelerator messages on the Windows option (job details log)
Message in NetBackup job details | Description |
|---|---|
not using change journal data for enumeration for <%%s> but will use it for change detection | NetBackup uses the change journal to help detect which files have changed. NetBackup also examines the file system metadata for each file to help detect which files have changed. Note: Before this message appears, another message explains why NetBackup does not rely entirely on the change journal data to detect changed files. |
not using change journal data for <%%s>: forced rescan requested | The option is enabled on the full backup schedule for the policy. As a result, NetBackup cannot rely entirely on the change journal data to detect changed files. NetBackup also examines the file system metadata for each file to help detect which files have changed. |
not using change journal data for <%%s>: filter checksum calculation failed | The backup uses a number of filters to determine which files and directories to include in the backup. The filters are the following: NetBackup exclude and include lists, the files and directories that are included in the Shadow Copy Components and in the system state backup, and others. During a backup, a checksum is calculated against the filters. When a new backup runs, the checksum for the current backup is compared against the checksum of the previous backup. If the checksums do not match, the change journal data cannot be used. Instead, Accelerator performs a regular file system scan to determine the files and folders to include in the backup. No action is required. If the filters do not change between backups, the change journal data is used at the next backup. |
not using change journal data for <%%s>: unable to validate change journal usage <reason=%%s> | Accelerator cannot use the option in the following cases:
In these cases, the option cannot be used. Accelerator performs a regular file system scan to determine the files and folders to include in the backup. No action is required. Accelerator uses the option at the next backup if all conditions are met. |
not using change journal data for <%%s>: unable to initialize change journal usage <reason=%%s> | Accelerator cannot use the option in the following cases:
Instead, Accelerator performs a regular file system scan to determine the files and folders to include in the backup. No action is required. When records have been purged, a new baseline is created when the current backup completes. If corruption existed, it is detected and the databases are re-created. Accelerator uses the option at the next backup. |
not using change journal data for <%%s>: hard link or reparse point change detected | Accelerator cannot use the option if a change corresponds to a hard link or to a reparse point. Note that the change may correspond to any number of files and directories and the NTFS change journal does not track all of them. No action is required. If no further changes occur to hard links or reparse points, the option can be used at the next backup. |
not using change journal data for <%%s>: not supported with true image backups | Collect true image restore information or Collect true image restore information with move detection is specified in the policy. To process the files and determine which files have changed, NetBackup performs a regular file system scan to determine the files and folders to include in the backup. It also queries the change journal to help determine which files have changed. |
not using change journal data for <%%s>: invalid schedule type | Accelerator does not support the selected schedule type with the option. The option is supported for incremental backups (cumulative or differential) or full backups. For full backups, must be enabled on the policy Attributes tab. |
not using change journal data for <%%s>: path must be local and not contain directory junctions and/or symbolic links | In the backup selections, a path contains a reparse point (directory junction or a symbolic link). The option cannot be used. NetBackup must perform a regular file system scan to back up the directories correctly. |
not using change journal data for <%%s>: change journal setup is not complete (may still be in progress) | The option was recently enabled. After Use Change Journal is first enabled, the NetBackup client may need time to process the NTFS change journal and set up its databases. The option may be ready at the next backup. |
not using change journal data for <%%s>: unable to locate journal data | The option was recently enabled. After Use Change Journal is first enabled, the NetBackup client may need time to process the NTFS change journal and set up its databases. The option may be ready at the next backup. |
not using change journal data for <%%s>: invalid change journal data | When many changes occur on a volume, the NetBackup Client Service may need to increase the size of the internal databases. As a result, the databases may become invalid. After the databases are increased in size and are synchronized with the NTFS change journal, they are marked as valid. The option is used with the next backup. |
not using change journal data for <%%s>: unable to apply snapshot | For a snapshot-based backup, NetBackup uses the change journal databases on the snapshot instead of on the live volume. An error occurred when NetBackup attempted to open the databases on the snapshot. When the next backup runs, NetBackup creates a new snapshot and the databases may be opened without error. |
not using change journal data for <%%s>: no previous track log | No previous full backup exists that used Accelerator. NetBackup supports the option with Accelerator on a full backup only if a previous full backup exists that used Accelerator. |
not using change journal data for <%%s>: not supported with regular full backups | The option is not enabled on the policy. For full backups, the option requires that Use Accelerator is enabled. |
not using change journal data for <%%s>: unable to validate change journal usage <reason=previous backup wasn't a successful backup> | If a backup is partially successful (status code 1), the next Accelerator backup cannot use the option. NetBackup can use the option after the next successful backup. |
not using change journal data for <%%s>: not supported | A backup selection in the policy is a resource for which the Windows change journal is not supported. Examples of unsupported resources are FAT volumes and FAT32 volumes. |
not using change journal data for <%%s>: not supported for remote frozen images | The backup has attempted to use a remote frozen image. The option is not supported with remote frozen images. |
not using change journal data for <%%s>: not enabled | The option is not enabled. |
not using change journal data for <%%s>: not configured for use | The option is not enabled. |
not using change journal data for <%%s>: unable to determine volume guid | An internal error occurred. The volumes to back up should be checked to ensure that a volume GUID is associated with each volume. |
not using change journal data for <%%s>: snapshot has not been applied (unable to track open files) | To use the change journal data, NetBackup must be able to take a snapshot of the backup volume to correctly identify and handle open files. This error occurs if a backup runs before NetBackup can take a snapshot of the volume. If a snapshot can be taken before the next backup occurs, NetBackup may be able to use change journal data at the next backup. |
not using change journal data for <%%s>: invalid policy type | The option is only supported for Standard or MS-Windows policies. |
not using change journal data for <%%s>: list of accelerator based backups does not match list of change journal based backups | On the client, NetBackup keeps track of both Accelerator backups and change journal-based backups. If the lists of these backups do not match, one of the following occurred:
If either case, the option cannot be used until the next full backup occurs. |
not using change journal data for <%%s>: previous backup had change journal data that was not complete (missing usn records) | The change journal databases are fixed in size: they can contain only a fixed number of records. If the volume undergoes a lot of activity, records may be purged from the change journal database before a backup can process them. In that case, the option cannot be used. No action is required. Accelerator uses the option at the next backup if all conditions are met. |
not using change journal data for <%%s>: not supported for non-local volumes / file systems | The backup selection in the policy is not for a local volume. For example, the backup selection specifies a UNC path. |
not using change journal data for <%%s>: no forced rescan schedule configured | This message appears only during Accelerator full backups. To use the change journal data during Accelerator full backups, a policy schedule with the option is required. |
not using change journal data for <%%s>: forcing rescan, each file will be read in order to validate checksums | This message appears only during full backups, when the policy is not configured with the option. Before this message appears, another message explains why the change journal data cannot be used. |