You must install the SQL Compliance Manager Collection Service on each cluster node for the service to work correctly when a failure occurs on the primary cluster node hosting the Collection Service.
Before upgrading, changing, or uninstalling SQL Compliance Manager on the passive node, you must delete the following registry entry: HKEY_LOCAL_MACHINE\Software\Idera\SQLcompliance\CollectionService\TraceDirectory. This step is unnecessary for new installations.
To install SQL Compliance Manager services on cluster nodes:
- Log on with an administrator account to the computer on which you want to install SQL Compliance Manager.
- Run
SQLCMInstall.exein the root of the SQL Compliance Manager installation kit on the first cluster node. - Review the information you need to start the installation and click Next.
Select the SQL Compliance Manager setup type and uncheck the IDERA Dashboard setup type.
The IDERA Dashboard does not provide support for clustered environment installations. If you want to use the IDERA Dashboard, review Deploy the IDERA Dashboard in a clustered environment.
Review and accept the license agreement by selecting the I accept the terms and conditions of the End User License Agreement checkbox.
- Specify if you want to register SQL Compliance Manager with an existent IDERA Dashboard.
If you select Yes, you need to provide the IDERA Dashboard location and administrator credentials. - Specify the location in which you want to install SQL Compliance Manager.
- Enable the Clustered Environment checkbox and select whether you are installing SQL Compliance Manager in an active or a passive node.
Specify a SQL Server Instance and a form of authentication to create the SQL Compliance Manager repository.
Test the connections to make sure the information is correct and click Next. - If you install on the currently active node, specify a trace directory on a shared disk, and click Next.
If you install on a passive node, the wizard skips this step. - Type the appropriate credentials in the provided fields under which the IDERA services run, and click Next.
IDERA uses this account to connect, discover, and gather configuration information from SQL Servers in your Business environment, the installer grants the "Log on as a Service" right to the account that you specify. - Review the installation settings and click Install.
- In Windows Services, stop the SQL Compliance Manager Collection service and set the Startup type to Manual.
Repeat the previous steps on each cluster node. Point to the SQL Compliance Manager Repository installed on the first node.
You cannot perform the installations concurrently, as the installers collide when checking the repository. You must perform the installations sequentially.
Once the installation of SQL Compliance Manager is completed, proceed to Register the SQL Compliance Manager Collection Service as a clustered resource.
When a primary node of an AG becomes a secondary node, previously collected trace files fail to process and remain gathered on the Passive node. Once the node becomes Active the trace files continue to process normally.