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.

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

Explanation: A drive has been detected without the expected compression device file<br />

used to configure that device. Automatic device configuration attempts to use a device file<br />

that supports hardware data compression. When multiple compression device files exist<br />

<strong>for</strong> a drive, automatic device configuration cannot determine which compression device<br />

file is best. It uses a non-compression device file instead.<br />

Recommended Action: If you do not need hardware data compression, no action is<br />

necessary. The drive can be operated without hardware data compression. If you need<br />

hardware data compression, refer to the chapter <strong>for</strong> your system type in the Media Manager<br />

Device Configuration <strong>Guide</strong> <strong>for</strong> UNIX <strong>for</strong> in<strong>for</strong>mation on configuring tape drives.<br />

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

If the “Preliminary <strong>Troubleshooting</strong>” or “<strong>Troubleshooting</strong> Installation and Configuration<br />

Problems” procedures did not reveal the problem, per<strong>for</strong>m the following procedures,<br />

skipping those steps that you have already per<strong>for</strong>med.<br />

The procedures assume that the software was successfully installed, but not necessarily<br />

configured correctly. If <strong>NetBackup</strong> or Media Manager has never worked properly, there<br />

are probably configuration problems. Repeat the checks mentioned in the<br />

“<strong>Troubleshooting</strong> Installation and Configuration Problems” procedure when you<br />

encounter errors. In particular, look <strong>for</strong> device configuration problems.<br />

You may also want to per<strong>for</strong>m each backup and restore twice. Per<strong>for</strong>m them first as a user<br />

that is a member of the Administrators group and then as a user that is not a member of<br />

the Administrator group. In all cases, ensure that you have read and write permissions on<br />

the test files.<br />

To Test Master Server and Clients<br />

1. Enable appropriate debug logs on the master server (see the “Using the Logs and<br />

Reports” chapter). If you do not know which logs apply, enable them all until you<br />

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

problem.<br />

2. Configure a test policy (set backup window to be open while you are testing). Name<br />

the master server as the client and a storage unit that is on the master server<br />

(preferably a nonrobotic drive). Also, configure a volume in the <strong>NetBackup</strong> volume<br />

pool and insert the volume in the drive. If you don’t label the volume by using the<br />

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

ID.<br />

3. Verify that the <strong>NetBackup</strong> services are running on the master server:<br />

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