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
Creating an MSDTC service group
MSDTC is a global resource and is accessed by more than one SQL Server service group. VCS recommends configuring one MSDTC service group in per cluster. VCS provides a configuration wizard that guides you through the process of configuring an MSDTC service group. You can also use this wizard to modify an MSDTC service group configuration.
Note:
Veritas recommends that you create only one MSDTC Server service group in a cluster.
You must use the MSDTC Configuration Wizard to configure the MSDTC Server service group. You cannot use the SQL Server Configuration Wizard to perform this task.
To create an MSDTC service group
- Start the MSDTC Configuration Wizard from the Apps menu on the Start screen.
- In the Select Configuration Option panel, click MSDTC Server - Service Group Configuration, click Create, and then click Next.
- Review and verify that you have met the prerequisites for configuring an MSDTC Server service group and then click Next.
- On the Service Group Configuration panel, specify the service group name and select the systems for the service group as follows:
Type a name for MSDTC service group.
In the Available Cluster Systems box, select the systems on which to configure the service group and click the right-arrow to move the systems to the Systems in Priority Order box. The systems listed in the Systems in Priority Order box represent the SystemList attribute of the service group. While selecting systems, make sure to select the systems that are not in the SystemList attribute for an Exchange service group configured in the cluster.
To remove a system from the service group's system list, select the Systems in Priority Order list and click the left arrow.
To change a system's priority in the service group's system list, select the system from the Systems in Priority Order and click the up and down arrows. The system at the top of the list has the highest priority while the system at the bottom of the list has the lowest priority.
To enable the service group to automatically come online on one of the systems, select the Include selected systems in the service group's AutoStartList attribute checkbox.
For information about the AutoStartList attribute, see the Cluster Server Administrator's Guide.
Click Next. If the cluster configuration is in read-only mode, the wizard prompts you before changing it to read-write mode. The wizard starts validating your configuration. Various messages indicate the validation status.
- On the Virtual Server Configuration panel, specify the information related to the virtual server as follows:
Type a 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. Ensure that the virtual server name is unique in the cluster.
Select IPv4 to configure an IPv4 address for the virtual server.
In the Virtual IP Address field, type a unique virtual IPv4 address for the MSDTC server.
In the Subnet Mask field, type the subnet to which the virtual IPv4 address belongs.
Select IPv6 to configure an IPv6 address for the virtual server. The IPv6 option is disabled if the network does not support IPv6.
Select the network from the drop-down list. The wizard uses the network prefix and automatically generates an IPv6 address that is valid and unique on the network.
For each system, select the public network adapter name. The Adapter Display Name field displays the TCP/IP enabled adapters on a system, including the private network adapters, if they are TCP/IP enabled. To view the adapters associated with a system, click the Adapter Display Name field and then click the arrow. Make sure that you select the adapters assigned to the public network, not the private.
Click Advanced Settings to configure the Lanman agent to perform Windows Active Directory (AD) update. These settings are applicable to the Lanman resource in the service group. On the Lanman Advanced Configuration dialog box, complete the following:
Check the Active Directory Update required check box to enable the Lanman agent to update the Active Directory with the virtual name. This sets the Lanman agent attributes ADUpdateRequired and ADCriticalForOnline to true.
In the Organizational Unit field, type the distinguished name of the Organizational Unit for the virtual server in the format CN=containername,DC=domainname,DC=com. To browse for an OU, click the ellipsis (...) button and search for the OU using the Windows Find Organization Units dialog box. By default, the Lanman resource adds the virtual server to the default container "Computers."
Click OK.
The user account for VCS Helper service must have adequate privileges on the specified container to create and update computer accounts.
Click Next.
- On the Specify Data Path panel, specify the drive letter for the MSDTC log and registry replication directory and click Next. If the directory does not exist, the wizard creates it. Veritas recommends using different paths for these directories.
Clear the Configure NetApp SnapMirror Resource(s) check box. This option is applicable only in case of a disaster recovery configuration. The SnapMirror resource is used to monitor replication between filers at the primary and the secondary site, in a disaster recovery configuration. If you are setting up a disaster recovery environment, check this check box to configure the SnapMirror resource at the primary site. The SnapMirror resource must be configured only after you have configured the cluster at the secondary site.
- On the Initiator Selection panel, select the initiator for the virtual disk from the list of available initiators displayed for each cluster node, and then click Next.
If you are configuring Multipath I/O (MPIO) over Fibre Channel (FC), you must select at least two FC initiators for each cluster node. Note that the node from which you run this wizard already has an initiator selected by default. This is the initiator that was specified when you connected the LUNs to this cluster node.
- On the Service Group Summary panel, review the service group configuration and change the resource names if desired and then click Next.
The Resources box lists the configured resources. Click on a resource to view its attributes and their configured values.
The wizard assigns unique names to resources. Change names of the resources, if desired.
To edit a resource name, select the resource name and either click it or press the F2 key. Press the Enter key after editing each resource name. To cancel editing a resource name, press the Esc key.
- Click Yes on the message that informs you that the wizard will run commands to create the service group.
Various messages indicate the status of these commands.
- In the Completing the MSDTC Configuration Wizard panel, check Bring the service group online check box if you wish to bring the configured service group online on the local system. To bring the service group online later, clear this check box.
- Click Finish to exit the wizard.
This completes the MSDTC Server service group configuration. You can now proceed to configure the MSDTC client manually.