Just an FYI.
ASR apparently *requires* DNS resolution. Even if the server and the client
have no dns configured when they are backed up.
I tried both a full backup/ASR restore when there was and wasn't a DNS
server involved and the only way ASR would work was under the DNS
configuration.
I don't really understand the logic here as now an ASR recovery of a DNS
server is impossible.
Just something to add to your checklist for ASR recovery...
--Shawn
----- Original Message -----
From: "Shawn Cox" <shawn.cox AT PCCA DOT COM>
To: <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
Sent: Monday, December 05, 2005 8:52 AM
Subject: [Networker] Windows ASR recovery
So what's the latest word on ASR recoveries in the Window's to Windows
world? Going through the archives of NETWORKER-L this weekend and there
seems to be lots of bugs open and unsuccessful ASR recoveries. I am able
to get the mini-client up and responding to pings, but the mini-client
cannot initiate a connection with the backup server that is sitting right
next to it on the same subnet and switch. All I get is a message from the
mini-client stating "waiting for the backup server to come online..."
--Shawn
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
wit 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
wit 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
| 