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

Format Optical Status Code: 10<br />

Message: tp<strong>for</strong>mat: Invalid robot<br />

Explanation: The <strong>for</strong>mat optical disk command tp<strong>for</strong>mat could not find a valid,<br />

specified robot in the device configuration.<br />

Recommended Action:<br />

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

Status Codes<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. Check the device configuration to see if a robot of type TLM (Tape Library<br />

Multimedia) or ODL (Optical Disk Library) is configured, matching the robot number<br />

passed on the tp<strong>for</strong>mat -r option.<br />

Format Optical Status Code: 11<br />

Message: tp<strong>for</strong>mat: Command interrupted<br />

Explanation: The <strong>for</strong>mat optical disk command tp<strong>for</strong>mat was interrupted because the<br />

optical mount request was canceled or not accomplished within the required time<br />

interval.<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. Resubmit the request and observe the Device Monitor <strong>for</strong> standalone optical mount<br />

requests, servicing them as needed. Look <strong>for</strong> pending requests indicating reasons <strong>for</strong><br />

the optical mount not being completed.<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!