NetBackup status code: 13
Message: file read failed
Explanation: A read of a file or socket failed.
The possible causes include the following:
A network communication problem that occurred on the master server, media server, or one of the clients.
An I/O error that occurred during a read from the file system.
Read of an incomplete file or a corrupt file.
A socket read failure caused by a network problem or a problem with the process that writes to the socket.
A problem specific to NetBackup Snapshot Client (see recommended actions).
The first EV-SQL backup after a NetBackup installation failed.
See the Troubleshooting section of the NetBackup for Enterprise Vault Agent Administrator's Guide.
On Windows, the file list that NetBackup generates for the snapshot copy operation does not have enough information to restore from the
tar32copy. For example, block number information is not correct because thetar32copy is not yet created.NetBackup does not support the policy's option for dual-boot VMs.
Locking timeouts in the VMware VDDK may cause simultaneous hotadd backups from the same VMware backup host to fail.
In the NetBackup Activity Monitor, the detailed status log may include messages similar to the following:
12/05/2014 06:43:53 - begin writing 12/05/2014 06:48:53 - Error bpbrm (pid=2605) socket read failed: errno = 62 - Timer expired 12/05/2014 06:48:55 - Error bptm (pid=2654) media manager terminated by parent process
The
/netbackup/logs/vxmslog may include repeated instances of a VDDK message similar to the following:12/08/2014 05:11:35 : g_vixInterfaceLogger:libvix.cpp:1844 <DEBUG> : [VFM_ESINFO] 2014-12-08T05:11:35.146-06:00 [7F1B1163F700 info Libs'] FILE: FileLockWaitForPossession timeout on '/var/log/vmware/hotAddLock. dat.lck/M34709.lck' due to a local process '15882-26732358(bpbkarv)'
Recommended Action: Do the following, as appropriate:
Check the NetBackup Problems report for clues on where and why the problem occurred.
Check that network communication works properly.
See "Resolving network communication problems" in the NetBackup Troubleshooting Guide.
For a FlashBackup client, check the
/var/adm/messageslog for errors like the following:Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache /dev/rdsk/c0t2d0s3 full - all snaps using this cache are now unusable
This error indicates that the cache partition is not large enough. If possible, increase the size of the cache partition. Or, if multiple backups use the same cache, reduce the number of concurrent backups. To reduce the number, reschedule some of them or reschedule the entire backup to a time when the file system is less active.
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.
Ensure that the latest service packs for all products and components (SQL Server, Exchange, Notes, etc.) have been installed.
Ensure that all the network hardware (NICs, hubs, switches, routers, etc.) throughout the environment are set to full duplex, not half duplex.
Check the following items regarding the NICs in your system:
Upgrade to the latest NIC drivers throughout the system.
Ensure that all NICs are set to full duplex, not half duplex.
See Troubleshooting network interface card performance in the NetBackup Troubleshooting Guide.
Increase the timeout settings on the NIC.
If NIC teaming is implemented, deactivate for testing purposes.
Replace the NIC itself on the affected client or server.
For NetBackup Snapshot Client, status code 13 may appear in the
/usr/openv/netbackup/logs/bpbkarlog.The log can indicate the following:
The files to back up reside on an IDE drive as opposed to SCSI. The off-host backup method was set to either NetBackup media server or Third-Party Copy Device. If you use off-host backup, the disk that contains the client files must be a SCSI or Fibre Channel device.
If the disk is an IDE drive, you may see the following in the
/usr/openv/ netbackup/logs/bpfislog:get_disk_info: FTL - /var/tmp/caa026fEU disk_inquiry failed. Errno = 25: Inappropriate ioctl for device
The following listing may appear in the
/usr/openv/netbackup/logs/bpbkarlog:bpbkar: INF - Processing /var bpbkar: ERR - get_disk_info() failed, status 13 bpbkar: ERR - tpc_get_disk_info() failed: err 13 bpbkar: ERR - bpbkar FATAL exit status = 13: file read failed bpbkar: INF - EXIT STATUS 13: file read failed
The files to back up exist on a file system that is not mounted. The file system that is specified as the snapshot source must be mounted. If the snapshot source is not mounted but the mount point is present, NetBackup may try to take a snapshot of the directory preceding the directory that was specified as the snapshot source.
For the NetBackup media server method, you may need to increase the client read timeout value. In some environments, NetBackup may require more read time than the default value allows. If the client read timeout is insufficient, the backup may fail and that causes this error.
To increase the client read timeout for all clients, in the NetBackup Administration Console, go to Host Properties > Master Servers > double-click the master server, then go to Properties > Timeouts. Then, increase the client read timeout.
On Windows, refresh the Backup, Archive, and Restore client console and retry the restore. This action refreshes the file list that is displayed in the client console and passes the correct information about the selected files.
To prevent timeouts in the VMware VDDK that cause simultaneous hotadd backups from the same VMware backup host to fail, do one of the following:
Reduce the number of hotadd backups that run simultaneously.
Increase the client-read timeout on the media server as appropriate (15 minutes or more):
In the NetBackup Administration Console, click Double-click on media server .
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.