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.1
- 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
- Home page of Compliance Accelerator website not found
- 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
Using SQL Server Reporting Services in an AlwaysOn environment
Microsoft does not fully support the use of SQL Server Reporting Services in an AlwaysOn environment and, consequently, neither does Compliance Accelerator. As the following article explains, however, it is possible to configure Reporting Services to work with an AlwaysOn availability group:
https://msdn.microsoft.com/hh882437.aspx
In summary, you must do the following to make the Compliance Accelerator reports work in an AlwaysOn environment:
Install SQL Server Reporting Services on all the replicas in the availability group.
On all the secondary replicas, assign the same reporting server credentials to the Vault Service account as you assigned to this account on the primary replica:
The System Administrator role
The Content Manager role on the Home folder
Use the Report Manager tool that comes with SQL Server to assign the credentials.
On the primary replica, use the Encryption Keys page of Reporting Services Configuration Manager to back up the encryption keys for the report server databases to a file.
Add the report server databases, ReportServer and ReportServerTempDB, to the availability group.
When you upload the Compliance Accelerator report templates through the Accelerator Manager website, take care to specify the correct URL for the reporting server. Rather than specify the name or address of a standalone SQL reporting server, you must specify the virtual network name of the appropriate availability group listener. For example, you might specify the reporting server URL as follows:
http://availability_group_listener/ReportServer
After failover occurs, do the following:
Use the Reporting Services Configuration Manager to point the report server service on the new primary replica to the failed-over databases, ReportServer and ReportServerTempDB.
Take care to specify the report server database credentials for the same domain user as you previously specified on the old primary replica.
On the Encryption Keys page of Reporting Services Configuration Manager, restore the encryption keys from the backup file that you previously created on the old primary replica.