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

Chapter 5, Media Manager Status Codes and Messages 299<br />

Status Codes<br />

Explanation: There was a failed request to create a backup copy, remove a backup copy,<br />

or replace the current copy of the local device databases. These databases are ltidevs<br />

and robotic_def, located in /usr/openv/volmgr/database (UNIX) or<br />

install_path\volmgr\database (<strong>Windows</strong>).<br />

Recommended Action:<br />

1. Examine the daemon debug log and command or interface output <strong>for</strong> a more detailed<br />

message on the system error, as follows.<br />

a. If not already enabled, enable debug logging by creating the necessary<br />

directories/folders. Increase the level of verbosity by adding the VERBOSE<br />

option in the vm.conf file and restarting the volume daemon / <strong>NetBackup</strong><br />

Volume Manager service, or start vmd with the verbose option.<br />

b. Retry the operation and examine the logs.<br />

2. Examine the permissions and check <strong>for</strong> the existence of the local device database files.<br />

Display the device configuration to determine whether or not the database is corrupt,<br />

and restore a saved copy of the databases from catalog backups, or delete them and<br />

recreate the device configuration as needed.<br />

Device Configuration Status Code: 44<br />

Message: Cannot discover devices. See the <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> details.<br />

Explanation: Any of the following: device discovery was attempted on a plat<strong>for</strong>m where<br />

it is not supported according to the currently installed software, there was an internal<br />

consistency problem with the global device database, or device discovery could not obtain<br />

or verify its lock file.<br />

Recommended Action:<br />

1. Check www.veritas.com and product release documentation <strong>for</strong> supported<br />

plat<strong>for</strong>ms <strong>for</strong> device discovery. Upgrade the installed software to the latest available<br />

patch level if documentation indicates that device discovery is supported on the<br />

targeted host plat<strong>for</strong>m.<br />

2. Examine the daemon debug log and command or interface output <strong>for</strong> a more detailed<br />

message on the system error, as follows.<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!