Cluster system state backup failed
Hi,
I have an issue with cluster node system state backup. It's win2003 cluster and I backup "Shadow Copy components:\" On Active node backup starts, backups 500 mb and it fails with errors:
2/11/2007 6:13:02 AM - begin writing
2/11/2007 6:14:11 AM - Error bpdm(pid=4624) socket operation failed - 10054 (at child.c.1172)
2/11/2007 6:14:12 AM - Error bpbrm(pid=4644) socket read failed, An existing connection was forcibly closed by the remote host. (10054)
2/11/2007 6:14:13 AM - Error bpdm(pid=4624) unable to perform read from client socket, connection may have been broken
2/11/2007 6:14:15 AM - Error bpbrm(pid=4644) could not send server status message
2/11/2007 6:14:25 AM - end writing; write time: 00:01:23
file read failed(13)
What I could do to correct this issue?
Thanks!
Comments
win 2003 and netbackup 6 have problems with shadow copy component.
Should I backup "system state" instead?
I ahd that problem on a cluster server and I disabled VSP on the client properties as directed by Symantec and that fixed it for me
This is a communication error and I do not think it has anything to do with Shadow copy or the policy.
The last time I saw this error, it was because someone installed NetBackup v5.1 client without any of the maintenance packs. This happens everytime when we do that and installing the latest maintenance pack 5 or 6 should correct the issue.
If that is not the issue, then check out the BPCD logs on the client side as the client is the one that is closing your connection on your server.
Hope this helps,
Joe
- Joe "Saving the bits each and every day"
This could be related to Shadow Copy and I think Shadow Copy is the only way to backup system state in Win 2003 so there is no way around it.
I had this problem at 5.1 mp4 and upgraded the client to mp5 and this fixed the problem.
Also make sure ALL volumes have at least a minimum of free space.
Would you like to reply?
Login or Register to post your comment.