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:
Note This command does not apply when you are backing up the Prime USM data.
Step 2 Run the following command and provide a password:
/bin/dbpasswd.pl dsn=qovr npwd=
is the installation directory
Step 3 Run the following command:
Step 4 After the backup is complete, verify if qovr.db is backed-up in the following directory:
If this is not present, copy it manually from:
If qovr.log is present, copy the file into
Step 5 Copy the creds file from
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:
Step 3 Install the QOVR DB.
Step 4 Run:
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/dbpasswd.pl dsn=qovr npwd=
Provide the same password that you entered in Step 2 of the backup procedure.
Step 5 Run the migration script:
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:
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:
saves the managed states of
monitored and partially monitored devices to the inventoryBackup file. No user input is needed while the script is running.
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:
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.
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:
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
This creates the qovr.log file and starts the QOVRDbEngine process.
Step 3 Stop the daemon manger. To do this, run:
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:
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
Step 2 Copy the Operations Manager and Service Monitor licenses from
is the directory in which you have installed Operations Manager. You must copy the
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
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.