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.

Status Codes<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong><br />

◆ vltopmenu binary is not executable<br />

◆ the disk (on which <strong>NetBackup</strong> is installed) is full<br />

◆ the following directory is removed or made inaccessible to root (where xxx is the<br />

session id):<br />

UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx<br />

<strong>Windows</strong>: install_path\netbackup\vault\sessions\vault_name\sidxxx<br />

Recommended Action: To identify which of the above conditions led to the failure,<br />

review the vault debug log in the following directory:<br />

UNIX: /usr/openv/netbackup/logs/vault<br />

<strong>Windows</strong>: install_path\<strong>NetBackup</strong>\logs\vault<br />

Also review the detail.log file in each of the sidxxx directories that had problems:<br />

UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx<br />

<strong>Windows</strong>: install_path\<strong>NetBackup</strong>\vault\sessions\vault_name\sidxxx<br />

Correct the problem and rerun the vault job. If the problem persists, please contact<br />

customer support and send the appropriate logs.<br />

<strong>NetBackup</strong> Status Code: 290<br />

Message: one or more errors detected during eject processing<br />

Explanation: This error occurs when more than one error is encountered during an eject<br />

procedure via vltopmenu. Any “eject” errors in the range 291 to 300 could have occurred<br />

in any of the sessions being ejected.<br />

Recommended Action: For detailed in<strong>for</strong>mation, review the vault debug log in the<br />

following directory:<br />

UNIX: /usr/openv/netbackup/logs/vault<br />

<strong>Windows</strong>: install_path\<strong>NetBackup</strong>\logs\vault<br />

Also review the detail.log in each of the sidxxx directories that had problems:<br />

UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx<br />

<strong>Windows</strong>: install_path\<strong>NetBackup</strong>\vault\sessions\vault_name\sidxxx<br />

(where xxx is the session id)<br />

The media that was not ejected may need to be ejected manually by means of<br />

vlteject or vltopmenu, after the problem has been identified and corrected.<br />

This error often indicates that the media were left in the offsite vault volume group<br />

but still physically reside in the robot or in the robotic MAP. To solve this problem, do<br />

one of the following:<br />

◆ Manually remove any media that are in the offsite vault volume group but are still in<br />

the robotic library.<br />

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