I just came back from a disaster recovery rehearsal in which we try to recover as many of our systems as we can in a test environment and Exchange was a bear to deal with. Here's what I tried: First I tried to load one of our servers, which has the same name as one of the cluster nodes, with the /disasterrecovery switch as a stand alone exchange server but it failed because the object wasn't found in AD. Next I renamed the server to the same name as our virtual exchange name because I'm assuming that's the name of the exchange object in AD. I tried it again and it says the object is a virtual object so I guess it needs to be a cluster when I do it. Next I rename it back to it's old name and create a single node cluster to try to mimic our environment. I find out during the install that /disasterrecovery isn't supported on a cluster. So how in the world do you recover an exchange cluster from a complete cluster failure? I can't seem to find any documentation from Microsoft on how this should be done. The only thing I was partially successful doing was loading up a stand alone exchange server with a new name and installing exchange on it. I then restored the exchange databases to the server without a problem. The only problem is all of the mailbox accounts still have the old name as their exchange server so I need to use the LDIFDE utility to make the change according to an article I read. Can anyone give me any good insight on what I should be doing?
"dbrink" wrote in message news:30509557-9E8B-44ED-82BE-3DB97C5C6FA0@microsoft.com... >I just came back from a disaster recovery rehearsal in which we try to > recover as many of our systems as we can in a test environment and > Exchange > was a bear to deal with. Here's what I tried: Your best bet is to use the process for a standby-cluster as described here: http://technet.microsoft.com/en-us/library/bb218968(TechNet.10).aspx -- Russ Kaufmann MVP - Windows Server - Clustering ClusterHelp.com, a Microsoft Certified Gold Partner Web http://www.clusterhelp.com Blog http://msmvps.com/clusterhelp The next ClusterHelp class is: May 12-15 in New York
"Russ Kaufmann [MVP]" wrote: > "dbrink" wrote in message > news:30509557-9E8B-44ED-82BE-3DB97C5C6FA0@microsoft.com... > >I just came back from a disaster recovery rehearsal in which we try to > > recover as many of our systems as we can in a test environment and > > Exchange > > was a bear to deal with. Here's what I tried: > > Your best bet is to use the process for a standby-cluster as described here: > http://technet.microsoft.com/en-us/library/bb218968(TechNet.10).aspx > > -- > Russ Kaufmann > MVP - Windows Server - Clustering > ClusterHelp.com, a Microsoft Certified Gold Partner > Web http://www.clusterhelp.com > Blog http://msmvps.com/clusterhelp > > The next ClusterHelp class is: > May 12-15 in New York > Thanks for the reply but I get a page not found error when following that link.
"dbrink" wrote in message news:F8A32B07-038F-4586-AAA2-971F0B732905@microsoft.com... >> "dbrink" wrote in message >> news:30509557-9E8B-44ED-82BE-3DB97C5C6FA0@microsoft.com... >> >I just came back from a disaster recovery rehearsal in which we try to >> > recover as many of our systems as we can in a test environment and >> > Exchange >> > was a bear to deal with. Here's what I tried: >> >> Your best bet is to use the process for a standby-cluster as described >> here: >> http://technet.microsoft.com/en-us/library/bb218968(TechNet.10).aspx >> > > Thanks for the reply but I get a page not found error when following that > link. Try this one: http://technet.microsoft.com/en-us/library/aa996470.aspx -- Russ Kaufmann MVP - Windows Server - Clustering ClusterHelp.com, a Microsoft Certified Gold Partner Web http://www.clusterhelp.com Blog http://msmvps.com/clusterhelp The next ClusterHelp class is: May 12-15 in New York