What you're seeing should absolutely not happen. Exchange doesn't go out and look for other servers. Something somebody did joined that server to your existing site.
Ed Crowley MCSE+I MVP Tech Consultant Compaq Computer "There are seldom good technological solutions to behavioral problems." -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Harmon, Josh Sent: Thursday, January 10, 2002 7:56 AM To: Exchange Discussions Subject: RE: Restore problem on Exchange 5.5 - dir will not start Ed C. asks: The server you're restoring to has the same organization and site name as your production environment but was installed without joining the site, right? =========================== Well... yes an no. When I first created the environment I did so following the DR whitepaper which says: 4. Select Create New Site (do not select Join Existing Site). 5. Use the same organization and site names. And from part 2: Question 35: If I have a good backup of the directory and information store and I am restoring a server to an existing site by reinstalling Exchange, should I select Create New Site or Join Existing Site during the Exchange installation? Answer: Be sure to select Create New Site. Do not select Join Existing Site. When you restart the server after restoring the databases, the restored server automatically synchronizes with existing servers in the site-even when you select Create New Site. If you attempt to Join Existing Site, you will receive an error because other servers in the site already have knowledge of the server you are restoring (its name matches the name of the crashed server). So I did that on all four machines using a Jan 1 backup... Directory connections work fine at that point (make a change on one and replicated out). It wasn't until I restored to December 13th that I had a problem. And all I did for that restore was a restore from an online backup (using Backup Exec). When that failed... I thought maybe it had to do with a bad exchange install so at this point I did uninstall and reinstall exchange (using above directiongs) and re-ran the restore. I finally got the one server to work by turning off the other directories. I agree that the directories would not co-exist or replicate... but where was my mistake. Am I misreading the DR. document? Obviously something went wrong... but I would like to figure out what my misstep was before it becomes a production issue. Appreciate your time Ed. Josh -----Original Message----- From: Ed Crowley [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 12:32 AM To: Exchange Discussions Subject: RE: Restore problem on Exchange 5.5 - dir will not start The server you're restoring to has the same organization and site name as your production environment but was installed without joining the site, right? You don't want to do that kind of a restore to a production machine. Ed Crowley MCSE+I MVP Tech Consultant Compaq Computer "There are seldom good technological solutions to behavioral problems." -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Harmon, Josh Sent: Wednesday, January 09, 2002 11:50 AM To: Exchange Discussions Subject: Restore problem on Exchange 5.5 - dir will not start I've got a test environment where I've done multiple restores over the past four years. Currently it's setup in a pretty precise mirror image of what i have in production. 4 Exchange servers, same site, same org. I had to do a restore on one of the servers yesterday and bring it back to December 13th (yup... they deleted a file that fell outside of our 21 day recover deleted items window!). Anyway, after the restore from December 13th--the directory service wouldn't start, I finally got it to start by shutting down the other 3 exchange servers... and then the dir service started on the restored system. I could also start the exchange services on the other 3 systems. However, I still cannot shutdown the service on the restored exchange server and restart the directory service. No error event logs.... just the "took too long to start" error message on the Win2k server. The event log just shows a startup and a shutdown of the directory service. I thought it might have to do with the old date of the restore.... so I restored the server with the original dir and info store from Jan 1. Same result. Any ideas? All servers are Windows 2000 Server, sp2 Exchange 5.5 sp4 Did install ADC (from ex sp2 cd) on one of the AD servers in the testnetwork... although the service is stopped in all scenarios. Josh Harmon _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
