Showing results for 
Search instead for 
Did you mean: 

Backup fail with status code 13, 42 after writing some data

Level 4

Hi All


I am facing one issue from long time.we have one master server in solaris 10 and NBU version 6.5.6 and media server OS version 6.5.3 . i am trying to backup windows 2003 client.once i refire backup backup come active state and writing some data after that it got failed sometime with error 13 and sometime 42c and 40.i check all setting network connectivity is fine.i check with command bpclntcmd from master, media and client all are working fine.Please help.




Level 6

Do these happen at times of high network load?

Possible faulty network components? (e.g. loose cables, dodgy NICs).

The fact that the backup works initially confirms what you are saying, in that there is no connectivity issues as far as the software is concerned so maybe you need to concentrate on the physical aspects of connectivity?

Level 4

if there is no connectivity then backup got failed with status code 41.but here it write some data after that it fails

Level 6


"...The following things can all help prevent Status 13 errors:

  • Ensure that the latest service packs for all products and components (SQL, Exchange, Notes, etc.) have been installed.
  • Ensure that all the network settings throughout the environment (NICs, hubs, switches, routers, etc.) are set to full duplex, not half duplex
  • Increase the timeout settings on the NIC, if available.
  • Try a different NIC, if available.
  • If NIC teaming is implemented, deactivate for testing purposes.  Refer to Microsoft Knowledge Base Q Article 254101.;en-us;254101



In-depth Troubleshooting Guide for Exit Status Code 13 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 6.0

Level 4

thanks alot

Level 6

E/Cs 40 and 42 (there are quite a few, I just looked!)

Just follow the links in the following Status Code Chart:

Level 5

basic network troubleshooting can help identify the problem, mundane things like speed/duplex, port errors, network interface driver related issues, high i/o at the time of the backup (or low traffic priority), number of network segments backup is transversing (you're not doing something silly like trying to backup over a VPN, WAN or tunnel of some sort).


All of these things may be the cause of your loss of connectivity.

Level 4

We had similar issues to these and it turned out that the media servers doing the backup were on ports that were oversubscribed on the switch.   The networking guys put us on a cisco blade that shared the bandwidth among multiple ports.  Once the backups were going and we started pumping data, there were a lot of pause errors and packet drops on the switch.  Once we moved our media servers to a cisco blade that didn't share an ASIC with multiple ports (each port had its own ASIC giving us the full rate), these errors went away.