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
Configuring the quorum device for high availability
The proper configuration of a quorum device is critical to providing the highest availability with InfoScale Storage.
Although a single basic disk used as a physical disk resource can serve as the Microsoft clustering quorum device, this introduces a nonredundant component into an otherwise highly available system.
In general, a disk group containing a dedicated, three-way mirrored volume makes an ideal quorum device. Such a device tolerates two disk failures, because it is mirrored, and server and interconnect failures, because SFW can import it when the disks and at least one server are running.
For a server to take ownership of a disk group containing the cluster quorum device, SFW must successfully import the disk group, and obtain SCSI reservations on more than half of its disks. Disk groups containing odd numbers of disks are best for use as quorum devices because of this behavior.
An SFW cluster disk group containing a volume used as a quorum device should contain that volume only. Any other volumes in that disk group fail over whenever the quorum device changes ownership.