NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
Chapter 5, Media Manager Status Codes and Messages 225
Status Codes
1. Examine command output (if available), debug logs, and system logs for a more
detailed message on the error, as follows.
a. If not already enabled, enable debug logging by creating the necessary
directories/folders. Increase the level of verbosity by adding the VERBOSE
option in the vm.conf file and restarting the daemons/services, or by executing
the command’s verbose option, if available.
b. Retry the operation and examine the logs.
2. Check the usage statement for expected usage and compare with the parameters
being sent to start the new process.
3. Ensure that change volume requests from a newer release version level are not sent to
vmd on an older, incompatible version level.
Media Manager Status Code: 51
Message: cannot auto-eject this robot type
Explanation: A request to change volume residence with media eject was sent to vmd (the
Media Manager volume daemon on UNIX or NetBackup Volume Manager service on
Windows), but the volume’s robot type does not support automated media eject.
Recommended Action:
1. Examine command output (if available), debug logs, and system logs for a more
detailed message on the error, as follows.
a. If not already enabled, enable debug logging by creating the necessary
directories/folders. Increase the level of verbosity by adding the VERBOSE
option in the vm.conf file and restarting the daemons/services, or by executing
the command’s verbose option, if available.
b. Retry the operation and examine the logs.
2. Ensure that change volume residence requests (with eject for the robot type involved
with a newer release version level) are not sent to vmd on a system running an older,
incompatible software version level.
Media Manager Status Code: 52
Message: cannot auto-inject this robot type
NetBackup 4.5 Troubleshooting Guide for Windows