SCR Failover Using /RecoverCMS Fails with RU3 Installed

Recently I was at a customer site who is using CCR & SCR for the replication strategy. The configuration has been going great and we have all the users routed through the Client Access Servers for OWA & Activesync.

With all this success, we were anxious to get started on our SCR testing. The client was a little worried about how SCR failovers would happen and of course nervous about losing data. Not to worry, we’ve done these failovers with a reasonable amount of success for a few years now….

Well halfway through the failover, we have the databases restored and try to take over the cluster…. and Boom!!! A Big annoying error pops up stating:

You must perform disaster recovery using the same version of Exchange as the last installed version. The current installed version is ‘8.1.240.6’; the last version installed is ‘8.1.291.2’

Alright fine… we can get through this. A quick google search and…. nothing :(

The problem is briefly mentioned in the some Exchange Blog Comments, an experts-exchange post, and some MSExchange.org forums. The problem of trying to move the CMS from the production cluster to the SCR standby cluster. Scott Schnoll mentioned a few months ago (July 2008 in a comment that this was a known issue)…. but no good details on the fix or the status. So I called Microsoft to get the details on the issue.

This problem comes up when actually running the command:

Setup.com /RecoverCMS /CMSName:<ClusterName> /CMSIPAddress:<IPAddress>

The tech on the phone informs us that this is a well known issue and is not going to be fixed until SP2 for Exchange 2007. This means RU4 & RU5 won’t contain the fix. The workaround is simple and hopefully won’t cause problems. The steps are as follows:

First we need to fix the version number of the machine account in Active Directory. To do this, we need to open up ADSI Edit from any computer in the domain and connect to the configuration naming context of the nearest DC to the Exchange Server.

Once there, browse to Services, Microsoft Exchange, <organizationname>, Administrative Groups, Exchange Administrative Group (FYDIBOHF23SPDLT), Servers, <ClusterName>

Now, Right+Click on the ClusterName, and open the properties.

When the properties box comes up, scroll down to find the attribute ‘serialNumber’, highlight the serialnumber and click the remove button. Then edit the text ,replacing “Version 8.1 (Build 30240.6)” with “Version 8.1 (Build 30291.2)”

If you are editing versions past RU3, the versions may be different; however, they will be called out in the error message when you run the /recovercms command. Essentially, the fix is to replace the serialnumber in ADSIEdit with the last build number called out in the error message (provided the serialnumber in ADSIEdit is in fact the first number called out in the error.
Once the updates are complete, don’t forget to click the add button and save the changes before closing out of ADSI Edit.

Hope this Helps!!

Advertisements

Tags: , , , , , , ,

6 Responses to “SCR Failover Using /RecoverCMS Fails with RU3 Installed”

  1. Henrik Walther Says:

    Hi Josh,

    I’m quite sure the fix will be included in RU5, that’s what I heard via various MS sources.

    Henrik

  2. Josh Maher Says:

    Hey Henrik, I hope so…It would be great if we could get a confirmation from MS though.

  3. Exchange 2007 and Beyond: SAN to DAS and Back Again? « Power Windows Says:

    […] Here’s another reason why SCR could be a sketchy DR solution. […]

  4. storage area networking Says:

    Network Area Storage (NAS) is easier to share files on the network but the price is still too expensive, especially for use only at home.

  5. Sam Says:

    Hi Josh,

    Regular visitor to your blog and its always informative, would be grateful if you could help out on the following :

    What is the version number in

    Adsiedit-> Configuration > Services > Microsoft Exchange > Org name > Administrative Groups> Administrative group name > Servers

    once on the servers tab, right click and check the version number attribute ?

    what does that version number relates to ?

    what changes / effects this version number ?

    would be grateful

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: