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
About the agent for MSDTC service
The MSDTC agent brings the MSDTC service online, monitors its status, and takes it offline. The agent provides high availability for the MSDTC service in a clustered environment.
Online | Brings the configured MSDTC service online. |
Offline | Takes the configured MSDTC service offline. |
Monitor | Monitors the configured MSDTC service. |
Clean | Forcibly stops the configured MSDTC service. Cleans up after a resource fails to come online, fails to go offline, or fails to detect as ONLINE when resource is in an ONLINE state. |
Note:
The agent for MSDTC comprises of two component; the MSDTC client and the MSDTC server. These components must not be configured on the same cluster node.
The MSDTC agent is configured as a resource of type MSDTC.
type MSDTC ( static int IMF{} = { Mode=3, MonitorFreq=5, RegisterRetryLimit=3 } static i18nstr ArgList[] = { "LanmanResName:VirtualName", "MountResName:MountPath", LogPath } str LanmanResName str MountResName i18nstr LogPath )
Table: MSDTC agent required attributes
Required Attributes | Definition |
---|---|
LanmanResName | Name of the Lanman resource on which the MSDTC resource depends. Type and dimension: string-scalar |
MountResName | The mount resource name on which the MSDTC resource depends. Type and dimension: string-scalar |
LogPath | The path for MSDTC logs. This attribute can take localized values. Type and dimension: string-scalar |