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
Assigning privileges to the existing SQL Server databases and logs
Note:
The following steps are required only if you have configured the SQL Server cluster account while creating the SQL Server service group earlier.
While installing SQL Server, if the user account specified for the SQL Server services is not a member of the local administrators group, then the SQL Server services and databases may not be accessible after a service group failover. For such a case, you configure the SQL Server cluster account while creating the SQL Server service group.
The SQL Server cluster account gets full control privileges to all the new databases and log files that are created after the service group is configured.
However, if databases were created before the service group is configured, you have to manually assign the SQL Server cluster account with full control privileges to the existing databases and log files associated with the instances in the service group.
To assign privileges to the existing SQL Server databases and logs
- On the node where the SQL Server service group is online, navigate to the following directory from Windows explorer:
dataRootDirectory\SQLInstanceName\MSSQL\
The directory contains various directories including DATA, FTData, JOBS, Log, repldata. Here,
dataRootDirectory
is the path that you specified while installing SQL Server. - Assign the SQL Server cluster account with full control privileges to the following directories:
DATA
Log
- Navigate inside the DATA folder and then assign the SQL Server cluster account with full control privileges to the following files in that directory:
tempdb.mdf
templog.ldf
- Repeat these steps for all the instances that are configured in the SQL Server service group.
This ensures the existing SQL Server databases are accessible after a service group failover.