Veritas NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 170
Explanation: Usually indicates a problem with the 3pc.conf
file or the mover.conf
file. (For detailed causes, see recommended actions.)
For more information on these files, see the NetBackup Snapshot Client Configuration document available at the following location:
https://www.veritas.com/content/support/en_US/article.TECH51377.html
For help accessing this document, see Snapshot Client Assistance in the NetBackup Snapshot Client Administrator's Guide.
Recommended Action: Do the following, as appropriate:
If a non third-party copy device is listed in
3pc.conf
file, correct it or remove the non third-party copy device entry.If an incorrect LUN is specified in the
3pc.conf
file or the device does not exist, correct the3pc.conf
file as appropriate.If an appropriate
mover.conf
file (with or without file name extension) cannot be found, the/usr/openv/netbackup/logs/bptm
log may show the following:09:51:04 [22281] <2> setup_mover_tpc: no mover.conf.vertex_std_tpc or mover.conf file exists, cannot perform TPC backup 09:51:04 [22281] <16> bptm: unable to find or communicate with Third-Party-Copy mover for policy vertex_std_tpc
Make sure that an appropriate
mover.conf
file exists in/usr/openv/netbackup
on the media server. This file can be any of the following:mover.conf.policy_name
file, where policy_name exactly matches the name of the policy.mover.conf.storage_unit_name
, where storage_unit_name exactly matches the name of the storage in the Backup Policy Management Policy attributes dialog box (such as nut-4mm-robot-tl4-0).mover.conf
file (no extension) for the configurations that have only one third-party copy device.
Note that NetBackup looks for an appropriate
mover.conf
file in the order.If the SCSI pass-through path of the third-party copy device, as entered in the
mover.conf
file, does not exist, the bptm log may show the following:09:50:12 [22159] <16> setup_mover_tpc: open of passthru path /dev/sg/cXtXlX failed, No such file or directory 09:50:12 [22159] <16> bptm: unable to find or communicate with Third-Party-Copy mover for policy vertex_std_tpc
Correct the SCSI pass-through path of the third-party copy device that is entered in the
mover.conf
file.If the third-party copy device returned an error, you may see either of the following messages in
/usr/openv/netbackup/logs/bptm
log:cannot process extended copy error due to truncated sense data, may be HBA problem disk error occurred on extended copy command, key = 0x0, asc = 0x0, ascq = 0x0
(where key, asc, and ascq are all zero)
Your host-bus adapter (HBA) and its driver may need to be updated, or NetBackup Snapshot Client may not support them. The supported host-bus adapters are listed.
See the NetBackup Release Notes.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.