NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
Chapter 5, Media Manager Status Codes and Messages 287
Status Codes
Explanation: There was a failed request to synchronize the global device database with
the local drive (ltidevs) or robot (robotic_def) databases. This could be caused by
the Media Manager volume daemon / NetBackup Volume Manager Service not running
on the global device database host. This could also be caused by conflicting information
between the global device database and the local databases mentioned above.
Recommended Action:
1. Examine command output (if available), debug logs, and system logs for a more
detailed message on the error.
a. If not already enabled, enable debug logging by creating the necessary
directories/folders (including the tpcommand log). Increase the level of verbosity
by adding the VERBOSE option in the vm.conf file and restarting the
daemons/services, or execute the command’s verbose option, if available.
b. Retry the operation and examine the logs.
2. Verify that vmd is running on the global device database host.
3. Examine the device configurations of other hosts sharing the same global device
database, looking for conflicts such as duplicate robot numbers with conflicting robot
types.
Device Configuration Status Code: 6
Message: Robot type is not supported on this platform
Explanation: A request was made to add a robot, but the robot type is not supported on
the device host.
Recommended Action: Check www.veritas.com and product release documentation
for supported device configurations.
Device Configuration Status Code: 7
Message: Invalid SCSI port number for the robot
Explanation: A request was made to add or change the SCSI port number for a robot, but
the SCSI port number provided was not valid.
Recommended Action:
NetBackup 4.5 Troubleshooting Guide for Windows