|About Vocera Clusters / Geographically Distributed Clusters|
Before you manually rejoin independent clusters, you must decide which cluster has the database and other files you want to preserve. The active node in the cluster with the chosen database becomes the new active node in the single cluster.
To manually rejoin independent clusters after a WAN link failure:
The following events occur:
The standby node of the abandoned cluster enters discovery mode, sees the active node of the preserved cluster, and comes online as a standby node for it. This new standby node then performs a remote restore from the active node.
The formerly active node of the abandoned cluster restarts, enters discovery mode, sees the active node of the preserved cluster, and comes online as a standby node for it. This new standby node then performs a remote restore from the active node.
The badges that were connected to the abandoned cluster find the active node and connect to it, because the active node is still in their cluster list.
For Vocera Telephony Gateway server or Vocera Report Server machines that were previously connected to an abandoned cluster, you must check the cluster list, find the active node, and connect to it.
A remote restore of a very large database (50,000 spoken names) across a WAN may take 20 minutes or more, depending on the actual size of the database, the speed of the WAN, the available bandwidth, and other issues outside the control of Vocera.