Upgrade the nodes in your VMware Identity Manager cluster one at a time. Expect some downtime during upgrade and plan the timing of your upgrade accordingly.
For general load-balancing information, see the 3.3 version of the Installing and Configuring VMware Identity Manager for Linux guide, such as the Using a Load Balancer or Reverse Proxy to Enable External Access to VMware Identity Manager topic.
For load-balancing information specific to VMware NSX-T™ or VMware NSX® for vSphere®, see the corresponding VMware Validated Design™ documentation that follows for guidance.
- For VMware NSX-T, see topics such as the following.
Type of Information Topic Name and Link VMware NSX-T Design Network Design for Cross-Region Workspace ONE Access VMware NSX-T Deployment Configure the Load Balancer for the Cross-Region Workspace ONE Access Cluster in Region A
- For VMware NSX for vSphere, see topics such as the following.
VMware NSX for vSphere Deployment Configure the Load Balancer for the Cross-Region Workspace ONE Access Cluster in Region A
- Take snapshots of the database and the VMware Identity Manager nodes.
- Remove the appropriate nodes from the load balancer, depending on the database type.
- Internal PostgreSQL Database. Remove replica nodes from the load balancer while keeping the database master node intact.
- Microsoft SQL Database. Remove all nodes except one from the load balancer.
- If you are upgrading with VMware vRealize Suite Lifecycle Manager, disable the health monitors on the load balancer.
- Upgrade the node that is still connected to the load balancer.
- After the node is upgraded, leave it connected to the load balancer.
The connection ensures that the VMware Identity Manager service is available while you upgrade the other nodes.
- Upgrade the other nodes one at a time.
- After all the nodes are upgraded, add them back to the load balancer.