Symantec NetBackup Robotic status code 242 to status code 245
Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Robotic daemons or processes issue these status codes. They are also issued by programs that call the robotic operations, such as the vmchange command and
the media and device management user interfaces.
Below are some of the NetBackup Robotic status code 242 to status code 245 which may be received while using the Symantec NetBackup tool.
Robotic status code 242
Message: Robot media access port does not exist
Explanation: the requested media access port was not valid for use with the
Recommended Action: Use the robot test utility or a vendor administrative
interface to verify the media access port address based on the location of the
media. Choose a media access port that is valid, or let one be automatically selected,
and retry the robotic operation.
Robotic status code 243
Message: Cannot open/create the media access port status file
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 and Linux) 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. 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 error happens when an administrator or operator
cancels an eject request. The request may have been canceled for a number of
reasons: missing or faulty media, to allow the media access port to be used for
other requests, or 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: Arobotic mount operation could not be completed because physical
drive resources are not available for the request. This error may result from an
environment that is based on virtualized resources, such as one involving the
Storagenet 6000 Storage Domain Manager (SN6000).
The SN6000 virtualizes tape drives. Some SN6000 configurations may have more
logical drives than the number of physical drives (or equivalent resources) available
for drive requests. 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 required logical drives exceeds the physical drives
available, a NetBackup job may be started with insufficient drive resources. Instead
of queueing the job in the scheduler, the job runs and encounters the resource
issue when it makes an ACS tape mount request.
¦ Install the Shared Storage Option (SSO) license for mount requests to requeue
when physical drive resources are not available.
¦ The number of drives that can be in use at any one time is limited. Configure
backup windows so the different storage units that are tied to the same physical
drives are active only at non-overlapping times. Increase the media mount
timeout to avoid job failures when the job cannot get a physical drive due to
the drives all being busy.
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about NetBackup Robotic status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.