Upgrading with a Clean Installation

You can do a Full High Availability upgrade with a clean installation on the secondary cluster member and synchronize the primary cluster member. This type of upgrade causes downtime to the cluster members.

To upgrade Full High Availability with a clean installation:

1. Make sure the primary cluster member is active and the secondary is standby: check the status of the members.
2. Start failover to the second cluster member.

   The secondary cluster member processes all the traffic.

3. Log in with SmartConsole to the management server of the secondary cluster member.
4. Click Change to Active.
5. Configure the secondary cluster member to be the active management server.

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

6. Upgrade the primary cluster member to the appropriate version.
7. Log in with SmartConsole to the management server of the primary cluster member.

   Make sure version of the SmartConsole is the same as the server.

8. Upgrade the version of the object to the new version.
9. Install the policy on the cluster object.

   The primary cluster member processes all the traffic.

   Note - Make sure that the For Gateway Clusters install on all the members option is cleared. Selecting this option causes the installation to fail.

10. Install the secondary member.
11. From SmartConsole, configure the cluster object.
    1. Change the secondary details (if necessary).
    2. Establish SIC.

Synchronization for Management High Availability starts automatically.