Veritas Enterprise Vault™ Compliance Accelerator Installation Guide
- Introducing Compliance Accelerator
- Preparing to install Compliance Accelerator
- Configuration options for Compliance Accelerator
- Supported versions of Enterprise Vault in Compliance Accelerator environments
- Prerequisites for Compliance 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 Compliance Accelerator environment
- Disabling the Windows Search Service on the Compliance Accelerator server
- Ensuring that the Windows Server service is running on the Compliance Accelerator server
- Configuring the SQL Server Agent service
- Assigning SQL Server roles to the Vault Service account
- Verifying that Enterprise Vault expands distribution lists
- Installing Compliance Accelerator
- Installing the Compliance Accelerator server software
- Allowing Enterprise Vault to communicate with Compliance Accelerator through the Windows firewall
- Creating the configuration database and customer databases
- Uploading the Compliance Accelerator report templates
- Configuring Compliance Accelerator for use in a SQL Server AlwaysOn environment
- Installing Compliance Accelerator in a clustered environment
- Maximizing security in your Compliance Accelerator databases
- Installing the Compliance Accelerator client software
- Uninstalling Compliance Accelerator
- Installing the Compliance Accelerator server software
- Appendix A. Ports that Compliance Accelerator uses
- Appendix B. Troubleshooting
- Error messages appear in the event log when upgrading to Compliance Accelerator 12.2
- 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 Compliance Accelerator customer databases when Symantec Endpoint Protection is running
- Permissions error when uninstalling the Compliance Accelerator client from a UAC-enabled computer
- Uninstalling the Compliance Accelerator client from a shared location may prevent other users from starting the client
Prerequisites for the SQL Server computer
The SQL Server computer must be running one of the following:
SQL Server 2012 x64 Edition, Original Release or later
SQL Server 2014 x64 Edition
SQL Server 2016 x64 Edition
Compliance Accelerator supports SQL Server AlwaysOn availability groups and failover cluster instances for high availability and disaster recovery.
The AlwaysOn 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 AlwaysOn 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 AlwaysOn features require that the SQL Server instances reside on Windows Server Failover Clustering nodes.
For the best results when deploying Compliance Accelerator in an AlwaysOn environment, we recommend that you ensure the following:
All the server instances that host availability replicas for an AlwaysOn availability group are using the same SQL Server collation. For more information, see the following Microsoft article:
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 master key. You can do this by exporting the service master 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: