How to Upgrade From No SP or SP1 to SP2 for Microsoft Exchange 2003 When Neverfail Heartbeat is Installed

Follow

Summary

This Knowledgebase article provides the procedures to upgrade Microsoft Exchange 2003 No SP to SP1 or SP2 and Microsoft Exchange 2007 no SP to SP1.


More Information

With Neverfail Heartbeat V5.2.2 and Earlier Installed

The following upgrade procedure of upgrading from no SP or SP1 to SP2 for Microsoft Exchange 2003 offers the following benefits:
  • Exchange data is isolated on each server, ensuring no data corruption can take place.
  • Stores will always mount when the roles are changed.
  • An immediately recoverable server is always available should the service pack cause data corruption or problems with Exchange services. The failed server can then be removed from the Network and services started on the other server.
  • It is quicker, especially in a WAN, where a large amount of data needs to be verified.
    The extra time spent performing the upgrade easily outweighs the benefits and the minimal recovery time should disaster strike.
Procedure
  1. Is Security Update 913446 (security bulletin MS06-007) installed (applies only to Windows Server 2003 SP1 – SP1 is not required for the upgrade but recommended by Microsoft)?
    1. YES - proceed to Step 2.
    2. NO -
      1. Shutdown Neverfail Heartbeat leaving the protected application running.
      2. Install Security update 913446 (security bulletin MS06-007) on both servers.
      3. Reboot both servers.
      4. Allow system to synchronize.
  2. Via the Neverfail Heartbeat Client Management, perform a switchover and wait for Secondary server to become active.
  3. Shutdown Neverfail Heartbeat leaving the application running.
  4. Dismount Exchange stores via Exchange System Manager.
  5. Install SP2 on the Secondary server.
  6. If asked, do not reboot the server (it will be rebooted just after step 15).
  7. Verify if stores mount and Exchange is operational.
  8. Stop Exchange using the following method:

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

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

  9. Launch the Configure Server wizard.
  10. Change the server role to Secondary / passive.
  11. Via the Service Control Manager, start Neverfail Heartbeat on the Secondary server.
  12. Stop the Neverfail Heartbeat Service.
  13. On the Primary Server
    1. Launch the Configure Server wizard.
    2. Change the role to Primary / active.
    3. Start Neverfail Heartbeat.
    4. When Exchange has started, shutdown Neverfail Heartbeat leaving the application running.
    5. Install SP2 on the Primary Server.
  14. If asked, please reboot the Server.
  15. Verify Exchange is operational.
  16. Start Neverfail Heartbeat on the Primary Server; please ignore this step if the Primary was rebooted at step 14.
  17. If asked at step 6, reboot the Secondary Server, otherwise start Neverfail Heartbeat on the Secondary server.
  18. Start Neverfail Heartbeat Management Client and check that the system completes the full system check.

With Neverfail Heartbeat V5.3 and Later Installed

The following upgrade procedure of upgrading from no SP or SP1 to SP2 for Microsoft Exchange 2003 offers the following benefits:
  • Exchange data is isolated on each server, ensuring no data corruption can take place.
  • Stores will always mount when the roles are changed.
  • An immediately recoverable server is always available should the service pack cause data corruption or problems with Exchange services. The failed server can then be removed from the Network and services started on the other server.
  • It is quicker, especially in a WAN, where a large amount of data needs to be verified.
    The extra time spent performing the upgrade easily outweighs the benefits and the minimal recovery time should disaster strike.

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'.

  1. Is Security Update 913446 (security bulletin MS06-007) installed (applies only to Windows Server 2003 SP1 – SP1 is not required for the upgrade but recommended by Microsoft)?

    Note: For Windows Server 2003 SP2, no additional update is necessary.
    1. YES - proceed to Step 2.
    2. NO -
      1. Shutdown Neverfail Heartbeat leaving the protected application running.
      2. Install Security update 913446 (security bulletin MS06-007) on both servers.
      3. Reboot both servers.
      4. Allow system to synchronize.
  2. Via the Neverfail Heartbeat Client Management, perform a switchover and wait for Secondary server to become active.
  3. Shutdown Neverfail Heartbeat leaving the application running.
  4. Dismount Exchange stores via Exchange System Manager.
  5. Install SP2 on the Secondary server.
  6. Verify if stores mount and Exchange is operational.
  7. Install Exchange 2003 SP2 on the Primary server.
  8. Start Neverfail Heartbeat on the Secondary server.
  9. Start Neverfail Heartbeat on the Primary server.
  10. Start the Neverfail Heartbeat Management Client and check that a Full System Check completes.
  11. Perform a switchover to make the Primary server active again.
  12. Verify that Exchange is operational.


Applies To

Microsoft Exchange 2003


Related Information

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

Knowledgebase article #2248 - How to Upgrade From No SP to SP1 for Microsoft Exchange 2007 When Neverfail Heartbeat is Installed

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

KBID-862

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.