Arctera Enterprise Vault™ eDiscovery Installation Guide

Last Published:
Product(s): Enterprise Vault (15.2)
  1. Introducing eDiscovery
    1.  
      About eDiscovery desktop application
    2.  
      About eDiscovery web application
    3.  
      Feature comparison: Arctera eDiscovery desktop application Vs Arctera eDiscovery web application
    4.  
      Key features of eDiscovery
    5. Product documentation
      1.  
        White papers on the Arctera Support website
      2.  
        eDiscovery training modules
  2. Preparing to install eDiscovery
    1. Configuration options for eDiscovery
      1.  
        eDiscovery configuration for large installations
      2.  
        eDiscovery configuration for smaller installations
    2.  
      Supported versions of Enterprise Vault in eDiscovery environments
    3. Prerequisites for Arctera eDiscovery
      1.  
        Prerequisites for the SQL Server computer
      2.  
        Prerequisites for the Arctera eDiscovery server computer
      3.  
        Prerequisites for the Enterprise Vault server computer
    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 eDiscovery environment
    8.  
      Disabling the Windows Search Service on the eDiscovery server
    9.  
      Ensuring that the Windows Server service is running on the eDiscovery 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 eDiscovery
    1. Installing the eDiscovery server software
      1.  
        Allowing Enterprise Vault to communicate with eDiscovery through the Windows firewall
      2. Creating the configuration database and customer databases
        1.  
          Configuring analytics database locations
      3. Setting up a Insight eDiscovery Custodian Manager website
        1.  
          Assigning the required Active Directory permissions to the Insight eDiscovery Custodian Manager synchronization account
      4.  
        Uploading the eDiscovery report templates
      5. Configuring eDiscovery for use in a SQL Server Always On environment
        1.  
          Using SQL Server Reporting Services in an Always On environment
      6. Installing eDiscovery in a clustered environment
        1.  
          Configuring eDiscovery for use in a Network Load Balancing cluster
      7.  
        Maximizing security in your eDiscovery databases
  4. Appendix A. Ports that eDiscovery uses
    1.  
      Default ports for eDiscovery
    2.  
      Changing the ports that eDiscovery uses
  5. Appendix B. Troubleshooting
    1.  
      Error messages appear in the event log when upgrading to eDiscovery 15.2
    2.  
      Enterprise Vault eDiscovery Manager service not created
    3.  
      Enterprise Vault eDiscovery 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 eDiscovery customer databases when Symantec Endpoint Protection is running
    6.  
      Permissions error when uninstalling the eDiscovery client from a UAC-enabled computer
    7.  
      Uninstalling the eDiscovery client from a shared location may prevent other users from starting the client
  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 eDiscovery

Configuring analytics database locations

When you enable a case for analytics, eDiscovery must fetch all the case items from Enterprise Vault into the customer database, and index them. This requires a large amount of disk space. eDiscovery lets you define locations to host the analytics table file groups and indexes. You can add more locations when you need more disk space.

The Customer page of the eDiscovery Manager website lists existing analytics database locations, and lets you add more. Next to each location, check marks in the Table File Group and Full Text Indexes columns show whether the location is used for table files, search indexes, or both.

When you plan and configure analytics database locations, consider the following:

  • The volume of data. The collection and indexing of analytics data can generate very large databases and index files. As a rough guide, collecting one million items that are all 20 kilobytes in size can produce a database that is 40 gigabytes or more in size. However, this can vary from one environment to another.

    The Best Practices Guide for eDiscovery provides extensive information on how to size your eDiscovery databases appropriately. You can obtain this guide from the Arctera Support website at https://www.veritas.com/docs/100024378.

  • Performance. Host each database location on a physically separate disk. If you have more than one analytics database location, eDiscovery uses them in rotation to spread the data and the disk access requirements.

    Each eDiscovery case uses only one location for the search index and one location for the database.

The following examples show two valid configurations for analytics database locations.

Table: Analytics database locations: example 1

Location

Table File Group

Full Text Indexes

C:\SQL\Data

Selected

Selected

D:\SQL\Data

Selected

Selected

E:\SQL\Data

Selected

Selected

F:\SQL\Data

Selected

Selected

Table: Analytics database locations: example 2

Location

Table File Group

Full Text Indexes

C:\SQL\Data

Cleared

Selected

D:\SQL\Data

Cleared

Selected

E:\SQL\Data

Selected

Cleared

F:\SQL\Data

Selected

Cleared

To add a database location for analytics

  1. Browse to the eDiscovery Manager website.
  2. Right-click the appropriate customer, and then click Properties.
  3. Under Database Locations For Analytics, click New Location.
  4. Enter the path to the new database location. Note the following:

    • The database locations must reside on the SQL server, and you must use local paths to refer to them. For example, do not use UNC paths to refer to database locations.

    • The eDiscovery Manager website does not verify that the specified locations exist. You must ensure that the paths are valid.

  5. Select Table File Group, Full Text Indexes, or both.
  6. Click OK next to the new location.
  7. Repeat steps 3 through 6 if you want to add more database locations.