I'm only just getting to read your reply, but I think Sub had a good
point - our environment is we start with our backup tapes and bare metal
and build a disaster recovery site, at Sunguard's DR facility. At the
end of the test the boxes all get blanked again. So we're not bringing
the original boxes back up and we're not planning to restore back from
the DR site. 

(In a real disaster, I'd plan to run at the site until we could return
to our location, then I'd rebuild servers from scratch using the backup
tapes from the DR site.)

-- 
be - MOS

Make me look like LINDA RONSTADT again!!
 

> -----Original Message-----
> From: Chris Scharff [mailto:[EMAIL PROTECTED] 
> Sent: Friday, January 14, 2005 4:57 PM
> To: Exchange Discussions
> Subject: RE: Testing Disaster Recovery
> 
> In this instance it's 'testing' so the real server is going 
> to want to come back online eventually. So renaming the 
> source server in AD before bringing the new server online 
> prevents Bill from having to go through the same steps he 
> didn't want to have to do with the target server, but with 
> your suggestion he'd do them on failback to the original server. 
> 
> For many of our customers we build their target DR server 
> using the methods Bill described pre-disaster than then 
> rename the box to server-dr. In the event of a disaster we 
> rename/reboot/change in AD to computer account for server to 
> server-rn and then rename server-dr to server. In this way 
> failback is completed by simply reversing the steps.
> Not as important in a 'real' disaster where hardware is dead 
> or glowing, but for testing and planning purposes 
> significantly streamlines the process. Now overall our 
> process is a little different because the work is done around 
> our OneSwitch product which is a replication technology 
> rather than restoring from tape, but for this part of the 
> process the steps are not too divergent. 
> 
> 
> 
> --
> Chris Scharff
> Messaging Services Architect
> MessageOne
> [o] 512.652.4500 x244
> [m] 512.560.2984
> [f] 512.652.4504
>  
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] On 
> > Behalf Of subsoniq
> > Posted At: Friday, January 14, 2005 3:33 PM
> > Posted To: swynk
> > Conversation: Testing Disaster Recovery
> > Subject: Re: Testing Disaster Recovery
> > 
> > 
> > In instances like this I've always reset the computer account 
> > of the dead server, and when I build the new server I give it 
> > the same computer name before joining it to the domain, this 
> > works for me.
> > 
> > 
> > On Fri, 14 Jan 2005 15:16:57 -0600, Chris Scharff 
> > <[EMAIL PROTECTED]> wrote:
> > > You can rename the computer account in AD even if the 
> > computer is no 
> > > longer on the network IIRC. Now you need to be careful in how you 
> > > bring the original server back online in your 'test 
> > disaster' but it's 
> > > just about getting the steps right.
> > > 
> > > We spent a bunch of time coding various permutations of 
> pear shaped 
> > > scenarios requiring for DR, but in a scripted test scenario 
> > it's much 
> > > more straightforward.
> > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED] On 
> > Behalf Of 
> > > > East, Bill Posted At: Friday, January 14, 2005 2:54 PM 
> Posted To: 
> > > > swynk
> > > > Conversation: Testing Disaster Recovery
> > > > Subject: RE: Testing Disaster Recovery
> > > >
> > > >
> > > > We did not. In this scenario the original machine was in 
> > the middle 
> > > > of a smoking, slightly radioactive crater.
> > > >
> > > > > -----Original Message-----
> > > > > From: Chris Scharff [mailto:[EMAIL PROTECTED]
> > > > > Sent: Friday, January 14, 2005 2:50 PM
> > > > > To: Exchange Discussions
> > > > > Subject: RE: Testing Disaster Recovery
> > > > >
> > > > > Did you rename the original machine (the one being replaced
> > > > in this DR
> > > > > scenario)?
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: [EMAIL PROTECTED]
> > > > > > [mailto:[EMAIL PROTECTED] On
> > > > Behalf Of
> > > > > > East, Bill Posted At: Friday, January 14, 2005 1:12 
> > PM Posted To:
> > > > > > swynk
> > > > > > Conversation: Testing Disaster Recovery
> > > > > > Subject: Testing Disaster Recovery
> > > > > >
> > > > > >
> > > > > > We just completed our annual DR testing. This was the
> > > > first year in
> > > > > > which we managed to get all of the servers up and 
> > running, yay us.
> > > > > >
> > > > > > One of the things that led to this outcome was the
> > > > installation of
> > > > > > Exchange 2000 SP3 (not Enterprise) with the 
> /disasterrecovery 
> > > > > > switch. In short, we:
> > > > > > * Built a new server with the old server's name, service
> > > > packed and
> > > > > > install the ArghServe client
> > > > > > * Ran exchange setup with the aforementioned switch
> > > > > > * Ran ArghServe to put the databases back.
> > [snip]
> > 
> 
> _________________________________________________________________
> List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
> Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
> To subscribe: http://e-newsletters.internet.com/discussionlists.html/
> To unsubscribe send a blank email to 
> [EMAIL PROTECTED]
> Exchange List admin:    [EMAIL PROTECTED]
> To unsubscribe via postal mail, please contact us at:
> Jupitermedia Corp.
> Attn: Discussion List Management
> 475 Park Avenue South
> New York, NY 10016
> 
> Please include the email address which you have been contacted with.
> 
> 
> 


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to [EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.

Reply via email to