Accelerator messages in the NDMP backup job details log
This topic provides explanations of some specific messages that appear in an NDMP job details log when Accelerator for NDMP is enabled.
The messages in the NetBackup job details include messages that are generated directly from the filer. To find the messages from the filer, look for the NDMP host name in the message following the PID number as in the following example:
mm/dd/yyy hh:mm:ss - Info ndmpagent (pid=10780) [NDMP_host_name]: Filetransfer: Transferred 146841088 bytes in 2.855 seconds throughput of 50231.929 KB/s
Note:
Some messages that are generated directly from the filer, such as filer volume is full, may require your immediate attention. Consult the documentation for the filer to determine how to resolve any issues with the filer that are indicated by a message from the filer in the job details.
Messages similar to the following appear in the job details log for the first full NDMP backup that uses Accelerator for NDMP.
mm/dd/yyyy 1:28:47 PM - Info bpbrm(pid=3824) accelerator enabled ... ... mm/dd/yyyy 1:28:53 PM - Info ndmpagent(pid=10556) accelerator optimization is <off>, unable to locate accelerator tracklog ... ... mm/dd/yyyy 1:29:05 PM - Info ndmpagent(pid=10556) accelerator sent 1310720 bytes out of 1310720 bytes to server, optimization 0.0%
Note the following items about messages for the first Accelerator-enabled full backup:
accelerator enabled
This message indicates that the Accelerator option is being used.
accelerator optimization is <off>, unable to locate accelerator tracklog
Because this is the first full backup, NetBackup creates a new track log. More information about the locations of the track log is available:
accelerator sent 1310720 bytes out of 1310720 bytes to server, optimization 0.0%
Because this is the first full backup, all data is backed up and no optimization occurs yet.
Messages similar to the following appear in the job details log for subsequent incremental NDMP backups that use Accelerator for NDMP.
mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) accelerator optimization is <on> mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) BASE_DATE will be used to determine changed files for accelerator mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) please ignore references to LEVEL in future messages ... ... mm/dd/yyyy 2:14:14 PM - Info ndmpagent(pid=10044) accelerator sent 1104896 bytes out of 100310720 bytes to server, optimization 15.7%
Note the following items about messages for the subsequent incremental accelerator backups:
accelerator optimization is <on>
This message indicates that a track log exists and the backup shall perform with the Accelerator option.
BASE_DATE will be used to determine changed files for accelerator and please ignore references to LEVEL in future messages
These messages are a reminder that Accelerator for NDMP uses BASE_DATE and DUMP_DATE rather than dump levels to identify changed data. Messages that refer to dump levels come from the filer. However, the message to ignore references to LEVEL also appears in the job detail logs as a reminder that dump levels are not used with Accelerator for NDMP.
accelerator sent 1104896 bytes out of 100310720 bytes to server, optimization 15.7%
This message provides the amount of data that was sent to the server and the percentage of optimization that was realized.
Messages similar to the following appear in the job details log for subsequent full NDMP backups that use Accelerator for NDMP.
mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) accelerator optimization is <on> mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) BASE_DATE will be used to determine changed files for accelerator mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) please ignore references to LEVEL in future messages ... ... mm/dd/yyyy 1:40:27 PM - Info ndmpagent(pid=12244) accelerator sent 887296 bytes out of 1159725056 bytes to server, optimization 99.9%
Note the following items about messages for the subsequent incremental accelerator backups:
accelerator optimization is <on>
This message indicates that a track log exists and the backup shall perform with the Accelerator option.
BASE_DATE will be used to determine changed files for accelerator and please ignore references to LEVEL in future messages
These messages are a reminder that Accelerator for NDMP uses BASE_DATE and DUMP_DATE rather than dump levels to identify changed data. Messages that refer to dump levels come from the filer. However, the message to ignore references to LEVEL also appears in the job detail logs as a reminder that dump levels are not used with Accelerator for NDMP.
accelerator sent 887296 bytes out of 1159725056 bytes to server, optimization 99.9%
This message provides the amount of data sent to the server and the percentage of optimization that was realized.
Messages similar to the following appear in the job details log for full NDMP backups that use Accelerator for NDMP with the Accelerator forced rescan option.
mm/dd/yyyy 2:13:43 PM - Info bpbrm(pid=8628) Accelerator enabled backup with "Accelerator forced rescan", all data will be scanned and processed.Backup time will be longer than a normal Accelerator enabled backup. ... ... mm/dd/yyyy 2:13:46 PM - Info ndmpagent(pid=10044) accelerator optimization is <on> but 'forced rescan' is enabled
Note the following items about messages for accelerator forced rescan backups:
Accelerator enabled backup with "Accelerator forced rescan", all data will be scanned and processed. Backup time will be longer than a normal Accelerator enabled backup and accelerator optimization is <on> but 'forced rescan' is enabled
These messages indicate that a forced rescan is enabled and that the job shall run longer than a normal Accelerator full backup. Though accelerator optimization is on, the job may run slightly longer than accelerated full backups.
More information about Accelerator for NDMP is available: