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: |
SQLCMInstall.exe
in the root of the SQL Compliance Manager installation kit on the first cluster node.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.
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. |
| | | | | | | |