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.

Status Codes<br />

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

1. Examine command output (if available), debug logs, and system logs <strong>for</strong> a more<br />

detailed message on the error.<br />

a. Enable debug logging by creating the necessary directories/folders. Increase the<br />

level of verbosity by adding the VERBOSE option in the vm.conf file and<br />

restarting the daemons/services, or execute the command’s verbose option, if<br />

available.<br />

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

2. Ensure that the device files and optical drive library address are correct, since this<br />

error may occur if the device paths or drive address was incorrectly configured. Use<br />

the tp<strong>for</strong>mat -o (overwrite) option if you want to re<strong>for</strong>mat the optical platter. If the<br />

platter is WORM (write-once, read-many), it cannot be re<strong>for</strong>matted.<br />

Format Optical Status Code: 8<br />

Message: tp<strong>for</strong>mat: Must be root<br />

Explanation: The <strong>for</strong>mat optical disk command tp<strong>for</strong>mat was run by a non-root user.<br />

Recommended Action: Execute tp<strong>for</strong>mat only as the root user.<br />

Format Optical Status Code: 9<br />

Message: tp<strong>for</strong>mat: Tape request failed<br />

Explanation: The <strong>for</strong>mat optical disk command tp<strong>for</strong>mat encountered a situation where<br />

the optical volume could not be mounted.<br />

Recommended Action:<br />

1. Examine command output (if available), debug logs, and system logs <strong>for</strong> a more<br />

detailed message on the error.<br />

a. Enable debug logging by creating the necessary directories/folders. Increase the<br />

level of verbosity by adding the VERBOSE option in the vm.conf file and<br />

restarting the daemons/services, or execute the command’s verbose option, if<br />

available.<br />

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

2. Verify the integrity of the device and media, and check the system device files <strong>for</strong><br />

correctness according to the <strong>NetBackup</strong> Device Configuration <strong>Guide</strong>. Investigate robotic<br />

errors and determine whether mount requests are being canceled by the<br />

administrator.<br />

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