Which member of a high-availability cluster should be upgraded first in a Zero downtime upgrade?
Which member of a high-availability cluster should be upgraded first in a Zero downtime upgrade?
In a high-availability cluster, the Standby Member should be upgraded first during a zero downtime upgrade. This is because the Standby Member is not actively handling traffic or providing services, so upgrading it first ensures minimal disruption to the ongoing operations. Once the Standby Member is upgraded and verified to be working correctly, it can take over the active role during the upgrade of the other members, preserving the availability of the services.
The Cluster Member M1 is Active. Action plan: Upgrade, or Clean Install the Standby Cluster Members M2 and M3. The upgraded Cluster Members M2 and M3 change their cluster state to Ready. The old Cluster Member M1 changes its cluster state to Active Attention. In SmartConsole, change the version of the cluster object to R80.30. Install the Access Control Policy on the upgraded Cluster Members M2 and M3. Perform a controlled cluster failover from the Active old Cluster Member M1. The upgraded Cluster Member M2 (or M3) changes its cluster state to Active. The other upgraded Cluster Member M3 (or M2) changes its cluster state to Standby. Upgrade, or Clean Install the old Cluster Member M1. Install the Access Control Policy on the cluster object. Cluster states of the Cluster Members are: one is Active, others are Standby. On each Cluster Member, change the CCP mode to Auto. Install the Threat Prevention Policy on the cluster object.