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 the monitoring options
Use the detail monitoring capability of the VCS agent forSQL Server to monitor the status of a SQL Server instance.
The agent provides the following levels of application monitoring:
Basic monitoring queries the Windows Service Control Manager (SCM) to verify whether the configured SQL Server services are continuously active.
Detail monitoring queries the databases to verify their availability.
Table: Methods of configuring detail monitoring
Method | Description |
---|---|
Database list-based monitoring | The agent monitors only the list of databases that are specified in the its DBList attribute. It uses Microsoft ActiveX Data Objects (ADO) to establish a connection with the selected databases to verify the health of those databases.
|
Script-based detail monitoring | The agent uses a script to monitor the status of the SQL Server instance.
A sample SQL script is provided with the agent for this purpose. Customize the script to meet your configuration requirements, or use your own script, which can be placed at any other location. The script is located at: where, Use a separate script for each SQL Server service group in the cluster and place it on every node in the service group. |
You can enable and configure detail monitoring by running the SQL Server Agent Configuration Wizard.
Note:
If you provide input for both types of detail monitoring, database list-based monitoring takes precedence and script-based monitoring is not performed.
Note:
The VCS agent monitors the computer context of the services that are configured for high availability. If the SQL Server service is not started in the virtual server context - that is, outside VCS - the resource goes into the UNKNOWN state. To avoid this situation, ensure that you start all the SQL Server-related services from within VCS.