Role replication with vCenter Server protected by vCenter Server Heartbeat in linked mode group (2044840)
When the Primary node of a vCenter Server Heartbeat server pair is the active node, any changes to roles, permissions, and licenses on any of the vCenter Servers in a linked mode group will be successfully replicated to other vCenter Servers.
In the event of a switchover or failover where the Secondary vCenter Server Heartbeat server becomes active, any changes to the roles, permissions, and licenses on any of the vCenter Servers in the linked mode group will not be replicated. These changes will only be replicated when the Primary vCenter Server Heartbeat server becomes active again.
This issue is only experienced in rare situations as changes to roles, permissions and licenses are not frequently performed post-vCenter Server setup. Generally, the Primary vCenter Server Heartbeat node is the active node and switchover or failover to Secondary vCenter Server Heartbeat node is typically the result of maintenance or an outage on the Primary server.
Note: The vCenter Server Heartbeat product is working as designed.
- Make Secondary vCenter Server Heartbeat node the active node.
- On the active sever, using the System Tray icon, navigate to Shutdown Group > Stop all protected applications.
- To isolate vCenter Server from the linked mode group, navigate to Start >All Programs > VMware > vCenter Server Linked Mode Configuration > Modify linked mode configuration > Isolate this vCenter Server instance from linked mode group.
- Join vCenter Server back to linked mode group by navigating to Start > All Programs > VMware > vCenter Server Linked Mode Configuration > Modify linked mode configuration > Join vCenter Server instance to an existing linked mode group or another instance.
- Start VMware vCenter Server Heartbeat by right-clicking the System Tray icon and selecting Start Group.