Veritas Data Insight 6.1 Installation Guide

Last Published:
Product(s): Data Insight (6.1)
  1. Understanding the Veritas Data Insight architecture
    1.  
      About Veritas Data Insight
    2.  
      About the Management Server
    3. About the Collector worker node
      1.  
        About the Collector
      2.  
        About the Scanner
    4.  
      About the Indexer worker node
    5.  
      About the Classification Server
    6.  
      About the Self-Service Portal node
    7.  
      About Communication Service
    8.  
      About the DataInsightWatchdog service
    9.  
      About the DataInsightWorkflow service
    10. About Veritas Data Insight installation tiers
      1.  
        About three-tier installation
      2.  
        About two-tier installation
      3.  
        About single-tier installation
  2. Preinstallation
    1.  
      Preinstallation steps
    2.  
      Operating system requirements
    3. System requirements for Veritas Data Insight components
      1.  
        System requirements for classification components
    4.  
      Supported file servers and platforms
    5.  
      Supported browsers
    6.  
      List of ports
    7.  
      Web server version
  3. Installing Veritas Data Insight
    1.  
      About installing Veritas Data Insight
    2.  
      Performing a single-tier installation
    3.  
      Performing a two-tier installation
    4.  
      Performing a three-tier installation
    5.  
      Installing the Management Server
    6.  
      Installing the worker node
    7.  
      Installing the Classification Server
    8.  
      Installing the Self-Service Portal
    9.  
      Installing a Linux Indexer worker node
  4. Upgrading Veritas Data Insight
    1.  
      Upgrading Data Insight to version
    2.  
      Upgrading the product data using the Upgrade Data Wizard
    3.  
      Names and locations of cache files
    4.  
      Upgrading the Data Insight web service for SharePoint
  5. Post-installation configuration
    1.  
      Post-installation configuration
    2.  
      Registering the worker node
    3. About post-installation security configuration for Management Server
      1.  
        About SSL client/server certificates
      2.  
        Generating Management Console certificate
    4.  
      Configuring your corporate firewall
  6. Installing Windows File Server agent
    1.  
      About Windows File Server agent
    2.  
      Installing Windows File Server agent manually
    3.  
      Configuring the Windows File Server using ConfigureWindowsFileServer.exe
  7. Getting started with Data Insight
    1.  
      About the Data Insight Management Console
    2.  
      Logging in to the Data Insight Management Console
    3.  
      Logging out of the Data Insight Management Console
    4.  
      Displaying online help
  8. Uninstalling Veritas Data Insight
    1.  
      Uninstalling Veritas Data Insight
  9. Appendix A. Installing Data Insight using response files
    1.  
      About response files
    2.  
      Installing Data Insight using response files
    3.  
      Sample response files

Sample response files

The following example shows a response file for the Management Server:

# Installation folder

sys.installationDir=C\:\\Program Files\DataInsight

# Data folder

matrix.datadir=C\:\\DataInsight\\data

# Name for Management Server node

matrix.nodename=host.company.com

matrix.console.name=host.company.com

# Ports for DataInsightWeb, DataInsightComm, DataInsightConfig

matrix.webserver.port$Long=443

matrix.commd.port$Long=8383

matrix.queryd.port$Long=8282

matrix.install.mode=ms

matrix.worker.iswinnas$Boolean=false

# Username/Domain for initial administration

matrix.initial.admin.login=Administrator

matrix.initial.admin.domain=WISDOM

matrix.initial.admin.isgroup$Boolean=false

# If the Management Server is part of Active Directory domain, specify if Management Server domain should be scanned.

matrix.scan.ad$Boolean=true

# Specify whether services should be started after installation

matrix.ms.startServices$Boolean=true

sys.programGroupAllUsers$Boolean=true

createDesktopLinkAction$Boolean=true

createQuicklaunchIconAction$Boolean=true

sys.programGroupDisabled$Boolean=false

matrix.launch.console$Boolean=false

Sample response file for installing a Collector node

# Installation folder

sys.installationDir=C\:\\Program Files\DataInsight

# Data folder

matrix.datadir=C\:\\DataInsight\\data

#Address for Collector node

matrix.nodename=host.company.com

matrix.worker.name=host.company.com

# Ports for DataInsightComm, DataInsightConfig

matrix.commd.port$Long=8383

matrix.queryd.port$Long=8282

matrix.install.mode=worker

matrix.worker.isindexer$Boolean=true

createQuicklaunchIconAction$Boolean=true

sys.programGroupDisabled$Boolean=true

createDesktopLinkAction$Boolean=true

sys.programGroupAllUsers$Boolean=true

matrix.launch.register$Boolean=false

Sample response file for launching the worker node registration wizard

# Address of the Management Server

matrix.console.name=<IP address of the Management Server>

#Path to commd.keystore

matrix.ms.keystore=C\:\\DataInsight\\data\\commd.keystore

# Whether services should be started after registration

matrix.worker.startServices$Boolean=true

matrix.launch.console$Boolean=false

Sample response file for installing a server with the Collector and Indexer roles

# Installation folder

sys.installationDir=C\:\\Program Files\DataInsight

# Data folder

matrix.datadir=C\:\\DataInsight\\data

#Address for Collector node

matrix.nodename=host.company.com matrix.worker.name=host.company.com

# Ports for DataInsightWeb, DataInsightComm, DataInsightConfig

matrix.commd.port$Long=8383

matrix.queryd.port$Long=8282 matrix.install.mode=worker

matrix.worker.isindexer$Boolean=false

createQuicklaunchIconAction$Boolean=true

sys.programGroupDisabled$Boolean=true

createDesktopLinkAction$Boolean=true sys.programGroupAllUsers$Boolean=true

matrix.launch.register$Boolean=false

Sample response file for launching the worker node registration wizard

# Address of the Management Server

matrix.console.name=<IP address of the Management Server>

#Path to commd.keystore

matrix.ms.keystore=C\:\\DataInsight\\data\\commd.keystore

# Whether services should be started after registration

matrix.worker.startServices$Boolean=true

matrix.launch.console$Boolean=false

Sample response file for installing a Windows File Server node

Run the following command:

Veritas_DataInsight_windows_winnas_6_1_N_x64.exe - q - console - varfile <path to varfile> -wait <timeout>

# Installation folder

matrix.upgrade$Boolean=false

sys.installationDir=<INSTALLDIR>

#For example, C\:\\Program Files\DataInsight

matrix.install.mode=worker

matrix.worker.isindexer$Boolean=false

matrix.worker.iscollector$Boolean=true

matrix.worker.iswinnas$Boolean=true

matrix.datadir=<DATADIR>

#For example, C\:\\DataInsight\\data

matrix.worker.name=<FILER_FQDN>

# worker.name property is the name of Windows File Server.

matrix.commd.port$Long=8383

matrix.queryd.port$Long=8282

matrix.enable.drwatson$Boolean=true

matrix.launch.register$Boolean=false

matrix.launch.console$Boolean=false

#sys.programGroup.name=Veritas Data Insight

#sys.service.selected.114$Boolean=true

#sys.languageId=en

#sys.programGroup.linkDir=/usr/local/bin

#sys.service.startupType.1393=auto

#sys.programGroup.enabled$Boolean=true

#sys.service.selected.1393$Boolean=true

#sys.service.startupType.114=auto

#sys.programGroup.allUsers$Boolean=true

## Registration properties:

#matrix.register.node.during.install$Boolean=true

#matrix.register.node.varfile=<PATH TO VAR FILE>

# matrix.register.node.varfile can be the path of the varfile. For example, C\:\\Temp\\DataInsight\\winnas.varfile.

#matrix.console.name=<COLLECTOR FQDN>:<COMMD PORT>

(Default Communication Service port is 8383) For example, DICollector1.win.local:8383

#matrix.ms.keystore=<PATH TO KEYSTORE>

# For example, C\:\\Temp\\DataInsight\\commd.keystore

#matrix.shortcuts$Boolean=true

#matrix.worker.startServices$Boolean=true

#matrix.launch.configure.winnas.filer$Boolean=true

#matrix.launch.console$Boolean=false

Sample configuration file for configuring a Windows File Server as a filer

Navigate to <Data Insight Install directory>\bin folder and run the following command:

Configcli register_filer <Name of configuration file>

For example: Configcli register_filer C:\\tempp\\Registerfiler.conf

The configuration file contains the following properties:

filer.id=11

filer.name=FileServer1.SAMGWIN.local

filer.type=WINNAS

filer.scanNewSharesImmediately$Boolean=true

filer.monitorAllShares$Boolean=true

filer.excludeShares=*$

filer.winnas.clustered$Boolean=false

filer.winnas.with.agent=true

filer.indexer.name=Indexer1.SAMGWIN.local

filer.collector.name=Collector1.SAMGWIN.local

Where,

filer.id is the ID of the Windows File Server. If adding a new filer, leave this field empty.

filer.name is the FQDN of the Windows File Server.

filer.type will be WINNAS.

filer.indexer.name is the FQDN of the Indexer.

Sample response file for installing the Self-Service Portal node

sys.programGroupDisabled$Boolean=false

# Installation folder

sys.installationDir=C\:\\Program Files\DataInsight

sys.languageId=en

matrix.portal.port$Long=443

matrix.worker.iswinnas$Boolean=false

matrix.install.mode=worker

matrix.worker.winnas.plat=WLH

matrix.datadir=C\:\\DataInsight\\data

createQuicklaunchIconAction$Boolean=true

matrix.nodename=testnode.tulip.local

sys.programGroupName=Veritas Data Insight version

matrix.launch.console$Boolean=false

matrix.launch.register$Boolean=true

matrix.worker.isportal$Boolean=true

matrix.commd.port$Long=8383

sys.programGroupAllUsers$Boolean=true

matrix.worker.name= testnode.tulip.local

createDesktopLinkAction$Boolean=true

matrix.workflowd.port$Long=8686

matrix.queryd.port$Long=8282

sys.adminRights$Boolean=true

Sample response file to launch the worker node registration wizard to register the Collector, Indexer, Windows File Server, and the Portal nodes with the Management Console

matrix.launch.console$Boolean=false

sys.languageId=en

sys.adminRights$Boolean=true

matrix.console.name=10.209.109.239

sys.installationDir=C\:\\Program Files\DataInsight

matrix.worker.startServices$Boolean=true

matrix.ms.keystore=C\:\\TempDir\\keys\\commd.keystore

Sample response file to upgrade a Collector node

matrix.upgrade$Boolean=true

# Indicates that upgrade has been requested

matrix.upgrade.data.during.install$Boolean=true

# Indicates that data be upgraded automatically during the upgrade

matrix.upgrade.backup$Boolean=false

#Indicates if data directory should first be backed up temporarily before the data is upgraded.

matrix.backup.dir$String=

#Indicates where data should be backed up. If empty or not defined, %tmp% will be used

matrix.upgrade.backup.restore$Boolean=true

#Indicates if old data should be restored back in case upgrade fails. You must set matrix.upgrade.backup to true for this to take effect.

matrix.upgrade.backup.delete$Boolean=true

#Indicates if backup copy can be deleted after upgrade is successful. You must set matrix.upgrade.backup to true for this to take effect.

Sample response file to upgrade a Windows File Server Agent

matrix.upgrade$Boolean=true

# Indicates that upgrade has been requested.

matrix.upgrade.data.during.install$Boolean=true

#Indicates that data be upgraded automatically during the upgrade.

matrix.upgrade.backup$Boolean=false

#Response file if any to be passed to UpgradeData.exe whenmatrix.upgrade.data.during.install is set to true. This is optional and is generally not needed.

# The response file supports following variables:

#Format for UpgradeData.exe varfile

## Indicates if data directory should first be backed up temporarily before the data is upgraded.

matrix.backup.dir$String=

#Indicates where data should be backedup. If empty or not defined, %tmp% is used.

matrix.upgrade.backup.restore$Boolean=true

#Indicates if the old data should be restored in case upgrade fails. You must set matrix.upgrade.backup to true for this to take effect.

matrix.upgrade.backup.delete$Boolean=true

#Indicates if backup copy can be deleted after the upgrade is successful. You need to set matrix.upgrade.backup to true for this to take effect.