Error 13 when backingup the Shadow Copy Components:\
Updated: 22 May 2010 | 6 comments
Running Net-Backup 5.1 MP4
I have 2 servers out of 300 that fail with a status code 13, "file read failed(13)" when backing up "Shadow Copy Components:\"
rror bpbrm(pid=3552) socket read failed, An existing connection was forcibly closed by the remote host. (10054)
02/08/07 15:43:23 - Error bptm(pid=5788) socket operation failed - 10054 (at child.c.1135)
02/08/07 15:43:24 - Error bptm(pid=5788) unable to perform read from client socket, connection may have been broken
02/08/07 15:43:25 - end writing; write time: 00:00:05
file read failed(13)
02/08/07 15:43:23 - Error bptm(pid=5788) socket operation failed - 10054 (at child.c.1135)
02/08/07 15:43:24 - Error bptm(pid=5788) unable to perform read from client socket, connection may have been broken
02/08/07 15:43:25 - end writing; write time: 00:00:05
file read failed(13)
The other drive letters (C:, D:) backup fine on the server.
Any Idea's
discussion Filed Under:
Comments
we have the same problem
we have the same problem here. 50% of our servers dont backup the VSS or VSP. The bpfis application just quits. 5.1mp6 tried and failed...
Any ideas or solutions for this are welcome...
What O/S on these servers?
What O/S on these servers? Have you checked that it supported under 5.1?
Also - can you backup Shadow Copy Components to disk using Ntbackup? If that fails as well. it's a Microsoft issue.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
The OS is W2k3 sp1. Versions
The OS is W2k3 sp1. Versions of NBU masters are 5.1 mp5 or mp6.
Ntbackup of the VSS/system state works fine.
What we have is error 13's and 42s, bpfis exe crashes everytime. All the logs talk about a loss of socket communication.
2009-09-09 06:14:15 - Error bpbrm(pid=5988) socket read failed, An existing connection was forcibly closed by the remote host. (10054)
2009-09-09 06:14:16 - Error bptm(pid=616) socket operation failed - 10054 (at child.c.1135)
2009-09-09 06:14:17 - Error bptm(pid=616) unable to perform read from client socket, connection may have been broken
2009-09-09 06:17:29 - end writing; write time: 00:03:25
Like mentioned above, all the drives do get their backup correctly. Only the VSS or the VSP fails of the system state fails.
I have a server without AV that does this so that's rulled out. Firewalls are also excluded since the vnetd works fine elsewhere.
I'll try with another master server to see if the issue is there or not...
the test master server works
the test master server works fine and i can't find a difference in settings... :(
Made a test on the master
Made a test on the master that doesn't work. Created a new policy and now the VSS work! But not on the old policy... weird...
Ok First check if any of the
Ok
First check if any of the hard drives on the client is full. Free up some space if this is the case.
Check messages that regard to various regisry problems in the system log on the client. Registry on the client may be just broken in some way.
Try to reboot the client.
Would you like to reply?
Login or Register to post your comment.