NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
Chapter 5, Media Manager Status Codes and Messages 235
Status Codes
Explanation: A process timed out while connecting to vmd (the Media Manager volume
daemon on UNIX or NetBackup Volume Manager service on Windows) or to oprd (the
operator request daemon/process). This problem can occur when a connection is
attempted and the server process is not running. It can also occur if the network or server
is heavily loaded and has slow response time.
Recommended Action:
1. On the host (Media Manager host, Device Host, or volume database host) where vmd
is the recipient of the connection, verify that the daemon/service is running. If the
daemon/service is not running, start it. On Windows, vmd is the NetBackup Volume
Manager service.
2. If vmd is already running, examine command output, debug logs, and system logs for
a more detailed message on the error.
a. If not already enabled, enable debug logging by creating the necessary
directories/folders. Increase the level of verbosity by adding the VERBOSE
option in the vm.conf file and restarting the daemons/services, or execute the
command’s verbose option, if available.
b. Retry the operation and examine the logs.
3. Verify that the correct host names are defined in the configuration. Each robot
definition contains a volume database host where volumes are configured for use in
the robot. Each group of servers shares a common global device database host, which
vmd manages.
4. Check the services file. On UNIX, verify that the /etc/services file (and NIS
services if NIS is used) has entries for the vmd service. (Note that oprd is always
started by the vmd service.) 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, which is noted in the man page for vmd(1M).
5. Verify that all operating system patches or service packs are installed.
6. 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 Media Manager
configuration file, vm.conf, that increase the load. Consider placing the volume
database on a higher performance server and file system if performance is an issue.
Consider using inventory filtering for robot types that support it, to reduce the
number of volumes in the volume configuration.
NetBackup 4.5 Troubleshooting Guide for Windows