InfoScale™ 9.0 Storage Foundation and High Availability Solutions HA and DR Solutions Guide for Microsoft SQL Server - Windows
- Section I. Getting started with Storage Foundation and High Availability Solutions for SQL Server
- Introducing SFW HA and the VCS agents for SQL Server
- How is application availability achieved in a VMware virtual environment
- How VCS monitors storage components
- Deployment scenarios for SQL Server
- Reviewing the active-passive HA configuration
- Reviewing a standalone SQL Server configuration
- Reviewing the campus cluster configuration
- Reviewing the Replicated Data Cluster configuration
- About setting up a Replicated Data Cluster configuration
- Disaster recovery configuration
- Reviewing the disaster recovery configuration
- Notes and recommendations for cluster and application configuration
- Configuring disk groups and volumes for SQL Server
- About managing disk groups and volumes
- Configuring the cluster using the Cluster Configuration Wizard
- Installing SQL Server
- Completing configuration steps in SQL Server
- Introducing SFW HA and the VCS agents for SQL Server
- Section II. Configuring SQL Server in a physical environment
- Configuring SQL Server for failover
- About configuring the SQL Server service group
- Configuring the service group in a non-shared storage environment
- Configuring an MSDTC Server service group
- Configuring campus clusters for SQL Server
- Configuring Replicated Data Clusters for SQL Server
- Setting up the Replicated Data Sets (RDS)
- Configuring a RVG service group for replication
- Configuring the resources in the RVG service group for RDC replication
- Configuring the VMDg or VMNSDg resources for the disk groups
- Configuring the RVG Primary resources
- Adding the nodes from the secondary zone to the RDC
- Verifying the RDC configuration
- Configuring disaster recovery for SQL Server
- Setting up your replication environment
- About configuring disaster recovery with the DR wizard
- Configuring replication and global clustering
- Configuring the global cluster option for wide-area failover
- Testing fault readiness by running a fire drill
- About the Fire Drill Wizard
- Prerequisites for a fire drill
- Preparing the fire drill configuration
- Deleting the fire drill configuration
- Configuring SQL Server for failover
About installing SQL Server for high availability configuration
Before installation, note the following prerequisites:
Ensure that you have installed the product and configured SFW HA on all the systems on which you wish to configure SQL Server.
For information about installing the Arctera InfoScale™ products using the installation wizard or the CLI, see the Arctera InfoScale™ Installation and Upgrade Guide.
If you are using Windows LDM storage, ensure that the disks are accessible from all the systems where you plan to install SQL Server.
Arctera recommends that you create volumes for the following:
SQL Server data
Registry replication
User defined database
User defined database logs
FILESTREAM-enabled database objects
Installing SQL Server on the first system
In case of shared storage, you must install the SQL Server instance on the local disk and install the SQL Server database files and analysis service files on the shared disk. The shared disks must be accessible from all the systems where you wish to install and configure SQL Server.
In case of non-shared storage, you must install the database files on the disks residing on a datastore that is accessible from all the systems where you want to install and configure SQL Server. These disks are deported and imported during a failover.
Installing SQL Server on additional systems
Irrespective of how the storage is configured (whether shared or non-shared), install the SQL Server instances, database files and analysis service files on the local system disk.
If you are installing multiple instances of SQL Server on the same system, ensure the following:
Assign a unique name and a unique instance ID to each SQL Server instance. When installing SQL Server on additional systems for the same instance, ensure that you specify the same instance name and ID.
The order of the instance installation does not matter. You must ensure that the instances are installed with the same name and ID on all the systems.
Assign a unique port number for each instance.
Ensure that the [NT AUTHORITY\SYSTEM] account is granted the sysadmin server role (from SQL Management Studio Console) on each system.
The logged-on user must be a domain user with local Administrator privileges.
The logged-on user must be a member of the local Administrators group on all systems where you want to install SQL Server.
Ensure that the disk group is imported and the volumes are mounted to the first system for this SQL Server instance.
See About disk groups and volumes.