Data Migration Guide for LAN Management Solution 3.0 - Chapter 3: Migrating Data to LAN Management Solution 3.0 on Windows [CiscoWorks LAN Management Solution]

Table Of Contents

Migrating Data to LAN Management Solution 3.0 on Windows

Migrating Data From LMS 2.6 or LMS 2.5.1

Local Migration From LMS 2.6 or LMS 2.5.1

Remote Migration From LMS 2.6 or LMS 2.5.1

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

Migrating Data From LMS 2.5

Remote Migration From LMS 2.5

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

Migrating Data From LMS 2.2 or RWAN 1.3

Remote Migration From LMS 2.2 or RWAN 1.3

Before You Begin Migration

Migration From LMS 2.2 or RWAN 1.3

Migrating Data to LAN Management Solution 3.0 on Windows

This chapter describes how to migrate data to CiscoWorks LAN Management Solution (LMS) 3.0 on Windows.

This chapter has the following sections:

•Migrating Data From LMS 2.6 or LMS 2.5.1

•Migrating Data From LMS 2.5

•Migrating Data From LMS 2.2 or RWAN 1.3

Migrating Data From LMS 2.6 or LMS 2.5.1

This section explains how to migrate data from LMS 2.6 or LMS 2.5.1 to LMS 3.0.

You can migrate to LMS 3.0 in two ways:

•Local Migration From LMS 2.6 or LMS 2.5.1

•Remote Migration From LMS 2.6 or LMS 2.5.1

Figure 3-1 Migrating Data From LMS2.6 or LMS 2.5.1

Local Migration From LMS 2.6 or LMS 2.5.1

Install LMS 3.0 over LMS 2.6 or LMS 2.5.1. The data for CS, RME, CM, DFM, and CV is automatically migrated during installation.

For IPM, run the following command:

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP [-t temporary_directory]

where BKP is the backup directory. It is created either by running the wrapper.pl or during inline upgrade.

You must give the complete path for BKP. For example, if BKP is under C:\, give the path as C:\BKP.

Before upgrading LMS, make sure to upgrade to the supported version of the OS.

For details on Supported OS, see the Installing and Getting Started with CiscoWorks LAN Management Solution 3.0 (Maintenance Kit).

Remote Migration From LMS 2.6 or LMS 2.5.1

This section explains the procedure of Migrating Data for CS, RME, CM, DFM, IPM and CV to a remote machine.

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

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

To migrate data to a remote machine:

Step 1 Login as administrator into Machine A.

Step 2 From LMS 3.0 DVD, locate the WindowsLMSBackup.tar file under disk 1 directory.

Step 3 Copy the file (WindowsLMSBackup.tar) to a directory (dir1) in the local server.

The tar file contains wrapper.pl and other required files.

Step 4 Untar the file to get wrapper.pl

Step 5 Back up CS, RME, CM, IPM, DFM, and CV data.

To do this using CLI, enter the following command:

NMSROOT\bin\perl dir1\wrapper.pl BKP

where BKP is the backup directory and dir1 is the directory containing wrapper.pl.

You must give the complete path for dir1 and BKP. For example, if BKP is under C:\, give the path as C:\BKP.

Step 6 Login as administrator into Machine B.

Step 7 Install LMS 3.0.

Step 8 Copy the backup directory BKP that contains the CS, RME, CM, IPM and DFM data from Machine A to any temporary location.

Note You can preserve the time stamp of the files by entering the option -p with the copy command: cp -r -p <source> <destination>.

Step 9 Stop the daemon manager by entering:

net stop crmdmgtd

Step 10 Restore the backed up data by entering:

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP [-t temporary_directory]

where BKP is the backup directory.

You must give the complete path for BKP. For example, if BKP is under C:\, give the path as C:\BKP.

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

Step 11 Examine the log files in the following location to verify that the database was restored.The files are:

NMSROOT\log\restorebackup.log

NMSROOT\log\migration.log

NMSROOT\log\rme_base.log

NMSROOT\log\ipm_base.log

Note Migration.log will be created only when either RME or IPM is migrated.

Step 12 Start the daemon manager by entering:

net start crmdmgtd

Migrating Data From LMS 2.5

This section explains how to migrate data from LMS 2.5 to LMS 3.0.

You can migrate to LMS 3.0 only through Remote Migration.

Note Local Migration of data from LMS 2.5 to LMS 3.0 is not supported.

Figure 3-2 Migrating Data From LMS 2.5

Remote Migration From LMS 2.5

This section explains the procedure of Migrating Data for CS, RME, CM, DFM, IPM and CV to a remote machine.

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

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

To migrate data to a remote machine:

Step 1 Login as administrator into Machine A.

Step 2 From LMS 3.0 DVD, locate the WindowsLMSBackup.tar file under disk 1 directory.

Step 3 Copy the file (WindowsLMSBackup.tar) to a directory (dir1) in the local server.

The tar file contains wrapper.pl and other required files.

Step 4 Untar the file to get wrapper.pl

Step 5 Back up CS, RME, CM, IPM, DFM, and CV data.

To do this using CLI, enter the following command:

NMSROOT\bin\perl dir1\wrapper.pl BKP

where BKP is the backup directory and dir1 is the directory containing wrapper.pl.

You must give the complete path for dir1 and BKP. For example, if BKP is under C:\, give the path as C:\BKP.

Step 6 Login as administrator into Machine B.

Step 7 Install LMS 3.0.

Step 8 Copy the backup directory BKP that contains the CS, RME, CM, IPM, DFM, and CV data from Machine A to any temporary location.

Note You can preserve the time stamp of the files by entering the option -p with the copy command: cp -r -p <source> <destination>.

Step 9 Stop the daemon manager by entering:

net stop crmdmgtd

Step 10 Restore the backed up data by entering:

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP [-t temporary_directory]

where BKP is the backup directory.

You must give the complete path for BKP. For example, if BKP is under C:\, give the path as C:\BKP.

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

Step 11 Examine the log files in the following location to verify that the database was restored.The files are:

•NMSROOT\log\restorebackup.log

•NMSROOT\log\migration.log

•NMSROOT\log\rme_base.log

•NMSROOT\log\ipm_base.log

Note Migration.log will be created only when either RME or IPM is migrated.

Step 12 Start the daemon manager by entering:

net start crmdmgtd

Migrating Data From LMS 2.2 or RWAN 1.3

This section explains how to migrate data from LMS 2.2 or RWAN 1.3 to LMS 3.0.

You can migrate to LMS 3.0 only through Remote Migration.

Note Local Migration of data from LMS 2.2 or RWAN 1.3 to LMS 3.0 is not supported.

Figure 3-3 Migrating Data From LMS 2.2 or RWAN 1.3

Remote Migration From LMS 2.2 or RWAN 1.3

This section explains the remote migration of data from LMS 2.2 or RWAN 1.3 to LMS 3.0. It contains the following topics:

•Before You Begin Migration

•Migration From LMS 2.2 or RWAN 1.3

Before You Begin Migration

When you attempt to restore your data during remote 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-4 describes the procedure to migrate from LMS 2.2 or RWAN 1.3.

Figure 3-4 Steps for Migration From LMS 2.2 or RWAN 1.3

Migration From LMS 2.2 or RWAN 1.3

In this section, the machine that has LMS 2.2 or RWAN 1.3 data is referred to as Machine A and the remote machine where you need to install LMS 3.0 and restore the data, is referred to as Machine B.

To migrate data:

Step 1 Login as administrator into Machine A.

Step 2 From LMS 3.0 DVD, locate WindowsLMSBackup.tar file under disk 1 directory.

Step 3 Copy the file (WindowsLMSBackup.tar) to a directory (dir1) in the local server.

The tar file contains wrapper.pl and other required files.

Step 4 Untar the file to get wrapper.pl

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

Step 6 Back up CS, RME, CM, and IPM data.

To do this using CLI, enter the following command:

NMSROOT\bin\perl dir1\wrapper.pl BKP

where BKP is the backup directory and dir1 is the directory containing wrapper.pl.

You must give the complete path for dir1 and BKP. For example, if BKP is under C:\, give the path as C:\BKP.

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

Step 7 Login as administrator into Machine B.

Step 8 Install LMS 3.0.

If you are upgrading to DFM 3.0, assemble the files needed for DFM migration or else go to Step 9.

a. Copy the DFM 3.0 Upgrade Kit from Machine B to a directory say dir in Machine A.

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 in Machine B. 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 in Machine A, 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), where C is the System drive.

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 9 Copy the LMS data from Machine A to any temporary location in Machine B as follows:

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

Note You can preserve the time stamp of the files by entering the option -p with the copy command: cp -r -p <source> <destination>.

b. For DFM, copy the following files, also.

File Name

Location in LMS 2.2

Copy into this location in LMS 3.0

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.2 or RWAN 1.3 to LMS 3.0

Step 10 Stop the daemon manager by entering:

net stop crmdmgtd

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

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP [-t temporary_directory]

where BKP is the backup directory.

You must give the complete path for BKP. For example, if BKP is under C:\, give the path as C:\BKP.

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

Step 12 Examine the log files in the following location to verify that the database was restored.The files are:

•NMSROOT\log\restorebackup.log

•NMSROOT\log\migration.log

•NMSROOT\log\rme_base.log

•NMSROOT\log\ipm_base.log

Note Migration.log will be created only when either RME or IPM is migrated.

Step 13 Start the daemon manager by entering:

net start crmdmgtd