Upgrading Vocera Voice Server on a New Server

This section shows you how to upgrade, migrating your data and settings, with minimal down-time.

If you have an existing Vocera Voice Server system—standalone or cluster— install version 5.3.1 on new server.

If you have customized any of the Vocera properties files, be sure to back up those files before you begin any upgrade process. See, Backing up Vocera Data.

  1. Use the backup utility in your current Vocera Voice Server installation to backup your data.
  2. Copy any customized files to a flash drive or to a temporary location on a network drive that is accessible from your new Vocera Voice Server machine. For example:
    • \vocera\backup\MostRecentBackup.zip

      If you are upgrading a Vocera cluster, this file is on any of the nodes.

    • \vocera\config\badge.properties

      If you are upgrading a Vocera cluster, this file is on the active node.

    • \vocera\server\profiles.txt

      If you are upgrading a Vocera Voice Server cluster, this file is on the active node.

    • \vocera\server\Properties.txt

      If you are upgrading a Vocera Voice Server cluster, this file is on the active node.

  3. Set up your new 5.3.1 server as follows:
    1. Install the 5.3.1 Vocera Voice Server software.
      At the end of the installation program, do not reboot.
    2. If your Vocera installation had a modified Properties.txt file, merge the changes into the corresponding file on your new server.
    3. Copy badge.properties from your flash drive or network drive to the new \vocera\config\ directory.
    4. Copy MostRecentBackup.zip from your flash drive or network drive to the new \vocera\backup\ directory.
    5. Reboot the server you are upgrading.
      After you reboot, the Vocera Voice Server automatically restores your Vocera database.
    6. Perform the post-installation tasks to completely migrate your data to Vocera Version 5.3.1:
  4. Install or upgrade Vocera components on any other machines:
    Component Details
    Badge Configuration Utilities See the Vocera Device Configuration Guide.
    Vocera SIP Telephony Gateway See Upgrading Vocera SIP Telephony Gateway.
    Vocera Client Gateway See Upgrading Vocera Client Gateway.

  5. If Vocera Messaging Interface (VMI) client applications connect to your Vocera system, update them all. The VMI applications must be modified to connect to the new Vocera Voice Server IP address(es).
    Before moving badges over to the new Vocera system, ensure that VMI applications are able to connect to the Vocera Voice Server and send messages.
  6. Move the badges from your current production server to the 5.3.1 server that you just upgraded as follows:
    1. Use the Badge Properties Editor to edit the Vocera Voice Server IP Address field in the \vocera\config\badge.properties file that resides on your production Vocera system.
      Enter the IP address of the 5.3.1 server that you just upgraded. If you are creating a cluster, this becomes your initial active node. Make sure you update the Vocera Voice Server IP Address field for all types of badges. See the Vocera Device Configuration Guide.
    2. Restart your production Vocera Voice Server, as described in Stopping and Restarting the Server.
      When the Vocera Voice Server restarts, it downloads the edited badge.properties file to your existing badges, and then they automatically connect to the 5.3.1 system. The 5.3.1 server is now your production system.
    3. Leave your existing Vocera Voice Server running, even though the currently active badges are not connected to it.
      When users boot badges that haven't been used recently, they will connect to the Vocera Voice Server at that IP address, download the new badge.properties file, and then connect to the current 5.3.1 server.
  7. If you are migrating to a cluster, use the cluster setup documentation to configure the remaining nodes.