Data Migration Guide for LAN Management Solution 2.6 - Chapter 3: Migrating Data to LAN Management Solution 2.6 on Windows [CiscoWorks LAN Management Solution 3.2 and earlier]

Table Of Contents

Migrating Data to
LAN Management Solution 2.6 on Windows

Migrating Data from LMS 2.5/LMS 2.5.1

Local Migration from LMS 2.5/LMS 2.5.1

Remote Migration from LMS 2.5/LMS 2.5.1

Migrating Data for CS, RME, CM ,DFM and CV

Migrating Data for IPM

Migrating Data From LMS 2.1/LMS 2.2/RWAN 1.2/RWAN 1.3

Before You Begin Migration

Local Migration from LMS 2.1/LMS 2.2/RWAN 1.2/RWAN 1.3

Remote Migration From LMS 2.1/LMS 2.2/RWAN 1.2/RWAN 1.3

Understanding LMS Backup Files Created During CS Installation

Migrating Data to
LAN Management Solution 2.6 on Windows

This chapter describes the steps involved in migrating data for CiscoWorks LAN Management Solution (LMS) 2.6 on Windows.

This chapter has the following sections:

•Migrating Data from LMS 2.5/LMS 2.5.1

•Migrating Data From LMS 2.1/LMS 2.2/RWAN 1.2/RWAN 1.3

•Understanding LMS Backup Files Created During CS Installation

Migrating Data from LMS 2.5/LMS 2.5.1

This section explains the procedure for migrating data from LMS 2.5/LMS 2.5.1 to LMS 2.6.

Note LMS 2.5 users have to install LMS 2.5.1, before installing LMS 2.6

Figure 3-1 Migrating Data from LMS 2.5.1

You can migrate to LMS 2.6 in two ways:

•Local Migration from LMS 2.5/LMS 2.5.1

•Remote Migration from LMS 2.5/LMS 2.5.1

Local Migration from LMS 2.5/LMS 2.5.1

Install LMS 2.6 over LMS 2.5.1. The data from LMS 2.5.1 is automatically migrated to LMS 2.6 during installation. For details on installing LMS 2.6, see the Quick Start Guide for LAN Management Solution 2.6 (Maintenance Kit).

Remote Migration from LMS 2.5/LMS 2.5.1

This section explains the procedure for migrating data to a remote machine. It contains the following topics:

•Migrating Data for CS, RME, CM ,DFM and CV

•Migrating Data for IPM

In this section, the machine that has LMS 2.5.1 data is referred to as Machine A and the remote machine where you need to install LMS 2.6 and restore the data, is referred to as Machine B.

Migrating Data for CS, RME, CM ,DFM and CV

To migrate data to a remote machine:

Step 1 Login as administrator into Machine A.

Step 2 Back up CS, RME, CM and DFM data as follows:

•Using CLI:

Enter the following command:

NMSROOT\bin\perl NMSROOT\bin\backup.pl BKP num_generations

where num_generations is the maximum backup generations to be kept in the backup directory

If BKP is the backup directory, the data is stored in the directories BKP/1, BKP/3, and BKP/3 etc., where BKP/n stores the data of the nth generation.

Data is stored in BKP/0 if:

–Backup is done from CLI without specifying the num_generations.

–Immediate backup is done from GUI.

•Using GUI :

–Go to Common Services > Server > Admin >Backup.

–Click Help, and follow the instructions to back up your data.

Step 3 Login as administrator into Machine B.

Step 4 Install LMS 2.6.

Step 5 Copy the CS, RME, CM and DFM data from Machine A to any temporary location.

For CV, copy the user's device preference files from Machine A. The files are available at :
NMSROOT\MDC\tomcat\webapps\CVng\WEB-INF\classes\cvuserprefs\

The files have to be placed with the same directory structure in Machine B.

Step 6 Stop the daemon manager by entering:

net stop crmdmgtd

Step 7 Restore the backed up data by entering:

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP -gen generationNumber -t temporary_directory

For more details, see Syntax and Usage for Restore and Backup Script, page B-1.

Step 8 Examine the log file in the following location to verify that the database was restored.

The location is NMSROOT\log\restorebackup.log

Step 9 Start the daemon manager by entering:

net start crmdmgtd

Migrating Data for IPM

To migrate IPM data to a remote machine:

Step 1 Login as administrator into Machine A.

Step 2 Back up IPM data by entering the following command:

IPMServer\bin\ipm dbbackup

The data is backed up to the following location:

IPMServer\Sybase\Backup1

where, IPMServer is IPMROOT\Server and IPMROOT is the directory where you installed IPM.

Step 3 Login as administrator into Machine B.

Step 4 Copy the following seed files/directories from Machine A to Machine B:

–IPMServer\etc\source

–IPMServer\etc\target

–IPMServer\etc\collector

–IPMServer\etc\ipm.env

–IPMServer\etc\ipmDbPref.conf

–IPMServer\Server\htdocs\reports

Note Maintain the same directory structure while copying the files to Machine B.

Step 5 Copy the backed up IPM data from Machine A to the following location:

IPMServer\Sybase\Backup1

Step 6 Stop the IPM Processes by entering:

IPMServer\bin\ipm stop

Step 7 Restore the IPM data by entering:

IPMServer\bin\ipm dbrestore

Step 8 Restart IPM processes by entering:

IPMServer\bin\ipm start

Migrating Data From LMS 2.1/LMS 2.2/RWAN 1.2/RWAN 1.3

To migrate data from LMS 2.1/LMS 2.2:

Step 1 Install LMS 2.5.1

LMS 2.5.1 is a prerequisite for installing LMS 2.6. For more details on installation , see Quick Start Guide for LMS 2.5.1 available on Cisco.com at:

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/2.5.1/quickstart/guide/lms251qn.html

Step 2 Install LMS 2.6 and migrate data into it.

This section explains migration of data from LMS 2.1/LMS 2.2 and RWAN 1.2 and RWAN 1.3 to LMS 2.6. It contains the following topics:

•Before You Begin Migration

•Local Migration from LMS 2.1/LMS 2.2/RWAN 1.2/RWAN 1.3

•Remote Migration From LMS 2.1/LMS 2.2/RWAN 1.2/RWAN 1.3

Figure 3-2 Migrating Data From LMS 2.1/LMS 2.2/RWAN 1.2/RWAN 1.3

* Real-Time Monitor (RTM) and Access Control List Manager are not part of LMS 2.5.1.

You can migrate to LMS 2.5.1 in two ways—Local Migration or Remote Migration. For more details, see "Understanding Terms Used in the Data Migration Guide" section on page 1-3.

We recommend that you use Remote Migration to migrate to LMS 2.5.1.

Before You Begin Migration

When you attempt to restore your data during remote or local migration, you may see the following error message, and must follow the instructions in the message:

"ERROR: Unable to copy from backup archive folder to temporary folder POSSIBLE REASON:

Some files in the backup archive might not have enough permissions to read and copy.

SUGGESTION TO RESOLVE:

1. Open 'Windows Explorer'.

2. Right click on the generation folder (DB_BKP\0) and select 'Properties'

3. Click the 'Security tab'

4. Select/De-Select the allow/deny boxes so that you have permission to read

5. Click the 'Advanced button'

6. Enable the 'Reset permissions on all child objects.......' check boxes.

7. Click 'Apply', and 'OK' Button

Try doing the restore again, you should succeed."

Figure 3-3 describes the steps involved in local migration from LMS 2.1/LMS 1.2/RWAN 1.2.

Figure 3-3 Steps for Migration from LMS 2.1/LMS 2.2/RWAN 1.2/ RWAN 1.3

Local Migration from LMS 2.1/LMS 2.2/RWAN 1.2/RWAN 1.3

To migrate data on the same machine:

Step 1 Login as administrator to the machine where LMS is installed.

Step 2 Set the permissions on the backup folder as described in "Before You Begin Migration" section.

Step 3 Verify that your operating system is supported for LMS 2.6. For details on OS platforms supported by LMS 2.6, see "System Requirements" section on page 1-2.

Step 4 Install Common Services 3.0.3 which is a part of LMS 2.5.1.

CS 3.0.3 installer prompts you for a backup directory during local migration, and automatically does a backup. The automatic backup facility only backs up data for CS, RME, CM, and DFM. It does not back up the data for IPM.

Step 5 Install one or more of the required LMS 2.5.1applications.

We recommend that you upgrade all the applications that were in LMS 2.1/LMS2.2/RWAN 1.2/RWAN 1.3.

At the end of RME installation, the following warning message appears. You may ignore them.

=======- Possible Warnings/Errors Encountered - =======

WARNING: Please install/upgrade all the required apps

WARNING: in the bundle and then run the migration scripts

[...]

==========================================================

Data for CS, CM, and IPM are automatically migrated when you upgrade the respective applications.

Step 6 Install LMS 2.6. The data from LMS 2.5.1 is automatically migrated to LMS 2.6 during installation. For details on installing LMS 2.6, see the Quick Start Guide for LAN Management Solution 2.6 (Maintenance Kit).

Step 7 If you are upgrading RME and/or DFM, stop the daemon manager by entering:

net stop crmdmgtd

Step 8 Restore the LMS data by entering:

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP -gen generationNumber -t temporary_directory

For more details, see "Syntax and Usage for Restore and Backup Script" section on page B-1.

Data for all applications except IPM are migrated now. The restorebackup.pl script overwrirtes the already existing data for CS, CM, RME, and DFM.

If there is a mismatch in the applications installed and the applications in the backup archive, the following warning messages appear:
WARNING: There is a mismatch between the list of applications 
installed in this machine and the list of applications present in the 
backup archive. The application data from the backup archive will get 
restored only if that application is installed in this machine. Do you 
want to continue the Restore operation?  (y-continue or n-quit, y/n)?y 
Applications to be restored are............ : [Common Services] [Campus Manager] [Resource Manager Essentials] [Device Fault Manager]

Step 9 Examine the log file in the following location to verify that the database was restored.

The location is NMSROOT\log\restorebackup.log

Step 10 Start the daemon manager by entering:

net start crmdmgtd

Remote Migration From LMS 2.1/LMS 2.2/RWAN 1.2/RWAN 1.3

In this section, the machine that has LMS 2.1/LMS 2.2 data is referred to as Machine A and the remote machine where you need to install LMS 2.6 and restore the data, is referred to as Machine B.

To migrate data:

Step 1 Login as administrator into Machine A.

Step 2 Set the permissions of the backup folder as described in "Before You Begin Migration" section.

Step 3 Back up your LMS data. To do this you need to back up CS, RME, DFM, and CM data. You can do this either by:

•Using CLI:

–Enter the following command:

NMSROOT\bin\perl NMSROOT\bin\backup.pl BKP num_generations

For details, see "Syntax and Usage for Backup Script" section on page A-1.

where num_generations is the maximum backup generations to be kept in the backup directory

If BKP is the backup directory, the data is stored in the directories BKP\1, BKP\2, and BKP\3 etc., where BKP\n stores the data of the nth generation.

Data is stored in BKP/0 if:

–Backup is done from CLI without specifying the num_generations.

–Immediate backup is done from GUI.

Or

•Using GUI:

–Using the CD One, Fifth Edition Administration GUI go to Server Configuration > Administration > Database Management > Back Up Data Now.

–Click Help, and follow the instructions to back up your data.

If you are upgrading IPM, create the necessary backup files.

To take a backup, run rbackup.exe from the IPM 2.6 CD-ROM root directory.

This stops all IPM servers that are running and takes a backup of the database, the seed files, the environment variables, and the version information.

While running rbackup.exe, the default backup directory is the
backup directory under the IPM installation root directory. However, you can specify any directory.

When using a custom directory, some of the files do not have proper permissions. While you move these files to remote machine, you need to manually modify their permissions.

Step 4 Login as administrator into Machine B.

Step 5 Install LMS 2.5.1.

You must first install Common Services (CS 3.0.3), then optionally install one or more of the required LMS applications.

Step 6 Install LMS 2.6.

If you are upgrading to DFM 2.0.6, assemble the files needed for DFM migration or else proceed to Step 7.

a. Copy the DFM 2.0.6 Upgrade Kit from Machine B to a directory say dir.

The upgrade kit named cw-dfm-20-UpgradeKit-win.zip is available at NMSROOT\bin\ in Machine B. It contains the DFMMigrate.pl script and other required files.

b. Locate your copy of the 1.2.x DFM.rps file. It is normally located in NMSROOT\objects\smarts\repos\icf\.

If you plan to use a copy of this file that was created during a backup, the file will be located in the backup directory you specified when using CiscoWorks Common Services or CiscoWorks 2000 CD One.

Caution Do not rename the DFM.rps file, otherwise Step c will fail.

c. Use the DFMMigrate.pl script to create the required migration files.

–Move to the directory dir, into which you copied the cw-dfm-20UpgradeKit-win.zip file.

–Unzip the file. It creates a directory called cw-dfm-20-UpgradeKit-win.

–Change to the directory where DFMMigrate.pl is located. In this case, it is dir\cw-dfm-20-UpgradeKit-win\smarts\

–Run the DFMMigrate.pl script:
NMSROOT\bin\perl  dir\cw-dfm-20-UpgradeKit-win\smarts\ 
DFMMigrate.pl -n NMSROOT -o DFM.rps_directory
The command variables are:

NMSROOT

CiscoWorks installation directory (by default, C:\Program Files\CSCOpx).

DFM.rps_directory

Full pathname of directory containing DFM 1.2.x DFM.rps file. For DFM 1.2.x installations, this file is located in NMSROOT\objects\smarts\repos\icf\
For example (the following command is one line):
C:\Progra~1\CSCOpx\bin\perl   dir\cw-dfm-20-UpgradeKit-win\smarts\ 
DFMMigrate.pl   -n C:\Progra~1\CSCOpx   -o C:\Progra~1\CSCOpx\objects\ 
smarts\repos\icf\
This creates the text files ICseed.txt, ICinventory.txt, and ICptm.xml and places them in dir\cw-dfm-20-UpgradeKit-win\smarts\conf.

Step 7 Copy the LMS data from Machine A to any temporary location in Machine B as follows:

a. For CS,CM, RME, and DFM, copy the BKP directory that you created in Step 3a.

b. For IPM, copy the backup directory that you created in Step 3b.

c. For DFM, copy the following files .

File Name

Location in LMS 2.1

Copy into this location in LMS 2.5.1

ICseed.txt

dir\cw-dfm-20-UpgradeKit-win\
smarts\conf

NMSROOT\objects\smarts\conf

ICinventory.txt

ICptm.xml

mail_notify.conf

NMSROOT\objects\smarts\conf\
notifier

NMSROOT\objects\smarts\conf\notifier

trap_notify.conf

Note For CV, no data will be migrated from LMS 2.1/LMS 2.2 to LMS 2.6

Step 8 Stop the daemon manager by entering:

net stop crmdmgtd

Step 9 Restore CS, CM, DFM, and RME data by entering:

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP -gen generationNumber -t temporary_directory

For more details, see "Syntax and Usage for Restore and Backup Script" section on page B-1.

If you created IPM backup data, restore it as follows:

a. Copy the entire contents in this directory to the backup directory under the directory where you have installed IPM 2.6.

b. Change your working directory to the bin directory of the IPM server.

c. Make sure that the License Server process (called LicenseServer) is up and running. (Server Configuration > Administration > Process Management > Process Status)

d. Run ipm upgrade at the command prompt.

IPM data is now migrated.

Step 10 Examine the log file in the following location to verify that the database was restored.

The location is NMSROOT\log\restorebackup.log

Step 11 Start the daemon manager by entering:

net start crmdmgtd

Understanding LMS Backup Files Created During CS Installation

If DB_BKP is the directory you gave during the CS installation process, the location of the backup directory and structures are as follows:

•DB_BKP\automaticbackup\cmfbackup

•DB_BKP\automaticbackup\mcbackup

The DB_BKP\automaticbackup\cmfbackup directory and the DB_BKP\automaticbackup\mcbackup directory are used to store LMS backup data and VMS backup data respectively.

VMS is another solutions bundle available from Cisco. VMS applications are sometimes known as MC or Monitoring Center applications, hence the mc in the directory name.

If the DB_BKP\automaticbackup\mcbackup directory is empty, there are no VMS based applications installed in the machine.

To restore data on LMS 2.5.1 Server, you should specify DB_BKP\automaticbackup\cmfbackup as the backup directory.

Table 3-1 Restoring LMS Data from Backup

To restore...

Enter...

The most recent version of LMS backup data

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d DB_BKP\automaticbackup\
cmfbackup

The nth generation of LMS backup data

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d DB_BKP\automaticbackup\
cmfbackup -gen n

The 1st generation of LMS backup data

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d DB_BKP\automaticbackup\
cmfbackup -gen now

The 3rd generation of LMS backup data

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d DB_BKP\automaticbackup\
cmfbackup -gen 3