Table Of Contents
Migrating QPM
Migrating to a New QPM Server on Solaris
Exporting and Importing QPM Application Data
Exporting QPM Application Data
Importing QPM Application Data
Migrating QPM
This chapter contains the following topics:
•
Migrating to a New QPM Server on Solaris
•
Exporting and Importing QPM Application Data
Migrating to a New QPM Server on Solaris
You can migrate QPM application data from one QPM 4.0 server to another. This section describes the sequence of tasks for migrating QPM 4.0 information to a new QPM server running Solaris.
Note
You need to buy a new license for remote migration beacuse QPM license is a node-lock license. Also, the device limit with the new license should be equal to or more than the device limit supported by the old server.
To migrate to a new QPM 4.0 server:
Step 1
Take a backup of the CS 3.0.5 data using the Common Services Backup utility (available in QPM 4.0 under Administration > Configuration Backup).
Step 2
Export all QPM 4.0 application data from the old QPM server using the export.pl utility either in the QPM DVD or in the QPM installation folder.
See Exporting QPM Application Data for details.
Step 3
Copy the CS backup data and the QPM export data to the new server.
Step 4
Install CiscoWorks Common Services 3.0.5 on the new server.
See Installing Common Services on Solaris, page 2-2
Step 5
Install QPM 4.0. on the new server.
See Installing QPM on Solaris, page 2-7 for details.
Step 6
Execute the CSrestorebackup.pl script (in CS 3.0.5) in the new server to restore the CS data.
Step 7
Import the QPM 4.0 application data to the new server using the import.pl utility in the QPM installation folder in the new server.
See Importing QPM Application Data for details.
Before you begin to work with QPM, ensure that you have the appropriate permissions. See Chapter 3, "Setting Up the QPM Server" for details.
If you are working with ACS user permissions, register the new QPM server in CiscoWorks and ACS. See Setting up ACS User Groups and Permissions for QPM, page 3-11 for details.
Exporting and Importing QPM Application Data
The following topics describe how to use the QPM export and import utilities:
•
Exporting QPM Application Data
•
Importing QPM Application Data
Note
The export utility is available on the QPM installation DVD, and is also copied to the QPM server during the installation process. The import utility will be available in the QPM server after the installation.
Exporting QPM Application Data
You can export the following QPM application data:
•
QPM database containing device and policy information
•
QPM monitoring task information
•
QPM reports
•
QPM configuration information
Use the export utility when you want to migrate QPM application data from one QPM 4.0 server to another.
You must specify the destination folder to which you want the data exported.
To export the application data, go to the root directory and enter the following commands to start the export utility:
# cd /opt/CSCOpx/MDC/qpm/bin
# /opt/CSCOpx/bin/perl export.pl destination directory
where /opt/CSCOpx is the default installation directory, and destination directory is the directory to which you want to export the data.
The utility stops CiscoWorks services, and exports the QPM data. When the export process is completed, the CiscoWorks services are restarted
Importing QPM Application Data
Use the import.pl utility to import the QPM application data that was exported from QPM.
Note
The exported data is platform dependent. Therefore you cannot import the QPM data onto a Solaris server if this data was exported from a Windows server.
When you use the import utility, any existing QPM data is overwritten.
To import the application data, go to the root directory and enter the following commands to start the import utility:
# cd /opt/CSCOpx/MDC/qpm/bin
# /opt/CSCOpx/bin/perl import.pl export directory
where /opt/CSCOpx is the default installation directory, and export directory is the directory that contains the exported data.
The utility stops CiscoWorks services, and imports the QPM data. When the import process completes, the CiscoWorks services are restarted.