Exchange Server Forums

Setup /RecoverCMS fails

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> High Availability >> Setup /RecoverCMS fails

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Setup /RecoverCMS fails - 4.Jul.2008 12:09:16 PM

de.blackman

Posts: 1448
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline

I am in the process of configuring SCR in a my environment. We have a single copy cluster configured in production (active/passive

) and a passive node of a cluster without the mailbox role installed in the DR site (yes, these servers are physically in different locations).

Obviously all my exchange servers have SP1 installed but in addition have installed update rollup 2 on them. SCR has been configured and replication is working flawlessly! currently no active users are on the servers so we are testing different scenarios but we do have test accounts. When I run the SETUP /RECOVERCMS to activate the DR server, I am getting the following error:

"You must perform disaster recovery using the same version of Exchange as the last installed version. The current installed version is �8.1.278.2�; the last version installed is '8.1.240.6"

I cannot get the setup to run at all! Has anyone seen this error before? Any ideas would be helpful.

_____________________________

De BlackMan
List Moderator
"Did you backup your Information Store Today?!"

Post #: 1

Featured Links*

RE: Setup /RecoverCMS fails - 5.Jul.2008 12:48:54 PM

Exchange_Geek

Posts: 1026
Joined: 31.Dec.2006
Status: offline

Yes, we have seen such issues earlier - there are only two solutions for this.

1) Search for the value in the registry value at location v8.0 for 8.1.240.6 and replace that with 8.1.278.2. Once thats done try the /recovercms - see if it works - else go to ADSIEDIT and check the properties of "your E2k7 box" - the attribute is server version - replace 8.1.240.6 with 8.1.278.2 {i dont rem but it was something like 8.1 (30240.6) and that needs to be replaced with (30278.2) } -excuse me for gettting some data wrong - since i dont have my lab access right now unable to tell u exactly.

2) flatten down everything and that should work all the time (too nasty a solution but thats what PSS Team always states)

(in reply to de.blackman)

Post #: 2

RE: Setup /RecoverCMS fails - 15.Jul.2008 11:51:35 AM

ScottSchnoll

Posts: 15
Joined: 26.Jan.2008
Status: offline

This is a known issue. No need for extensive hacks or registry or AD changes. Simply remove the UR from the system, run /recoverCMS and after the CMS is back, re-install the UR.

Hope this helps.

_____________________________

Regards,

Scott Schnoll
Principal Technical Writer - Exchange Team
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights.

(in reply to de.blackman)

Post #: 3

RE: Setup /RecoverCMS fails - 25.Jul.2008 11:00:11 AM

de.blackman

Posts: 1448
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline

Thanks for the input guys! I have overcome that obstacle now and have been able to clear the CMS on the production environment. Now I am faced with another issue. Currently everything is running out of the DR site and am reconfiguring the production environment so that I can restore everything to the way it was (i.e.: exchange is running out of the production environment)

In the technet article(http://technet.microsoft.com/en-us/library/bb738150(EXCHG.80).aspx), it mentions

"If the storage used by the original failover cluster was unaffected by the failure of SITEA and if the original databases and their transaction logs for the three storage groups still exist on NODEA, it may be possible to use them for continuous replication purposes without having to perform a full reseed for each storage group on NODEA"

GREAT!!! ummm How???

The databases in the environment are still intact and range in size but are mostly over 80GB. I have tried to update the storage group copy but it keeps asking me to delete my transaction logs and database files. Is there no way of having the transaction logs deleted while leaving the database files and having only the logs replicated over from the DR site since it is currently the active site??

Any help is greatly appreciated!

Thanks

< Message edited by de.blackman -- 25.Jul.2008 11:04:02 AM >

_____________________________

De BlackMan
List Moderator
"Did you backup your Information Store Today?!"

(in reply to de.blackman)

Post #: 4