Status 14 - file write failed

[kiger]

I am having problems with FULL backups for a remote site. The remote site is connected with a T1, and we are backing up the remote server to defined disk storage. Cummulative backups are working fine. The full backup will run anywhere from 5 minutes to 7 hours before failing with a status 14 - file write failed. We have several remote sites that we are backing up to our data center and all the others work fine. Anyone have any ideas??

 

[PGPhantom]

14 errors are nearly always network related. Make sure you are using full duplex and not auto negotiate - This means on the NICs and the router\switch. Most issues can be resolved by doing this step.

 

[kiger]

We have already done this, our network guys have verified that the switch is set to 100/full. One thing that I have found out, OTM was installed and at one time enabled on this server. I went ahead and uninstalled and installed Veritas back on it (just did this today). I am scheduling a full backup for tonight, so hopefully (but not expecting) it will work.

 

[kiger]

Okay, now the cummulative incremental is receiving status code 14...job ran for 6 1/2 minutes and cancelled with a 14. Double checked the server and the NIC card is set at 100/Full. Any ideas??

 

[PGPhantom]

What NIC's are you using on the media server and client? Can you define flow control as that should be se to RX/TX.

I could guess on a lot of causes but ... Can you enable bpbrm logging on the media server, kick off a backup and then check what is happening in the log - This will indicate communications issues etc.

 

[sgoldsmith]

We have seen this before when backups are travelling over LAN's that have other traffic on them (for example User data traffic as well as backup data traffic).

The other time we have seen this is when traffic is being routed over serveral subnets or VLAN's.

Have a look at the network topology and see if either of these are the case?