NetBackup 4.5 Troubleshooting Guide for Windows - Symantec
15.04.2013 • Views
Share Embed Flag

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
ePAPER READ
DOWNLOAD ePAPER
gcT66iuDWQ

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

START NOW

Status Codes<br />

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

◆ Could not open a pipe to vmchange -verify_eject call.<br />

◆ Unexpected output from vmchange -verify_eject call.<br />

◆ There are no MAP elements to eject media into.<br />

◆ The robotic library had problems putting media into the MAP.<br />

◆ The user hit Return in interactive mode without first removing the media from the<br />

MAP. In this case, the media that were in the MAP will be put back into their original<br />

slots in the robotic library.<br />

Recommended Action: For detailed in<strong>for</strong>mation about why the process was aborted,<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 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 />

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

◆ Inventory the robotic library. This puts any media that were in the offsite vault<br />

volume group back into the robotic volume group. Then, rerun the vault sessions that<br />

failed.<br />

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

Message: Database backup failed<br />

Explanation: The catalog backup step failed during a vault job.<br />

Recommended Action: For detailed in<strong>for</strong>mation about why the process failed, review the<br />

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 in each of the sidxxx directories that had problems, to<br />

find the actual problem that caused the catalog backup (bpbackupdb) to fail:<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 />

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

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!