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
Sample configuration
A sample setup is used to illustrate the installation and configuration tasks for two instances of SQL server, Billing and Payroll. During normal operation, one instance will be online on each of the two servers. If a failure occurs, the instance on the failing node will be brought online on the other server, resulting in two instances running on one server.
During the configuration process, create virtual IP addresses for the following:
Billing virtual server (virtual IP address is the same on all nodes)
Payroll virtual server (virtual IP address is the same on all node)
Cluster IP address
You should have these IP addresses available before you begin to deploy your environment.
The IP addresses are required only in case of IPv4. In an IPv6 network environment, the configuration wizards automatically generate a unique and valid IPv6 address based on the network prefix advertised by the routers.
The following table describes the objects created and used during the installation and configuration.
Table: Active-active configuration objects
Name | Description |
---|---|
SYSTEM1 & SYSTEM2 | server names |
SQL_CLUS1 | virtual SQL server cluster |
BILLING_VS_SYS_FILES PAYROLL_VS_SYS_FILES | volume for the SQL Server system data files for the billing instance volume for the SQL Server system data files for the payroll instance |
BILLING_DATA PAYROLL_DATA | volume for a SQL Server user-defined database for the billing instance volume for a SQL Server user-defined database for the payroll instance |
BILLING_LOG PAYROLL_LOG | volume for a SQL Server user-defined database log file fort he billing instance volume for a SQL Server user-defined database log file for the payroll instance |
BILLING_REGREP PAYROLL_REGREP | volume for the list of registry keys replicated among the nodes for the billing instance volume for the list of registry keys replicated among the nodes for the payroll instance |
BILLING_INST PAYROLL_INST | instance name for the billing instance instance name for the payroll instance |
BILLING_VS PAYROLL_VS | virtual SQL server name for the billing instance virtual SQL server name for the payroll instance |
BILLING_SG PAYROLL_SG | SQL Server service group for the billing instance SQL Server service group for the payroll instance |