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
Configuring a disaster recovery set up for SQL Server
This section provides information on how to install and configure the high availability and SQL Server components on the primary and secondary sites, with the intent of creating a parallel setup for the SQL service group on both sites. The configuration process is the same for both sites.
Note:
You must perform the tasks at the primary site first. After the configuration is complete at the primary site, proceed to perform the tasks at the secondary site.
Before you begin to create the SQL Server service group for the cluster at the secondary site, make sure that the SQL Server service group at the primary site is offline.
The following table lists the tasks to set up a disaster recovery environment for SQL Server.
Table: Tasks for SQL Server disaster recovery set up
Task | Description |
---|---|
Review the configuration | Review the system configuration before you start deploying VCS and SQL Server in your environment. |
Install the product and configure the VCS cluster | Install Veritas InfoScale Availability on all the systems where you want to configure an application for availability and configure a VCS cluster: For details refer to theVeritas InfoScale Installation and Upgrade Guide. See About installing the VCS agents. See Configuring the cluster using the Cluster Configuration Wizard. |
Configure volumes or LUNs on the shared storage | Create volumes or LUNs required for SQL Server and ensure that the volumes or LUNs (virtual disks) are connected to the first cluster node. During the creation of virtual disks and volumes for the secondary site, make sure the following is exactly the same as the cluster on the primary site:
|
Install and configure SQL Server on the first node | |
Install and configure SQL Server on the additional nodes | See About installing SQL Server on additional systems. Note: The instance name must be the same on the primary site and secondary site. |
Configure the SQL Server service group | See About configuring the SQL Server service group. Note: The service group name and virtual computer name must be same on both, the primary site and secondary site. |
Configure DR components | After configuring the high availability and SQL Server components on the primary and secondary sites, complete the disaster recovery solution by configuring the disaster recovery components for both sites. See Prerequisites . See Linking clusters: Adding a remote cluster to a local cluster . See Converting a local service group to a global service group . See Bringing a global service group online . |