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

Explanation: There were no problems detected with the requested operation.<br />

Recommended Action: None, unless this was a database backup per<strong>for</strong>med through a<br />

database extension product (<strong>for</strong> example, <strong>NetBackup</strong> <strong>for</strong> Oracle or <strong>NetBackup</strong> <strong>for</strong> SQL<br />

Server). In those instances, code 0 means the backup script that started the backup ran<br />

without error. However, you must check other status as explained in the related<br />

<strong>NetBackup</strong> manual to see if the database was successfully backed up.<br />

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

Message: the requested operation was partially successful<br />

Explanation: A problem that may require corrective action was detected during the<br />

requested operation.<br />

Recommended Action: Check the All Log Entries report and also the progress log (if<br />

there is one).<br />

Some of the problems that can show up under status code 1 are:<br />

◆ A file or directory path that is more than 1023 characters long.<br />

For <strong>NetBackup</strong> ServerFree Agent: the maximum pathname length is 1000 characters<br />

<strong>for</strong> frozen image backups, not 1023. When the frozen image is created, a new mount<br />

point is added to the beginning of the file path. If this new mount point plus the<br />

original file path exceeds 1023 characters, the backup fails with status code 1. The<br />

progress log includes the entry “ERR - Skipping long dir path.”<br />

◆ Could not open a file.<br />

◆ Read error encountered in a file.<br />

◆ File is of an unknown type.<br />

◆ On clients using Open Transaction Manager (OTM) <strong>for</strong> open file management, the<br />

OTM cache may be full. See the recommended actions under status code 11.<br />

◆ A vault job may terminate with status code 1 if non-fatal errors are encountered<br />

during one or more of the following operations:<br />

◆ duplication<br />

◆ suspension of unvaulted media<br />

◆ expiration of disk images<br />

◆ execution of vlt_ejectlist_notify script<br />

◆ catalog backup<br />

◆ eject and/or report<br />

In the event of a non-fatal error, Vault will attempt to complete all the steps<br />

configured in the vault profile.<br />

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