How to configure a VCS SQL Server group to monitor and control MSDTC and/or the SQLServerAgent
| Article:TECH10593 | | | Created: 2001-01-11 | | | Updated: 2004-01-21 | | | Article URL http://www.symantec.com/docs/TECH10593 |
Problem
How to configure a VCS SQL Server group to monitor and control MSDTC and/or the SQLServerAgent
Solution
The VERITAS Cluster Server (VCS) SQL Enterprise Agent
is set by default to monitor the SQLServer service only. In some instances, it
may be desirable to expand the agent's capabilities and have MSDTC and the
SQLServerAgent under the agent's control. This TechNote will describe the
procedures for modifying the SQL agent to facilitate control of these resources.
Resolution:
1. Open the VERITAS Cluster Manager; highlight and
offline the SQL service group. (Figure 1)
Figure 1
2. Highlight the SQL service group and select Add
Resource. (Figure 2)
Figure 2
3. In the Add Resource box, type the name of the
resource to be added in the Resource Name section (in this case, MSDTC).
Next, select the Generic Service resource from the Resource Type listing.
Finally, select the SQL group from the available group listings in the
Service Group selection box*. (Figure 3)
Figure 3
4. Once the resources have been added, verify that they
appear under the Generic Service resource listing in Cluster Manager, under the
SQL service group. (Figure 4)
Figure 4
5. Open Control Panel Services and verify that the
MSDTC and SQLServerAgent service startup types are set to manual on both nodes.
(Figure 5)
Figure 5
6. Open Cluster Manager and select the Attributes
tab. Highlight each of the resources and double-click on the Service Name
attribute. Enter the name of the service to be monitored in the Scalar
Value box (in this case, MSDTC and SQLServerAgent). (Figure
6)
Figure 6
7. Highlight the SQL service group and select the
Resource tab. The new resources that have been added are listed but are
not part of the current dependency tree. (Figure 7)
Figure 7
8. Highlight the MSDTC resource and link it to the
MSSQL resource so that the MSDTC is the parent resource. If done correctly, the
following message will appear. (Figure 8)
Figure 8
9. Highlight the SQLServerAgent and link it to the
MSSQL resource so that the SQLServerAgent is the parent resource. If done
correctly, the following message will appear. (Figure 9)
Figure 9
10. Through Cluster Manager, right-click on the SQL
group and select Online. Confirm that all of the resources come online.
(Figure 10)
Figure 10
*Setting the MSDTC and/or the SQLServerAgent resources
to critical will cause the entire SQL service group to fault, in the event that
either of these resources faults.
Thank you.