This question may have been posed before but I'm not sure I saw the response:

My nightly backup schedule kicks off at 1900 and is usually completed right 
around 0100 the next day. Occasionally, when I review my queues in the morning, 
I see a backup job still running. As I drill down I notice that the  backup 
actually ended the write process around 2200 but the job never ended. KILL 
within the NetBackup GUI has no effect so I end up issuing a KILL against the 
bpbrm process that is still running. This kills the task and gives the error 
indicating a socket write fail. I guess the good news is that the backup 
actually shows up in the list when I attempt to do a restore so all is not 
lost. It's just annoying. Anybody else ever seen this and what do you do about 
it?

Regards,


Dennis F. Dwyer
Enterprise Storage Manager
Tampa Electric Company

(813) 225-5181  - Voice
(813) 275-3599  - FAX

Visit our corporate website at www.tecoenergy.com