05.01.2013 Views

NetBackup Troubleshooting Guide - Zedat

NetBackup Troubleshooting Guide - Zedat

NetBackup Troubleshooting Guide - Zedat

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>Troubleshooting</strong> Installation and Configuration Problems<br />

When this condition exists, you can frequently perform backups but not restores.<br />

“<strong>NetBackup</strong> Status Code: 174” in the “<strong>NetBackup</strong> Status Codes and Messages”<br />

chapter provides further explanation. Also see the Media Manager Device<br />

Configuration <strong>Guide</strong>.<br />

◆ On UNIX, pass-through paths to the tape drives have not been established. Also<br />

see the Media Manager Device Configuration <strong>Guide</strong>.<br />

2. Check for the following problems with the daemons or services:<br />

◆ Daemons or services do not start during reboot (configure system so this occurs).<br />

◆ Wrong daemons or services are started (problems with media server start up<br />

scripts).<br />

◆ Configuration was changed while daemons or services were running.<br />

◆ On Windows, the %SystemRoot%\System32\drivers\etc\services file<br />

does not have an entry for vmd, bprd, bpdbm and bpcd. Also, ensure there are<br />

entries for the processes for configured robots (see the Media Manager System<br />

Administrator’s <strong>Guide</strong> for Windows for a list of these processes).<br />

◆ On UNIX, the /etc/services file (or NIS or DNS) does not have an entry for<br />

vmd, bprd, bpdbm, or robotic daemons.<br />

3. If you found and corrected any configuration problems, retry the operation and check<br />

for <strong>NetBackup</strong> status codes or messages.<br />

a. Check the All Log Entries report for <strong>NetBackup</strong> errors for the appropriate time<br />

period. This report can show the context in which the error occurred and can<br />

often have specific information that is useful when the error can result from a<br />

variety of problems.<br />

If the problem involved a backup or archive, check the Backup Status report. This<br />

report gives you the status code.<br />

If you find a status code or message in either the Backup Status or All Log Entries<br />

report, go to the “<strong>NetBackup</strong> Status Codes and Messages” chapter or “Media<br />

Manager Status Codes and Messages” chapter and perform the recommended<br />

corrective actions.<br />

b. If the problem pertains to device or media management and either <strong>NetBackup</strong><br />

does not provide a status code or you cannot correct the problem by following the<br />

instructions in status codes chapters, check the system log on UNIX systems, or<br />

the Event Viewer Application log on Windows systems for <strong>NetBackup</strong> entries.<br />

c. Check appropriate debug logs that are enabled and correct problems you detect.<br />

16 <strong>NetBackup</strong> <strong>Troubleshooting</strong> <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!