Storage Foundation and High Availability 8.0.1 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
Prerequisites for installing SQL Server
Before you begin installing SQL Server, note the following prerequisites for installing in the SFW environment:
Make sure that you have created the SFW disk groups and volumes for SQL Server.
Make sure that you have created the SQL Server resource group and added the resource for the SQL Server disk group.
Make sure that the SFW cluster disk group for SQL Server is imported to the first node and the volumes are mounted.
Make sure that each node has a local drive letter in common with all the other nodes in the cluster to enable installation of the binaries in exactly the same path on each cluster node.
If you are installing on a secondary site for a disaster recovery configuration, make sure that you take the SQL Network Name resource offline on the primary site before you begin installation on the secondary site. This will also offline the dependent resources. If the sites are on the same subnet and therefore use the same SQL IP address, ensure that the IP Address resource is offline on the primary site before beginning installation on the secondary site.
Ensure that the [NT AUTHORITY\SYSTEM] account is granted the sysadmin server role (from SQL Management Studio Console) on each node.