Symantec NetBackup Device management status code 32 to status code 35

SQLServerF1

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. These status codes appear in exit status and command output for the ltid,
tpclean, tpreq, and tpunmount commands, and in system or debug logs. Programs
that call those commands, such as media and device management user interfaces
and the vmoprcmd command also presented these codes.

Below are some of the NetBackup Device management status code 32 to status code 35 which may be received while using the Symantec NetBackup tool.

Device management status code 32
Message: Error in getting semaphore
Explanation: ltid made an attempt to obtain a semaphore that was used for
arbitrating access to shared memory. (ltid is the Media Manager device daemon
on UNIX and Linux or the NetBackup Device Manager service on Windows) The
request failed due to a system error. The error probably indicates a lack of system
resources for semaphores, or mismatched software components.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ On UNIX and Linux servers, gather the output of the ipcs -a command to see
what resources are currently in use. Check the installed software components
and verify that they are all at a compatible release version.

Device management status code 33
Message: Error in SEMAPHORE operation
Explanation: A process was unable to perform a semaphore operation (such as
lock or unlock) associated with resources maintained by ltid. (ltid is the Media
Manager device daemon on UNIX and Linux or the NetBackup Device Manager
service on Windows.)
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ On UNIX and Linux servers, gather the output of the ipcs -a command to see
what resources are currently in use.

Device management status code 35
Message: Request terminated because media is unavailable (in DOWN drive,
misplaced, write protected or unmountable)
Explanation: A mount request was canceled because the media being requested
is not available. It may be in a DOWN drive or misplaced, write protected, or
unmountable. Another possible cause of this message is that you are using a
cleaning tape with no cleanings remaining.
Recommended Action: Use robotic inventory or manual means to compare the
contents of media in the robotic library with the volume configuration. Then
update the configuration as needed. Determine the physical location of the media.
Check integrity of the drive, drive path, and media if the media is found in a
logicallyDOWNdrive. Verify that the media is not a misconfigured cleaning tape.
Move the media into the robotic library and update the volume configuration if
the media was not present in the library. Set the cartridge tab to allow write access,
or request the media with read-only access if the write protection was the cause
of the error.
If the problem is a cleaning tape with no cleanings remaining, replace the cleaning
tape.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device management status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *