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
- Planning for SFW cluster disk groups and volumes
- Implementing a dynamic mirrored quorum resource
- Installing SQL Server and configuring resources
- Configuring disaster recovery
- Configuring Volume Replicator: Setting up an RDS
- Normal Volume Replicator operations and recovery procedures
- Appendix A. Configure InfoScale Storage in an existing Microsoft Failover Cluster
Sample SQL Server high-availability cluster storage configuration
The number of disk groups for SQL Server depends on the planned organization of the data. The application program files need to be installed on the local drive of the server. Data files and other related files, such as logs, or FILESTREAM filegroups (if implemented), are placed on the shared storage in a cluster disk group.
Arctera recommends that you place database files, log files, and FILESTREAM filegroups on separate volumes.
You create at least one disk group for the system data files. You may want to create additional disk groups for user databases.
The following figure shows an example configuration of the disk groups and volumes for SQL Server in a Microsoft cluster environment.
SQL disk group INST1_DG contains the following volumes:
INST1_DB1_VOL contains the SQL database. Each database typically resides on a separate volume.
INST1_DB1_LOG contains the transaction log.
INST1_SYS_FILES contains the volume for Microsoft SQL Server system data files.
This configuration is a simple example. The recommended practice for disk groups and volume layout is dependent on your environment.
Note:
If FILESTREAM is implemented, the configuration should also contain a separate volume for the FILESTREAM filegroup.