Here's the update! Spend the day on the phone to Microsoft PSS (mainly waiting for them to ring back ...)
Initially was looking like we would install fresh Exchange on Server1 then restore the database onto it. Never got as far as that as I was waiting for advice on how to install Exchange (like did I need to /forestprep /domainprep or /disasterrecovery) eventually spoke to someone who knew that moving the database to a server with a new name would not work without going through AD and fixing the server name pointers. At that point it was suggested that the original flaky server problem may be due to and APC Java problem with certificates expiring:- << The problem is caused by Java Cryptography Extension version 1.2.1 expiring on 27th July. To get the servers back running, reboot into safe mode and run MSConfig, click on the Services tab, check the box "Hide All Microsoft" and then click "Disable All" Reboot into normal mode. For more info on the probnlem access the Sun website: http://sunsolve.sun.com/search/document.do?assetkey=1-26-101796-1&search clause=101796 >> I tried to start this but had to leave site before the server had completed a boot into safe mode. Hopefully tomorrow I will fix the flakiness and then be able to bring back Exchange. Not sure if this will work straight away as I did restore data to it from 31st July so maybe this is the cause of the Services hanging. Will know more tomorrow! Thanks for the help Ian -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geni Sent: 23 August 2005 17:34 To: Exchange Discussions Subject: re: Disaster Recovery problem Ian, when you say Exchange does not run, do you mean the IS, MTA, etc., won't start? What messages appear in the System Event Log? What was in the event log before the restore to indicate general flakiness? Start with the basics. Go back and figure out what was causing the flaky performance first; until you resolve that, restoring your d/b isn't going to do you a bit of good. You can't restore your Exchange d/b onto a server with a different name and expect it to start. You'd have to bring up a NEW Exchange server in the same site, migrate your mailboxes and public folders, and hope the clients repointed themselves (they usually will, but not always). Have you tried running the eseutil utilities against a COPY of the d/b? (Do NOT run eseutil hard utilities against the only copy of your d/b unless you want a real disaster on your hands.) Been there, done all that, got the t-shirt. It isn't fun. I've had (knock vigorously on wood) a stable Exchange infrastructure for the last five years, but it sure as hell wasn't when I started here, so I got to do all kinds of disaster recovery and learn what not to do on the fly. _________________________________________________________________ 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.
