Plan when to perform the ESXi maintenance or upgrade.

• If the ESXi server hosts all the nodes in a Breeze cluster, you must perform the maintenance during a maintenance window.

• If the ESXi server is host to a single node from a multi-node Breeze cluster, you can perform the upgrade during a maintenance window or during a period of low activity.

• NOTE: In some solutions with multiple Breeze clusters, nodes from different Breeze clusters can be present on the same ESXi host. For example: Nodes from Breeze cluster 1 and cluster 2 can reside on the same ESXi host. Be aware that for clusters with 2+ nodes, Breeze supports a single node failure for each cluster. Refer to solution documentation for specific recommendations regarding actions requiring a maintenance window.

Obtain the materials required for the ESXi upgrade or patch.

For an ESXi upgrade, you require:

• An upgrade ESXi image.

• A license for the updated version of ESXi.

Back up the cluster database.

If the cluster database is enabled, take a backup. See Backing up a cluster database.

Set the cluster or nodes affected to deny new services.

See Preparing Breeze nodes for ESXi maintenance.

• Putting a Breeze node in a 2+ node cluster into deny new service can degrade overall performance as the activity load shifts to the cluster's remaining in-service nodes. Consult the solution documentation for more information.

• For some solutions, a maintenance window is required, and the entire cluster must be placed in deny new service. Consult the solution documentation for more information.

Move the nodes to another ESXi host.

If the solution supports vMotion:

1. If used, disable DRS/vSphere HA.

2. Using vMotion with high priority, move the node(s) to another available ESXi host.

3. Wait until the vMotion is complete.

If the solution requires a node power down:

1. If used, disable DRS/vSphere HA.

2. Migrate the breeze node(s) to another ESXi host.

3. Wait until the migration is complete.

Perform the ESXi maintenance.

See Upgrading the ESXi host.

Add the ESXi license.

If upgrading ESXi, add a license for the updated version. See Adding the new ESXi vSphere license.

Move the nodes back to their original ESXi host.

If the solution supports vMotion:

1. Using vMotion with high priority, move the node(s) back to their original ESXi host.

2. If previously used, re-enable DRS/vSphere HA.

3. Wait until all maintenance tests pass and all services are running. See Running maintenance tests.

If the solution requires a node power down:

1. Migrate the Breeze node(s) back to their previous ESXi host.

2. If previously used, re-enable DRS/vSphere HA.

3. Power on the nodes.

4. Wait until all maintenance tests pass and all services are running. See Running maintenance tests.

Set the nodes back to accept new service

• If only doing maintenance on one ESXi host:

  Set the node(s) back to accept new service.

• If doing maintenance on multiple ESXi hosts:

  If required by the solution, keep the cluster in deny new service until you have completed maintenance on all ESXi hosts.

See Accepting new service after ESXi maintenance.

Reboot the Breeze cluster

Some solutions require a cluster reboot after all Breeze nodes are back online. Consult the solution documentation for more information.

• This can apply even if you have only restarted one Breeze node.

Set the nodes and clusters back to accepting new services.

See Accepting new service after ESXi maintenance.