Troubleshooting guide

Chapter 4, Status Codes and Messages 85
Status Codes
This indicates that the cache partition is not large enough. If possible, increase the size
of the cache partition. Or, if multiple backups are using the same cache, either reduce
the number of concurrent backups by rescheduling some of them or reschedule the
entire backup to a time when the file system is less active.
3. For detailed troubleshooting information, create an activity log directory for the
process that returned this status code, retry the operation, and check the resulting
activity log.
Status Code: 14
Message: file write failed
Explanation: A write to a file or socket failed. Possible causes include:
◆ I/O error writing to the file system.
◆ Write to a socket failed. This can be caused by a network problem or a problem with
the process reading from the socket.
◆ Writing to a full disk partition.
◆ The bpfsmap temporary directory (usually /tmp) became full (on Auspex
FastBackup jobs).
Recommended Action:
◆ Check the NetBackup Problems report for clues on where and why the problem
occurred.
◆ On Auspex FastBackup jobs (for NetBackup 3.0), increase the size of the /tmp
partition; there is a TMPDIR file which can be created for NetBackup 3.1.1.
◆ For detailed troubleshooting information, create an activity log directory for the
process that returned this status code, retry the operation, and check the resulting
activity log.
◆ Make sure that routers, bridges, and other network devices are all at “full” duplex.
◆ Use a “sniffer” program to determine the number of packets being rejected and/or
re-requested.
◆ On Windows NT/2000 systems, the client bpbkar log may contain a 10054
“Connection Reset Error”error (usually indicates a hardware error). Somewhere
between the NetBackup client and server, the connection was reset. When NetBackup
receives this error, it is unable to continue the backup. This error has been attributed
to the following:
◆ A hiccup in the network.
◆ A bad network interface card on a NetBackup client.