Data migration

Use the following steps to migrate customizations from a previous version of Network Configuration Manager:

Procedure

Extract the file Data-Migration9.4.0.0.zip on the Application Server host. Recommended outside the NCM installed location.
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\archive-utility.pl to perform the restore.

Note:
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.
Type the command:
```
source /etc/voyence.conf
```
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

Note:
The backup image file will be written to Data-Migration-9.4.0.0\41Xto94\scripts\migration \data-image directory.
If you plan to use the same host for 9.4.Uninstall Network Configuration Manager 4.1.1.x.
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 9.4 is installed on a different host (other than 4.1.X), copy the Data-Migration-9.4.0.0.zip file to that host and extract it.
Copy the backup image to the new 9.4 host. Go to the 41Xto94/scripts/migration folder
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.
Do not add new Device Servers to your NCM deployment until you completed migration.
For existing Device Servers that are staying on the same hosts, uninstall 4.1.x and install NCM 9.4 following DS installation procedure in the Install Guide.
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:
1. From the [Product directory], run the command:
```
./cgi-bin/cflist.cgi > cflist.txt
```
2. 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 address has to be updated.
3. Run the command:
  
  ./cgi-bin/cfwrite.cgi < cflist.txt

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.vmware.com';