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 for SFW cluster disk groups and volumes
A dynamic cluster disk group is a collection of one or more disks that behave as a single storage repository and which can potentially be accessed by different computers. Within each disk group, you can have dynamic volumes with different layouts.
Note:
You create a cluster disk group and volumes on only one node of a cluster. The volumes can be accessed by other nodes in a high-availability cluster by first deporting the cluster disk group from the current node and then importing it on the desired node. In a campus cluster, the volumes are mirrored across the storage arrays.
Before creating a disk group, consider the following:
The type of volume configurations that are required.
The number of LUNs required for the disk group.
The implications of backup and restore operations on the disk group setup.
The size of databases and logs which depend on the traffic load.
The number of disk groups and volumes that are needed for the SQL Server instance. Typically an SFW disk group corresponds to an the SQL Server instance, with a separate volume for each database and for the transaction log.
For campus clusters, consider the following:
The disk groups and number of disks on each site
For campus clusters, each disk group must contain an equal number of disks on each site.
Each volume should be a mirrored volume with one plex of the volume on Site A's storage array and the other plex of the volume on Site B's storage array.
In a Microsoft cluster, plan to include a disk group for the mirrored quorum resource. If possible, use small disks. Microsoft recommends 500 MB for the quorum disk. The number of disks recommended are as follows:
In a high-availability configuration, Arctera recommends using at least 3 disks for the mirrored quorum resource.
In a campus cluster configuration, because each site must contain an equal number of disks, Arctera recommends a 4-way mirrored quorum, 2 mirrors on each site.
The following topics provide additional guidelines for specific configurations: