Cluster Server 8.0 Implementation Guide for Microsoft SQL Server - Windows
- Section I. Introducing Veritas InfoScale solutions for application high availability
- Understanding the InfoScale solutions for application high availability
- About the VCS agents for SQL Server
- How VCS monitors storage components
- How application availability is achieved in a physical environment
- How is application availability achieved in a VMware virtual environment
- Managing storage and installing the VCS agents
- Installing SQL Server
- Understanding the InfoScale solutions for application high availability
- Section II. Configuring SQL Server in a physical environment
- Overview
- Configuring the VCS cluster
- Configuring the SQL Server service group
- Configuring a SQL Server service group using the wizard
- Making SQL Server user-defined databases highly available
- Verifying the service group configuration
- Administering a SQL Server service group
- Configuring an MSDTC service group
- Configuring the standalone SQL Server
- Configuring an Active/Active cluster
- Configuring a disaster recovery setup
- Section III. Configuring SQL Server in a VMware environment
- Configuring application monitoring using the Veritas High Availability solution
- Administering application monitoring
- Administering application monitoring using the Veritas High Availability tab
- Administering application availability using Veritas High Availability dashboard
- Understanding the dashboard work area
- Section IV. Appendixes
- Appendix A. Troubleshooting
- Error and warning messages from VCS agent for SQL Server
- Troubleshooting application monitoring configuration issues
- Troubleshooting Veritas High Availability view issues
- Appendix B. Using the virtual MMC viewer
- Appendix A. Troubleshooting
About the VCS agents for SQL Server
This agent provides high availability for Microsoft SQL Server by monitoring the SQL Server instance and its services in a VCS cluster.
The agent detects an application failure if a configured virtual server becomes unavailable. When this occurs, the SQL Server service group is failed over to the next available system in the service group's system list. The configured SQL Server services and virtual server are started on the new system. The agent monitors specific resources within an enterprise application, determines the status of these resources, brings them online, and takes them offline. The agent also provides active-active support for SQL Server. In an active-active configuration, several SQL Server instances are intended to run on a single node when necessary.
The VCS agent package for SQL Server includes the following:
Agent for SQL Server Database Engine | This agent provides high availability for SQL Server Database Engine. If the SQL Server Database Engine service is not running, the agent returns a failure status and declares the service as offline. |
Agent for SQL Server FILESTREAM | The agent provides high availability for the SQL Server FILESTREAM feature. The agent monitors the Windows FILESTREAM configuration settings for the SQL Server instance. |
GenericService agent for SQL Server Agent service and Analysis service | VCS employs the GenericService agent to provide high availability for the SQL Server Agent service and the Analysis service. The VCS GenericService agent monitors the SQL Server Agent service and Analysis service. If the services are not running, the agent declares the services as offline. |
Agent for SQL Server Microsoft Distributed Transaction Coordinator (MSDTC) | The agent provides high availability for MSDTC, which is a service used for distributed transactions. If the MSDTC service is not running, the agent returns a failure status and declares the service as offline. |