Symantec NetBackup Media Manager status code 56 to status code 60

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 56 to status code 60 which may be received while using the Symantec NetBackup tool.

Media Manager status code 56
Message: invalid database version header
Explanation: nbpushdata cannot find a recognizable EMM database version in
the EMM database, and cannot initialize with the database currently in place.
¦ 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.
¦ From catalog backups or another source if available, restore an earlier version
of the database file: /usr/openv/volmgr/database/volDB (UNIX and Linux)
or install_path\Volmgr\database\volDB (Windows). Then restart vmd.

Media Manager status code 57
Message: error auto-generating volume group
Explanation: A request was made to add or change volumes in the volume
configuration by using automatic generation of the volume group name.Aunique
volume group name cannot be generated because the available combinations were
used up.
Recommended Action: Consolidate volumes into volume groups within the
targeted robot number so that a new volume group can be generated automatically.
Or provide a specific volume group name.

Media Manager status code 58
Message: daemon cannot obtain socket
Explanation: vmd cannot bind to its socket. (vmd is the NetBackup Volume Manager
daemon on UNIX and Linux and the NetBackup Volume Manager service on
Windows.) When vmd attempts to bind to its configured port number, system call
fails. The call fails usually because another process having acquired the port
before the vmd daemon or service started.
¦ Examine the daemon debug log for a more detailed message on the system
error.
¦ If another process has the port, use other system commands to determine the
process. Based on the result, either change the port number in your services
file or map, or terminate the process that has acquired the port.
¦ UNIX and Linux only: Another possible cause for this error is the use of the
kill command to terminate vmd. To stop vmd, the recommended method is to
use the Terminate Media Manager Volume Daemon option on the Special
actions menu in vmadm. (Or use the equivalent command line request,
vmctrldbm -t). The use of the kill command to stop this process can leave
it unable to bind to its assigned port the next time it restarts. When the socket
problem occurs, the daemon debug log contains lines similar to the following:
unable to obtain bound socket, Address already in use (125)

Media Manager status code 59
Message: daemon failed accepting connection
Explanation: vmd cannot accept a new connection due to a system call failure.
(vmd is the NetBackup Volume Manager daemon on UNIX and Linux and the
NetBackup Volume Manager service on Windows.)
¦ Examine the daemon debug log for a more detailed message on the system
error. 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.
¦ Obtain the specific system call failure from the debug log, and investigate the
operating system functionality that is related to the failure.

Media Manager status code 60
Message: cannot perform operation on this host
Explanation: A requested operation is not functional on a particular host.
¦ 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.
¦ Robot inventory update must be initiated only on the host where the robotic
control and drives are configured.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Media Manager 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 *