Cisco Prime Collaboration Upgrade and Migration Guide, 10.0
Migrating from Cisco Unified Communications Management Suite
Downloads: This chapterpdf (PDF - 270.0KB) The complete bookPDF (PDF - 586.0KB) | Feedback

Table of Contents

Migrating from Cisco Unified Communications Management Suite

Migrating Data from Prime UOM and Prime USM

Backing Up Prime UOM and Prime USM

Restoring the Prime UOM and Prime USM Backup on

Backing Up and Restoring DDV Configurations Using Utilities

Post-Migration Tasks for Prime UOM and Prime USM

Migrating Licenses from Cisco Unified Operations Manager and Cisco Unified Service Monitor 2.x/8.0/8.5/8.6 to Prime Collaboration

Migration Script Messages

Migrating from Cisco Unified Communications Management Suite

This section details the procedure for migrating data from Prime UOM and Prime USM application to Prime Collaboration. Review the Migrating to Prime Collaboration section before you start with the migration procedures.


Note Migration from Cisco Prime Unified Provisioning Manager 9.0 and Cisco Prime Collaboration Manager 1.2 to Prime Collaboration 10.0 is not supported. If you want to upgrade to Prime Collaboration 10.0, you must first upgrade to Prime Collaboration 9.5. See Cisco Prime Collaboration Upgrade and Migration Guide 9.5 for details.


Migrating Data from Prime UOM and Prime USM

You can migrate data from:

  • Prime UOM standalone installation
  • Prime UOM and Prime USM coresident installation
  • Prime UOM and Prime USM coexistent installation

Note Migration is not supported from a standalone Prime USM installation, unless it is part of a coexistent setup.


To migrate to Prime Collaboration from Prime UOM:

1. Install Prime Collaboration on a virtualized server

2. Back up Prime UOM/Prime USM data.

If you have made customizations and want to preserve the managed state information in the detailed Device View, you must back up Detailed Device View configurations and restore them separately. See Backing Up and Restoring DDV Configurations Using Prime UOM Utilities.

3. Restore the backed-up data on the Prime Collaboration server.


Note If Prime UOM and Prime USM are in coexistent mode, you must first migrate Prime USM, and then migrate Prime UOM.


Backing Up Prime UOM and Prime USM

To back up Prime UOM and Prime USM:


Step 1 Run the following commands to stop the processes:

  • net stop OMHealthMonitor

Note This command does not apply when you are backing up the Prime USM data.


  • net stop CRMDMgtd

Step 2 Run the following command and provide a password:

NMSROOT /bin/perl NMSROOT /bin/dbpasswd.pl dsn=qovr npwd= password

NMSROOT is the installation directory .

Step 3 Run the following command:

NMSROOT /bin/perl NMSROOT /bin/backup.pl BackupDirectory

Step 4 After the backup is complete, verify if qovr.db is backed-up in the following directory:

BackupDirectory /0/qovr/database

If this is not present, copy it manually from:

NMSROOT /databases/qovr/qovr.db

If qovr.log is present, copy the file into BackupDirectory /0/qovr/database.

Step 5 Copy the creds file from NMSROOT /qovr/config/ptm to BackupFolder /0/qovr.


Note This step applies only for coexistent or coresident installations of Prime UOM and Prime USM.


Step 6 Copy the backup folder to the Prime Collaboration server. (If you use FTP or SFTP, we recommend that you copy the file in binary mode.)

It is important to copy the backup to the /opt folder, which has the space needed for the operation.


 

Restoring the Prime UOM and Prime USM Backup on Prime Collaboration

Prime Collaboration installation includes a migration script that enables you to restore the backup.

To restore the backup:


Step 1 Log in to the server as root via SSH, using port 26.

Step 2 Run the following command to stop the processes:

/opt/emms/emsam/bin/cpcmcontrol.sh stop

Step 3 Install the QOVR DB.

/opt/CSCOpx/bin/qovrDbInstall.sh

Step 4 Run:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/dbpasswd.pl dsn=qovr npwd= password

Provide the same password that you entered in Step 2 of the backup procedure.

Step 5 Run the migration script:

/opt/CSCOpx/bin/PC-MigrationTool.sh

Enter your choice from the following options:

    • 1— Cisco Prime Operations Manager/Service Monitor (Co-Resident)
    • 2— Cisco Prime Operations Manager (Standalone)
    • 3—Cisco Prime Service Monitor (Standalone)

Note If you are migrating a coexistent installation, first run the script after choosing option 3, and then run the script again with option 2. You must not restart the processes until both backups are restored.


Review the Migration Script Messages section for details about the messages that are displayed during the migration.

Step 6 Provide the location of the backup.

Step 7 After the operation completes, restart the processes:

/opt/emms/emsam/bin/cpcmcontrol.sh start


Note When you are migrating a coexistent installation, you must not restart the processes until the Prime UOM restore is done.



 


Note If you do not need to back up the DDV, you may proceed with the post-migration tasks. See Post-Migration Tasks for Prime UOM and Prime USM.


Backing Up and Restoring DDV Configurations Using Prime UOM Utilities

The Prime UOM backup utility backs up the states of all components of all types of monitored or partially monitored devices in the Detailed Device View (DDV). The backup utility does not cover suspended devices.


Note Ensure that the daemon processes for the system are up and running to allow for data backup.


To run the backup utility:


Step 1 Open a DOS prompt and enter:

% PROGRA~1\CSCOpx\objects\vhm\utilities\inventoryBackup default

Where default saves the managed states of all monitored and partially monitored devices to the inventoryBackup file. No user input is needed while the script is running.


Caution Backup on a network drive is not supported. Although the CLI is functional, we recommend you do not use it because of network connectivity issues. As a result, the mapped network drive on the server will not be available for selection in the user interface.

If you prefer to enter a specific filename or a list of specific device IP addresses, enter:

% PROGRA~1\CSCOpx\objects\vhm\utilities\inventoryBackup

The script prompts you to enter the filename and device information.

Step 2 Transfer the file to the Prime Collaboration server using FTP. We recommend that you copy in binary mode.


Caution After you migrate to Prime Collaboration, you can run the inventoryRestore script only after rediscovering all devices. During device rediscovery, the system may be under a heavy load, resulting in the user interface becoming unresponsive. The dashboards may not refresh during this time. We recommend that you wait to perform any user interface action until device discovery is complete.

Step 3 To restore, run:

/opt/CSCOpx/objects/vhm/utilities/inventoryRestore.sh filename


 

Resolving QOVR DB Issue

Sometimes, QOVRDbEngine will not come up after migration from Prime UOM 9.0 to Prime Collaboration 10.0. This is observed when there is an issue in taking the backup of qovr.log file. To resolve this issue:


Step 1 Remove the qovr.log file from /opt/CSCOpx/databases/qovr.

Step 2 Start the QOVRDbEngine process using the command pdexec QOVRDbEngine .

This creates the qovr.log file and starts the QOVRDbEngine process.

Step 3 Stop the daemon manger. To do this, run:

./cpcmcontrol.sh stop


Note You must wait till the process gets completely shut down. This operation might take a few minutes to complete.


Step 4 Start the daemon manager. To do this, run:

./cpcmcontrol.sh start


 

Post-Migration Tasks for Prime UOM and Prime USM

After you complete running the migration script, you might need to wait for about 30 minutes before Prime Collaboration is ready to proceed with the post-migration tasks.

See Getting Started with Prime Collaboration and Feature Support After Migration—Prime Collaboration Assurance for information about feature availability and post-migration tasks.

Migrating Licenses from Cisco Unified Operations Manager and
Cisco Unified Service Monitor 2.x/8.0/8.5/8.6 to Prime Collaboration

Data migration is not supported from Operations Manager and Service Monitor 2.x/8.0/8.5/8.6 to Prime Collaboration. You can only migrate the licenses.

To migrate the licenses:


Step 1 Install Prime Collaboration. See Quick Start Guide for Prime Collaboration 10.0 for details.

Step 2 Copy the Operations Manager and Service Monitor licenses from
<install directory> /CSCOpx/etc/licenses.

<install directory> is the directory in which you have installed Operations Manager. You must copy the .lic files.

Step 3 Transfer the files using SFTP to the /opt/CSCOpx/etc/licenses directory in the Prime Collaboration server.


Note Use Port 26 when you do SFTP to the Prime Collaboration server.


Step 4 Add the Prime Collaboration 10.0 upgrade license via the Prime Collaboration UI. See the Managing Licenses chapter in the Prime Collaboration 10.0 Assurance - Advanced Guide for details.

Step 5 (Optional) Add Prime Collaboration incremental license, if you want to manage additional end points than supported by the current license.

Step 6 (Optional) If you want to use Analytics, add the Analytics license that would enable you to manage the same or higher ed point count than Assurance.


 

Migration Script Messages

Table 3-1 lists the messages that the migration script displays, and provides additional information about these messages.

 

Table 3-1 Migration Messages

Message
Notes

The license details in the server are different from the backup data. After restoring, please check the license available in the server.

Your current license count is lower than your earlier license count. If you restore the data now, devices that exceed the current licence count will be moved to Suspended state.

Cannot evaluate the hostname, hence the certificate may be from this host or another host.

You have selected to migrate Cisco Prime Operations Manager (Standalone)

If you are having Cisco Prime Operations Manager (Standalone) and Cisco Prime Service Monitor (Standalone) in different servers in co-existent Model

You need to first migrate Cisco Prime Service Monitor (Standalone) followed by Cisco Prime Operations Manager (Standalone)

Are you sure you want to continue to migrate Cisco Prime Operations Manager (Standalone)

When you migrate a coexistent installation of Prime UOM and Prime USM, ensure that you first select option 3 to migrate Prime USM, and then select option 2 to migrate Prime UOM.

You must restart the processes only after the Prime UOM restore is complete.

The backup archive is from a different OS. Your current Platform is: Soft Appliance. You are attempting to perform a Cross Platform Restore.

The list of applications installed on this CiscoWorks server does not match the list of applications in the backup archive. If you restore data from this backup archive, it may cause problems in the CiscoWorks applications.

Do you want to continue the restore operation?

You may ignore this message.

Licenses can also be restored, do you want to restore Licenses?

To make sure all the existing devices go to the managed state, you need to perform rediscovery after restore.