I am in a windows environment. After installing networker 7.5.2.4 on the 
DR server with the same name and IP as the original, I perform an MMRecov 
and go through the steps of changing the res.r to res. I have included on 
this system a host file with all the clients and there respective ip 
addresses. 

After all this is complete, I then go through the steps of starting the 
services from the command line. net start nsrexecd(2 seconds), net start 
nsrd(20 minutes) and net start gstd(2 seconds). If I perform these steps 
in production the nsrd only takes about 1 minute. 

In the past we have tried starting the nsrd in debug mode and noticed that 
it tries to resolve each client. This is not feasible in the cold site 
because the domain controller is not avaiable until I restore it.

Has anyone else tested this with any success. I have been to DR about 6 
times in the last three years and each time Networker takes up most of the 
test. 

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