Storage Foundation and High Availability 8.0.2 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
InfoScale requirements for Microsoft clustering solutions
Refer to Microsoft documentation for Microsoft cluster requirements.
Use the following requirements as a guideline for InfoScale Storage with Microsoft SQL Server in a Microsoft cluster:
One CD-ROM drive accessible to the system on which you are installing InfoScale Storage.
Each system requires 1 GB of RAM for SFW.
The storage disks must be shared between the cluster nodes.
Note:
In a Microsoft Azure environment you cannot configure shared storage. Microsoft Azure does not support provisioning of shared disks. Due to this Microsoft limitation, in an Azure environment, InfoScale Storage cannot be used in cluster configurations that require shared storage.
SCSI or Fibre Channel host bus adapters (HBAs) can be used to access shared storage.
Microsoft clustering requires at least two network adapters per system (one NIC to connect each system to the public network, and one NIC for the private network on each system). Veritas recommends using three network adapters (two NICs exclusively for the private network and one for the public network). Route each private NIC through a separate hub or switch to avoid single points of failure.
Using static IP addresses for the public network and private network cards is highly recommended and is required for a Volume Replicator configuration. You also need a static IP address for the cluster itself. Verify that name resolution is configured for each node.
Verify that the DNS and Active Directory Services are available. Make sure a reverse lookup zone exists in the DNS. Refer to the Microsoft documentation for instructions on creating a reverse lookup zone.
Microsoft clustering requires at least two disks for SQL, one for SQL database files and one for SQL log files.
For a campus cluster configuration, the following applies:
The configuration requires two sites with a storage array for each site, with an equal number of disks at each site for the mirrored volumes.
Interconnects between the clusters are required for the storage and the network.
Each system in a Microsoft cluster must be in the same Windows Server domain and must be using the same operating system version.
InfoScale Storage requires administrator privileges to install the software.
Installing InfoScale Storage requires a reboot, but a reboot on the active cluster node causes it to fail over. Therefore, use a "rolling install" procedure to install InfoScale Storage first on the inactive cluster node. Then move the cluster resources to the other node and install on the now inactive node.
Refer to the Microsoft documentation for details on establishing a failover cluster. In addition, you should be aware of the following SFW related requirement: Setting up a Microsoft failover cluster creates physical disk resources for all the basic disks on the shared bus. In the SFW environment, this means that before you create your SFW cluster disk groups, you must first remove these physical disk resources from the cluster. Otherwise, a reservation conflict occurs. After creating the SFW cluster disk groups, corresponding Volume Manager Disk Group (VMDg) resources are added to the cluster, under the available storage. The VMDg resource name corresponds to the cluster disk group name. You can then assign any of these resources to an application service group.
Note:
You can install the Microsoft Failover Cluster option on a machine that is not a member of a Microsoft cluster. However, if that machine becomes the first node in a Microsoft cluster, the Volume Manager Disk Group resource type must be manually registered. For more information, see the Veritas InfoScale Installation and Upgrade Guide.