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

failed<br />

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

bpbkar: ERR - bpbkar FATAL exit status = 13: file read<br />

bpbkar: INF - EXIT STATUS 13: file read failed<br />

◆ The files to back up exist on a file system that is not mounted. The file system<br />

specified as the frozen image source must be mounted. If the frozen image source is<br />

not mounted but the mount point is present, <strong>NetBackup</strong> may try to take a frozen<br />

image of the directory above the directory that was specified as the frozen image<br />

source.<br />

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

Message: file write failed<br />

Explanation: A write to a file or socket failed. Possible causes include:<br />

◆ I/O error writing to the file system.<br />

◆ Write to a socket failed. This can be caused by a network problem or a problem with<br />

the process reading from the socket.<br />

◆ Writing to a full disk partition.<br />

Recommended Action:<br />

◆ Check the <strong>NetBackup</strong> Problems report <strong>for</strong> clues on where and why the problem<br />

occurred.<br />

◆ For detailed troubleshooting in<strong>for</strong>mation, create a debug log directory <strong>for</strong> the process<br />

that returned this status code, retry the operation, and check the resulting debug log.<br />

◆ Make sure that routers, bridges, and other network devices are all at “full” duplex.<br />

◆ Use a “sniffer” program to determine the number of packets being rejected and/or<br />

re-requested.<br />

◆ On <strong>Windows</strong> systems, the client bpbkar log may contain a 10054 “Connection Reset<br />

Error”error (usually indicates a hardware error). Somewhere between the <strong>NetBackup</strong><br />

client and server, the connection was reset. When <strong>NetBackup</strong> receives this error, it is<br />

unable to continue the backup. This error has been attributed to the following:<br />

◆ A hiccup in the network.<br />

◆ A bad network interface card on a <strong>NetBackup</strong> client.<br />

◆ A bad network interface card on the <strong>NetBackup</strong> server.<br />

◆ Faulty routers.<br />

◆ Other applications interfering with <strong>NetBackup</strong> connections.<br />

◆ On Novell systems, status code 14 has also been attributed to network issues. Try a<br />

“sniffer” program, as suggested above.<br />

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