Please enter search query.
Search <book_title>...
Veritas Data Insight Administrator's Guide
Last Published:
2020-07-14
Product(s):
Data Insight (6.1.5)
- Section I. Getting started
- Introduction to Veritas Data Insight administration
- Configuring Data Insight global settings
- Overview of Data Insight licensing
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Data Insight integration with Symantec Data Loss Prevention (DLP)
- Configuring advanced analytics
- About open shares
- About bulk assignment of custodians
- Section II. Configuring Data Insight
- Configuring Data Insight product users
- Configuring Data Insight product servers
- About node templates
- About automated alerts for patches and upgrades
- Configuring saved credentials
- Configuring directory service domains
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp file server monitoring
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Data Insight and cluster-mode NetApp devices
- Configuring EMC Celerra or VNX monitoring
- Configuring EMC Isilon monitoring
- Configuring EMC Unity VSA file servers
- Configuring Hitachi NAS file server monitoring
- Configuring Windows File Server monitoring
- Configuring Veritas File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring NetApp file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Data Insight web service for SharePoint
- Adding web applications
- Adding site collections
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Adding SharePoint Online accounts
- Adding site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Section VI. Configuring ECM data sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Section IX. Remediation
- Section X. Reference
- Appendix A. Backing up and restoring data
- Appendix B. Data Insight health checks
- Appendix C. Command File Reference
- Appendix D. Data Insight jobs
- Appendix E. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Backing up and restoring the Indexer node
You must mandatorily backup the nodes that serve as the Indexer roles in a Data Insight deployment.
To back up the Data Insight server with Indexer role
- Log in to the server with the Indexer role.
- 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
- Install the operating system. Use the same version, host name (recommended for ease of configuration), and architecture as was installed before the backup.
- Install the same version of Data Insight that was installed before the backup.
- 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.
- Specify the original location of the
$data
directory as the previous install. By default, the$data
directory is located atC:\DataInsight\data
. - 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.
- Complete the installation. Do not start the services at this time; clear the Start services now option when the installer prompts for it.
- Delete the
$data
folder that is created as a part of the new installation and copy the backed up data to this location. - Start the Data Insight services, which include DataInsightComm, DataInsightWatchdog, and DataInsightConfig.
- 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
- Repeat steps 1 through 6 as described in the section, Restoring the Indexer node.
- Edit
$data/conf/<nodename>.conf
and enter the new server name. - 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.
- 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 >';
- Log in to the Management Server and stop the DataInsightComm, DataInsightWeb, and DataInsightConfig services.
- Perform 3 on the Management Server.
- 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
- Start all Data Insight services on the Management Server.
- On each worker node, except the Windows File Server agents, stop DataInsightComm and DataInsightConfig services.
- 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
- 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.