It actually only worked once. We have this problem on 3 of our servers and they all have a huge amount of data and wondering if that is problem. It dies very quickly. The dailies run with no problem, just dies on the fulls, so once again wondering if it can't handle the amount of data? No problem with other servers running the same OS, but than again no as much data on them. If we break up the data meaning not backing up the entire c:\ it will work, just a pain to do it that way, have to check for new directories added.
I will look into the chimney stuff, saw that in another post and was curious what that was all about, will read your documentation. Thanks for suggestions and will respond once I find out.
I was wondering why only full backup was failing . if the issue is really the cable, even incr should have show network related problems.
we too have error codes 24. still trying to get solution.
We had this kind of issues on the Netbackup server side and when verified the Ethernet card statistics we found huge number of CRC errors and Later we completely relaced the Cables and also connection to switch port and later it went fine without any issues.
These socket write failed issues are generally occur when there is any network related issues. We need monitor network traffic between the Netbackup server/client and switch port.