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
Converting a local service group to a global service group
After linking the clusters, use the Global Group Configuration wizard to convert a local service group that is common to the global clusters to a global group. This wizard also enables you to convert global groups into local groups.
To convert a local service group to a global group
- From Cluster Explorer, click Configure Global Groups on the Edit menu.
or
From the Cluster Explorer configuration tree, right-click the cluster, and click Configure Global Groups.
or
From the Cluster Explorer configuration tree, right-click the service group, click Configure As Global, and proceed to step 3b.
- Review the information required for the Global Group Configuration wizard and click Next.
Enter the details of the service group to modify as follows:
Click the name of the service group that will be converted from a local group to a global group, or vice versa.
From the Available Clusters box, click the clusters on which the group can come online. Click the right arrow to move the cluster name to the Clusters for Service Group box; for global to local cluster conversion, click the left arrow to move the cluster name back to the Available Clusters box. A priority number (starting with 0) indicates the cluster on which the group will attempt to come online. If necessary, double-click the entry in the Priority column and enter the new value.
Select the policy for cluster failover as follows:
Manual
Prevents a group from automatically failing over to another cluster.
Auto
Enables a group to automatically fail over to another cluster if it is unable to fail over within the cluster, or if the entire cluster fails.
Connected
Enables a group to automatically fail over to another cluster if it is unable to fail over within the cluster.
Click Next.
- Enter or review the connection details for each cluster. Click the Configure icon to review the remote cluster information for each cluster:
Cluster not in secure mode
Enter the IP address of the remote cluster, the IP address of a cluster system, or the host name of a cluster system.
Verify the port number.
Enter the user name.
Enter the password.
Click OK.
Repeat these steps for each cluster in the global environment.
Cluster in secure mode
Enter the IP address of the remote cluster, the IP address of a cluster system, or the host name of a cluster system.
Verify the port number.
Choose to connect to the remote cluster with the credentials used for the current cluster connection, or enter new credentials, including the user name, password, and domain.
If you connected to the remote cluster earlier through the wizard, you can use the credentials from the previous connection.
Click OK.
Repeat these steps for each cluster in the global environment.
- Click Next, then click Finish.
At this point, you must bring the global service group online from Cluster Explorer.