Enterprise Vault™ Compliance Accelerator Installation Guide

Last Published:
Product(s): Enterprise Vault (15.1)
  1. Introducing Compliance Accelerator
    1.  
      About Compliance Accelerator desktop application-specific updates
    2. 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 Veritas Surveillance
        1.  
          Additional requirements for Veritas Surveillance
        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.  
        Configuring a dedicated server for Intelligent Review processing (optional deployment configuration)
      4. Configuring Compliance Accelerator for use in a SQL Server Always On environment
        1.  
          Using SQL Server Reporting Services in an Always On environment
      5. Installing Compliance Accelerator in a clustered environment
        1.  
          Configuring Compliance Accelerator for use in a Network Load Balancing cluster
      6.  
        Maximizing security in your Compliance Accelerator databases
    2.  
      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 15.1
    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.  
      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 Surveillance
  7. Appendix D. Introducing Veritas Surveillance web client
    1.  
      About Veritas Surveillance
    2.  
      Feature comparison: Compliance Accelerator desktop application Vs Veritas Surveillance web application

Configuring Compliance Accelerator for use in a SQL Server Always On environment

You may want to implement high availability and disaster recovery for Compliance Accelerator by configuring it for use in an SQL Server Always On environment. An Always On solution can take advantage of two major SQL Server features for configuring high availability: availability groups and failover cluster instances. The SQL Server documentation provides extensive instructions on how to configure applications for use in such environments.

If you move your Compliance Accelerator databases from a standalone SQL Server computer to an Always On availability group or failover cluster instance (FCI), you must update your configuration accordingly. The following procedures outline the required steps.

Caution:

If you are upgrading to the latest version of Compliance Accelerator from an earlier version, you must complete the upgrade before you move the databases to an Always On availability group or FCI. You cannot move the databases and then upgrade Compliance Accelerator.

To configure Compliance Accelerator for use in a SQL Server Always On environment

  1. Open the Accelerator Manager website (http://server_name/EVBAAdmin).
  2. In the left pane of the Accelerator Manager website, right-click the server name and then click Properties.

  3. Set the required details for the Compliance Accelerator configuration database. You can specify either of the following:

    • The name or IP address of a standalone SQL Server computer.

    • The virtual network name or IP address of an Always On availability group listener or FCI.

    You must append the port number if you have chosen to use a non-default port. For example, SQLServer,1234.

  4. For each customer database, do the following:

    • In the left pane of the Accelerator Manager, right-click the required database and then click Properties.

    • In the SQL Server field, set the required details for the database.

      As before, you can specify the name or IP address of a standalone SQL Server computer or an Always On availability group listener or FCI; and you must append the port number if you have chosen to use a non-default port.