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. The only funny thing that happened was after we did the restore. We rebooted and the server refused to go through the Windows startup. We identified this as a SID problem, removed the server from the DC, took it off the network and put it into Workgroup mode, then put it back on the network and rejoined it to the domain. At that point we had to re-add it to about half a dozen domain groups. So my question would be, what steps could we have taken to avoid this little dance, if any? It would save us an hour or so in our DR plan if we could. -- be - MOS Fry: I must be a robot. Why else would human women refuse to date me? Leela: Oh, lots of reasons. _________________________________________________________________ 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.
