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

Table Of Contents

Migrating Data to CiscoWorks LAN Management Solution 3.2 on Solaris

Migrating Data From LMS 2.6 or 2.6 SP1

Local Migration From LMS 2.6 or 2.6 SP1

Remote Migration From LMS 2.6 or 2.6 SP1

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

Migrating Data From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1

Local Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1

Remote Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1

Migrating Data for CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal and CV

Migrating Data to CiscoWorks LAN Management Solution 3.2 on Solaris

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

This chapter has the following sections:

•Migrating Data From LMS 2.6 or 2.6 SP1

•Migrating Data From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1

Migrating Data From LMS 2.6 or 2.6 SP1

This section explains how to migrate data from LMS 2.6 or 2.6 SP1 to LMS 3.2.

You can migrate to LMS 3.2 in two ways:

•Local Migration From LMS 2.6 or 2.6 SP1

•Remote Migration From LMS 2.6 or 2.6 SP1

Figure 3-1 shows the migration of data from LMS 2.6 to LM S 3.2.

Figure 3-1 Migrating Data from LMS 2.6 to LMS 3.2

Figure 3-2 shows the migration of data from LMS 2.6 SP1 to LMS 3.2

Figure 3-2 Migrating Data from 2.6 SP1 to 3.2

Local Migration From LMS 2.6 or 2.6 SP1

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

Note You must install LMS 3.2 without HUM 1.2. HUM 1.2 installation should be initiated only after LMS 3.2 installation and data migration are completed. This note is applicable only if HUM 1.2 is a part of LMS 3.2 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 enter the absolute path for BKP. For example, if BKP is under /opt, enter the path as NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d /opt/BKP.

Note We recommend you to stop the daemon manager, before you take the backup of LMS data.

For details on installing LMS 3.2, see the Installing and Getting Started with CiscoWorks LAN Management Solution 3.2.

Remote Migration From LMS 2.6 or 2.6 SP1

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 2.6 SP1 data is referred to as Machine A and the remote machine where you need to install LMS 3.2 and restore the data, is referred to as Machine B.

Note We recommend you to stop the daemon manager, before you take the backup of LMS data.

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

To migrate data to a remote machine:

Step 1 Log in as root into Machine A.

Step 2 From the LMS 3.2 DVD, locate the SolarisLMSBackup.tar file under disk1/install directory.

Step 3 Copy the file (SolarisLMSBackup.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

Note If you need to backup DFM 2.0.10, install DFM 2.0.11 before taking the backup. If not, the backup will fail.

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

To do this using CLI, go to the location of wrapper.pl and enter the following command:

NMSROOT/bin/perl wrapper.pl BKP

where BKP is the backup directory.

For example, if BKP is under /opt, enter the path as NMSROOT/bin/perl wrapper.pl /opt/BKP

Step 6 Log in as root into Machine B.

Step 7 Install LMS 3.2.

Note You must install LMS 3.2 without HUM 1.2. HUM 1.2 installation should be initiated only after LMS 3.2 installation and data restoration are completed. This note is applicable only if HUM 1.2 is a part of LMS 3.2 installation.

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 -rp source destination.

Step 9 Stop the daemon manager by entering:

/etc/init.d/dmgtd stop

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 absolute path for BKP. For example, if BKP is under /opt, give the path as NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d /opt/BKP.

For more details, see Syntax and Usage for Restore Script.

The application list in the backed up data should exactly match the application list in the machine where it is restored except for CiscoWorks Assistant and Portal. If there is a difference then the behavior of the applications after upgrade will be unpredictable.

For more information, see Notes for Remote Migration.

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

•/var/adm/CSCOpx/log/restorebackup.log

•/var/adm/CSCOpx/log/migration.log

•/var/adm/CSCOpx/log/rme_base.log

•/var/adm/CSCOpx/log/ipm_base.log

Note The migration.log will be created only when either RME or IPM is migrated. However, the rme_base.log and ipm_base.log are created only when RME and IPM are migrated.

Step 12 Start the daemon manager by entering:

/etc/init.d/dmgtd start

Migrating Data From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1

This section explains how to migrate data from LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1

You can migrate to LMS 3.2 in two ways:

•Local Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1

•Remote Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1

Figure 3-3 shows the migration of data from LMS 3.0 to LMS 3.2.

Figure 3-3 Migrating Data from LMS 3.0 to LMS 3.2

Figure 3-4 shows the migration of data from LMS 3.0 December 2007 Update to LMS 3.2.

Figure 3-4 Migrating Data from LMS 3.0 December 2007 Update to LMS 3.2

Figure 3-5 shows the migration of data from LMS 3.1 to LMS 3.2.

Figure 3-5 Migrating Data from LMS 3.1 to LMS 3.2

Local Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1

Install LMS 3.2 over LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1. The data for CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal and CV is automatically migrated during installation. HUM is a add-on application and it is optional.

Note We recommend you to stop the daemon manager, before you take the backup of LMS data.

For details on installing LMS 3.2, see the Installing and Getting Started with CiscoWorks LAN Management Solution 3.2 at this location:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html

Remote Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1

This section explains the procedure of Migrating Data for CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal and CV to a remote machine. HUM is a add-on application and it is optional.

In this section, the machine that has LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 is referred to as Machine A and the remote machine where you need to install LMS 3.2 and restore the data, is referred to as Machine B.

Note We recommend you to stop the daemon manager, before you take the backup of LMS data.

Migrating Data for CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal and CV

To migrate data to a remote machine:

Step 1 Log in as root into Machine A.

Step 2 Back up CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal, and CV data.

To do this using CLI, enter the following command:

NMSROOT/bin/perl NMSROOT/bin/backup.pl BKP

where BKP is the backup directory.

You must enter the absolute path for BKP. For example, if BKP is under /opt, give the path as NMSROOT/bin/perl NMSROOT/bin/backup.pl /opt/BKP

Step 3 Log in as root into Machine B.

Step 4 Install LMS 3.2.

Step 5 Transfer the backup directory BKP that contains the CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal and CV data as a compressed file (example .tar) from Machine A to any temporary location.

Step 6 Stop the daemon manager by entering:

/etc/init.d/dmgtd stop

Step 7 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 enter the absolute path for BKP. For example, if BKP is under /opt, give the path as NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d /opt/BKP.

For more details, see Syntax and Usage for Restore Script.

The application list in the backed up data should exactly match the application list in the machine where it is restored. If there is a difference then the behavior of the applications after upgrade will be unpredictable.

For more information, see Notes for Remote Migration.

You can also restore data from CiscoWorks LMS 3.1 to the CiscoWorks LMS 3.2 server with Symantec Veritas implementation.

For details on High Availability (HA) implementation, see the Installing and Getting Started with CiscoWorks LAN Management Solution 3.2 at this location:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html

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

•/var/adm/CSCOpx/log/restorebackup.log

•/var/adm/CSCOpx/log/migration.log

•/var/adm/CSCOpx/log/rme_base.log

Note The migration.log and the rme_base.log will be created only when RME is migrated.

Step 9 Start the daemon manager by entering:

/etc/init.d/dmgtd start

	Data Migration Guide for LAN Management Solution 3.2
	Chapter 3: Migrating Data to LAN Management Solution 3.2 on Solaris
Data Migration Guide for LAN Management Solution 3.2 Notices Preface Chapter 1: Overview Chapter 2: Migrating Data to LAN Management Solution 3.2 on Windows Chapter 3: Migrating Data to LAN Management Solution 3.2 on Solaris Chapter 4: Troubleshooting Errors in Data Migration Chapter 5: Guidelines to Post-Upgrade Activities Appendix A: Syntax and Usage for Backup Script Appendix B: Syntax and Usage for Restore and Backup Script Index	Download this chapter Chapter 3: Migrating Data to LAN Management Solution 3.2 on Solaris Download the complete book Data Migration Guide for LAN Management Solution 3.2 - PDF of Entire Book (PDF - 1 MB) Table Of Contents Migrating Data to CiscoWorks LAN Management Solution 3.2 on Solaris Migrating Data From LMS 2.6 or 2.6 SP1 Local Migration From LMS 2.6 or 2.6 SP1 Remote Migration From LMS 2.6 or 2.6 SP1 Migrating Data for CS, RME, CM, DFM, IPM and CV Migrating Data From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 Local Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 Remote Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 Migrating Data for CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal and CV Migrating Data to CiscoWorks LAN Management Solution 3.2 on Solaris This chapter describes how to migrate data to CiscoWorks LAN Management Solution (LMS) 3.2 on Solaris. This chapter has the following sections: •Migrating Data From LMS 2.6 or 2.6 SP1 •Migrating Data From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 Migrating Data From LMS 2.6 or 2.6 SP1 This section explains how to migrate data from LMS 2.6 or 2.6 SP1 to LMS 3.2. You can migrate to LMS 3.2 in two ways: •Local Migration From LMS 2.6 or 2.6 SP1 •Remote Migration From LMS 2.6 or 2.6 SP1 Figure 3-1 shows the migration of data from LMS 2.6 to LM S 3.2. Figure 3-1 Migrating Data from LMS 2.6 to LMS 3.2 Figure 3-2 shows the migration of data from LMS 2.6 SP1 to LMS 3.2 Figure 3-2 Migrating Data from 2.6 SP1 to 3.2 Local Migration From LMS 2.6 or 2.6 SP1 Install LMS 3.2 over LMS 2.6 or 2.6 SP1. The data for CS, RME, CM, DFM, and CV is automatically migrated during installation. Note You must install LMS 3.2 without HUM 1.2. HUM 1.2 installation should be initiated only after LMS 3.2 installation and data migration are completed. This note is applicable only if HUM 1.2 is a part of LMS 3.2 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 enter the absolute path for BKP. For example, if BKP is under /opt, enter the path as NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d /opt/BKP. Note We recommend you to stop the daemon manager, before you take the backup of LMS data. For details on installing LMS 3.2, see the Installing and Getting Started with CiscoWorks LAN Management Solution 3.2. Remote Migration From LMS 2.6 or 2.6 SP1 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 2.6 SP1 data is referred to as Machine A and the remote machine where you need to install LMS 3.2 and restore the data, is referred to as Machine B. Note We recommend you to stop the daemon manager, before you take the backup of LMS data. Migrating Data for CS, RME, CM, DFM, IPM and CV To migrate data to a remote machine: Step 1 Log in as root into Machine A. Step 2 From the LMS 3.2 DVD, locate the SolarisLMSBackup.tar file under disk1/install directory. Step 3 Copy the file (SolarisLMSBackup.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 Note If you need to backup DFM 2.0.10, install DFM 2.0.11 before taking the backup. If not, the backup will fail. Step 5 Back up CS, RME, CM, IPM, DFM, and CV data. To do this using CLI, go to the location of wrapper.pl and enter the following command: NMSROOT/bin/perl wrapper.pl BKP where BKP is the backup directory. For example, if BKP is under /opt, enter the path as NMSROOT/bin/perl wrapper.pl /opt/BKP Step 6 Log in as root into Machine B. Step 7 Install LMS 3.2. Note You must install LMS 3.2 without HUM 1.2. HUM 1.2 installation should be initiated only after LMS 3.2 installation and data restoration are completed. This note is applicable only if HUM 1.2 is a part of LMS 3.2 installation. 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 -rp source destination. Step 9 Stop the daemon manager by entering: /etc/init.d/dmgtd stop 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 absolute path for BKP. For example, if BKP is under /opt, give the path as NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d /opt/BKP. For more details, see Syntax and Usage for Restore Script. The application list in the backed up data should exactly match the application list in the machine where it is restored except for CiscoWorks Assistant and Portal. If there is a difference then the behavior of the applications after upgrade will be unpredictable. For more information, see Notes for Remote Migration. Step 11 Examine the log files in the following location to verify that the data was restored. The files are: •/var/adm/CSCOpx/log/restorebackup.log •/var/adm/CSCOpx/log/migration.log •/var/adm/CSCOpx/log/rme_base.log •/var/adm/CSCOpx/log/ipm_base.log Note The migration.log will be created only when either RME or IPM is migrated. However, the rme_base.log and ipm_base.log are created only when RME and IPM are migrated. Step 12 Start the daemon manager by entering: /etc/init.d/dmgtd start Migrating Data From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 This section explains how to migrate data from LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 You can migrate to LMS 3.2 in two ways: •Local Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 •Remote Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 Figure 3-3 shows the migration of data from LMS 3.0 to LMS 3.2. Figure 3-3 Migrating Data from LMS 3.0 to LMS 3.2 Figure 3-4 shows the migration of data from LMS 3.0 December 2007 Update to LMS 3.2. Figure 3-4 Migrating Data from LMS 3.0 December 2007 Update to LMS 3.2 Figure 3-5 shows the migration of data from LMS 3.1 to LMS 3.2. Figure 3-5 Migrating Data from LMS 3.1 to LMS 3.2 Local Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 Install LMS 3.2 over LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1. The data for CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal and CV is automatically migrated during installation. HUM is a add-on application and it is optional. Note We recommend you to stop the daemon manager, before you take the backup of LMS data. For details on installing LMS 3.2, see the Installing and Getting Started with CiscoWorks LAN Management Solution 3.2 at this location: http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html Remote Migration From LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 This section explains the procedure of Migrating Data for CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal and CV to a remote machine. HUM is a add-on application and it is optional. In this section, the machine that has LMS 3.0 or LMS 3.0 December 2007 Update or LMS 3.1 is referred to as Machine A and the remote machine where you need to install LMS 3.2 and restore the data, is referred to as Machine B. Note We recommend you to stop the daemon manager, before you take the backup of LMS data. Migrating Data for CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal and CV To migrate data to a remote machine: Step 1 Log in as root into Machine A. Step 2 Back up CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal, and CV data. To do this using CLI, enter the following command: NMSROOT/bin/perl NMSROOT/bin/backup.pl BKP where BKP is the backup directory. You must enter the absolute path for BKP. For example, if BKP is under /opt, give the path as NMSROOT/bin/perl NMSROOT/bin/backup.pl /opt/BKP Step 3 Log in as root into Machine B. Step 4 Install LMS 3.2. Step 5 Transfer the backup directory BKP that contains the CiscoWorks Assistant, CS, RME, CM, DFM, IPM, HUM, Portal and CV data as a compressed file (example .tar) from Machine A to any temporary location. Step 6 Stop the daemon manager by entering: /etc/init.d/dmgtd stop Step 7 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 enter the absolute path for BKP. For example, if BKP is under /opt, give the path as NMSROOT/bin/perl NMSROOT/bin/restorebackup.pl -d /opt/BKP. For more details, see Syntax and Usage for Restore Script. The application list in the backed up data should exactly match the application list in the machine where it is restored. If there is a difference then the behavior of the applications after upgrade will be unpredictable. For more information, see Notes for Remote Migration. You can also restore data from CiscoWorks LMS 3.1 to the CiscoWorks LMS 3.2 server with Symantec Veritas implementation. For details on High Availability (HA) implementation, see the Installing and Getting Started with CiscoWorks LAN Management Solution 3.2 at this location: http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html Step 8 Examine the log files in the following location to verify that the data was restored. The files are: •/var/adm/CSCOpx/log/restorebackup.log •/var/adm/CSCOpx/log/migration.log •/var/adm/CSCOpx/log/rme_base.log Note The migration.log and the rme_base.log will be created only when RME is migrated. Step 9 Start the daemon manager by entering: /etc/init.d/dmgtd start
	© 1992-2009 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.