Veritas Enterprise Vault™ Compliance Accelerator Installation Guide
- Introducing Compliance Accelerator
- Preparing to install Compliance Accelerator
- Configuration options for Compliance Accelerator
- Prerequisites for Compliance Accelerator
- Security requirements for temporary folders
- Installing Compliance Accelerator
- Installing the Compliance Accelerator server software
- Configuring Compliance Accelerator for use in a SQL Server AlwaysOn environment
- Installing Compliance Accelerator in a clustered environment
- Installing the Compliance Accelerator client software
- Installing the Compliance Accelerator server software
- Appendix A. Ports that Compliance Accelerator uses
- Appendix B. Troubleshooting
Prerequisites for the Compliance Accelerator server computer
Table: Required software for Compliance Accelerator server installation lists the software items that you must install and configure on the computer that is to run the Compliance Accelerator server software.
Table: Required software for Compliance Accelerator server installation
Item | Notes |
---|---|
.NET Framework | You require .NET Framework 4.5.2. See the |
Enterprise Vault | If Compliance Accelerator is installed on a separate computer from Enterprise Vault, you must install the Enterprise Vault software on the Compliance Accelerator computer. As a minimum, you require an 11.0.1 version of one of the following:
See Supported versions of Enterprise Vault in Compliance Accelerator environments. There is no need to configure Enterprise Vault after you have installed it on your Compliance Accelerator server computer; do not run the Enterprise Vault configuration wizard. In addition, if the Enterprise Vault Admin service is running on your Compliance Accelerator server computer, we recommend that you stop it and set its startup type to Disabled. To search on content with Compliance Accelerator, set indexing on the Enterprise Vault archives to full. |
You require IIS 7.5 or later with ASP.NET, IIS 6.0 Management Compatibility, and Windows Authentication. | |
Notes client | You require version 8.5.3 or later of the Notes client so that client users can export Domino items. Install the client in single-user mode, using the account under which the Accelerator Manager service runs. |
You require Outlook 2013 so that client users can export Exchange Server items in PST format and download the original versions of the items. The export-to-PST feature requires a 32-bit version of Outlook 2013; it does not work with the 64-bit version. Add the AttachmentMax and RecipientMax values to the registry on the Compliance Accelerator server to avoid problems when processing items that have many attachments or many recipients. See Configuring Outlook to enable the processing of items with many attachments or many recipients. | |
Visual C++ Redistributable | You require both of the following:
The installation files for the Visual C++ 2008 SP1 package are in the |
Web browser | You require one of the following:
For optimum results, do the following:
|
Windows | You require Windows Server 2012, Standard Edition or DataCenter Edition. We recommend that you do the following:
|
For the best results, we recommend that you install the Compliance Accelerator server software on a computer that has the following:
64-bit architecture.
At least 4 GB of memory.
Sufficient hard drive space to accommodate the searches and export runs that you expect to undertake.
All transaction requests from Compliance Accelerator clients to the Enterprise Vault and Compliance Accelerator servers use the Temp folder of the Vault Service account for temporary storage. Therefore, you must ensure that this folder has sufficient free space to handle large Compliance Accelerator searches and export runs. On both the Compliance Accelerator and Enterprise Vault servers, the Vault Service account's Temp folder must be on a drive that has a minimum of 40 GB of free space. However, 80 GB of free space is preferable.
Exclude the Vault Service account's Temp folders from antivirus scanning.
Multiple hard drives. For example, you might use drive C for the operating system, drive D for the CD or DVD drive, drive E for the Temp folder of the Vault Service account, and drive F for the export output folder. You might split the Windows paging file across drives E and F.