Cluster Server 8.0 Implementation Guide for Microsoft SQL Server - Windows
- Section I. Introducing Veritas InfoScale solutions for application high availability
- Understanding the InfoScale solutions for application high availability
- About the VCS agents for SQL Server
- How VCS monitors storage components
- How application availability is achieved in a physical environment
- How is application availability achieved in a VMware virtual environment
- Managing storage and installing the VCS agents
- Installing SQL Server
- Understanding the InfoScale solutions for application high availability
- Section II. Configuring SQL Server in a physical environment
- Overview
- Configuring the VCS cluster
- Configuring the SQL Server service group
- Configuring a SQL Server service group using the wizard
- Making SQL Server user-defined databases highly available
- Verifying the service group configuration
- Administering a SQL Server service group
- Configuring an MSDTC service group
- Configuring the standalone SQL Server
- Configuring an Active/Active cluster
- Configuring a disaster recovery setup
- Section III. Configuring SQL Server in a VMware environment
- Configuring application monitoring using the Veritas High Availability solution
- Administering application monitoring
- Administering application monitoring using the Veritas High Availability tab
- Administering application availability using Veritas High Availability dashboard
- Understanding the dashboard work area
- Section IV. Appendixes
- Appendix A. Troubleshooting
- Error and warning messages from VCS agent for SQL Server
- Troubleshooting application monitoring configuration issues
- Troubleshooting Veritas High Availability view issues
- Appendix B. Using the virtual MMC viewer
- Appendix A. Troubleshooting
MSDTC sample dependency graph
The following figure is a sample dependency graph, which depicts the resources and their dependencies a typical MSDTC service group.
An MSDTC service group is configured to monitor the state of the MSDTC services in a VCS cluster.
As the dependency graph depicts:
The virtual name for the MSDTC server is configured using the Lanman resource, and the service group IP address is configured using the IP and NIC resources.
This graphic depicts shared storage configured in a NetApp environment.
If the shared storage is managed using Windows LDM, the VCS Mount and DiskRes resources replace the NetAppSnapDrive, NetAppSnapMirror, and NetAppFiler resources.
In case of non-shared storage managed using Windows LDM, the VCS Mount and NativeDisks resources should be configured instead.
In case the storage belongs to a VMware virtual environment, the VCS Mount, NativeDisks, and VMwareDisks resources are configured instead of the NetApp resources.
The MSDTC registry is replicated using the RegRep and RegRepNetAppSnapDrive resources.
The MSDTC resource comes online after each of these resources are brought online.