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
Creating a SQL Server user-defined database
You can use SFW HA to manage SQL Server user-defined databases. For making the user-defined databases highly available, create the user-defined databases and then configure them in the SQL Server service group. Refer to the Microsoft SQL Server documentation for instructions on how to create databases.
Refer to the following guidelines before creating and configuring the user-defined databases:
If you have not already created volumes for a user-defined SQL Server database and its transaction log, create them first.
Create the SQL Server database for the desired SQL Server virtual server instance, and point the database files and transaction log to the new volumes created for them.
Refer to the Microsoft SQL Server documentation for instructions.
After creating the database, you may have additional steps to complete in the SQL Server configuration. Perform the desired steps depending on your configuration plans.
If you have already configured the SQL Server service group, run the SQL Server Configuration Wizard again to modify the SQL Server service group. This allows the wizard to add storage agent resources for the new database, to the existing service group.
See Modifying a SQL Server service group to add VMDg and MountV resources.
You must run the SQL Server Configuration Wizard in the modify mode only if you create user-defined databases after creating the SQL Server service group.
Note:
If you have configure the SQL Server service group in a non-shared storage configuration (dynamic disk groups configured on local disks), you have to modify the service group manually either using the Cluster Manager (Java Console) or the command line. The wizard currently cannot configure resources (VMNSDg agent) required for monitoring non-shared storage.