I didn't read this in great detail because my eyes got tired, but it looks like you have the general idea. There's no reason the DC and recovery server can't be one and the same.
Ed Crowley MCSE+I MVP "There are seldom good technological solutions to behavioral problems." -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Russell L. Hansen Sent: Tuesday, April 06, 2004 7:40 PM To: Exchange Discussions Subject: Procedures for creating an Exchange 2000 Recovery Server A friend of mine recently asked me how to go about setting up a recovery server. I've done this before, but it's been awhile and I wanted a memory check. The procedure below (unless I'm mistaken) will work on dissimilar hardware and will allow the recovery server to be moved to the production network if the production server fails. (Of course any modifications made in the production network in AD or exchange will have to be manually duplicated to bring it up to date.) This uses what I call a transition server and the recovery server. ------------------------------------------------------------------------ --- 0. Complete an online backup of the production Exchange Server. 1. Install windows 2000 server with DNS service on the Transition Server and make it a member of the production domain. 2. Run DCPROMO.EXE on this server to promote it to Domain Controller. 3. Setup an Active Directory integrated DNS zone for the Forest's root domain. 4. Ensure the TCP/IP settings are configured so that it uses itself for DNS name resolution. 5. Ensure all replication tasks are complete. 6. Remove the Transition Server from the production network and place in an isolated network. 7. On the production network, remove the Transition Server domain controller object from Active Directory. (This can be done with NTDSUTIL and ADSIEDIT.) 8. In Active Directory Sites and Services, ensure that all replication connection objects are removed. 9. Establish the Transition Server as a global catalog. 10. On the Transition Server, seize the FSMO roles. (This can be done with NTDSUTIL.) 11. On the Transition Server, remove the production domain controller object from Active Directory. (This can be done with NTDSUTIL and ADSIEDIT.) 12. Ensure all replication connection objects are removed from Active Directory Sites and Services. 13. Remove DNS references to the production network domain controller. 14. Install windows 2000 server with DNS service on the Recovery Server and make it a member of the isolated network's domain. (Use the same server name as the production Exchange Server, ensure partition drive letters match the production server, and partition sizes are sufficient to hold the database files.) 15. Run DCPROMO.EXE on this Recovery Server to make it a domain controller in the isolated network's domain. 16. Establish an Active Directory integrated DNS zone in DNS. 17. Ensure the TCP/IP settings are configured so that it uses itself for DNS name resolution. 18. Configure the Recovery Server to be a global catalog server. 19. Transfer (not seize) all FSMO roles to the Recovery Server. 20. Remove the global catalog service from the Transition Server. 21. Run DCPROMO.EXE a second time on the Transition Server to demote it to just a member server. 22. Shut down and retire the Transition Server. 23. On the Recovery Server, remove the Transition Server object from Active Directory Users and Computers. 24. On the Recovery Server, using ADSIEdit.exe, remove the Exchange schema modifications from Active Directory. 25. Install Exchange 2000 Server on the Recovery Server. 26. Apply service packs and hot fixes to match condition of production server. 27. Connect Tape drive to the Recovery Server. 28. Restore Exchange Database to original location. 29. Verify that the restored database will mount. 30. Run EXMERGE.EXE to extract desired mailbox to a PST file. 31. Open PST file in Outlook. 32. Export desired messages/folders to new PST file. 33. Move new PST file to production network. 34. Have the user logon to Outlook and assist them with importing the messages. ------------------------------------------------------------------------ --- Let me know if I've missed anything... Russ Hansen MCSE +I, MCSE(2k), CCNA, NCP (614) 374-1300 [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang =english To unsubscribe: mailto:[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/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[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.
