Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
Solved!
Go to SolutionC
Castromotorbox
2 Intern
•
217 Posts
0
5973
July 3rd, 2012 02:00
Timeout during Recovery with DataDomain
Hi,
We are experiencing a curious problem:
For some client, when we start a recover Job (from the client itself or directed restore, doesn't matter).
In the console, we see the job running, but he still waiting for some 40-50 minute...
These client are Linux or Windows, There is no Network différence between them.
Backup works perfectly and we are using DDBoost.
Here is a log of one of this timeout restore, its a windows machine.
In the middle of the log (who is pretty long, sorry, level 5), I put the indication of the Timeout.
Thanks for your help.
Greg
1 Attachment
Timed_out_Restore.txt
Timed_out_Restore.txt
CarlosRojas
1 Rookie
•
1693 Posts
2652
0
Posted July 3rd, 2012 02:00
Hi Gregoire,
What is the NetWorker version on client and server?
I found this KB that could be useful:
https://solutions.emc.com/emcsolutionview.asp?id=esg108478
Thank you.
Carlos.
Castromotorbox
2 Intern
•
217 Posts
2652
0
Posted July 3rd, 2012 02:00
Hi Carlos,
So Networker server is a windows machine with 7.6.2 build 697.
Client is a Windows machine too with Networker client 7.6.2.1 build 638
I try these restore with many sort of file, and i use the - noforce option to not write recovered file on the client machine.
Thanks for your help.
Greg
CarlosRojas
1 Rookie
•
1693 Posts
2652
0
Posted July 3rd, 2012 02:00
Hi,
Forgot to mention, did you try to restore any other files?
Recover daemon.raw should fail and I wouldn't suggest you to test that type of restore, recover production files of NetWorker.
Thank you.
Carlos.
CarlosRojas
1 Rookie
•
1693 Posts
2652
0
Posted July 3rd, 2012 03:00
Hi Greg,
Could you please try to upgrade the clients to the same build as NetWorekr server and try again?
The data was backed up using NetWorker server devices or any storage node or DFA?
Thank you.
Carlos.
Castromotorbox
2 Intern
•
217 Posts
2660
0
Posted July 3rd, 2012 04:00
Hi Carlos,
Ok I try to update my client in build 697. Server, Storage Node and client have the same version.
Now for this client it work!!!
I'm gonna try with the other one and give you a feedback as soon as possible.
Thanks.
Greg
CarlosRojas
1 Rookie
•
1693 Posts
2652
1
Posted July 3rd, 2012 04:00
Hi Greg,
Try to have NW server, storage node and client in same version.
Did you configure the client to restore through storage node or directly from server?
Thank you.
Carlos,
Castromotorbox
2 Intern
•
217 Posts
2652
0
Posted July 3rd, 2012 04:00
Hi,
We make the backup on a DataDomain device thru a Storage Node.
I upgrade the client and try again. give you som feedback soon.
Thanks
Greg
CarlosRojas
1 Rookie
•
1693 Posts
2660
0
Posted July 3rd, 2012 05:00
Hi Greg,
Good to hear that.
Will wait for your feedback, anyway did you restore the same files or something else?
And in the previous attempts, did the files get restored despite the timeout or not?
Thank you.
Carlos.
Castromotorbox
2 Intern
•
217 Posts
2660
0
Posted July 3rd, 2012 05:00
Hi,
I restore the same file. But with noforce option. By the previous attempt, the restore was successfull (with only skipped restored file)
Greg
Castromotorbox
2 Intern
•
217 Posts
3279
1
Posted August 27th, 2012 04:00
Hi,
I found the reason of this time out. DFA (Direct File Access)... I guess than after version 7.6.2 (?) the client try to go direct to DataDomain by default. What he couldn't do in our environnment. We have to specify, with an empty file named "nodirectfile" withou extention in a debug folder in nsr folder, that this client must NOT going directly on the backup device.
Thanks for your help.
Greg