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

6. Examine other debug logs or the status on the client.<br />

7. If a backup on a <strong>Windows</strong> <strong>NetBackup</strong> client fails with status code 11 and the client is<br />

using Open Transaction Manager (OTM) <strong>for</strong> open file management, it is possible that<br />

the error was caused by the OTM cache file being full. If this is the case and bpbkar<br />

debug logs are turned on, a message similar to the following should appear at the end<br />

of the backup:<br />

04/28/99 11:27:56 AM: [216]: ERR - OTM Error:0xe0001005<br />

04/28/99 11:27:59 AM: [216]: INF - OTM Terminate - disabled <strong>for</strong> all<br />

processes<br />

04/28/99 11:27:59 AM: [216]: FTL - Backup operation aborted!<br />

If this error is encountered, try one of the following (the first is preferred):<br />

◆ Set maximum OTM cache size to zero (0); at run time, OTM will determine how<br />

much cache is needed and set it accordingly.<br />

◆ Increase either the initial OTM cache size or the maximum OTM cache size on<br />

your own, depending on the requirements of your installation and your usage of<br />

OTM.<br />

If resizing OTM cache does not fix the problem, you may not have enough free disk<br />

space.<br />

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

Message: file open failed<br />

Explanation: An open of a file failed.<br />

Recommended Action:<br />

◆ For <strong>NetBackup</strong> ServerFree Agent only:<br />

Status code 12 may appear in the /usr/openv/netbackup/logs/bptm or bpdm<br />

log, accompanied by the following:<br />

tpc_read_config failed: cannot open file<br />

/usr/openv/volmgr/database/3pc.conf<br />

This may indicate that the policy is configured with either <strong>NetBackup</strong> Media Server<br />

or Third-Party Copy Device as the offhost backup method, but that the 3pc.conf file<br />

does not exist or is in the wrong location. (When upgrading from <strong>NetBackup</strong> 4.0V to<br />

<strong>4.5</strong>, you must recreate the 3pc.conf file.) For instructions on creating the 3pc.conf<br />

file, refer to the latest version of the <strong>NetBackup</strong> ServerFree Agent System Administrator’s <strong>Guide</strong>.<br />

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