Just found another TN: http://www.symantec.com/docs/TECH143964:
Backups intermittently fail with status 24 or 42 within a few seconds of the start of data transfer.
Error
The job details display one of two symptoms depending on the timing.
Typically the failure will appear as a status 24 because the client will report the failure to bpbrm while bptm is still getting the media ready.
10/21/2010 11:29:21 - started process bpbrm (pid=3462)
10/21/2010 11:29:29 - Error bpbrm (pid=3462) from client myclient: ERR - Cannot write to STDOUT. Errno = 32: Broken pipe
10/21/2010 11:29:25 - connecting
10/21/2010 11:29:25 - connected; connect time: 0:00:00
10/21/2010 11:29:34 - Error bptm (pid=3464) media manager terminated by parent process
10/21/2010 11:29:35 - end writing
socket write failed (24)
(....Lots of troubleshooting info.........)
Solution
This problem was resolved on multiple client hosts by stopping and restarting the inetd process via the Service Management Facility. On two of the client hosts, the entire host needed to be rebooted to resolve the problem.
The precise root cause was not available, but it is likely that at the time inetd was last started, there was an unusual and incompatible combination of TCP and/or kernel tunables in place. One or more of the setting must have been changed to a compatible value before the problem was noticed because all settings appeared normal during debugging. However, the restarted instance of inetd clearly picked up a better environment than the prior instance.
