Professional Documents
Culture Documents
Status Code 13
Yes
No
No
One
Many
Upgrade to the latest NIC drivers on the client . Enable Client logging : UNIX: /usr/openv/netbackup /logs/bpbkar Windows <install_path>\VERITAS : \NetBackup\logs\bpbkar
Upgrade to the latest NIC drivers on the master /media server . Enable Media server logging : UNIX: /usr/openv/netbackup /logs/bpbrm Windows <install_path>\VERITAS : \NetBackup \logs\bpbrm Enable Client logging : UNIX: /usr/openv/netbackup /logs/bpbkar Windows <install_path>\VERITAS : \NetBackup \logs\bpbkar
Table of Contents
Status Code: 13 file read failed Page 1 of 4
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
Page 2 of 4
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:
Page 3 of 4
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
3 Search
Click here to Search other documents on Status 13
Also, you may click below to perform a search on the following relevant items:
Page 4 of 4