Status Code: 13 File read failed

Status Code: 13

File read failed

A Status 13 will occur due to network issues on the master or client.  This error indicates a read operation of a file or socket failed.  This can also occur for Flash Backup or Advanced Client backups.

Table of Contents

1 Flash Backup and the Advanced Client options. 3

1.1    Offhost backup method or Third-Party Copy Device. 3

1.2    Snapshot mount point is present but not mounted. 3

2 Network issues. 4

3 Search. 4

1  Flash Backup and the Advanced Client options

For a Status 13 encountered on a Flash Backup, or any policy backup using the Advanced Client options it is recommended to check the OS logs (messages or syslog).

Example UNIX /var/adm/messages log showing a full snapshot partition.

unix: WARNING: sn_alloccache: cach/dev/rdsk/c0t2d0s3 full – all snaps using this cache are now unusable.

This indicates that the cache partition is not large enough. If possible, increase the size of the cache partition. 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.

Status code 13 may appear in the bpbkar log file for Flash Backup and Advanced client backups and can indicate the following:

1.1    Offhost backup method or Third-Party Copy Device

When using the offhost backup, the disk containing the client files must be a SCSI or Fibre Channel device.  A status 13 can occur if the files to back up reside on an IDE drive as opposed to SCSI, and the offhost backup method was set to either NetBackup Media Server or Third-Party Copy Device.   These two options are not supported on IDE drives.  If the disk is an IDE drive, you may see the following:

Example from the UNIX /usr/openv/netbackup/logs/online_util/log.<date> file:

get_disk_info: FTL - /var/tmp/caa026fEU disk_inquiry failed. Errno = 25: Inappropriate ioctl for device

Example error in the UNIX /usr/openv/netbackup/logs/bpbkar/log.<date> file:

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

1.2    Snapshot mount point is present but not mounted

A Status 13 can occur when the files to back up exist on a file system that is not mounted. The file system 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 above the directory that was specified as the snapshot source.

If the above fails to resolve the issue please gather the following logs at verbosity 5 from when an error occurs and open a support call:

Logs to collect from the Master server:

·         The UNIX /usr/openv/netbackup/logs/bprd/log.<date> file.

Logs to collect from the Media Server:

·         The UNIX /usr/openv/netbackup/logs/bptm/log.<date> file.

·         The UNIX /usr/openv/netbackup/logs/bpbrm/log.<date> file.

Logs to collect from the Client:

·         The UNIX /usr/openv/netbackup/logs/bpbkar/log.<date> file.

·         The UNIX /usr/openv/netbackup/logs/bpfis/log.<date> file.

·         The UNIX /usr/openv/netbackup/logs/online_util/log.<date> file.

2 Network issues

The main cause of status code 13 generally stems from the network interface card (NIC) on the client.  It is possible that other components of the network can also play a part in the generation of this error code.

It is strongly suggested to review the settings of the network path used to get from the client to the media server. Ensure that all ports, cards and switches are set to the same media and transport type (Example: 100base Full Duplex).

On the Windows clients network errors are seen as 10054 and 10053 errors in the bpbkar logs. These errors may also present themselves in text format in both UNIX and Windows logs as:

·         A connection was reset by the remote Host

·         Software caused a connection to abort

These messages indicate that a socket was closed based on a network stack issue.

Example error from the UNIX /usr/openv/netbackup/logs/bptm/log.<date> file:

<16> fill_buffer: socket operation failed - 10054 (at ..\child.c.1091)

<16> fill_buffer: unable to perform read from client socket, connection may have been broken

Corresponding example from the UNIX /usr/openv/netbackup/logs/bpbrm/log.<date> file:

<16> bpbrm readline: socket read failed, An existing connection was forcibly closed by the remote host. (10054)

<2> inform_client_of_status: INF - Server status = 13

<2> put_long: (11) network write() error: An existing connection was forcibly closed by the remote host. ; socket = 496

<16> inform_client_of_status: could not send server status message

Example error from the Windows <install_path>\NetBackup\logs\bpbkar\<date>.LOG file:

<16> dtcp_write: TCP - failure: send socket (1968) (TCP 10054: Connection reset by peer)
<16> dtcp_write: TCP - failure: attempted to send 32768 bytes