β08-22-2012 01:41 PM
Hi again.
So, I am trying to do a cross restore, but keep getting this error message. I have tried a bunch of things, yet nothing seems to work.
Server: Windows 2008 R2, Netbackup 7.1.0.4
Source client: windows 2003, netbackup 7.1.0.4 client. Physical server.
Destination client: Windows 2008 R2, Netbackup 7.1.0.4. Virtual server, with VMware. Has a 1tb lun assigned.
This is a file server I am trying to virtualize, so I want to move all my data from the source to the destination.
I tried restoring files from the source to the source, and the destination, to the destination. No problem there.
But each time I try to go from Source to Destination, I keep getting the same error:
****************************************************************
So now I am stuck, tried opening the firewall, putting everything in the host file, tried bptestbpcd, bpclntcmd, bpcoverage, bpgetconfig, and I can see every single thing, yet, I can not do a restore. The backups work ok.
What might I have missed? Please assist.
Thanks.
β08-22-2012 01:46 PM
oh, one more thing.
The server is in one domain, and both clients are on another domain.
There is a trust relashinship between the AD, but I donΒ΄t know if that could cause the problem.
β08-23-2012 12:14 AM
β08-23-2012 05:49 AM
Here are the logs Marianne.
I noticed something strange on the Tar log, a line that goes:
β08-23-2012 07:06 AM
09:26:41.934 [7672.1548] <16> bpbrm readline: socket read failed, An existing connection was forcibly closed by the remote host. (10054)
The exchange message is just as it does its usual checks before doing anything so dont worry about that one.
The above line is the issue - the network connection gets closed
Also the tar log just seems to stop as if it crashes or something blocks it
Any Anti-Virus or Access Protection or firewall that could slam the door shut when you try to write files across the link to this server?
Connection seems OK but then everything stops - check the Application event log on the destination client to see if there are any clues
β08-23-2012 07:10 AM
Seems "something" terminated the network connection before data could be transferred.
bpbrm started bptm (media manager) process at 09:24:29 and established connection to client at 09:24:31
Client (bpcd) confirmed connection at 09:24:35 and started tar process.
Last entry in tar log is at 09:24:36 while bptm was still loading tape and positioning it. (no errors in tar log - message that you saw is not an error: <2> is notice/debug info)
bptm finished positioning at 09:26:37 and started reading at 09:26:39
Here bptm reports the 'boken connection':
09:26:41.934 [7404.7552] <16> write_to_out: cannot write data to socket, 10054
We cannot say why connection was broken - just that it happened.
tar was ready to receive data, bptm tried to send data.
Any possibility of monitoring network connection between client and media server?
Any errors in Event Viewer on client?
Any errors/messages/logs on firewall between media server and client?
β08-23-2012 07:22 AM
but that is the strange thing.
I CAN do a restore from DESTINATION to DESTINATION, and from SOURCE to SOURCE, what I canΒ΄t do is from SOURCE to DESTINATION, so I assume it must be something related with the cross restore.
some permits that the source has and the destination doesnΒ΄t, something like that.
There was a firewall but it was deactivated, and also the windows firewall though it is off, I set an inbound and outboud rule to permit any.
β08-23-2012 07:31 AM
Many Anti-Virus programs are set to trust local files by default - but may not trust cross domain files and may try to block them
If you have AV turned on the try turning it off (including all of it add-ons) whilst the restore runs
β08-23-2012 07:34 AM
Anything in Event Viewer logs? Check all of them - Application, Security...
All we know for sure is that "something" broke the connection.
Because NBU did not terminate the connection, all we can do is REPORT the broken connection.