Status Code: 14

file write failed

Status 14 errors are indicative of an issue writing to a file or a socket. This can be due to a network communication failure, or an issue with the client writing to its own file system. The best initial step for troubleshooting this error is to identify which client(s) are exhibiting the error. Then, check the NetBackup problems report and enable the necessary logging.

Status Code 14

Is ample disk space available on all of the Clients volumes?

NO

Free Disk space and retry the operation

YES

ONE

How many clients are affected?

MANY

Client Logs Logs Client

UNIX: UNIX: /usr/openv/Netbackup/logs/ bpcd /usr/openv/netbackup/logs/ bpcd /usr/openv/Netbackup/logs/ bpbkar /usr/openv/netbackup/logs/ s bpbkar Windows : Windows: <install_path>\Netbackup\logs\ bpcd <install_path>\NetBackup\logs\ bpcd <install_path>\NetBackup\logs\ bpbkar <install_path>\Netbackup\logs\ bpbkar

Master Server Logs Master Server Logs

UNIX: UNIX : /usr/openv/netbackup/logs/bprd /usr/openv/Netbackup/logs/ bprd Windows: Windows : <install_path>\NetBackup\logs\bprd <install_path>\Netbackup\logs\ bprd

Media Server Logs Media UNIX: Server Logs

UNIX : /usr/openv/netbackup/logs/ bpbrm /usr/openv/Netbackup/logs/ bpbrm Windows: Windows : <install_path>\NetBackup\logs\ bpbrm <install_path>\Netbackup\logs\bpbrm

Network communication issues. Section 1

Client Logs Client UNIX: Logs

UNIX : /usr/openv/netbackup/logs/ bpcd /usr/openv/Netbackup/logs/ bpcd /usr/openv/netbackup/logs/bpbkar /usr/openv/Netbackup/logs/ bpbkar Windows: Windows : <install_path>\NetBackup\logs\ bpcd <install_path>\Netbackup\logs\ bpcd <install_path>\NetBackup\logs\bpbkar <install_path>\Netbackup\logs\bpbkar

File system write failure. Section 2

Network communication issues. Section 1

File system write failure. Section 2

Status Code: 14 file write failed

Page 1 of 7

Table of Contents
1 Network Communication Failure............................................................................................... 3 1.1 Windows Socket Errors...................................................................................................... 3 1.1.1 10053 and 10054 errors in the WINDOWS bpbkar log.................................................3 1.1.2 10055 socket errors error in the WINDOWS bpbkar log...............................................4 1.2 Name Resolution................................................................................................................. 4 2 File System write failure............................................................................................................ 6 2.1 Full volumes....................................................................................................................... 6 2.2 OTM/VSP (Windows) ........................................................................................................ 6 2.3 NDMP Backups and Unix................................................................................................... 6 3 Links.......................................................................................................................................... 7

Status Code: 14 file write failed

Page 2 of 7

Network Communication Failure

It is important to enable the bpbkar and bpcd logs on the client whenever a Status 14 occurs. Obtaining logging from the actual client itself is the best method of determining the root cause. Many times, this root cause will be related to network communication. If it is seen that many clients are involved with the failure, the bpbrm log should be enabled on the Media Servers involved and the bprd log should be enabled on the Master Server. The main cause of Status Code 14 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. When a Status 14 error is seen, the following errors may also present themselves in text format in both UNIX and Windows logs: 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. 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). Additionally, the switch being used should be checked for any problems or errors. Available firmware updates for the switch should also be considered. The following actions are often resolutions to these network oriented errors: Update drivers for the NIC if possible (especially if using Gigabit cards). Set the NIC and switch to 100Mbps/Full rather than auto-negotiate. Replace/Inspect cabling for the NIC. Replace the NIC.

As stated in the first bullet above, always ensure that the latest NIC drivers possible are being used for the Network Adapter on the client.

1.1

Windows Socket Errors

On Windows clients in particular, socket errors from the operating system may be reported in the client bpbkar log. Search logs for the actual occurrence of the Status 14 error and observe if any of these are reported.

1.1.1 10053 and 10054 errors in the WINDOWS bpbkar log

On Windows systems, the client bpbkar log may contain a 10053 or 10054 socket error which usually indicates a NIC or Network Communication issue. Example of a 10054 error in the bpbkar log: <2> tar_base::V_vTarMsgW: FTL - tar file write error (10054) <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 14: file write failed The 10053 and 10054 are Windows socket errors. When NetBackup receives an error such as this, it is unable to continue the backup. These socket errors can be
Status Code: 14 file write failed

Page 3 of 7

translated by typing the following from the command line: net helpmsg 10053 or net helpmsg 10054 The resolutions mentioned above often address these types of socket errors.

1.1.2 10055 socket errors error in the WINDOWS bpbkar log

The 10055 error is indicating that there are not enough open data ports available to complete the requested operation. This could mean that other applications on the host are using the ports requested by NetBackup. An example follows: <2> tar_base::V_vTarMsgW: FTL - tar file write error (10055) <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 14: file write failed This socket error can be translated by typing the following from the command line: net helpmsg 10055 One possible solution to this error is described in Microsoft article 196271. The workaround that this Microsoft article provides is to raise the number of ports available to Windows by modifying the Windows Registry.

1.2 Name Resolution

Name resolution should also be analyzed if the Status 14 is seen. Using bpclntcmd bpclntcmd is a useful utility that can be run from any host. It will help determine if name resolution is working properly from NetBackups perspective. Test bpclntcmd between hosts where problems exist. This is often between the Client and Media Server. Windows command location: %install_path%\VERITAS\NetBackup\bin\ UNIX command location: /usr/openv/netbackup/bin Switches and variations:
bpclntcmd bpclntcmd bpclntcmd bpclntcmd -pn -self -hn <hostname_of_master server, media server, or client> -ip <ip_of_master server, media server, or client>

The goal of these commands is to make sure the hostname is seen the same way after each command with no errors. Below is an explanation of what each switch does: -pn - The client process on the host connects to the Master Server and asks the question "Who am I?". The second line of the output is the result. This is how the client process on the host is being seen by the Master Server. -self - Checks how the local host can be resolved. Ideally, there should be only 1 unique hostname and 1 unique IP address. -hn - Checks the given hostname and returns an IP.
Status Code: 14 file write failed

Page 4 of 7

-ip - Checks the given IP and returns a hostname. If there is any inconsistency or errors in the results of these commands, it may be necessary to add a local host entry in the operating system for the host to ensure proper name resolution. Even if name resolution is known to be good, adding local host entries on the hosts involved with the failure can assist in resolution. For example, suppose that one client is failing with Status 14 and the aforementioned resolutions have been attempted. Add a host entry on that clients host table for itself, the Media Server and the Master Server. Then, add those same entries on the Media and Master servers host tables, ensuring that all hosts involved have host entries for both themselves and each other.

Status Code: 14 file write failed

Page 5 of 7

2
2.1

File System write failure

If network communication is good between the client and the Master and Media servers, then the client may be having an issue writing to its own file system.

Full volumes
Ensure that no volumes are full on the client in question. Also, volumes may actually be more likely to approach their capacity during backup when open file backups (such as OTM and VSP) are enabled. This is because open file backups require cache file space. Free space on volumes as needed.

2.2

OTM/VSP (Windows)
Temporarily disabling OTM (Open Transaction Manager) or VSP (VERITAS Snapshot Provider) may help focus on the source of the problem. For troubleshooting purposes, it is important to understand whether the Status 14 errors stop occurring when either of these open file options are disabled. If errors only occur when open file backups are active, specific adjustments of OTM and VSP settings may be needed.

2.3

NDMP Backups and Unix

If an NDMP backup involving millions of files is attempted, it is possible that a status 14 can result. This is due to the fact that the swap partition (/tmp) or NetBackup mount point on the master server is not large enough to accommodate the inode map file (inodemap.<pid>) that is being constructed during the NDMP backup. This file resides in /tmp or /usr/openv/netbackup/BPFSMAP_TMPDIR . It is possible to calculate the potential size (in bytes) of the inode map file that will be written by multiplying 60 * the number of files that will be backed up. With this information, it is possible to take one of two plans of action to remedy the error: 1. Run df k to look for full partitions. When NetBackup is stopped on the master, ensure that the temp directory is empty:
/usr/openv/netbackup/BPFSMAP_TMPDIR

2. Create the symbolic link BPFSMAP_TMPDIR in /usr/openv/netbackup to point to a file partition that is large enough to accommodate the inode map file.

Status Code: 14 file write failed

Page 6 of 7

Links
Click here to Search for other documents on Status Code 14
Also, you may click below to perform a search on the following relevant items: Status Code 14 file write failed

Status Code: 14 file write failed

Page 7 of 7