Enterprise Vault™ Discovery Accelerator Installation Guide

Last Published:
Product(s): Enterprise Vault (14.2)
  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 Always On environment
        1.  
          Using SQL Server Reporting Services in an Always On 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 14.2
    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

Using SQL Server Reporting Services in an Always On environment

Microsoft does not fully support the use of SQL Server Reporting Services in an Always On environment and, consequently, neither does Discovery Accelerator. As the following article explains, however, it is possible to configure Reporting Services to work with an Always On availability group:

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

In summary, you must do the following to make the Discovery Accelerator reports work in an Always On environment:

  • Install SQL Server Reporting Services on all the replicas in the availability group.

  • On all the secondary replicas, assign the same reporting server credentials to the Vault Service account as you assigned to this account on the primary replica:

    • The System Administrator role

    • The Content Manager role on the Home folder

    Use the Report Manager tool that comes with SQL Server to assign the credentials.

    See Uploading the Discovery Accelerator report templates.

  • On the primary replica, use the Encryption Keys page of Reporting Services Configuration Manager to back up the encryption keys for the report server databases to a file.

  • Add the report server databases, ReportServer and ReportServerTempDB, to the availability group.

  • When you upload the Discovery Accelerator report templates through the Accelerator Manager website, take care to specify the correct URL for the reporting server. Rather than specify the name or address of a standalone SQL reporting server, you must specify the virtual network name of the appropriate availability group listener. For example, you might specify the reporting server URL as follows:

    http://availability_group_listener/ReportServer

  • After failover occurs, do the following:

    • Use the Reporting Services Configuration Manager to point the report server service on the new primary replica to the failed-over databases, ReportServer and ReportServerTempDB.

      Take care to specify the report server database credentials for the same domain user as you previously specified on the old primary replica.

    • On the Encryption Keys page of Reporting Services Configuration Manager, restore the encryption keys from the backup file that you previously created on the old primary replica.