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

Explanation: tar returned a successful exit status.<br />

Recommended Action: None.<br />

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

Message: tar received an invalid argument<br />

Explanation: One of the parameters passed to tar was not valid.<br />

◆ Recommended Action: On a <strong>Windows</strong> client, create a tar debug log directory, retry<br />

the operation, and check the log.<br />

◆ On a Macintosh client, check the version file that is in the bin folder in the <strong>NetBackup</strong><br />

folder in the Preferences folder. If the software is not at the correct level, install the<br />

correct software as explained in the installation guide.<br />

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

Message: tar received an invalid file name<br />

Explanation: tar cannot write to the file that is specified with the -f parameter.<br />

Recommended Action:<br />

1. Create a bpcd debug log directory on the client (on a Macintosh <strong>NetBackup</strong> creates<br />

the log automatically).<br />

2. On a <strong>Windows</strong> client, create a tar debug log directory.<br />

3. Increase the debug or log level as explained in the debug log topics in Chapter 3.<br />

4. Rerun the operation, check the resulting debug logs <strong>for</strong> the parameters passed to tar<br />

and call customer support.<br />

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

Message: tar received an invalid archive<br />

Explanation: The data passed to tar was corrupt.<br />

Recommended Action:<br />

1. Create a bpcd debug log directory on the client (on a Macintosh <strong>NetBackup</strong> creates<br />

the log automatically).<br />

2. On a <strong>Windows</strong> client, create a tar debug log directory.<br />

3. Increase the debug or log level as explained in the debug log topics in Chapter 3.<br />

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