If you build a server on your test LAN that joins your test domain fine then install exchange on it and restore the IS from your production server. Then run the consistency adjuster you should be fine. Don't try to perform a full disaster recovery of a production DC to your test LAN (Full OS, etc.), this will not work.
Mark Smith -----Original Message----- From: McCready, Robert [mailto:[EMAIL PROTECTED]] Sent: July 11, 2002 4:06 PM To: MS-Exchange Admin Issues Subject: RE: Disaster Recovery I was successful with building a BDC on the network, then removing it from the network and making it the PDC in the lab. That gave me all the correct SAM/SID information, and I had no problems restoring. I just thought there might be some way to restore the Server in a completely separate lab? Technet says that if you do the isinteg -patch and run the consistency adjuster, that you will then have an account with a correct SID in the lab. I must be doing something wrong. Robert -----Original Message----- From: Jim Holmgren [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 4:00 PM To: MS-Exchange Admin Issues Subject: RE: Disaster Recovery Put the PC in the same domain as your production server, but with a DIFFERENT computer name and exactly the same Exchange site and org name (both are case sensitive and don't forget any spaces or punctuation). -Jim Jim Holmgren MCSE, CCNA [EMAIL PROTECTED] Network Engineer Advertising.com We bring innovation to interactive communication. Advertising.com -- Superior Technology. Superior Performance. -----Original Message----- From: McCready, Robert [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 3:55 PM To: MS-Exchange Admin Issues Subject: Disaster Recovery Exchange 5.5, NT 4.0, Veritas 8.5. I'm trying to build a Test lab for Exchange and test restoring our Exchange backups. I have given the test lab the same Computer Name, Site Name and Organization name. However, I cannot complete a successful restore. I believe this is because the SAM accounts do not match. I've tried just restoring the Information store first, and then running an isinteg -patch, followed by running the consitency adjuster, just like Technet suggested. However, either the Information Store would not start, or I would get a communications error with the Exchange Server. I appear to be running in circles here. Has anybody restored their Exchange site to a Test lab that didn't have a matching SAM or SID? Thanks! Robert List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm *********************************************************** The information transmitted in this email is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this email in error, please contact the sender and permanently delete the email from any computer. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
