Upgrading Full High Availability

In This Section: Upgrading with Minimal Downtime Upgrading with a Clean Installation

To upgrade Full High Availability for cluster members in Standalone configurations, there are different options:

• Upgrade one machine and synchronize the second machine with minimal downtime.
• Upgrade with a clean installation on one machine and synchronize the second machine with system downtime.

Upgrading with Minimal Downtime

You can do a Full High Availability upgrade with minimal downtime on the cluster members.

To upgrade Full High Availability with minimal downtime:

1. Check the status of the cluster members. Run: cphaprob state

   Make sure the Primary cluster member is Active and the Secondary cluster member is Standby.

2. Start failover to the Secondary cluster member.

   On the Primary cluster member, run: cpstop

   The Secondary cluster member becomes the new Active member and processes all the traffic.

3. Log in with SmartConsole to the Security Management Server of the Secondary cluster member.
4. Click Change to Active.
5. Configure the Security Management Server on the Secondary cluster member to be Active.

   Note - We recommend that you export the database using the Management Server Migration Tool.

6. Upgrade the Primary cluster member to the desired Check Point version.
7. Log in with SmartConsole to the Security Management Server of the Primary cluster member.

   Make sure you use the SmartConsole of the same Check Point version as the Security Management Server.

8. Open the cluster object.
9. Change the version of the object to the new version and click OK.
10. Install the Access Policy on the cluster object.

    Note - Make sure that the For Gateway Clusters install on all the members option is cleared. The Primary cluster member now processes all the traffic.

11. Upgrade the Secondary cluster member to the desired Check Point version.

Synchronization for Management High Availability starts automatically.