|
|
Explanation: Usually indicates a problem with the 3pc. file or the mover.conf file. (For detailed causes, see recommended actions.)
For more information on these files, refer to the NetBackup Snapshot Client Configuration online document.
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. file, correct it or remove the non third-party copy device entry.
If an incorrect lun is specified in the 3pc. file or the device does not exist, correct the 3pc. 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.