NetBackup Troubleshooting Guide - Zedat
05.01.2013 • Views
Share Embed Flag

NetBackup Troubleshooting Guide - Zedat

NetBackup Troubleshooting Guide - Zedat

NetBackup Troubleshooting Guide - Zedat

SHOW MORE
SHOW LESS
ePAPER READ
DOWNLOAD ePAPER
zedat.fu.berlin.de

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

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

START NOW

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

◆ To check the daemons on a UNIX system, execute:<br />

/usr/openv/netbackup/bin/bpps -a<br />

◆ To check the services on a Windows system, use the <strong>NetBackup</strong> Activity Monitor<br />

or the Services application in the Windows Control Panel.<br />

4. Start a manual backup of a policy by using the manual backup option in the<br />

<strong>NetBackup</strong> administration interface. Then, restore the backup.<br />

This verifies:<br />

◆ <strong>NetBackup</strong> server software is functional, including all daemons or services,<br />

programs, and databases.<br />

◆ Media Manager can mount the media and use the drive you configured.<br />

If a failure occurs, first check the <strong>NetBackup</strong> All Log Entries report. For failures<br />

relating to drives or media, verify that the drive is in an UP state and the hardware is<br />

functioning.<br />

To further isolate the problem, use the debug logs. The “Functional Overview”<br />

appendix explains the basic sequence of events (log messages are more detailed than<br />

the information in that appendix).<br />

If the debug logs do not reveal the problem, check the following:<br />

◆ Systems Logs or Event Viewer System logs<br />

◆ Event Viewer Application logs on Windows systems<br />

◆ vmd debug logs on the EMM database host for the device<br />

◆ bptm debug logs<br />

See the vendor manuals for information 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 />

On a UNIX <strong>NetBackup</strong> server, you can verify only the Media Manager part of the<br />

configuration, by using the tpreq command to request a media mount. Verify that<br />

the mount completes and check which drive the media was mounted on. Repeat the<br />

process until the media has been mounted and unmounted on each drive from the<br />

host where the problem was occurring. If this works, the problem is probably with the<br />

policy or storage unit configuration. When you are done, tpunmount the media.<br />

22 <strong>NetBackup</strong> <strong>Troubleshooting</strong> <strong>Guide</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!