Possible causes include the following:

• An I/O error that occurred during a write to the file system.

• Write to a socket failed. Cause of this failure: A network problem or a problem with the process that reads from the socket.

• Writing to a full disk partition.

• Check the NetBackup Problems report for clues on where and why the problem occurred.

• For detailed troubleshooting information, create a debug log directory for the process that returned this status code. Then retry the operation and check the resulting debug log.

• Make sure that routers, bridges, and other network devices are all at "full" duplex.

  See "Backup Performance and NIC Cards" in the Troubleshooting Guide.

• Use a "sniffer" program to determine the number of packets being rejected or re-requested.

• On Windows 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 cannot 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.

  • A bad network interface card on the NetBackup server.

  • Faulty routers.

  • Any other applications that interfere with NetBackup connections.

• On Novell systems, status code 14 has also been attributed to network issues. Try a "sniffer" program.

• The error occurs while you use the NetBackup-Java interface: The application server (bpjava processes) for the NetBackup-Java interface probably ran out of disk space in the file system containing /usr/openv/netbackup/logs/user_ops. The application server writes temporary files into directories in the /user_ops directory. Try clearing up disk space in the file system.