Configuring and Managing Clusters / About Vocera Voice Server Clusters |
Each standby node automatically synchronizes its data with the data on the active node to ensure that it is constantly ready to take control of the cluster.
The standby nodes perform two types of synchronization:
A remote restore synchronizes all the data on the standby node with the active node. It occurs the first time a standby node comes online, any time a cluster member comes out of discovery mode as a standby node, and any time the Vocera Control Panel stops and restarts the active node.
A remote restore reads data directly from the database and does not require a backup file.
Ongoing updates synchronize the data on the standby node with any changes that occur after the most recent remote restore. The active node records all database transactions that occur after the remote restore starts in a queue, and the standby node uses the queue to update its database.
In addition, a few special files are synchronized outside the remote restore and ongoing updates processes. The following table provides details about how the various types of files used by Vocera are synchronized:
Type of Data |
Synchronization Details |
---|---|
The configuration database |
|
Text, voice, and email messages |
|
All user recordings, such as learned names, learned commands, and so forth |
|
Vocera Report Server logs |
|
The badge.properties file |
Best Practice: Modify badge.properties on the active node, and then restart the active node. This action loads badge.properties into memory on the active node and forces the standby nodes to perform a remote restore and synchronize it. |
Backup files |
Best Practice: Perform a backup after bringing the cluster online. All nodes will then start with the same backup file. |
Several types of files are intentionally not synchronized by the Vocera Voice Server during any process. The following table provides details about these files:
Type of Data |
Reason not Synchronized |
---|---|
The properties.txt file |
|
Vocera Voice Server logs |
|
Third-party (Tomcat, Apache, MySQL, and Nuance) logs |
|