Hi,
I am guessing you have already run the nsrck -L7 more than once
when you found that the first attempt had failed or was stuck for some
reason. The easiest way out of this would be a quick restart of the
NetWorker services. IN case you do not wanto do this, see if there are
any "ansrd" services running? If yes, then kill them and try again.
Also, the first thing you make sure is that there is a drive available
for recovery.
HTH,
Rovin D'Souza (EMC Proven NetWorker specialist)
rovinabi AT gmail DOT com
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Michael Leone
Sent: Monday, August 02, 2010 8:33 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] nsrck -L7 always showing "Server busy" ..
As some may remember, I am in the process of doing a D/R recovery of my
backup server from a 2 year old bootstrap tape, since my current NW
server
doesn't have any history before that time, and all my clientIDs changed
at
that time (due to me not recovering the server correctly at that time).
And I need to recover something from a client from before that time. So
what I have done:
Set up a Windows server, with the same name as the old server
(it only has a single stand-alone tape drive, as opposed to the library
it
had back then)
Physically unplugged it from the LAN
Added entries to the hosts file (127.0.0.1 as the IP of the server, so
that a "ping servername" returns a success)
Installed NW 7.4.0
Added the single tape drive
Did an mmrecov
Replaced the "res" directory with the one the mmrecov created
Started NW 7.4.0
Deleted the library, and added the single tape drive (\\.\Tape1)
Set all groups to disabled, so they wouldn't autostart
Set all storage node devices (AFTD devices, in my case) to disabled, so
it
wouldn't constantly complain that it couldn't communicate with the
storage
nodes.
So now I am ready to recover the client index that I need. But when I do
a
nsrck -L7 admncry001
It says that it is recovering the client index, but then eventually
comes
back with a "server busy; retying in 30 seconds" message.
So what step did I miss? I see nothing in the log, that indicates why
the
nsrck -L7 isn't working, and there is no parameter in nsrck to specify
the
device. All the licenses show that they are still within the grace
period.
--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
