NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
Explanation: A robotic daemon/process could not create or open a status file in the
database directory/folder.
Recommended Action: Investigate why the robot status file in the directory
/usr/openv/volmgr/database (UNIX) or folder install_path\Volmgr\database
(Windows) cannot be created or opened. On Windows, check which account the
NetBackup Device Manager service (and thus the robotic process) is running under and
compare it against the security properties of the database folder.
Robotic Status Code: 244
Message: The eject command was aborted by the user
Explanation: An administrator or operator canceled an eject media request.
Recommended Action: This happens when an eject request has been canceled by an
administrator or operator. The request may have been canceled for a number of reasons,
such as missing or faulty media, the need to allow the media access port to be used for
other requests, or the desire to perform the operation at a later time. Check with the
administrator or operator for more information.
Robotic Status Code: 245
Message: Physical drive is not available
Explanation: A robotic mount operation could not be completed because physical drive
resources are not available for the request. This is probably the result of operating in an
environment based on virtualized resources, such as one involving the Storagenet 6000
Storage Domain Manager (SN6000).
The SN6000 virtualizes tape drives. Some configurations of the SN6000 may involve a
different number of logical drives as compared to the number of physical drives (or
equivalent resources) available for satisfying the requests for drive resources. Also, the
relationship between the number of logical drives and physical drives may change as
hardware failures occur. NetBackup scheduling, drive allocation, and drive assignment
algorithms can only determine logical drive availability; NetBackup attempts to fully
utilize all configured and available logical drives. If the number of logical drives being
utilized exceeds the number of physical drives available, a NetBackup job may be started
when insufficient drive resources are available for the job. Instead of queueing the job in
the scheduler, the job runs and does not encounter the resource issue until the time it
makes an ACS tape mount request.
Recommended Action:
356 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows