Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
How to migrate customizations and data from an existing Network Configuration Manager installation to a new installation of Network Configuration Manager 9.4. The KB article contains instructions for the migration of data from Smarts NCM v4.1.1.x to 9.4 on both Windows and Linux systems.
The migration scripts can be downloaded from here:https://support.emc.com/products/31946_Service-Assurance-Suite/Tools/Tool Title:Smarts Network Configuration Manager (NCM) Data Migration script from 4.1.1.x to 9.4Prerequisites and order of migration tasksThe recommended order of migration tasks for new installations is as follows: Step Task 1 Review the minimum system requirements mentioned in EMC Smarts Network Configuration Manager Support Matrix document. 2 Install the operating system, including any prerequisites. Install the appropriate package groups for use with Network Configuration Manager. 3 Ensure all firewalls adhere to the Communication security settings table mentioned in EMC Smarts Network Configuration Manager Security Configuration Guide . 4 For Windows only: Enable Network Time Protocol (NTP). Copy the files included with the Network Configuration Manager distribution to a writeable directory, such as C:\Installers. Do not run the installer from a read-only file system, such as a CD or mounted ISO. If the installation must be done from a read-only file system, the Network Configuration Manager components must be installed individually. 5 Install Network Configuration Manager version 9.4 If errors occur during installation, refer to the EMC Smarts Network Configuration Manager Troubleshooting Guide for a list of solutions. 6 Configure Network Configuration Manager using instructions in the EMC Smarts Network Configuration Manager Installation Guide . 7 Install Report and Compliance advisors using instructions in the EMC Smarts Network Configuration Manager Installation Guide 8 Begin using Network Configuration Manager using the steps in Appendix A, Getting Started with Network Configuration Manager in the EMC Smarts Network Configuration Manager Installation Guide. 9 Perform migration as described in this document. Data migration procedures for Windows--------------- Migration overview You can perform a migration to version 9.4 from the following version of Network Configuration Manager: Network Configuration Manager 4.1.1.x versions and beyond Migration is not supported from 9.x versions.Migration prerequisites If you are using RSA token server: before performing migration download the server certificate from the RSA token server. Add this certificate to 9.4 keystore before running the restore script.Procedure Create the RSA.cer by downloading the certificate from https:\\<RSA token server>:<port> Refer to RSA documentation for details about accessing the token server. Run the following commands in the 9.4 Application server: %JAVA_HOME%\bin\keytool -keystore %JAVA_HOME%\jre\lib\security\cacerts -import -file RSA.cer -alias VCRSA Restart vcmaster service. Before attempting to run Data Migration, Java must be installed on the system where the Data Migration script will be run. In a distributed setup, stop the vcmaster services in the remote server before starting the migration. Data migration Use the following steps to migrate customizations from a 4.1.1.X version of Network Configuration Manager: Procedure: 1. Extract the file Data-Migration9.4.0.0.zip on the Application Server host. Recommended outside the NCM installed location. 2. For migrating from 4.1.1.0, 4.1.2 and 4.1.3 use the scripts in folder 41Xto94. Go to the \Data- Migration-9.4.0.0\41Xto94\scripts\migration folder. For migration from NCM 4.1.1.1 use the scripts in folder 4111to94. Go to the \Data-Migration- 9.4.0.0\4111to94\scripts\migration The archived database data will not be migrated by default. If you would like to preserve the archived data from 4.x in your 9.4 installation, then it must be restored into the Network Configuration Manager 4.1.1 or higher database prior to executing the migration script. Use [product directory]\tools\archive-utility.pl to perform the restore. NOTICE: If you are migrating from Network Configuration Manager version 4.1.1 Patch 1, which was a security patch with a limited release, the lockbox passphrase and the database password provided in Network Configuration Manager version 4.1.1 Patch 1 should remain the same during the 9.4 installation. 3. Run the script 9.4Migration_Backup.pl. A backup image file is created. Running this script will stop all the services. perl 9.4Migration_Backup.pl NOTICE: The backup image file will be written to Data-Migration- 9.4.0.0\41Xto94\scripts\migration \data-image directory. 4. If you plan to use the same host for 9.4, uninstall Network Configuration Manager 4.1.1.x. 5. Install Network Configuration Manager 9.4. The Network Configuration Manager 9.4 installation should be same as Network Configuration Manager 4.1.1.x. If you have installed Report advisor on Network Configuration Manager 4.1.1, then you must have Report advisor installed on Network Configuration Manager 9.4 as well. 6. If 9.4 is installed on a different host (other than 4.1.1.x), copy the Data-Migration- 9.4.0.0.zip file to that host and extract it. 7. Copy the backup image to the new 9.4 host. Go to the 41Xto94\scripts\migration folder. 8. Run the script 9.4_DataRestore.pl with the backup image as argument. For example: perl 9.4_DataRestore.pl <backup image> NOTICE: The 9.4_DataRestore.pl script is using Term::Readkey module of Strawberry Perl installed on the host. This module is used to hide the database and system administrator passwords on the console. All the services are started after the successful migration. The 9.4_DataRestore.pl script automatically invokes the updateCredential.pl script. You are prompted for Network Configuration Manager System administrator credentials. Type the system administrator credentials. Device Server migration 1. Do not add new Device Servers to your NCM deployment until you completed migration. 2. On existing Device Servers that are staying on the same hosts, uninstall 4.1.1.x and install NCM 9.4 following DS installation procedure in the Install Guide. 3. If you are moving one of your existing DS servers to a new host, follow installation procedure in the Install Guide and perform the steps below Update the InfraDB entry with the new hostname of the Device Server. This is required so that device to DS mappings is updated with the new hostname of the DS. To update the InfraDB entry, perform the following steps: a. From the [Product directory], run the command: .\cgi-bin\cflist.cgi > cflist.txt b. Edit the cflist.txt to change the Device server FQDN and IP address to the new Device server FQDN and IP address. For example, POP 1000 "< >"......ADDR=< > Please note: In case of multiple device servers, entries for all the device server hostnames should be updated. c. Run the command: .\cgi-bin\cfwrite.cgi < cflist.txt 4. Manually update the cm_device_server table with the updated Device Server hostname To update the cm_device_server table, run the following command from [Product directory] \db\controldb\bin : psql.exe -h <database_server_IP_address> -d voyencedb -U pgdba -p 5435 -c "update cm_device_server set device_server_name='Device_Server_name';" Example: psql.exe -h <database_server_IP_address> -d voyencedb -U pgdba -p 5435 -c "update cm_device_server SET device_server_name ='linb056.lss.emc.com';" Error Handling After performing migration, the log files are generated in the folder from where you run the migration scripts. Check and use the log files for any failures and troubleshooting. Additional data migration information Clear the browser cache. The Network Configuration Manager 9.4 uses a newer version of Java than previous version of Network Configuration Manager. This new version of Java will cause a user interface (UI) error to occur if the browser and Java Web Start caches are not cleared after upgrading from previous versions of Network Configuration Manager. The first configuration pull of a device will show as a new revision, even if the configuration is the same as it was prior to the migration. This is normal behavior and does not indicate an error. ------------------------------------------------------------------------------------------------------------------- Data migration procedures for Linux /CentOS--------------- This section includes the following topics about migration on the linux/CentOS platform: Migration overview You can perform a migration to version 9.4 from the following version of Network Configuration Manager: Network Configuration Manager all 4.1.1.x versions and beyond 4.1.1.0. Migration is not supported from 9.x versions Prerequisites If you are using RSA token server: before performing migration download the server certificate from the RSA token server. Add this certificate to 9.4 keystore before running the restore script. Create the RSA.cer by downloading the certificate from https:\\<RSA token server>:< port> Refer to RSA documentation for details about accessing the token server. Run the following command in the 9.4 Application Server: source /etc/voyence.conf $JAVA_HOME/bin/keytool -keystore $JAVA_HOME/jre/lib/security/cacerts -import -file /RSA.cer -alias VCRSA Restart vcmaster service. Before attempting to run Data Migration, Java must be installed on the box where the Data Migration script will be run. In a distributed setup, stop the vcmaster services in the remote server before starting the migration. Data migrationUse the following steps to migrate customizations from a previous version of NetworkConfiguration Manager:Procedure: 1. Extract the file Data-Migration9.4.0.0.zip on the Application Server host. Recommended outside the NCM installed location. 2. For migrating from 4.1.1.0, 4.1.2 and 4.1.3 use the scripts in folder 41Xto94. Go to the \Data-Migration-9.4.0.0\41Xto94\scripts\migration folder. Here X refers to patch number.For migration from NCM 4.1.1.1 use the scripts in folder 4111to94. Go to the \Data-Migration-9.4.0.0\4111to94\scripts\migration The archived database data will not be migrated by default. If you would like to preserve the archived data from 4.x in your 9.4 installation, then it must be restored into the Network Configuration Manager 4.1.1 or higher database prior to executing the migration script. Use [product directory]\tools\archiveutility. pl to perform the restore.NOTICE: If you are migrating from Network Configuration Manager version4.1.1 Patch 1, which was a security patch with a limited release, the lockboxpassphrase and the database password provided in Network ConfigurationManager version 4.1.1 Patch 1 should remain the same during the 9.4installation. 3. Type the command: source /etc/voyence.conf 4. Run the script 9.4Migration_Backup.pl. A backup image file is created. Running this script will stop all the services. perl 9.4Migration_Backup.plNOTICE: The backup image file will be written to Data-Migration-9.4.0.0\41Xto94\scripts\migration \data-image directory. 5. If you plan to use the same host for 9.4.Uninstall Network Configuration Manager 4.1.1.x. 6. Install Network Configuration Manager 9.4 The Network Configuration Manager 9.4 installation should be same as Network Configuration Manager 4.1.1.x. If you have installed Report advisor on Network Configuration Manager 4.1.1, then you must have Report advisor installed on Network Configuration Manager 9.4 as well. 7. If 9.4 is installed on a different host (other than 4.1.1.x), copy the Data-Migration- 9.4.0.0.zip file to that host and extract it. 8. Copy the backup image to the new 9.4 host. Go to the 41Xto94/scripts/migration folder 9. Run the script 9.4_DataRestore.pl with the backup image as argument. For example: perl 9.4_DataRestore.pl <backup image> All the services are started after the successful migration. The 9.4_DataRestore.pl script automatically invokes the updateCredential.sh script. You are prompted for Network Configuration Manager System administrator credentials. Type the system administrator credentials. Device Server migration. 1. Do not add new Device Servers to your NCM deployment until you completed migration. 2. For existing Device Servers that are staying on the same hosts, uninstall 4.1.1.x and install NCM 9.4 following DS installation procedure in the Install Guide. 3. If you are moving one of your existing DS servers to a new host, follow installation procedure in the Install Guide and perform the steps below: Update the InfraDB entry with the new hostname of the Device Server. This is required so that device- to-DS mappings are updated with the new hostname of the DS. To update the InfraDB entry, perform the following steps: a. From the [Product directory], run the command: ./cgi-bin/cflist.cgi > cflist.txt b. Edit the cflist.txt to change the Device server FQDN and IP address to the new Device server FQDN and IP address. For example :POP 1000 "<hostname>"......ADDR=<IP address> Please Note: In case of multiple device servers, all the device server hostnames/IP addresses have to be updated. c. Run the command: ./cgi-bin/cfwrite.cgi < cflist.txt 4. Update the cm_device_server table with the Device server hostname. To update the cm_device_server table, run the following commands: su - pgdba psql voyencedb <NCM_database_password> update cm_device_server set device_server_name='<Device Server name>'; Example: update cm_device_server SET device_server_name ='linbgq056.lss.emc.com'; Error handling After performing migration, the log files are generated in the folder from where you run the migration scripts. Check and use the log files for any failures and troubleshooting. Additional data migration information Clear Browser Cache. The Network Configuration Manager 9.4 uses a newer version of Java than previous version of Network Configuration Manager. This new version of Java will cause a user interface (UI) error to occur if the browser and Java Web Start caches are not cleared after upgrading from previous versions of Network Configuration Manager. The first configuration pull of a device will show as a new revision, even if the configuration is the same as it was prior to the migration. This is normal behavior and does not indicate an error. Other Related Information Obtain documentation including release notes and installation instructions for this product on EMC Online Support at: https://support.emc.com > Support by Product > Product Name > Documentation. A Documentation Index with links to relevant articles and guides is available on the EMC Community Network (ECN). Log in and search for the Documentation Index for your product. (https://community.emc.com/community/products). The following documents contain useful information for migration tasks: EMC Smarts Network Configuration Manager Support Matrix EMC Smarts Network Configuration Manager Troubleshooting Guide EMC Smarts Network Configuration Manager Installation Guide EMC Smarts Network Configuration Manager Security Configuration Guide
How much space will I need?On a Migration it can take 3 times the amount of space as your current NCM database.Example: If your current Database is 80GB, you should plan to have 240GB of free space available.How much time will it take?A lot will depend on the size of the database, back-up and restore times, CPU and Memory.Can I migrate from 4.10 to 9.4?No, this is not possible, you must first upgrade 4.10 to 4.11***After running the Script I see the following ERROR: Final Archive creation failedPlease see KB 206596 for more details.