Symantec NetBackup Media Manager status code 67 to status code 70

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 67 to status code 70 which may be received while using the Symantec NetBackup tool.

Media Manager status code 67
Message: unable to send exit status
Explanation: vmd cannot send the status of a requested operation to the requestor.
(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 send or write system call failure from the debug log, and
investigate the operating system functionality that is related to the failure.
¦ Use the following steps to check whether the command or the application
interface that sends the request aborts prematurely: enable reqlib debug logs,
retry the operation, check the debug logs, and observe application interface
output.

Media Manager status code 68
Message: too many volumes in volume group
Explanation: A request was made to add or change volumes in the volume
configuration but the volume number was at its allowable limit. The limit is based
on the number of volumes that is allowed in a particular type of robot.
¦ 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.
¦ Check to see if volumes are defined in theEMMdatabase. They may be defined
in the EMM database, which is associated with a slot number zero that may
not exist in the robot. Run a robot inventory. Show contents of robot report
and observe the starting slot number. If the starting slot number is one and a
volume is defined in the robot at slot zero, delete the volume entry. Or move
it to stand-alone so that the remaining available media slots can be used.

Media Manager status code 69
Message: failed sending request to vmd
Explanation: A request cannot be sent to vmd or to oprd, even though the initial
connection to the server process was successful. (vmd is the NetBackup Volume
Manager daemon on UNIX and Linux or NetBackup Volume Manager service on
Windows; oprd is the operator request daemon or process.)
¦ 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.
¦ Check to see whether the vmd or the oprd process continues to run once it
receives the connection from the requestor. Run netstat -a or an equivalent
socket diagnostic utility. Check the following to see if the server process is
hung up: the daemon debug log on the server-side system and the process
status of vmd or oprd.

Media Manager status code 70
Message: cannot connect to vmd [on host host name]
Explanation: A process times out while connecting to the following: vmd (the
NetBackup Volume Manager daemon on UNIX and Linux or NetBackup Volume
Manager service on Windows) or to oprd (the operator request daemon or process).
This problem can occur when a connection is attempted and the server process
is not running. It also can occur if the network or server is heavily loaded and has
slow response time.
¦ On the host where vmd is the recipient of the connection, verify that the daemon
or the service is running. (The host is the Media Manager host, the Device
Host, or the EMM server.) If the daemon or the service is not running, start it.
On Windows, vmd is the NetBackup Volume Manager service.
¦ If vmd is already running, 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.
¦ Verify that the correct host names are defined in the configuration.
¦ Check the services file. On UNIX and Linux, verify that the /etc/services file
(and NIS services if NIS is used) has entries for the vmd service. (Note that the
vmd service always starts oprd.) On Windows, verify that the
%systemroot%\system32\drivers\etc\services file has the correct entry
for vmd. Also verify that the vmd port number in the services file agrees with
the port number configuration. The port number is noted in the man page for
vmd(1M).
¦ Verify that all operating system patches or service packs are installed.
¦ Ensure that the Media Manager configuration is not tuned so that the load on
vmd exceeds its ability to service requests. Look for entries in the vm.conf file
that increase the load. Consider placing the EMM database on a higher
performance server and file system if performance is an issue. To reduce the
number of volumes in the volume configuration, use inventory filtering for
the robot types that support it
¦ Check utilities such as ipcs -a to ensure that shared memory functions
properly. The oprd process may not respond because it cannot attach to shared
memory.

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 *