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

related to 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. On UNIX servers, gather the output of the ipcs -a command to see what resources<br />

are currently in use.<br />

Device Management Status Code: 35<br />

Message: Request terminated because media is unavailable (in DOWN drive, misplaced,<br />

write protected or unmountable)<br />

Explanation: A mount request has been canceled because the media being requested is<br />

not available. It may be in a DOWN drive, misplaced, write protected, or unmountable.<br />

Recommended Action: Use robotic inventory or manual means to compare the contents<br />

of media in the robotic library with the volume configuration, and update the<br />

configuration as needed. Determine the physical location of the media. Check integrity of<br />

the drive, drive path, and media if the media is found in a logically DOWN drive. Verify<br />

that the media is not a misconfigured cleaning tape. Move the media into the robotic<br />

library and update the volume configuration if the media was not present in the library.<br />

Set the cartridge tab to allow write access, or request the media with read-only access if<br />

the write protection was the cause of the error.<br />

Device Management Status Code: 36<br />

Message: Request terminated by tpunmount call from another process<br />

Explanation: A request was made to change the limit <strong>for</strong> the number of times that a<br />

volume can be mounted with write access <strong>for</strong> one or more volumes in the volume<br />

configuration, and the value specified was not within the acceptable range. The maximum<br />

number of mounts value may also be invalid in the number of mounts/cleanings field of a<br />

barcode rule.<br />

Recommended Action:<br />

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