This post is more than 5 years old
217 Posts
0
5818
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
dramjass
151 Posts
1
July 9th, 2012 08:00
You can see if the Data Domain is the culprit here. Monitor the logging on the DD via a Putty console to see if it adds any value: log watch debug/ddfs.info
If it returns any 5xxx messages, then return them back in this thread.
Also, you may find it beneficial to upgrade to 7.6.3.7 as there have been several DD Boost fixes implemented since 7.6.2.7.
The same holds true for the DDOS (system show version). The latest release, 5.1.1.0, also contains updates to DD Boost on the DD side.
Another way to debug on the DD Boost side, is to enable debugging against the nsrmmd process. To do so:
- Disable the respective devices (RW & RO) for the device you are recovering from.
- Use the following comand on the NetWorker server: dbgcommand -p debug =4
- Enable the same device you disabled above. When nsrd spawn nsrmmd, it will put it into debug mode.
- Attempt the same recovery and it should log more information about DD Boost module events in the daemon.raw on the SN.
NOTE: 7.6.3.x provide the ability to enable debugging on a specific device via Diagnostic Mode.
Let me know if the above adds any value to determining what is occurring here.