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 />

Explanation: A request was made to release a shared drive with vmd/DA (the device<br />

allocator <strong>for</strong> the Shared Storage Option). The drive was not reserved by the requesting<br />

host, although it had been reserved <strong>for</strong> another host.<br />

This is an abnormal condition that could occur if there was a network problem or a<br />

suspended process. The following is a possible scenario:<br />

1. Host A reserves a shared drive.<br />

2. Host A becomes unavailable <strong>for</strong> some time, unable to communicate with other hosts.<br />

3. Host B determines that the host having the reservation (Host A) is no longer available,<br />

and makes a request to vmd/DA denoting Host A as unavailable.<br />

4. Some other host (such as Host A or Host C) reserves the drive.<br />

5. The host originally owning the drive reservation tries to release the drive.<br />

Recommended Action: Correct the network or process problem that led to the<br />

communications problem. Ensure that unique non-duplicate strings are being used <strong>for</strong><br />

host names and <strong>for</strong> SSO_HOST_NAME configuration file entries.<br />

Media Manager Status Code: 134<br />

Message: requested drive is not currently reserved<br />

Explanation: A request was made to release a shared drive with vmd/DA (the device<br />

allocator <strong>for</strong> the Shared Storage Option SSO), but the drive was not reserved by any hosts.<br />

This is an abnormal condition that could occur if there was a network problem or a<br />

suspended process. The following is a possible scenario:<br />

1. Host A reserves a shared drive.<br />

2. Host A becomes unavailable <strong>for</strong> some time, unable to communicate with other hosts.<br />

3. Host B determines that the host having the reservation (Host A) is no longer available,<br />

and makes a request to vmd/DA denoting Host A as unavailable.<br />

4. The host originally owning the drive reservation tries to release the drive.<br />

Recommended Action: Correct the network or process problem that led to the<br />

communications problem. Ensure that unique non-duplicate strings are being used <strong>for</strong><br />

host names and <strong>for</strong> SSO_HOST_NAME configuration file entries.<br />

268 <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!