We are excited to announce VMware Aria Suite Lifecycle 8.14 introduces an innovative capability known as “VMware Identity Manager Cluster Auto-Recovery”.
The new ‘autorecovery’ service minimizes the use of the time-consuming ‘Remediate’ process from the Suite Lifecycle UI.
New deployments of VMware Aria Suite Lifecycle 8.14 ship with the VMware Identity Manager Cluster Auto-Recovery enabled. You may enable the VMware Identity Manager Cluster Auto-Recovery feature for upgraded deployments on the ‘globalenvironment’ environment tile.
Table of contents
About the ‘autorecovery’ service
The ‘autorecovery’ service is a Linux service, running on all three nodes within the vIDM cluster.
With the new ‘autorecovery’ service:
- pgPool service starts and restarts are controlled programmatically.
- Only the primary role node will have the cluster VIP or delegateIP applied.
- Detachment of VIO is performed only on standby nodes with the standby role.
- Recovery is synchronized based on the node’s status as database primary and cluster leader is applied if all nodes are noting standby.
These significant improvements ensure duplicate operations are no longer executed on the cluster nodes.
Features of the ‘autorecovery’ service
- Remediates cluster VIP loss on primary role node.
- Resolves cluster issues due to network outages.
- Recovery of “down” cluster node/s.
- Avoids the necessity to initiate “Remediate” from UI in most cases, which involves node(s) restarts contributing to downtime.
- Eliminates the necessity of rebooting vIDM nodes because of PostgreSQL cluster problems.
- Recovery in cases with significant replication delay (‘significant’ configurable in bytes, more than 1000 bytes of lag between primary and secondary nodes)
- Recovery in rare cases of all nodes are in a ‘standby’ state
- Prevent discrepancies in the /etc/hosts
Downtime
No, there is no downtime when the auto-recovery script runs.
Toggle the VMware Identity Manager Cluster Auto-Recovery feature
Once enabled, users can come to the day-2 operations pane of ‘globalenvironment’ or vIDM and then choose to disable and vice-versa.
For additional information see our YouTube playlist, Cloud Management blog, and TechZone for additional content.
