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
Configuring the service group in a non-shared storage environment
If you are using a non-shared storage configuration, you have to use the VCS MountV - VMNSDg agents to monitor your local storage. Currently, the service group configuration wizards do not support configuring these agents in the service group. You have to configure these agents manually by using the Cluster Manager (Java Console) or the VCS commands.
VCS provides templates for configuring service groups that use non-shared storage agent resources.
The Java Console templates are located in the following directory:
%VCS_HOME%\Templates
Here, %VCS_HOME% is the default product installation directory, typically, C:\Program Files\Veritas\Cluster Server
.
For information about adding a service group using templates from the Java Console, refer to the Cluster Server Administrator's Guide.
The following steps describe how to create a service group using the Cluster Manager (Java Console).
To configure the service group in a non-shared storage environment
- Open the Veritas Cluster Manager - Java Console from the Apps menu on the Start screen.
- Log on to the cluster. On the Cluster Monitor window click File > New Cluster, then on the New Cluster window type localhost in the Host name field, and then click OK.
- Launch the service group configuration wizard. From the Cluster Explorer window menu, click Tools > Configuration Wizard.
- On the Service Group Configuration Wizard Welcome panel, click Next.
- Fill in the following information and then click Next:
Specify a name for the service group.
Select the systems for the service group. Click a system in the Available Systems box and then click the right arrow to move the systems to Systems for Service Group.
Leave the service group type as the default, Failover.
- Click Next again.
- In the Templates list, select the desired service group template depending on the configuration and then click Next.
Template name
Description
SQLServer-VMNSGroup
(SQL Server Agent service)
SQLServer-OlapVMNSGroup
(SQL Server Agent service, and SQL Server Analysis service)
SQLServer-VMNSFilestreamGroup
(SQL Server Agent service, and SQL Server FILESTREAM)
MSDTCVMNSGroup
(SQL Server MSDTC service)
Use these templates to create a single-node high availability service group that uses non-shared storage.
These templates include resources for configuring MountV and VMNSDg agents.
SQLServer-VirtVMNSGroup
(SQL Server Agent service)
SQLServer-OlapVirtVMNSGroup
(SQL Server Agent service, and SQL Server Analysis service)
SQLServer-VirtVMNSFilestreamGroup
(SQL Server Agent service, and SQL Server FILESTREAM)
MSDTCVirtVMNSGroup
(SQL Server MSDTC service)
Use these templates to create a single-node high availability service group in a VMware virtual environment.
These templates include resources for configuring MountV, VMwareDisks, and VMNSDg agents.
VvrRvgVMNSRVGGroup
Use this template to create a VVR replication service group on a single node that uses non-shared storage.
The Templates box lists the templates available on the system to which Cluster Manager is connected. The resource dependency graph of the templates, the number of resources, and the resource types are also displayed.
- Click Next. The wizard starts creating the service group.
- After the service group is successfully created, click Next to edit attributes using the wizard.
- The wizard lists the resources and their attributes. You must specify values for the mandatory attributes that appear in bold. The remaining resources listed in the window are preconfigured by the template and do not require editing.
To modify an attribute, do the following:
Click the resource.
Click the attribute to be modified.
Click the Edit icon at the end of the table row.
In the Edit Attribute dialog box, enter the attribute values.
Click OK.
For details on application-specific agent attributes, refer to the application-specific agent or solutions guide.
For details on the storage and network agent attributes, refer to the Cluster Server Bundled Agents Reference Guide.
- Click Finish.
- Right-click the newly created service group and select Enable Resources.
- Right-click the newly created service group, select Online from the context menu, and then select a system on which to bring the service group online.
If you are configuring the service group on a node at the secondary site in a DR environment, bring the service group online only after completing all the DR configuration steps.