Now that the IDERA Cluster Configuration Console is installed, you need to add the SQL Compliance Manager Agent to the clustered instance that is to be audited.
Use the following checklist to help you deploy and configure SQL Compliance Manager in a clustered environment.
|Follow these steps ...|
|Identify which cluster nodes host each virtual SQL Server instance. Make sure that you identify the currently active node as well as any passive nodes in the same cluster.|
|On each cluster node, open port 5200 for SQL Compliance Manager Agent communication.|
|For each cluster node, identify the folder you want to use for the SQL Compliance Manager Agent trace directory. If a cluster node hosts more than one virtual SQL Server instance, identify a trace directory for each additional instance you want to audit.|
|For each cluster node, identify the account you want to use for the SQL Compliance Manager Agent Service. Verify that this account can access the computer where you installed the Collection Server. Also make sure that this account belongs to the Administrators group on each node. Review the SQL Compliance Manager Agent Service permission requirements.|
Deploy the SQL Compliance Manager Agent to each cluster node using the Cluster Configuration setup program.
Add the SQL Compliance Manager Agent service on each cluster node using the Cluster Configuration Console.
Register the SQL Compliance Manager Agent as a generic service using the Microsoft Cluster Administrator tool.
Register each virtual SQL Server instance with SQL Compliance Manager using the Management Console. Note that you must choose manual deployment for the SQL Compliance Manager Agent.
Specify the SQL Server events you want to audit on each registered virtual SQL Server instance using the Management Console.
You must perform these steps on all nodes of the cluster.
On the CLR Trigger Location dialog window, specify the path on which trigger assembly files will reside. The path specified should be on a drive that is a part of the same resource group as the SQL Server instance to be audited.
Ensure the Agent Trace directory and the CLR Trigger location specified exist by creating the folder structure manually through Windows Explorer.
Registering the SQL Compliance Manager Agent service with Microsoft Failover Cluster Manager allows the Microsoft Cluster Service to manage the SQL Compliance Manager Agent service in failover situations. This configuration ensures that auditing will continue during a failover and no audit data is lost.
You must perform these steps only once, in the active node.
Go to the Registry Replication tab.
The Registry Replication tab is not available in Windows Server 2012.
If you are using Windows Server 2012, you must use the "Add-ClusterCheckpoint" PowerShell cmdlet to add the necessary setting.
For more information, see Add ClusterCheckPoint.
Add a specific registry path. To obtain the correct path, go to the IDERA Cluster Configuration Console and copy the Replicated Registry Key from the SQLcompliance Agent details.
On the Properties window, click Apply to save the changes, and click OK to return to the Resources tab.
After successfully deploy the SQL Compliance Manager Agent, you can start auditing your virtual SQL Server instances.