Enterprise Vault™ Discovery Accelerator Installation Guide
- Introducing Discovery Accelerator
- Preparing to install Discovery Accelerator
- Configuration options for Discovery Accelerator
- Supported versions of Enterprise Vault in Discovery Accelerator environments
- Prerequisites for Discovery Accelerator
- Configuring Outlook to enable the processing of items with many attachments or many recipients
- Setting the Windows and ASP.NET Temp folder permissions
- Security requirements for temporary folders
- Disabling networking facilities that can disrupt a Discovery Accelerator environment
- Disabling the Windows Search Service on the Discovery Accelerator server
- Ensuring that the Windows Server service is running on the Discovery Accelerator server
- Configuring the SQL Server Agent service
- Assigning SQL Server roles to the Vault Service account
- Installing and configuring the SQL full-text search indexing service
- Verifying that Enterprise Vault expands distribution lists
- Installing Discovery Accelerator
- Installing the Discovery Accelerator server software
- Allowing Enterprise Vault to communicate with Discovery Accelerator through the Windows firewall
- Creating the configuration database and customer databases
- Setting up a Custodian Manager website
- Uploading the Discovery Accelerator report templates
- Configuring Discovery Accelerator for use in a SQL Server Always On environment
- Installing Discovery Accelerator in a clustered environment
- Maximizing security in your Discovery Accelerator databases
- Installing the Discovery Accelerator server software
- Appendix A. Ports that Discovery Accelerator uses
- Appendix B. Troubleshooting
- Error messages appear in the event log when upgrading to Discovery Accelerator 15.0
- Enterprise Vault Accelerator Manager service not created
- Enterprise Vault Accelerator Manager service does not start
- "Access is denied" message is displayed when you try to create a customer database on a UAC-enabled computer
- Cannot create or upgrade Discovery Accelerator customer databases when Symantec Endpoint Protection is running
- Permissions error when uninstalling the Discovery Accelerator client from a UAC-enabled computer
- Uninstalling the Discovery Accelerator client from a shared location may prevent other users from starting the client
- Appendix C. Introducing Veritas Surveillance web client
- Appendix D. Installing and configuring the Enhanced Auditing feature
- Overview
- Prerequisites for the Enhanced Auditing feature
- Installing the Enhanced Auditing feature
- Post installation steps
- Upgrading the Enhanced Auditing setup
- Modifying the Enhanced Auditing setup
- Repairing the Enhanced Auditing setup
- Uninstalling the Enhanced Auditing setup
- Managing access from Discovery Accelerator
Configuring analytics database locations
When you enable a case for analytics, Discovery Accelerator must fetch all the case items from Enterprise Vault into the customer database, and index them. This requires a large amount of disk space. Discovery Accelerator 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 Accelerator 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 Discovery Accelerator provides extensive information on how to size your Discovery Accelerator databases appropriately. You can obtain this guide from the Veritas 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, Discovery Accelerator uses them in rotation to spread the data and the disk access requirements.
Each Discovery Accelerator 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 |
|---|---|---|
| Selected | Selected |
| Selected | Selected |
| Selected | Selected |
| Selected | Selected |
Table: Analytics database locations: example 2
| Cleared | Selected |
| Cleared | Selected |
| Selected | Cleared |
| Selected | Cleared |
To add a database location for analytics
- Browse to the Accelerator Manager website.
- Right-click the appropriate customer, and then click Properties.
- Under Database Locations For Analytics, click New Location.
- 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 Accelerator Manager website does not verify that the specified locations exist. You must ensure that the paths are valid.
- Select Table File Group, Full Text Indexes, or both.
- Click OK next to the new location.
- Repeat steps 3 through 6 if you want to add more database locations.