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

Recommended Action: Obtain additional in<strong>for</strong>mation by first creating debug logs and<br />

then attempting to recreate the error. The debug logs to create are as follows:<br />

◆ On the server, bptm, bpbrm, and bpdbm.<br />

◆ On <strong>Windows</strong> clients, bpbkar.<br />

◆ On other clients, bpcd.<br />

Note To increase the amount of in<strong>for</strong>mation included in the logs, see “Debug Logs on PC<br />

Clients” on page 46.<br />

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

Message: the image was not created with TIR in<strong>for</strong>mation<br />

Explanation: This is an internal error and should not be seen by customers.<br />

Recommended Action: Obtain detailed troubleshooting in<strong>for</strong>mation by creating debug<br />

logs <strong>for</strong> bptm and bpdbm on the server. Then, retry the operation and check the resulting<br />

debug logs.<br />

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

Message: the TIR in<strong>for</strong>mation is zero length<br />

Explanation: For a true-image backup, the client sent no file in<strong>for</strong>mation to the master<br />

server. <strong>NetBackup</strong> discovered this condition when it attempted to write the TIR<br />

in<strong>for</strong>mation to media.<br />

Recommended Action:<br />

1. Check the file list <strong>for</strong> the policy and the exclude and include lists on the client to verify<br />

that the client has files that are eligible <strong>for</strong> backup. For example, this status code can<br />

appear if the exclude list on the client excludes all files.<br />

2. To obtain detailed troubleshooting in<strong>for</strong>mation, create debug logs <strong>for</strong> bptm and<br />

bpdbm on the server. Then, retry the operation and check the resulting debug logs.<br />

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

Message: the error status has been written to stderr<br />

Explanation: If a Vault job fails with a status code greater than 255, it exits with status 252;<br />

the actual Vault status code is written to stderr. This is because status codes greater than<br />

255 are not supported by all operating systems. The Vault job then reports the actual<br />

status code found in stderr (<strong>for</strong> example, 256) as the job completion status, as seen in the<br />

Activity Monitor.<br />

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