Replace a Single Server or Cluster


Caution

Because this process is designed to work as a server replacement, you must perform it in the live environment. Cisco does not recommend doing this process on a "dead net" because a duplication of entire network environment is required, which is highly risky.

This section provides checklists of the steps that are required to replace a single server or a cluster:

  • If you are replacing an entire cluster, replace the servers in the order that is described in the following steps.
  • If you are replacing a publisher node in a cluster, or a single server that is not part of a cluster, go to the applicable procedure.
  • If you are replacing one or more subscriber nodes or dedicated TFTP servers, go to the applicable procedure.
Procedure
    Step 1   Replace the publisher node.
    Step 2   Replace any dedicated TFTP servers or other non-Cisco Unified Communications Manager cluster nodes.
    Step 3   Replace all backup subscriber nodes.
    Step 4   Replace all primary subscriber nodes.
    Step 5   Perform any remaining post-replacement tasks.
    Related Tasks
    Replace Publisher Node
    Replace Subscriber or Dedicated TFTP Server
    Complete Replacement

    Replace Publisher Node

    Complete the following tasks to replace the Cisco Unified Communications Manager publisher server. If you are replacing a single server that is not part of a cluster, follow this procedure to replace your server.

    Procedure
      Step 1   Perform the preparatory tasks.
      Step 2   Gather the necessary information about the old publisher server.
      Step 3   Back up the publisher server to a remote SFTP server by using Disaster Recovery System (DRS) and verify that you have a good backup.
      Step 4   Get new licenses of all the license types before system replacement.

      Get new licenses of all the license types: Software License Feature, CCM Node License Feature, and Phone License Feature.

      You only need a new license if you are replacing the publisher node.

      Step 5   Shut down and turn off the old server.
      Step 6   Connect the new server.
      Step 7   Install the same Cisco Unified Communications Manager release on the new server that was installed on the old server, including any Engineering Special releases. Configure the server as the publisher server for the cluster.
      Step 8   Restore backed-up data to the publisher server by using DRS.
      Step 9   Reboot all nodes in the cluster, starting with the subscriber nodes. Reboot the publisher node after all subscriber nodes finish rebooting. If the server is not in a cluster, then reboot the server.
      Step 10   Upload all of the new license files to the publisher server. Upload new license files for all of the license types: Software License Feature, CCM Node License Feature, and Phone License Feature.
      Step 11   Delete all invalid license files (those based on the old server MAC address).
      Step 12   Perform the post-replacement tasks.
      Related Tasks
      Before You Begin
      Install Software on Publisher Server
      Restore Backup File
      Upload License File
      Delete Invalid License Files
      Complete Replacement
      Related Information
      System Configuration Information
      Create Backup
      Obtain License File

      Replace Subscriber or Dedicated TFTP Server

      Complete the following tasks to replace a subscriber node or dedicated TFTP server (or another server type that is not a Cisco Unified Communications Manager server). A dedicated TFTP server is a node with Cisco Unified Communications Manager installed but with the Cisco Unified Communications Manager service disabled. The TFTP service runs as a dedicated TFTP server for the cluster.

      If you are also replacing the publisher node, you must replace it before replacing or reinstalling any other nodes. If the cluster uses backup subscriber nodes, replace or reinstall all backup subscriber nodes before replacing or reinstalling primary subscriber nodes.

      You can replace all backup subscriber nodes at the same time if this does not cause outages or oversubscription of primary subscriber nodes. You can replace all primary subscriber nodes at the same time if this does not cause outages or oversubscription of backup subscriber nodes.

      Follow the references in the For More Information column to get more information about a step.

      Procedure
        Step 1   Gather the necessary information about the old server.
        Step 2   If you are getting the system time from an NTP server, verify that the publisher node can synchronize with the NTP server before you install a subsequent node.
        Step 3   Shut down and turn off the old server.
        Step 4   Connect the new server.
        Step 5   Install the same Cisco Unified Communications Manager release on the new server that was installed on the old server, including any Engineering Special releases. Configure the new server to use the same configuration information as the old server.
        Step 6   Restore backed up data to the node by using DRS.
        Step 7   Reboot the new server.
        Step 8   Verify that the new server has the same number and status for all Critical services that you gathered before replacing the server.
        Step 9   Verify that the db Replicate state has a value of 2. This indicates that the database is set up on this node.
        Step 10   Perform the post-replacement tasks.
        Related Tasks
        Replace a Single Server or Cluster
        Install Software on Subscriber Server
        Restore Backup File
        Before You Begin
        Complete Replacement
        Replace Publisher Node
        Replace Subscriber or Dedicated TFTP Server
        Related Information
        System Configuration Information
        Verify NTP Status

        Replace MCS Hardware with Virtual Machines

        You can migrate an existing cluster of Unified Communication Manager nodes that are running on MCS hardware to a new virtualized cluster using the Cisco Prime Collaboration Deployment application. For information, see the Cisco Prime Collaboration Deployment Administration Guide.

        Replace a Virtual Machine and Migrate the Cluster

        You can migrate an existing cluster of virtualized Unified Communication Manager nodes to a new virtualized cluster using the Cisco Prime Collaboration Deployment application. For information, see the Cisco Prime Collaboration Deployment Administration Guide.