Learn how to migrate your data and any custom configuration files with minimal
downtime.
This topic describes how to upgrade from a
Vocera Voice Server cluster to a
Vocera Voice Server 5.3.3
cluster. For additional support, refer to the
Vocera Cluster Upgrade Checklist.
-
If Vocera Report Server is
running, shut it down:
-
On the Vocera Report Server computer, choose Start > All Programs >
Administrative Tools > Services. The Services window
appears.
-
Stop the Tomcat service.
-
Close the Services window.
-
Make sure Vocera badges are configured with the correct comma-separated list of
IP addresses in the Vocera Voice Server IP
Address property. If necessary, use the Badge Properties Editor to update the
badge.properties file on every cluster node. For
details, see the Vocera Badge Configuration Guide.
-
Shut down the standby Vocera Voice Server to
make it inactive. If there are multiple standby Vocera Voice Servers, shut down ALL of them.
This action does not affect the active Vocera Voice Server.
In the Vocera Control Panel, choose Run > Shutdown.
-
Upgrade the Vocera Voice Server on the
inactive node as follows:
-
(Optional for 5.1 and later) Uninstall the Vocera 5.3.1 or Vocera 5.3.2 software on the inactive node.
See
Uninstalling Vocera Voice Server Software.
Note: You do not need
to uninstall Vocera Voice Server software, if you are migrating from a Vocera 5.1 release to a
later 5x release. However, if you are migrating from a Vocera
release earlier than 5.1, this step is necessary. For example Vocera Voice Server 5.0 to 5.3.3 or 4.3 to 5.3.3.
-
Install the 5.3.3 Vocera Voice Server
software.
Important: At the end of the installation program, do
not reboot.
-
If your Vocera installation has modified configuration files (for
example, Properties.txt), merge the changes into
the corresponding file on your new server. See Upgrading Properties Files.
-
Reboot the server you are upgrading.
Important: After the Vocera Voice Server starts, it
initially comes up as an active node, and then within a
minute it rejoins the cluster and performs a remote restore. DO NOT
proceed to the next step until after the remote restore finishes.
With a large database, a remote restore can take several minutes.
After the remote restore finishes, the server comes online as a
standby node.
-
Shut down the Vocera Client Gateway and the Vocera SIP Telephony Gateway, as appropriate.
To shut down Vocera Client Gateway and Vocera SIP Telephony Gateway: Double-click the VSTG Service Stop and VCG Service Stop shortcut icon on
the Windows desktop.
Note: If the active node is running Vocera Voice Server version 4.x then learned names and learned commands may not be
synchronized from the active Vocera Voice Server to the standby 5.3.3 server.
-
In the Vocera Control Panel on the active node of the cluster, choose
Run > Shurdown. In the confirmation dialog box,
click OK.
Make sure the Vocera Voice Server node that has been updated to version 5.3.3 is now active.
Note: When the updated server becomes the active node, there is a service
interruption as badges connect to the server and are updated. The
badge update completes in approximately 5 minutes.
-
Upgrade the Vocera SIP Telephony Gateway and Vocera
Client Gateway to version 5.3.3, as
appropriate.
-
Upgrade the Vocera Voice Server on the inactive node as follows:
-
(Optional for 5.1 and later) Uninstall the Vocera 5.3.1 or Vocera 5.3.2 software on the inactive node.
See
Uninstalling Vocera Voice Server Software.
Note: You do not need
to uninstall Vocera Voice Server software, if you are migrating from a Vocera 5.1 release to a
later 5x release. However, if you are migrating from a Vocera
release earlier than 5.1, this step is necessary. For example Vocera Voice Server 5.0 to 5.3.3 or 4.3 to 5.3.3.
-
Install the 5.3.3
Vocera Voice Server software.
Important: At the end of the installation program, do
not reboot.
-
If your Vocera installation has a modified
Properties.txt file, merge the changes into the
corresponding file on your new server. See Upgrading Properties Files.
-
Reboot the server you are upgrading.
Important: After the Vocera Voice Server starts, it initially comes up as an active node, and then
within a minute it rejoins the cluster and performs a remote
restore. DO NOT proceed to the next step until after the remote
restore finishes. With a large database, a remote restore can take
several minutes. After the remote restore finishes, the server comes
online as a standby node.
-
Upgrade Vocera Report Server as
appropriate.
-
Perform the post-installation tasks to completely migrate your data to
Vocera 5.3.3: