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

Media Manager Status Code: 86<br />

Message: failed opening tmp output file<br />

Explanation: The Media Manager configuration file (vm.conf) or temporary working file<br />

could not be opened.<br />

Recommended Action: On UNIX: check <strong>for</strong> the existence and permissions of the<br />

/usr/openv/volmgr/misc directory, /tmp directory, and<br />

/usr/openv/volmgr/vm.conf file. On <strong>Windows</strong>: check <strong>for</strong> the existence and security<br />

properties of the install_path\Volmgr\vm.conf file.<br />

Media Manager Status Code: 87<br />

Message: failed redirecting tmp output file<br />

Explanation: The system call dup2(3C) failed during an attempt to direct interface<br />

output from a temporary file to the process’s standard output.<br />

Recommended Action: Investigate operating system functionality related to resource<br />

limits on the number of open files. Ensure that processes are not being interrupted by<br />

extraneous signals.<br />

Media Manager Status Code: 88<br />

Message: failed initiating child process<br />

Explanation: A command could not be executed. This can occur because the permissions<br />

of the command do not allow it to be executed, or because system resources, such as<br />

memory and swap space, are insufficient.<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 system 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 />

2. Check the permissions on the vmcheckxxx, vmupdate, and oprd binaries, and (on<br />

<strong>Windows</strong> only) the rdevmi installed binary.<br />

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