Veritas Data Insight Installation Guide
- Understanding the Veritas Data Insight architecture
- About the Collector worker node
- About Veritas Data Insight installation tiers
- Preinstallation
- Installing Veritas Data Insight
- Upgrading Veritas Data Insight
- Post-installation configuration
- Installing Windows File Server agent
- Getting started with Data Insight
- Uninstalling Veritas Data Insight
- Appendix A. Installing Data Insight using response files
Installing a Linux Classification Server or Collector worker node
You can opt to install the Collector or Classification Server installed with Red Hat Enterprise Linux 9.0. The Linux collector can be used for scanning and auditing functionality of Clustered NetApp fileserver and Generic Devices for NFSv3 exports only.
Ensure the following before initiating installation of Classification Server or Collector on the Linux server:
Following packages should be installed on RHEL9 collector before installation otherwise installer will ask for these packages -
initscripts
chkconfig
libnsl
nfs-utils
The firewall is configured to allow access to port 8383 between the Management Server, Indexer, and Collector.
The worker node should be able to ping itself and other nodes.
SSH to the Linux server where you want to install the worker node. You can install the package either as root or as non-root user. Ensure that you are logged in as that user.
To install the worker node
- Run the following command to launch the installer package:
sh Veritas_DataInsight_linux_7_0_0_N_RHEL9_x64.sh
where N is the build number.
- Welcome to the Veritas Data Insight Setup Wizard appears. Click Next.
- In the License Agreement window, select I accept the agreement, and click Next.
- In the Configure Type of Install, select Classification Server or Collector, depending on the type of installation.
- Enable FIPS Mode? Yes [y], No [n]
FIPS are standards and guidelines for federal computer systems that are developed by National Institute of Standards and Technology (NIST) in accordance with the Federal Information Security Management Act (FISMA) and approved by the Secretary of Commerce. Choice of FIPS mode should be same for Management server and Worker nodes. You can enable FIPS mode only during fresh product installation or upgrade. You will not be able to make any changes post product installation or upgrade.
- In the Select Destination Directory window, browse to the directory in which you want Classification Server or Collector to be installed. By default, the destination directory is /opt/DataInsight. Click Next.
- In the Configure Data Directory window, browse to the location where you want to store the product data. Select a location with enough free space, permissions, and high-performance disks.
- In the Worker Node address window, enter the Fully Qualified Host Name (FQHN) or IP address of the host. Ensure that the Management Server and the other worker nodes are able to resolve this hostname.
- In the Configure Networking window, enter the following information:
Communication Service Port
Configuration Service Port
Configuration service is a process that provides interface to configuration and other product data stored on the local system. This service port does not need to be accessible outside the host machine.
Note:
The installer validates whether the appropriate ports are free to accept connections.
- To register the worker node with the Management Server after you exit setup, select the Launch Worker Node Registration Wizard after exit checkbox.
See Registering the worker node.
Note:
Based on your Operating System's GUI settings and SSH client being used; Worker Node Registration GUI may not be available; in such cases to register the worker node, execute RegisterWorkerNode binary located in the Data Insight installation bin directory.
- To exit setup, click Finish.
- Optionally, to use an alternate location for the log files, edit the following files that are in the /opt/DataInsight/conf directory, to replace /opt/DataInsight/log with the new log location:
cli_logging.properties dscli_logging.properties commd_logging.properties watchdog_logging.properties webserver_logging.properties
Export the new log directory using the following command:
export MATRIX_LOG_DIR=/DataInsight/log
Add the export entry to .bash_profile file of the user to reflect the change when you restart the system. Execute the following command to update the profile path:
source .bash_profile
- When installing as a non-root user, after you have registered this node with the Management Server, add following entries to /etc/rc.local to automatically start the services after you restart the system:
su - <name of non-root user> # export MATRIX_LOG_DIR=/DataInsight/log (Optional) /opt/DataInsight/bin/DataInsightConfig start /opt/DataInsight/bin/DataInsightComm start /opt/DataInsight/bin/DataInsightWatchdog start exit
Run below command by root to provide appropriate permissions to non-root user:
setfacl -R -m u:non-root:rwx /etc/systemd/system
Where, non-root is username of non-root account. Replace non-root with your user.
Modify /etc/sudoers using visudo editor to add below entries for you user
non-root ALL=(ALL) NOPASSWD: /usr/bin/systemctl * non-root ALL=(ALL) NOPASSWD: /usr/bin/mount * non-root ALL=(ALL) NOPASSWD: /usr/bin/umount * non-root ALL=(ALL) NOPASSWD: /usr/bin/chown * non-root ALL=(ALL) NOPASSWD: /usr/bin/chmod * non-root ALL=(ALL) NOPASSWD: /home/non-root/DataInsight/bin/scanner *
Replace non-root with you user.
Replace /home/non-root/DataInsight/bin/scanner with <your INSTALL_DIR>/scanner.
Points to remember:
The DataInsightConfig service does not start after registration if the queryd.lock is present in the /tmp folder. The lock file is present if the installation is done using root, or when the machine is restarted. You must delete the queryd.lock file before you restart the DataInsightConfig service.
If previous installation is done using root user and Data Insight is configured for non-root user, delete following files:
rm /tmp/i4jdaemon__DIdata_DataInsight_bin_DataInsightComm rm /tmp/i4jdaemon__DIdata_DataInsight_bin_DataInsightWatchdog rm /var/run/queryd.pid