NetBackup 4.5 Troubleshooting Guide for Windows - Symantec
15.04.2013 • Views
Share Embed Flag

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
ePAPER READ
DOWNLOAD ePAPER
gcT66iuDWQ

Create successful ePaper yourself

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

START NOW

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

General Test and <strong>Troubleshooting</strong> Procedures<br />

To per<strong>for</strong>m this check, use the Activity Monitor or the Services application in the<br />

<strong>Windows</strong> Control Panel.<br />

4. Per<strong>for</strong>m a user backup and then a restore of a file. Per<strong>for</strong>m these operations from a<br />

client that has been verified to work with the master server.<br />

This test verifies:<br />

◆ <strong>NetBackup</strong> media server software<br />

◆ Media Manager on the media server can mount the media and use the drive that<br />

you configured<br />

◆ Communications between the master server process bpsched and media server<br />

processes bpcd and bpbrm<br />

◆ Communications between media server process bpbrm and client processes bpcd<br />

and bpbkar<br />

For failures relating to drives or media, ensure that the drive is in an UP state and the<br />

hardware is functioning.<br />

If you suspect a communications problem between the master and media servers,<br />

check the debug logs <strong>for</strong> the involved processes. If the debug logs don’t help you,<br />

check the following:<br />

◆ Event Viewer Application log<br />

◆ vmd debug logs<br />

See the vendor manuals <strong>for</strong> in<strong>for</strong>mation on hardware failures.<br />

If you are using a robot and this is an initial configuration, verify that the robotic drive<br />

is configured correctly. In particular, verify that:<br />

◆ The same robot number is used both in the Media Manager and storage unit<br />

configurations.<br />

◆ Each robot has a unique robot number.<br />

5. If you previously configured a nonrobotic drive and a robot attached to your media<br />

server, change the test policy to name the robot. Also, add a volume <strong>for</strong> the robot to<br />

the volume database host <strong>for</strong> the robot. Verify that the volume is in the <strong>NetBackup</strong><br />

volume pool and in the robot.<br />

Then, repeat this procedure starting with step 3, this time <strong>for</strong> a robot. This verifies that<br />

Media Manager can find the volume, mount it, and use the robotic drive.<br />

If a failure occurs, check the <strong>NetBackup</strong> All Log Entries report. Look <strong>for</strong> errors<br />

relating to devices or media. If the All Log Entries report doesn’t help, check:<br />

◆ vmd debug logs on the volume database host <strong>for</strong> the robot<br />

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

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!