InfoScale™ 9.0 Storage Foundation and High Availability Solutions HA and DR Solutions Guide for Microsoft SQL Server - Windows
- Section I. Getting started with Storage Foundation and High Availability Solutions for SQL Server
- Introducing SFW HA and the VCS agents for SQL Server
- How is application availability achieved in a VMware virtual environment
- How VCS monitors storage components
- Deployment scenarios for SQL Server
- Reviewing the active-passive HA configuration
- Reviewing a standalone SQL Server configuration
- Reviewing the campus cluster configuration
- Reviewing the Replicated Data Cluster configuration
- About setting up a Replicated Data Cluster configuration
- Disaster recovery configuration
- Reviewing the disaster recovery configuration
- Notes and recommendations for cluster and application configuration
- Configuring disk groups and volumes for SQL Server
- About managing disk groups and volumes
- Configuring the cluster using the Cluster Configuration Wizard
- Installing SQL Server
- Completing configuration steps in SQL Server
- Introducing SFW HA and the VCS agents for SQL Server
- Section II. Configuring SQL Server in a physical environment
- Configuring SQL Server for failover
- About configuring the SQL Server service group
- Configuring the service group in a non-shared storage environment
- Configuring an MSDTC Server service group
- Configuring campus clusters for SQL Server
- Configuring Replicated Data Clusters for SQL Server
- Setting up the Replicated Data Sets (RDS)
- Configuring a RVG service group for replication
- Configuring the resources in the RVG service group for RDC replication
- Configuring the VMDg or VMNSDg resources for the disk groups
- Configuring the RVG Primary resources
- Adding the nodes from the secondary zone to the RDC
- Verifying the RDC configuration
- Configuring disaster recovery for SQL Server
- Setting up your replication environment
- About configuring disaster recovery with the DR wizard
- Configuring replication and global clustering
- Configuring the global cluster option for wide-area failover
- Testing fault readiness by running a fire drill
- About the Fire Drill Wizard
- Prerequisites for a fire drill
- Preparing the fire drill configuration
- Deleting the fire drill configuration
- Configuring SQL Server for failover
Prerequisites for configuring the SQL Server service group
Note the following prerequisites before configuring the SQL Server service group for a high availability cluster, campus cluster, or a Replicated Data Cluster:
Verify that you have completed the steps in the high availability, campus cluster, or RDC workflows up through the step of installing SQL Server on all nodes.
See the following topics as appropriate:
See Tasks for configuring a new server for high availability.
See Tasks for configuring an existing server for high availability.
Verify that you have VCS Cluster Administrator privileges. This user classification is required to configure service groups.
You must be a local Administrator on the node where you run the wizard. If you wish to configure detail monitoring, you must have the permission to log on to the respective SQL Server instance.
Verify that the SQL Server instance is installed identically on all nodes that will participate in the service group.
For configuring a SQL Server service group, you must run the SQL Server Configuration Wizard from the first cluster node where you installed the SQL Server data directories on shared storage.
This is required as the wizard configures the resources for the SQL Server database and registry information installed on the shared storage and propagates this information to the remaining nodes that are part of the SQL Server service group.
Do not run the wizard from the additional nodes.
Note:
If you are using a non-shared storage configuration (dynamic disk groups configured on local disks), you have to configure the service group manually either using the Cluster Manager (Java Console) or the command line. The wizard currently cannot configure resources (VMNSDg agent) required for monitoring non-shared storage.
Verify that the drive containing the SQL Server system data files, registry replication information, and FILESTREAM enabled data objects is mounted on the node on which you are configuring the service group. For creating a service group, this must be the first cluster node where you installed SQL Server.
If you wish to configure high availability for FILESTREAM, ensure that FILESTREAM is configured for the SQL Server instance, and is enabled for the SQL Server instance on the node on which you run the wizard and disabled on all the remaining nodes. You can use the SQL Server Configuration Manager to enable FILESTREAM.
Refer to the Microsoft SQL Server documentation for instructions.
Assign a unique virtual IP address for the SQL Server instance. You specify this IP address when configuring the service group.
If you wish to use a script for detail monitoring, for example, to create a table and write data to it, note the location(s) of the script to use. Locate the script file.
In case of shared storage, ensure that the same file exists in the same location on all the cluster nodes.
See About the monitoring options.
A sample script is supplied in the following directory:
C:\Program Files\Veritas\Cluster Server\bin\SQLServer\sample_script.sql
Make sure that the following services are stopped on the first cluster node where you are running the wizard:
SQL Server
SQL Server Agent
SQL Server Analysis Services
Stop these services for the SQL Server instances that you wish to configure in the service group.
If you have configured a Firewall, ensure that your firewall settings allow access to ports used by the product.
For a detailed list of services and ports, refer to the Arctera InfoScale™ Installation and Upgrade Guide.