The following instructions guide you through the installation of SQL Diagnostic Manager in a Windows Server 2012 based clustered environment.
Things to consider before you install SQL Diagnostic Manager in a clustered environment
- Create a separate cluster resource group to host SQLDM services. A separate group allows the SQLDM services to fail without causing other resources in the group to failover.
- Before you create this separate cluster resource group, gather a dedicated IP, NetBIOS name, and a dedicated disk for the cluster resource group.
- SQLDM Collection, Management, and Predictive Analytics services can run as generic services on your newly-created cluster resource group.
- The system may request the network Name and network IP as part of cluster configuration.
Install SQLDM Services on Cluster Nodes
You must install the SQLDM services on each cluster node for the services to work correctly when a failure occurs on the primary cluster node hosting the SQLDM services.
To install SQLDM services on cluster nodes:
- Log on with an administrator account to the computer on which you want to install SQLDM.
- Run Setup.exe in the root of the SQLDM installation kit on the first cluster node.
- Click SQL Diagnostic Manager on the Quick Start window.
- On the Welcome window of the setup program, click Next.
- Review and accept the license agreement by clicking I accept the terms in the license agreement, and then click Next.
- Accept the default installation folder, or click Change to specify a different folder, and then click Next.
- Select the Typical setup type, and then click Next.
- Select the SQL Server instance and enter a database name.
- Enter the service account information, and then click Next.
- Click Install.
- In Windows Services, stop the SQLDM Management service and set the Startup type to Manual.
- In Windows Services, stop the SQLDM Collection service and set the Startup type to Manual.
- In Windows Services, stop the SQLDM Predictive Analytics service and set the Startup type to Manual.
Repeat the previous steps on each cluster node. Point to the SQLDM 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.
Configure the Cluster Resource Group
Cluster Resource Group settings must be modified to allow SQL Diagnostic Manager to recognize the cluster nodes. Note that in certain versions of 2012, the Registry Replication tab is missing. A PowerShell command, provided in the instructions below constitutes a workaround for this issue.
To configure the Cluster Resource Group:
- Select a disk that is configured in the Cluster Resource Group and create a directory on that disk that you want to use to hold local data for the services.
- On the primary node, edit the registry and add a new key named Default to the key \Software\Idera\SQLdm. In this key, add a string value called DataPath. Set its value to the full path to the data directory created in step 1 (as shown in the image at the end of the steps).
- In the Failover Cluster Management tool, right-click Roles> Configure Role....
- Click Next in the Before You Begin tab of the High Availability wizard.
- In the Select Role tab, select Generic Service.
- In the Select Service tab, select the SQLdm Management Service.
- Enter the network name and IP address for the SQLdm services.
- Select the clustered storage that hosts the path defined in step 1.
- Provide the Registry Replication defined in step 2.
- Verify the settings and click Next to complete the wizard.
- In Roles, click the newly created service name and stop Role.
- In Roles, select the newly created service name and select the Resources tab found at the bottom.
- Right-click on the SQLDM Management Service and select Properties
- On the Dependencies tab, add the name of service and disk, and then click Apply.
- On the General tab, select Use Network Name for computer name, and then click OK.
- To configure the Registry Replication entry, open PowerShell with administrator rights and execute the following command:
Add-ClusterCheckpoint -ResourceName "SQLdm Management Service (Default)" -RegistryCheckpoint "SOFTWARE\Idera\SQLdm\Default\DataPath"
- In Roles, right-click the newly created service and select Add a Resource and then select Generic Service
- Select the SQLDM Collection Service.
- Select Next and finish out the wizard.
- Right-click on the SQLDM Collection Service and select Properties.
- On the Dependencies tab, add the name of service and disk, and then click Apply.
- On the General tab, select Use Network Name for computer name, and click OK.
- To configure the Registry Replication entry, open PowerShell with administrator rights and execute the following command:
Add-ClusterCheckpoint -ResourceName "SQLdm Collection Service (Default)" -RegistryCheckpoint "SOFTWARE\Idera\SQLdm\Default\DataPath"
- In Roles, right-click the newly created service and select Add Resource and then select Generic Service
- Select the Predictive Analytics service from the list of resources
- Select Next and then Finish to exit the wizard
- Right-click on the SQLDM Predictive Analytics Service and select Properties.
- On the Dependencies tab, add the name of service and disk, and then click Apply.
- On the General tab, select Use Network Name for computer name, and click OK.
- To configure the Registry Replication entry, open PowerShell with administrator rights and execute the following command:
Add-ClusterCheckpoint -ResourceName "SQLdm Predictive Analytics Service(Default)" -RegistryCheckpoint "SOFTWARE\Idera\SQLdm\Default\DataPath"
- In Windows Services, bring the SQLDM Management service resource online.
- In Windows Services, bring the SQLDM Collection service resource online.
- In Windows Services, bring the SQLDM Predictive Analytics service resource online.
- On the active node on which you installed the SQLDM services, use the Management Service Configuration wizard (Start > All Programs > IDERA > SQL Diagnostic Manager > Tools > Management Service Configuration Wizard) to force the services to re-register.
- Test the configuration from the Management Service Configuration wizard before finishing the wizard.
Complete the Cluster Configuration in SQL Diagnostic Manager
Start the SQLDM Desktop Client and select SQLDM Repository. If the SQLDM Repository is clustered make sure to use the virtual server name for the SQL Server hosting the SQLDM Repository.