Unsolved
This post is more than 5 years old
1 Rookie
•
34 Posts
0
2755
January 27th, 2011 17:00
Failed to initialize recover
Recovery takes a long time and shows me this warning
73094:recover: Warning: Failed to initialize recover job with nsrjobd: Connection timed out
AllanW1
334 Posts
0
January 28th, 2011 06:00
hmmm. It sounds like the recover job had issues starting in the first place, not that recover itself was slow. This would need more investigation and I'd open a support case for it.
David_Hampson_90e289
2 Intern
•
243 Posts
0
February 1st, 2011 01:00
I'd agree with Allan on this; unless you have received some of the restore data at the client (which the error message seems to contradict) it looks like the restore is not beginning. Were you able to browse the backups from the client? Have you tried a directed restore of the data to a different client?
Michael891
1 Rookie
•
34 Posts
0
February 2nd, 2011 10:00
Hi David,
In either case you mention the situation is the same. I see that recovery takes at least 5 minutes to respond after alarm message(73094:recover: Warning: Failed to initialize recover job with nsrjobd: Connection timed out) but recovery is performed successfully.
Greetings
David_Hampson_90e289
2 Intern
•
243 Posts
0
February 3rd, 2011 01:00
Okay, so the data is being recovered successfully, but Networker is flagging an error. Is there anything that may affect this restore such as the client being on a slow link or behind a firewall?
Michael891
1 Rookie
•
34 Posts
0
February 3rd, 2011 17:00
Hello David,
The server has no restrictions or firewall. I perform the test in a small laboratory where I have no restriction and has the same warning.It seems that this error is presenting only on UNIX systems.