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
Creating a parallel environment in the secondary zone
After setting up a SFW HA environment in the primary zone, you set up a parallel environment in the secondary zone (zone 1).
Before you begin to configure the secondary zone, do the following:
Offline the following resources in the SQL Server service group in the primary zone:
SQL Server resource (sqlServiceGroupName - SQLServer)
SQL Virtual Server name resource (sqlServiceGroupName - Lanman)
SQL Virtual IP resource (sqlServiceGroupName - IP)
The remaining resources should be online, including the storage resources.
In VEA, make sure to remove all the drive letters from the configured volumes, to avoid conflicts when configuring the zones.
Then complete the following tasks to configure the secondary zone, using the guidelines shown:
Installing the Arctera InfoScale™ product.
For more information, see the Arctera InfoScale™ Installation and Upgrade Guide.
See Configuring disk groups and volumes for SQL Server.
During the creation of disk groups and volumes for the secondary zone, make sure the following is exactly the same as the cluster at the primary zone:
Disk group name
Volume sizes
Volume names
Drive letters
Installing and configuring SQL Server on the first cluster node
See About installing SQL Server on the first system.
When installing SQL Server make sure that you select the same installation options as you did for the primary zone. The instance name must be the same in the primary zone and secondary zone
See About installing SQL Server on additional systems.
After you install SQL Server on the nodes in the secondary zone, make sure to use VEA to remove all the drive letters from the configured volumes.
Adding a system to the existing cluster
You do not create another cluster in the secondary zone. Instead you add the systems to the existing cluster.
You do not create another SQL Server service group in the secondary zone. You continue with the remaining Volume Replicator configuration tasks, during which the secondary zone nodes will be added to the SQL Server service group.