Windows Server 2003 clustered environment

The following instructions guide you through the installation of SQL Diagnostic Manager in a Windows Server 2003 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:

1. Log on with an administrator account to the computer on which you want to install SQLDM.
2. Run Setup.exe in the root of the SQLDM installation kit on the first cluster node.
3. Click SQL Diagnostic Manager on the Quick Start window.
4. On the Welcome window of the setup program, click Next.
5. Review and accept the license agreement by clicking I accept the terms in the license agreement, and then click Next .
6. Accept the default installation folder, or click Change to specify a different folder, and click Next.
7. Select the Typical setup type and click Next.
8. Select the SQL Server instance and enter a database name.
9. Enter the service account information and click Next .
10. Click Install.
11. In Windows Services, stop the SQLDM Management service and set the Startup type to Manual.
12. In Windows Services, stop the SQLDM Collection service and set the Startup type to Manual.
13. In Windows Services, stop the SQLDM Predictive Analytics service and set the Startup type to Manual.

Configure the Cluster Resource Group

Cluster Resource Group settings must be modified to allow SQL Diagnostic Manager to recognize the cluster nodes.

To configure the Cluster Resource Group:

1. In the Cluster Administrator tool, create the Cluster Resource Group:
   • Select File > New > Group and give the group and description.
   • Add the nodes and click Finish .
2. In the Cluster Administrator tool, add a disk to the Cluster Resource Group:
   • Right-click the group you just created, select New > Resource and give it a name and description.
   • For the Resource Type, select Physical Disk .
   • Select the SQLdm group.
   • Click Next until you get to the last window and click Finish .
3. In the Cluster Administrator tool, add an IP address for the Cluster Resource Group:
   • Right-click the group and select New > Resource and give it a name and description.
   • Select the Resource type IP Address .
   • Enter the IP address that you acquired for your new Cluster Resource Group.
   • Click Finish .
4. In the Cluster Administrator tool, add the Network Name resource to the Cluster Resource Group:
   • Right-click the group and New > Resource and give it a name.
   • Select the Resource type Network Name .
   • Add the dependency for the IP address resource.
   • Specify the name and click Finish .
5. Select a Disk that is in a Cluster Resource Group and create a directory on that disk used to hold local data for the services.
6. On the primary node, create the default registry key and add the full data path value under HKEY_LOCAL_MACHINE\SOFTWARE\Idera\SQLdm\Default.
7. Create the DataPath value.
8. Select a Cluster Resource Group in which you want to define the SQLdm resources.
9. Create an IP Address resource for the SQLDM Services. If there is already an existing Network Name in the Cluster Resource Group, then you can skip this step.
   • Create an Network Name resource that maps to the IP Address
   • Create the Network Name resource and add the IP Address as a dependency
10. Create a Generic Service resource for the SQLdm Management Service.
    • Add the Disk for the shared data as a dependency
    • Add the Network Name as a dependency
    • Specify SQLdmManagementService$Default as the name of the service to start
11. After the service is added, right-click it and select Properties .
    • Select the Parameters tab and check the Use network name for computer name box
    • Select the Registry Replication tab and add SOFTWARE\Idera\SQLdm\Default
    • Click OK
12. Create a Generic Service resource for the SQLDM Collection Service.
    • Add the Disk for the shared data as a dependency
    • Add the Network Name as a dependency
    • Specify SQLdmCollectionService$Default as the name of the service to start
13. After the service is added, right-click it and select Properties .
    • Select the Parameters tab and check the Use network name for computer name box
    • Select the Registry Replication tab and add SOFTWARE\Idera\SQLdm\Default
    • Click OK
14. Create a Generic Service resource for the SQLdm Predictive Analytics Service.
    • Add the Disk for the shared data as a dependency
    • Add the Network Name as a dependency
    • Specify SQLdmPredictiveAnalyticsService$Default as the name of the service to start
15. After the service is added, right-click it and select Properties .
    • Select the Parameters tab and check the Use network name for computer name box
    • Select the Registry Replication tab and add SOFTWARE\Idera\SQLdm\Default
    • Click OK
16. In Windows Services, bring the SQLDM Management service resource online.
17. In Windows Services, bring the SQLDM Collection service resource online.
18. In Windows Services, bring the SQLDM Predictive Analytics service resource online.
    
    

 Complete the Cluster Configuration in SQL Diagnostic Manager

1. Use the Management Service Configuration wizard to force the services to re-register.
2. 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.
3. Verify that your configuration displays correctly in the SQLDM Desktop Client.