Enterprise Vault™ Compliance Accelerator Installation Guide

Last Published:
Product(s): Enterprise Vault (14.4)
  1. Introducing Compliance Accelerator
    1.  
      Key features of Compliance Accelerator
    2.  
      About the Compliance Accelerator components
    3. Product documentation
      1.  
        White papers on the Veritas Support website
  2. Preparing to install Compliance Accelerator
    1. Configuration options for Compliance Accelerator
      1.  
        Compliance Accelerator configuration for large installations
      2.  
        Compliance Accelerator configuration for smaller installations
    2.  
      Supported versions of Enterprise Vault in Compliance Accelerator environments
    3. Prerequisites for Compliance Accelerator
      1.  
        Prerequisites for the SQL Server computer
      2.  
        Prerequisites for the Compliance Accelerator server computer
      3.  
        Prerequisites for the Enterprise Vault server computer
      4.  
        Prerequisites for Compliance Accelerator client computers
      5. Prerequisites for Veritas Advanced Supervision
        1.  
          Additional requirements for Veritas Advanced Supervision
        2.  
          Set Kerberos Trusted Delegation
    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 Compliance Accelerator environment
    8.  
      Disabling the Windows Search Service on the Compliance Accelerator server
    9.  
      Ensuring that the Windows Server service is running on the Compliance 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
    14. Configuring Intelligent Review API Authentication and Authorization
      1.  
        Setting Kerberos trusted delegation between Compliance Accelerator Servers and Compliance Accelerator Database Servers
      2.  
        Setting Kerberos trusted delegation between Compliance Accelerator Servers and Compliance Accelerator Database Servers on IP address
  3. Installing Compliance Accelerator
    1. Installing the Compliance Accelerator server software
      1.  
        Allowing Enterprise Vault to communicate with Compliance Accelerator through the Windows firewall
      2.  
        Creating the configuration database and customer databases
      3.  
        Uploading the Compliance Accelerator report templates
      4.  
        Configuring a dedicated server for Intelligent Review processing (optional deployment configuration)
      5. Configuring Compliance Accelerator for use in a SQL Server Always On environment
        1.  
          Using SQL Server Reporting Services in an Always On environment
      6. Installing Compliance Accelerator in a clustered environment
        1.  
          Configuring Compliance Accelerator for use in a Network Load Balancing cluster
      7.  
        Maximizing security in your Compliance Accelerator databases
    2. Installing the Compliance Accelerator client software
      1.  
        Modifying the configuration file for the Compliance Accelerator client
      2.  
        Using the MSI installer package to install the Compliance Accelerator client
    3.  
      Uninstalling Compliance Accelerator
  4. Appendix A. Ports that Compliance Accelerator uses
    1.  
      Default ports for Compliance Accelerator
    2.  
      Changing the ports that Compliance Accelerator uses
  5. Appendix B. Troubleshooting
    1.  
      Error messages appear in the event log when upgrading to Compliance Accelerator 14.4
    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 Compliance Accelerator customer databases when Symantec Endpoint Protection is running
    6.  
      Permissions error when uninstalling the Compliance Accelerator client from a UAC-enabled computer
    7.  
      Uninstalling the Compliance Accelerator client from a shared location may prevent other users from starting the client
    8.  
      Error messages when the Intelligent Review (IR) API authentication and authorization fails
  6. Appendix C. Installing and configuring the Enhanced Auditing feature
    1.  
      Overview
    2.  
      Prerequisites for the Enhanced Auditing feature
    3.  
      Installing the Enhanced Auditing feature
    4.  
      Post installation steps
    5.  
      Upgrading the Enhanced Auditing setup
    6.  
      Modifying the Enhanced Auditing setup
    7.  
      Repairing the Enhanced Auditing setup
    8.  
      Uninstalling the Enhanced Auditing setup
    9.  
      Managing access from Veritas Advanced Supervision

Prerequisites for the SQL Server computer

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

  • SQL Server 2014 SP3 x64 Edition, Original Release or later

  • SQL Server 2016 SP2 x64 Edition, Original Release or later

  • SQL Server 2017 x64 Edition, Original Release

  • SQL Server 2019 x64 edition, Enterprise and Standard

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.

Compliance Accelerator supports SQL Server Always On availability groups and failover cluster instances for high availability and disaster recovery.

  • The Always On 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 Always On 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 Always On features require that the SQL Server instances reside on Windows Server Failover Clustering nodes.

For the best results when deploying Compliance Accelerator in an Always On environment, we recommend that you ensure the following:

  • All the server instances that host availability replicas for an Always On 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 primary key. You can do this by exporting the service primary 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