Veritas Data Insight Administrator's Guide

To back up the Data Insight server with Indexer role

1. Log in to the server with the Indexer role.
2. Backup the entire $data folder using backup tools such as Veritas NetBackup. The backup software should be capable of taking Volume Shadow Copy/Snapshot based backups. If your backup software does not have such a capability, you must stop all Data Insight services before backup, to avoid incomplete backup due to locked files.

To restore the Indexer node

1. Install the operating system. Use the same version, host name (recommended for ease of configuration), and architecture as was installed before the backup.
2. Install the same version of Data Insight that was installed before the backup.
3. Select the option to install the Indexer and Collector role while installing Data Insight. If installing Data Insight on a Linux server, select the option to install Indexer.
4. Specify the original location of the $data directory as the previous install. By default, the $data directory is located at C:\DataInsight\data.
5. Clear the Launch worker node registration wizard after exit checkbox. You do not need to register the worker node at this time as the registration information is already present in the data that you have backed up.
6. Complete the installation. Do not start the services at this time; clear the Start services now option when the installer prompts for it.
7. Delete the $data folder that is created as a part of the new installation and copy the backed up data to this location.
8. Start the Data Insight services, which include DataInsightComm, DataInsightWatchdog, and DataInsightConfig.
9. Check the status of the services and ensure that they come to running state.

   Successful start of all services indicates that the Indexer node is successfully restored.

To restore the Indexer node with a different host name or IP address

1. Repeat steps 1 through 6 as described in the section, Restoring the Indexer node.
2. Edit $data/conf/<nodename>.conf and enter the new server name.
3. Open the file, $data/conf/config.db.<N> (N being the latest version of config.db) in an SQLITE editor.

   Update the node_name and node_ip columns in node table with the host name and IP address of the new server.

4. Run the following SQL updates:

   update node set node_name='<new node name>'
    where node_name='<prev node name>';

   update node set node_ip='<new node name>'; 
   where node_name='<prev node name >'; 

5. Log in to the Management Server and stop the DataInsightComm, DataInsightWeb, and DataInsightConfig services.
6. Perform 3 on the Management Server.
7. Open a Windows command prompt and run the following command to increment the version of the config.db file that was changed in 2

   <INSTALL DIR>\DataInsight\bin\configdb - O -J dummy - j dummy

8. Start all Data Insight services on the Management Server.
9. On each worker node, except the Windows File Server agents, stop DataInsightComm and DataInsightConfig services.
10. If this node is a Collector for one or more Windows File Server agents, log in to each Windows File Server, stop the DataInsightComm and DataInsightConfig services.

    Perform step 3 on the worker node's config.db.N

11. Start the DataInsightComm and DataInsightConfig services on the Indexer and all other worker nodes where configdb.N was changed. Ensure that the worker nodes show online on the Data Insight Management Console.