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

Recommended Action:<br />

1. Examine the command input, debug logs, and system logs <strong>for</strong> a more detailed<br />

message on the system error.<br />

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

Status Codes<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, or start vmd with<br />

the verbose option<br />

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

2. Obtain the specific system call failure from the debug log, and investigate operating<br />

system functionality related to the failure. Execute the hostname system command to<br />

see if the command is operating correctly.<br />

Media Manager Status Code: 77<br />

Message: failed during tp<strong>for</strong>mat<br />

Explanation: A request was made to <strong>for</strong>mat an optical platter, and the request failed or<br />

was aborted by the administrator.<br />

◆ The optical volume <strong>for</strong>mat may have failed because a WORM (write-once, read many)<br />

platter cannot be re<strong>for</strong>matted.<br />

◆ If the overwrite label option was not specified and the <strong>for</strong>mat operation is not<br />

interactive, the <strong>for</strong>mat optical operation will fail if the platter has already been<br />

<strong>for</strong>matted.<br />

◆ If the administrator chooses to abort the <strong>for</strong>mat operation after it has been found that<br />

the platter has already been <strong>for</strong>matted, the <strong>for</strong>mat request will return with this status<br />

code.<br />

◆ The <strong>for</strong>mat operation may have failed due to a device or media problem.<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 <strong>for</strong>mat error.<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 daemons/services, or by executing<br />

the command’s verbose option, if available.<br />

b. Retry the operation and examine the logs.<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!