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
Before configuring the MSDTC service group
Note the following prerequisites before you configure the MSDTC service group:
You must be a Cluster Administrator. This user classification is required to create and configure a service group.
You must be a local Administrator on the node where you run the wizard.
Verify that the VCS agent for SQL Server is installed on all cluster nodes.
Verify that the VCS cluster is configured using the VCS Cluster Configuration Wizard (VCW).
Verify that the MSDTC service is installed on all nodes that will participate in the MSDTC Server service group.
Verify that the Distributed Transaction Coordinator (MSDTC) service is stopped.
Verify that you have created the volumes or LUNs (virtual disks) for storing MSDTC log and MSDTC registry replication information.
Verify that the volumes or LUNs created for the MSDTC logs and registry replication information are mounted or connected to the node where you run the wizard. In case of a shared storage configuration, ensure that they are dismounted or disconnected from all other nodes.
If you have configured a firewall, add the required ports and services to the firewall exceptions list.
For a detailed list of services and ports, refer to the Veritas InfoScale Installation and Upgrade Guide.
Keep the following information ready with you; the wizard prompts you for these details:
A unique virtual name for the MSDTC Server. This is the name that is used by MSDTC clients to connect to the MSDTC Server. The DTC service runs under this virtual name.
A unique virtual IP address for the for the MSDTC Server.
The virtual IP address is required only if you wish to configure an IPv4 address. In case of IPv6, the wizard prompts you to select the IPv6 network and automatically generates an IPv6 address that is valid and unique on the network. The wizard uses the prefix that is advertised by the router on the IPv6 network.