Enterprise Vault™ Discovery Accelerator Installation Guide

Last Published:
Product(s): Enterprise Vault (12.5)
  1. Introducing Discovery Accelerator
    1.  
      Key features of Discovery Accelerator
    2.  
      About the Discovery Accelerator components
    3. Product documentation
      1.  
        White papers on the Veritas Support website
      2.  
        Discovery Accelerator training modules
  2. Preparing to install Discovery Accelerator
    1. Configuration options for Discovery Accelerator
      1.  
        Discovery Accelerator configuration for large installations
      2.  
        Discovery Accelerator configuration for smaller installations
    2.  
      Supported versions of Enterprise Vault in Discovery Accelerator environments
    3. Prerequisites for Discovery Accelerator
      1.  
        Prerequisites for the SQL Server computer
      2.  
        Prerequisites for the Discovery Accelerator server computer
      3.  
        Prerequisites for the Enterprise Vault server computer
      4.  
        Prerequisites for Discovery Accelerator client computers
    4.  
      Configuring Outlook to enable the processing of items with many attachments or many recipients
    5.  
      Setting the Windows and ASP.NET Temp folder permissions
    6. Security requirements for temporary folders
      1.  
        Granting additional users and groups access to the temporary folders
    7.  
      Disabling networking facilities that can disrupt a Discovery Accelerator environment
    8.  
      Disabling the Windows Search Service on the Discovery Accelerator server
    9.  
      Ensuring that the Windows Server service is running on the Discovery Accelerator server
    10.  
      Configuring the SQL Server Agent service
    11.  
      Assigning SQL Server roles to the Vault Service account
    12.  
      Installing and configuring the SQL full-text search indexing service
    13.  
      Verifying that Enterprise Vault expands distribution lists
  3. Installing Discovery Accelerator
    1. Installing the Discovery Accelerator server software
      1.  
        Allowing Enterprise Vault to communicate with Discovery Accelerator through the Windows firewall
      2. Creating the configuration database and customer databases
        1.  
          Configuring analytics database locations
      3. Setting up a Custodian Manager website
        1.  
          Assigning the required Active Directory permissions to the Custodian Manager synchronization account
      4.  
        Uploading the Discovery Accelerator report templates
      5. Configuring Discovery Accelerator for use in a SQL Server AlwaysOn environment
        1.  
          Using SQL Server Reporting Services in an AlwaysOn environment
      6. Installing Discovery Accelerator in a clustered environment
        1.  
          Configuring Discovery Accelerator for use in a Network Load Balancing cluster
      7.  
        Maximizing security in your Discovery Accelerator databases
    2. Installing the Discovery Accelerator client software
      1.  
        Modifying the configuration file for the Discovery Accelerator client
      2.  
        Using the MSI installer package to install the Discovery Accelerator client
  4. Appendix A. Ports that Discovery Accelerator uses
    1.  
      Default ports for Discovery Accelerator
    2.  
      Changing the ports that Discovery Accelerator uses
  5. Appendix B. Troubleshooting
    1.  
      Error messages appear in the event log when upgrading to Discovery Accelerator 12.5
    2.  
      Enterprise Vault Accelerator Manager service not created
    3.  
      Enterprise Vault Accelerator Manager service does not start
    4.  
      "Access is denied" message is displayed when you try to create a customer database on a UAC-enabled computer
    5.  
      Cannot create or upgrade Discovery Accelerator customer databases when Symantec Endpoint Protection is running
    6.  
      Permissions error when uninstalling the Discovery Accelerator client from a UAC-enabled computer
    7.  
      Uninstalling the Discovery Accelerator client from a shared location may prevent other users from starting the client

Prerequisites for the SQL Server computer

The SQL Server computer must be running one of the following:

  • SQL Server 2012 x64 Edition, Original Release or later

  • SQL Server 2014 x64 Edition, Original Release or later

  • SQL Server 2016 x64 Edition, Original Release or later

  • SQL Server 2017 x64 Edition, Original Release

Note:

The sort order/collation of the SQL Server installation must be case-insensitive to match the Enterprise Vault installation. Case-sensitive installations are not supported.

Discovery Accelerator supports SQL Server AlwaysOn availability groups and failover cluster instances for high availability and disaster recovery.

  • The AlwaysOn availability group feature maximizes availability at the database level. An availability group provides a failover environment for a discrete set of user databases, known as availability databases, which fail over together.

  • The AlwaysOn failover cluster instance feature provides availability for the entire instance - a failover cluster instance (FCI). On the network, an FCI appears to be an instance of SQL Server running on a single computer, but it provides failover from one node to another.

Both of these AlwaysOn features require that the SQL Server instances reside on Windows Server Failover Clustering nodes.

For the best results when deploying Discovery Accelerator in an AlwaysOn environment, we recommend that you ensure the following:

  • All the server instances that host availability replicas for an AlwaysOn availability group are using the same SQL Server collation. For more information, see the following Microsoft article:

    https://msdn.microsoft.com/library/ff878487.aspx

  • For the account under which the Enterprise Vault Accelerator Manager service will run (typically the Vault Service account), you have created the same login on all the server instances that host availability replicas. For more information, see the following Microsoft article:

    https://msdn.microsoft.com/hh270282.aspx

    Note that for non-contained availability databases, you must explicitly create logins on the server instances that host the availability replicas.

  • All the availability replicas have the same service master key. You can do this by exporting the service master key of the primary replica to a backup file, with which you can then import the key into each secondary replica. See the following Microsoft articles for instructions on how to perform these activities:

    https://msdn.microsoft.com/library/ms190337.aspx

    https://msdn.microsoft.com/library/ms187972.aspx