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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

This verifies:<br />

◆ Communications between the client and master server<br />

◆ <strong>NetBackup</strong> software on the client<br />

If an error occurs, check the following:<br />

◆ All Log Entries report<br />

◆ Debug logs created in the previous step<br />

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

A likely cause <strong>for</strong> errors is a communications problem between the server and the<br />

client.<br />

11. When the test policy operates satisfactorily, repeat specific steps as necessary to verify<br />

other clients and storage units.<br />

12. When all clients and storage units are functional, test the remaining policies and<br />

schedules that use storage units on the master server. If a scheduled backup fails,<br />

check the All Log Entries report <strong>for</strong> errors, then follow the actions suggested in the<br />

status codes chapters.<br />

Testing Media Server and Clients<br />

If you are using media servers, verify their operation as explained in the following steps.<br />

Be<strong>for</strong>e proceeding, eliminate all problems on the master server by completing “To Test<br />

Master Server and Clients” on page 16.<br />

1. Enable appropriate debug logs on the servers (see the “Using the Logs and Reports”<br />

chapter). If you are uncertain which logs apply, enable them all until you solve the<br />

problem. Delete the debug log directories when you have resolved the problem.<br />

2. Configure a test policy with a user schedule (set the backup window to be open while<br />

you are testing).<br />

◆ Name the media server as the client and a storage unit that is on the media server<br />

(preferably a nonrobotic drive).<br />

◆ Add a volume on the volume database host <strong>for</strong> the devices in the storage unit<br />

(master server is recommended <strong>for</strong> the volume database host). Ensure the volume<br />

is in the <strong>NetBackup</strong> volume pool.<br />

◆ Insert the volume in the drive. If you do not prelabel the volume by using the<br />

bplabel command, <strong>NetBackup</strong> automatically assigns a previously unused<br />

media ID.<br />

3. Verify that all <strong>NetBackup</strong> services are running on the master and media servers.<br />

Chapter 2, <strong>Troubleshooting</strong> Procedures 19<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!