Veritas NetBackup™ Administrator's Guide, Volume I
- Section I. About NetBackup
- Section II. Configuring hosts
- Configuring Host Properties
- About the NetBackup Host Properties
- Access Control properties
- Bandwidth properties
- Busy File Settings properties
- Client Attributes properties
- Client Settings properties for UNIX clients
- Client Settings properties for Windows clients
- Data Classification properties
- Default Job Priorities properties
- Encryption properties
- Exchange properties
- Exclude Lists properties
- Fibre Transport properties
- Firewall properties
- General Server properties
- Global Attributes properties
- Logging properties
- Login Banner Configuration properties
- Media properties
- Network Settings properties
- Port Ranges properties
- Preferred Network properties
- Resilient Network properties
- Restore Failover properties
- Retention Periods properties
- Scalable Storage properties
- Servers properties
- SharePoint properties
- SLP Parameters properties
- Throttle Bandwidth properties
- Universal Settings properties
- User Account Settings properties
- Configuration options for NetBackup servers
- PREFERRED_NETWORK option for NetBackup servers
- THROTTLE_BANDWIDTH option for NetBackup servers
- Configuration options for NetBackup clients
- IGNORE_XATTR option for NetBackup clients
- VXSS_NETWORK option for NetBackup clients
- Configuring server groups
- Configuring host credentials
- Managing media servers
- Configuring Host Properties
- Section III. Configuring storage
- Configuring disk storage
- Configuring robots and tape drives
- About configuring robots and tape drives in NetBackup
- Adding a robot to NetBackup manually
- Managing robots
- Adding a tape drive to NetBackup manually
- Adding a tape drive path
- Correlating tape drives and device files on UNIX hosts
- Managing tape drives
- Performing device diagnostics
- Configuring tape media
- About NetBackup volume pools
- About WORM media
- About adding volumes
- Configuring media settings
- Media settings options
- Media type (new media setting)
- Media settings options
- About barcodes
- Configuring barcode rules
- Configuring media ID generation rules
- Adding volumes by using the Actions menu
- Configuring media type mappings
- Managing volumes
- About exchanging a volume
- About frozen media
- About injecting and ejecting volumes
- About rescanning and updating barcodes
- About labeling NetBackup volumes
- About moving volumes
- About recycling a volume
- Managing volume pools
- Managing volume groups
- Inventorying robots
- About showing a robot's contents
- About updating the NetBackup volume configuration
- About the vmphyinv physical inventory utility
- Configuring storage units
- About the Storage utility
- Creating a storage unit
- About storage unit settings
- Absolute pathname to directory or absolute pathname to volume setting for storage units
- Maximum concurrent jobs storage unit setting
- Staging backups
- Creating a basic disk staging storage unit
- Configuring storage unit groups
- Section IV. Configuring storage lifecycle policies (SLPs)
- Configuring storage lifecycle policies
- Storage operations
- Index From Snapshot operation in an SLP
- Snapshot operation in an SLP
- Retention types for SLP operations
- Capacity managed retention type for SLP operations
- Storage lifecycle policy options
- Using a storage lifecycle policy to create multiple copies
- Storage lifecycle policy versions
- Section V. Configuring backups
- Creating backup policies
- Planning for policies
- Policy Attributes tab
- Policy storage (policy attribute)
- Policy volume pool (policy attribute)
- Take checkpoints every __ minutes (policy attribute)
- Backup Network Drives (policy attribute)
- Cross mount points (policy attribute)
- Encryption (policy attribute)
- Collect true image restore information (policy attribute) with and without move detection
- Use Accelerator (policy attribute)
- Enable optimized backup of Windows deduplicated volumes
- Use Replication Director (policy attributes)
- Schedule Attributes tab
- Type of backup (schedule attribute)
- Frequency (schedule attribute)
- Multiple copies (schedule attribute)
- Retention (schedule attribute)
- Media multiplexing (schedule attribute)
- Start Window tab
- Include Dates tab
- How open schedules affect calendar-based and frequency-based schedules
- About the Clients tab
- Backup Selections tab
- Adding backup selections to a policy
- Verifying the Backup Selections list
- Pathname rules for UNIX client backups
- About the directives on the Backup Selections list
- ALL_LOCAL_DRIVES directive
- Files that are excluded from backups by default
- Disaster Recovery tab
- Active Directory granular backups and recovery
- Synthetic backups
- Using the multiple copy synthetic backups method
- Protecting the NetBackup catalog
- Parts of the NetBackup catalog
- Protecting the NetBackup catalog
- Archiving the catalog and restoring from the catalog archive
- Estimating catalog space requirements
- About the NetBackup relational database
- About the NetBackup relational database (NBDB) installation
- Using the NetBackup Database Administration utility on Windows
- Using the NetBackup Database Administration utility on UNIX
- Post-installation tasks
- About backup and recovery procedures
- Managing backup images
- Creating backup policies
- Section VI. Deployment Management
- Deployment Management
- Adding or changing schedules in a deployment policy
- Deployment Management
- Section VII. Configuring replication
- About NetBackup replication
- About NetBackup Auto Image Replication
- Viewing the replication topology for Auto Image Replication
- About the storage lifecycle policies required for Auto Image Replication
- Removing or replacing replication relationships in an Auto Image Replication configuration
- About NetBackup replication
- Section VIII. Monitoring and reporting
- Monitoring NetBackup activity
- About the Jobs tab
- About the Daemons tab
- About the Processes tab
- About the Drives tab
- About the jobs database
- About pending requests and actions
- Reporting in NetBackup
- Using the Logging Assistant
- Monitoring NetBackup activity
- Section IX. Administering NetBackup
- Management topics
- Accessing a remote server
- Using the NetBackup Remote Administration Console
- Run-time configuration options for the NetBackup Administration Console
- About improving NetBackup performance
- About adjusting time zones in the NetBackup Administration console
- Alternate server restores
- About performing alternate server restores
- Managing client backups and restores
- About client-redirected restores
- Powering down and rebooting NetBackup servers
- About Granular Recovery Technology
- About configuring Services for Network File System (NFS) on Windows 2012, 2012 R2, or 2016
- About configuring Services for Network File System (NFS) on Windows 2008 and 2008 R2
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 Attributes tab. option is supported for incremental backups (cumulative or differential) or full backups. For full backups, must be enabled on the policy |
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 Use Change Journal is first enabled, the NetBackup client may need time to process the NTFS change journal and set up its databases. option was recently enabled. AfterThe option may be ready at the next backup. |
not using change journal data for <%%s>: unable to locate journal data | The Use Change Journal is first enabled, the NetBackup client may need time to process the NTFS change journal and set up its databases. option was recently enabled. AfterThe 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 Use Accelerator is enabled. option requires that |
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. |