How to Upgrade Microsoft Exchange 2007 or 2010 without a Service Pack to SP1 When Neverfail Heartbeat is Installed

Follow

Summary

This Knowledgebase article provides the procedures to upgrade Microsoft Exchange 2003 with no Service Pack to SP1 or SP2 and Microsoft Exchange 2007 or 2010 with no Service Pack to SP1.


More Information

With Neverfail Heartbeat V5.2.2 and Earlier Installed

Prerequisite: Updating Exchange 2007 to Exchange 2007 SP1 on Windows Server 2003 x64 machines requires that the Operating System have SP2 or above installed ( http://technet.microsoft.com/en-us/library/aa996719(EXCHG.80).aspx ).

This procedure assumes that:

  • The Primary server is active
  • The Secondary server is passive
  • The Neverfail Heartbeat server pair is replicating
  • The Neverfail Heartbeat Management Client shows both the File System Status and Registry Status as Synchronized .

Procedure

Note: Prior to initiating this procedure, a Management IP address must be added to both servers. Once the Service Pack has been installed, the Management IP address can be removed if desired. For more information about configuring Management IP addresses on a Neverfail Heartbeat server pair, please see Knowledgebase article #208 - How to Configure Management IP Addressing and Routing with Neverfail Heartbeat .

If the Secondary server is the active server, please omit step one below.

On the Secondary Server:

  1. Using the Neverfail Heartbeat Management Client, perform a switchover and wait for Secondary server to become active.
  2. If the Mailbox Role is installed, dismount the Mailbox Stores.
  3. Shutdown Neverfail Heartbeat on all servers or shutdown Group leaving the protected application running.
  4. Install Exchange 2007 SP1 on the Secondary server. If Neverfail SCOPE locks files needed by the update procedure, manually stop the service (scopesvc) via the Service Control Manager.
  5. After the update finishes, verify that Exchange is operational.
On the Primary Server:

  1. If the Edge Transport role is installed, the ADAM service (ADAM_MSExchange) must be manually started via the Service Control Manager.
  2. Install Exchange 2007 SP1 on the Primary server. If Neverfail SCOPE locks files needed by the update procedure, manually stop the service (scopesvc) via the Service Control Manager.
  3. After the update finishes, stop the Exchange services that were started by the update by executing the following commands at the Windows Command Prompt:

    c$>cd c:\NeverfailInstallPath\r2\bin

    c$>..\scripts\exchange\stop.bat

    Note: This assumes Neverfail Heartbeat is installed on the C: drive. If it is installed on a different drive, please substitute the appropriate drive letter in the commands shown above.
  4. Start Neverfail Heartbeat on the Secondary server.
  5. Start Neverfail Heartbeat on the Primary server.
  6. Start the Neverfail Heartbeat Management Client and check that a Full System Check completes.
  7. Perform a switchover to make the Primary server active again.

With Neverfail Heartbeat V5.3 and Later Installed

Prerequisite: Updating Exchange 2007 to Exchange 2007 SP1 on Windows Server 2003 x64 machines requires that the Operating System have SP2 or above installed ( http://technet.microsoft.com/en-us/library/aa996719(EXCHG.80).aspx ).

This procedure assumes that:

  • The Primary server is active
  • The Secondary server is passive
  • The Neverfail server pair is replicating
  • The Neverfail Heartbeat Management Client shows both the File System Status and Registry Status as Synchronized .

Procedure

Note: Prior to initiating this procedure, a Management IP address must be added to both servers. Once the Service Pack has been installed, the Management IP address can be removed if desired. For more information about configuring Management IP addresses on a Neverfail server pair, please see Knowledgebase article #208 - How to Configure Management IP Addressing and Routing with Neverfail Heartbeat .

If the Secondary server is the active server, please omit step 1 below.

On the Secondary Server:

  1. Via the Neverfail Heartbeat Management Client, perform a switchover and wait for Secondary server to become active.
  2. If the Mailbox Role is installed, dismount the Mailbox Stores.
  3. Shutdown Neverfail Heartbeat on all servers or shutdown Group leaving the protected application running.
  4. Install Exchange 2007 SP1 or Exchange 2010 SP1 as appropriate on the Secondary server. If Neverfail SCOPE locks files needed by the update procedure, please manually stop the service (scopesvc) via the Service Control Manager.
  5. After the update finishes, verify that Exchange is operational.

On the Primary Server:

  1. If the Edge Transport role is installed, the ADAM service (ADAM_MSExchange) must be manually started via the Service Control Manager.
  2. Install Exchange 2007 SP1 or Exchange 2010 SP1 as appropriate on the Primary server. If Neverfail SCOPE locks files needed by the update procedure please manually stop the service (scopesvc) via the Service Control Manager.
  3. Start Neverfail Heartbeat on the Secondary server.
  4. Start Neverfail Heartbeat on the Primary server.
  5. Start the Neverfail Heartbeat Management Client and check that a Full System Check completes.
  6. Perform a switchover to make the Primary server active again.


Applies To

Microsoft Exchange 2003
Microsoft Exchange 2007
Microsoft Exchange 2010 including Edge Transport Role


Related Information

Knowledgebase article #1797 - How to Upgrade a Protected Application with Neverfail Heartbeat Installed (for upgrading other protected applications).

Knowledgebase article #862 -  How to Upgrade From No SP or SP1 to SP2 for Microsoft Exchange 2003 When Neverfail Heartbeat is Installed

Knowledgebase article #2298 - How to Upgrade Microsoft Exchange 2007 to SP3 When Neverfail Heartbeat Is Installed

KBID-2248

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.