Description

This process will preserve the existing deployment configuration and data with minimal downtime when migrating the MS to a new system.

Requirements

1. Backup of the DATA folder from the existing MS  NOTE: Please refer to Related Articles below for Backup/Restore of the MS.
   1. This can be taken after the new MS has Data Insight installed to minimize downtime.
2. New MS FQDN name and IP Address (if applicable).
3. New MS is joined to the same domain as the existing MS.

Migrating to a New Management Server Using the Same Name

1. On the new MS, install the same version of Data Insight (including any patches) as is currently running on the existing MS.
   1. The same drive/directory structure should be preserved between the two MS servers to simplify the configuration.
   2. Do not start the Data Insight services after the install
2. If not already done, take a backup of the \DataInsight\data folder on the existing MS.
3. Stop all Data Insight services on the new MS.
4. Copy the backup folder from Step 2 to a temporary location on the new MS.
5. Delete \DataInsight\data folder from the new MS.
6. Copy the data folder backup to \DataInsight\ on the new MS.
7.  Start the Data Insight services on the new MS.
8. Confirm connectivity to the console via browser access and that communication is restored between the MS and the rest of the nodes in the configuration.

Migrating to a New Management Server Using a Different Name

1. On the new MS, install the same version of Data Insight (including any patches) as is currently running on the existing MS.
   1. The same drive/directory structure should be preserved between the two MS servers to simplify the configuration.
   2. Do not start the Data Insight services after the install
2. If not already done, take a backup of the \DataInsight\data folder on the existing MS.
3. Stop all Data Insight services on the new MS if not already stopped from Step 1.
4. Take a copy of the \DataInsight\data\keys\webserver.keystore file from the new MS.
5. Copy the backup folder from Step 2 to a temporary location on the new MS.
6. Delete \DataInsight\data folder from the new MS.
7. Copy the data folder backup to \DataInsight\ on the new MS.
8. Replace the \DataInsight\data\keys\webserver.keystore with the one that was preserved in Step 4.
9. Edit the \DataInsight\conf\nodename.conf file in a text editor to update with the FQDN of the new MS.
10. Update the configuration database with the new name
    1. On the new MS open a command prompt with elevated permissions (Run as Administrator)
    2. Navigate to \Program Files\DataInsight\bin
    3. Edit the following command and update the values for node_name and node_ip with the new MS information as well as the file name of the highest version of the config.db.### file using the following syntax:
       sqlite3.exe \DataInsight\data\conf\config.db.xxx "update node set node_name='', node_ip='' where node_id=1;" 
       Example:
       > sqlite3.exe E:\DataInsight\data\conf\config.db.1456 "update node set node_name='DI.DOMAIN.COM', node_ip='DI.DOMAIN.COM' where node_id=1;" 
11. Run the following command to confirm the database updates were successful.
    1. > configdb.exe -p -T node
    2. The first entry is for the MS and should now show the new MS FQDN for node_name and node_ip.
12. Start the Data Insight services on the new MS.
13. Confirm connectivity to the console via browser access.
14. On each remaining node (Indexer, Collector, Classification, & Self-Service Portal) in the environment:
    1. Stop the DataInsightComm and DataInsightConfig services.
    2. Copy the \DataInsight\data\conf\config.db.### (highest number in the folder if there are multiple) and \DataInsight\data\conf\config.db.helper from the new MS to replace the existing files in the \DataInsight\data\conf\ folder of the node.
    3. Start the DataInsightComm and DataInsightConfig services.
15. It may take a few minutes after the service starts for the status to be reflected in the Data Insight console.

NOTES:

If the path of the DATA directory changes between the existing MS and the new MS, edit the \Program Files\DataInsight\datadir.conf file to reflect the new path before starting the services.

If using a third-part certificate (self-signed or CA), submit a new CSR if the MS name has changed. Please refer to the Post-Installation Configuration section of the Data Insight Installation Guide for the version of Data Insight for more information on securing the console.