InfoScale™ 9.0 Storage Foundation and High Availability Solutions Microsoft Clustering Solutions Guide for Microsoft SQL Server - Windows
- Introducing SFW solutions for a Microsoft cluster
- Planning for deploying SQL Server with SFW in a Microsoft cluster
- Workflows for deploying SQL Server with SFW in a Microsoft cluster
- Configuring SFW storage
- Tasks for configuring InfoScale Storage
- Planning for SFW cluster disk groups and volumes
- Considerations when creating disk groups and volumes for a campus cluster
- Considerations when creating volumes for a DR configuration using Volume Replicator replication
- Viewing the available disk storage
- Creating dynamic cluster disk groups
- Adding disks to campus cluster sites
- Creating dynamic volumes for high availability clusters
- Creating dynamic volumes for campus clusters
- Implementing a dynamic mirrored quorum resource
- Installing SQL Server and configuring resources
- Configuring disaster recovery
- Tasks for configuring the secondary site for disaster recovery for SQL Server
- Verifying the primary site configuration
- Creating a parallel environment for SQL Server on the secondary site
- Volume Replicator components overview
- Setting up security for Volume Replicator
- Creating resources for Volume Replicator
- Configuring Volume Replicator: Setting up an RDS
- Creating the RVG resource
- Setting the SQL server resource dependency on the RVG resource
- Normal Volume Replicator operations and recovery procedures
- Appendix A. Configure InfoScale Storage in an existing Microsoft Failover Cluster
Planning your SQL Server high availability configuration
You can configure InfoScale Storage and SQL Server in a Microsoft cluster for high availability on a single site.
In the example high availability configuration, you create a virtual server in an active/passive SQL Server configuration on a Microsoft cluster. The active node of the cluster hosts the virtual server. The second node is a dedicated redundant server able to take over and host the virtual server in the event of a failure on the active node. In a high availability configuration both nodes are located on the same site.
The following figure illustrates a typical two-node active/passive configuration.
The following are some key points about the configuration:
The SQL virtual server is configured on the active node (SYSTEM1). If SYSTEM1 fails, SYSTEM2 becomes the active node and the SQL virtual server comes online on SYSTEM2.
One or more application virtual servers can exist in a cluster, but each server must be managed by a separate application group configured with a distinct set of nodes in the cluster.
The SQL databases are configured on the shared storage on volumes contained in one or more cluster disk groups.
InfoScale Storage enables you to create a dynamic mirrored quorum. If the quorum resource fails, the mirror takes over for the resource.
In this configuration, Arctera recommends creating a three-way mirror for the quorum to provide additional fault tolerance. If possible, do not use the disks assigned to the quorum for any other purpose.
InfoScale Storage enables you to add fault-tolerance to data volumes. Arctera recommends mirroring log volumes and a mirrored striped RAID layout for data volumes.
During the configuration process you will create virtual IP addresses for the following:
Cluster IP address, used by Microsoft cluster
SQL virtual server IP address, which should be the same on all nodes
You should have these IP addresses available before you start deploying your environment.