15.04.2013 Views

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Status Codes<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong><br />

7. By checking utilities such as ipcs -a, ensure that shared memory is functioning<br />

properly. The oprd process may not be responding, because it is having trouble<br />

attaching to shared memory.<br />

Media Manager Status Code: 71<br />

Message: failed sending to vmd<br />

Explanation: An attempt to write data to a vmd socket failed. vmd is the Media Manager<br />

volume daemon (UNIX) or <strong>NetBackup</strong> Volume Manager service (<strong>Windows</strong>).<br />

Recommended Action:<br />

1. Examine command output (if available) and the daemon and reqlib debug logs <strong>for</strong> a<br />

more detailed message on the error.<br />

a. If not already enabled, enable debug logging by creating the necessary<br />

directories/folders. Increase the level of verbosity by adding the VERBOSE<br />

option in the vm.conf file and restarting the daemons/services, or by executing<br />

the command’s verbose option, if available.<br />

b. Retry the operation and examine the logs.<br />

2. Identify the system where vmd is running. This is usually termed the Media Manager<br />

host or volume database host, and defaults to the local system in some user interfaces<br />

(such as vmadm). Possible causes <strong>for</strong> the error are high network load, missing<br />

operating system patches or service packs, or unexpected vmd process failure.<br />

Media Manager Status Code: 72<br />

Message: failed receiving from vmd<br />

Explanation: An attempt to read data from a vmd socket failed. vmd is the Media<br />

Manager volume daemon (UNIX) or <strong>NetBackup</strong> Volume Manager service (<strong>Windows</strong>).<br />

Recommended Action:<br />

1. Examine command output (if available) and the daemon and reqlib debug logs <strong>for</strong> a<br />

more detailed message on the error.<br />

a. If not already enabled, enable debug logging by creating the necessary<br />

directories/folders. Increase the level of verbosity by adding the VERBOSE<br />

option in the vm.conf file and restarting the daemons/services, or by executing<br />

the command’s verbose option, if available.<br />

b. Retry the operation and examine the logs.<br />

236 <strong>NetBackup</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> - <strong>Windows</strong> NT/2000<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!