Guest

Cisco Unity

Unity 4.0(5) or Later to Cisco Unity Connection 8.x Flash Cutover Migration Guide

Document ID: 112976

Updated: May 16, 2011

   Print

Introduction

This document describes how to migrate user data and, optionally, voice messages from a Cisco Unity 4.0(5) or later system to Cisco Unity Connection 8.x. In order to complete the migration, you must use COBRAS (Cisco Objected Backup and Restore Application Suite) to export the user data from the Cisco Unity system.

Note: Cisco recommends that you allow the Cisco Unity servers to run for a few weeks so users can continue to access messages that were left before the migration.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco Unity 4.0(5) or Later

  • Cisco Unity Connection 8.x

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Background Information

Consolidated Object Backup and Restore Application Suite (COBRAS) is a set of tools designed to allow administrators to back up all subscribers, call handlers, interview handlers, name lookup handlers, public distribution lists, and schedules and to restore some or all of that information onto another Cisco Unity or Cisco Unity Connection server. COBRAS is specifically designed to allow for partial restores, restores onto different versions or products than the version that was backed up, and merges of data from multiple system backups. This tool does not provide the same functionality as DiRT (Disaster Recovery Tools) for Unity or the DRS (Disaster Recovery Service) built into Unity Connection in that it does not do a full backup of the entire database and it does not restore it all together on a new server.

Note: If the Cisco Unity server is configured as unified messaging, migrating messages is discouraged because of the following behaviors:

  • Two copies of migrated messages appear in the Microsoft Exchange mailbox for each user: the original message and the migrated message that is synchronized into the Exchange mailbox when a single inbox is configured.

  • If a user uses Microsoft Outlook to play the original message in Exchange (the copy that Cisco Unity put into Exchange when the message was received), the message remains unread in Unity Connection, and the message waiting indicator remains on. This issue occurs only with migrated messages. Playing the migrated message (the copy that was synchronized into the Exchange mailbox by the single inbox feature) or playing messages that are received after the migration turns off the message waiting indicator on the new extension as appropriate.

Procedure

Complete the steps described in this procedure in order to successfully migrate to Unity Connection 8.x.

Note: These tasks reference detailed instructions in other Unity Connection documentation as noted. Refer to the appropriate documentation for a successful migration.

  1. If you use the current Cisco Unity server rather than installing a new server, review the applicable Cisco Unity Connection 8.x Supported Platforms List to determine whether the server requires replacement hard disks or additional RAM.

  2. Copy or obtain reissued Cisco Unity license files, and obtain a Unity Connection upgrade license:

    1. Obtain reissued Cisco Unity license files with the MAC address of the new Cisco Unity Connection server.

    2. Save the reissued license files to a network location. Do not install the license files now; you do so later in the migration process.

    3. Obtain a Unity Connection upgrade license, which enables Unity Connection 8.x and is required for Unity Connection-specific features.

  3. Review the Requirements for Migrating from Cisco Unity 4.0(5) or Later to Cisco Unity Connection Version 8.x section of System Requirements for Cisco Unity Connection 8.x.

  4. Download these tools:

  5. Install the tools that you downloaded in step 4.

    • Install the Cisco Unity Disaster Recovery Backup tool on the secondary server.

    • Install all other tools on the active server, regardless of whether the active server is the primary or secondary server.

  6. Use the Cisco Unity Disaster Recovery tools to back up the server. This backup will not be used to restore data on the Unity Connection 8.x system; Cisco recommends it only so you can revert to Cisco Unity if necessary.

  7. Use COBRAS to export Cisco Unity data and, optionally, voice messages.

    • If you configured a single inbox and if Cisco Unity is configured as unified messaging, Unity Connection voice messages that are synchronized to Exchange are saved in the same mailbox in which Cisco Unity voice messages are now stored. In this case, Cisco recommends that you select the Include Corporate Email Addresses from Backup for New User Creation check box in COBRAS.

      When you restore Cisco Unity data on the Unity Connection server, the Exchange email addresses associated with Cisco Unity users are saved in the Corporate Email Address field on the User Basics page in Cisco Unity Connection Administration, which simplifies configuration of a single inbox later in the migration process.

      unityupgrade-01.gif

  8. If additional memory or replacement hard disks are required, add memory or replace hard disks.

  9. Install and begin the Unity Connection 8.x configuration. The configuration steps are described in Installation Guide for Cisco Unity Connection Release 8.x.

  10. Use COBRAS in order to restore Cisco Unity data on the Unity Connection server. For more information, refer to Cisco Unified Backup and Restore Application Suite (COBRAS). In addition, log in to CUC 8.x and make sure that the DB Proxy service is running

    • Any tool that needs to connect to the Unity Connection 2.1(1) or later database must have the IBM Informix ODBC drivers installed to be able to connect. Visit the Informix ODBC Drivers web page in order to download the drivers.

    • Any Cisco Unity export of any version can also be imported onto Connection 7.x or later. A Unity Connection export, however, can not be imported into any version of Cisco Unity.

  11. Complete the Unity Connection 8.x. configuration.

  12. Lauch Cobra import and connect to Unity Connection 8.x server.

  13. Test Unity Connection in order to confirm that the migration was successful.

Related Information

Updated: May 16, 2011
Document ID: 112976