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

3. On UNIX servers, gather the output of the ipcs -a command to see what resources<br />

are currently in use.<br />

Robot Error Status Code: 3<br />

Message: Error in getting shared memory<br />

Explanation: A robotic daemon/process was unable to get a shared memory identifier<br />

associated with a segment of shared memory that ltid maintains. (ltid is the Media<br />

Manager device daemon on UNIX or the <strong>NetBackup</strong> Device Manager service on<br />

<strong>Windows</strong>.)<br />

Recommended Action:<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 />

Robot Error Status Code: 4<br />

Message: Error in attaching the shared memory<br />

Explanation: A robotic daemon/process was unable to attach a shared memory segment<br />

that ltid maintains. (ltid is the Media Manager device daemon on UNIX or the<br />

<strong>NetBackup</strong> Device Manager service on <strong>Windows</strong>.)<br />

Recommended Action:<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 ltid.<br />

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

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