Storage Foundation and High Availability Solutions 8.0.2 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
- About the Veritas InfoScale solutions for monitoring SQL Server
- How application availability is achieved in a physical environment
- How is application availability achieved in a VMware virtual environment
- Managing storage using VMware virtual disks
- Notes and recommendations
- Modifying the ESXDetails attribute
- How VCS monitors storage components
- Shared storage - if you use NetApp filers
- Shared storage - if you use SFW to manage cluster dynamic disk groups
- Shared storage - if you use Windows LDM to manage shared disks
- Non-shared storage - if you use SFW to manage dynamic disk groups
- Non-shared storage - if you use Windows LDM to manage local disks
- Non-shared storage - if you use VMware storage
- What must be protected in an SQL Server environment
- About the VCS agents for SQL Server
- About the VCS agent for SQL Server Database Engine
- About the VCS agent for SQL Server FILESTREAM
- About the VCS GenericService agent for SQL Server Agent service and Analysis service
- About the agent for MSDTC service
- About the monitoring options
- Typical SQL Server configuration in a VCS cluster
- Typical SQL Server disaster recovery configuration
- SQL Server sample dependency graph
- MSDTC sample dependency graph
- Deployment scenarios for SQL Server
- Workflows in the Solutions Configuration Center
- Reviewing the active-passive HA configuration
- Reviewing the prerequisites for a standalone SQL Server
- Reviewing a standalone SQL Server configuration
- Reviewing the MSDTC configuration
- VCS campus cluster configuration
- Reviewing the campus cluster configuration
- VCS Replicated Data 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 the storage hardware and network
- Configuring disk groups and volumes for SQL Server
- About disk groups and volumes
- Prerequisites for configuring disk groups and volumes
- Considerations for a fast failover configuration
- Considerations for converting existing shared storage to cluster disk groups and volumes
- Considerations when creating disks and volumes for campus clusters
- Considerations for volumes for a Volume Replicator configuration
- Considerations for disk groups and volumes for multiple instances
- Sample disk group and volume configuration
- MSDTC sample disk group and volume configuration
- Viewing the available disk storage
- Creating a dynamic disk group
- Adding disks to campus cluster sites
- Creating volumes for high availability clusters
- Creating volumes for campus clusters
- About managing disk groups and volumes
- Configuring the cluster using the Cluster Configuration Wizard
- Installing SQL Server
- About installing and configuring SQL Server
- About installing multiple SQL Server instances
- Verifying that the SQL Server databases and logs are moved to shared storage
- About installing SQL Server for high availability configuration
- About installing SQL Server on the first system
- About installing SQL Server on additional systems
- Creating a SQL Server user-defined database
- 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
- Tasks for configuring a new server for high availability
- Tasks for configuring an existing server for high availability
- About configuring the SQL Server service group
- Configuring the service group in a non-shared storage environment
- Verifying the SQL Server cluster configuration
- About the modifications required for tagged VLAN or teamed network
- Tasks for configuring MSDTC for high availability
- Configuring an MSDTC Server service group
- About configuring the MSDTC client for SQL Server
- About the VCS Application Manager utility
- Viewing DTC transaction information
- Modifying a SQL Server service group to add VMDg and MountV resources
- Determining additional steps needed
- Configuring campus clusters for SQL Server
- Configuring Replicated Data Clusters for SQL Server
- Tasks for configuring Replicated Data Clusters
- Creating the primary system zone for the application service group
- Creating a parallel environment in the secondary zone
- Setting up security for Volume Replicator
- Setting up the Replicated Data Sets (RDS)
- Configuring a RVG service group for replication
- Creating the RVG service group
- Configuring the resources in the RVG service group for RDC replication
- Configuring the IP and NIC resources
- Configuring the VMDg or VMNSDg resources for the disk groups
- Modifying the DGGuid attribute for the new disk group resource in the RVG service group
- Configuring the VMDg or VMNSDg resources for the disk group for the user-defined database
- Adding the Volume Replicator RVG resources for the disk groups
- Linking the Volume Replicator RVG resources to establish dependencies
- Deleting the VMDg or VMNSDg resource from the SQL Server service group
- Configuring the RVG Primary resources
- Configuring the primary system zone for the RVG service group
- Setting a dependency between the service groups
- Adding the nodes from the secondary zone to the RDC
- Adding the nodes from the secondary zone to the RVG service group
- Configuring secondary zone nodes in the RVG service group
- Configuring the RVG service group NIC resource for fail over (VMNSDg only)
- Configuring the RVG service group IP resource for failover
- Configuring the RVG service group VMNSDg resources for fail over
- Adding nodes from the secondary zone to the SQL Server service group
- Configuring the zones in the SQL Server service group
- Configuring the application service group IP resource for fail over (VMNSDg only)
- Configuring the application service group NIC resource for fail over (VMNSDg only)
- Verifying the RDC configuration
- Additional instructions for GCO disaster recovery
- Configuring disaster recovery for SQL Server
- Tasks for configuring disaster recovery for SQL Server
- Tasks for setting up DR in a non-shared storage environment
- Guidelines for installing Veritas InfoScale Enterprise and configuring the cluster on the secondary site
- Verifying your primary site configuration
- Setting up your replication environment
- Assigning user privileges (secure clusters only)
- About configuring disaster recovery with the DR wizard
- Cloning the storage on the secondary site using the DR wizard (Volume Replicator replication option)
- Creating temporary storage on the secondary site using the DR wizard (array-based replication)
- Installing and configuring SQL Server on the secondary site
- Cloning the service group configuration from the primary site to the secondary site
- Configuring the SQL Server service group in a non-shared storage environment
- Configuring replication and global clustering
- Creating the replicated data sets (RDS) for Volume Replicator replication
- Creating the Volume Replicator RVG service group for replication
- Configuring the global cluster option for wide-area failover
- Verifying the disaster recovery configuration
- Adding multiple DR sites (optional)
- Recovery procedures for service group dependencies
- Configuring DR manually without the DR wizard
- Testing fault readiness by running a fire drill
- About disaster recovery fire drills
- About the Fire Drill Wizard
- About post-fire drill scripts
- Tasks for configuring and running fire drills
- Prerequisites for a fire drill
- Preparing the fire drill configuration
- System Selection panel details
- Service Group Selection panel details
- Secondary System Selection panel details
- Fire Drill Service Group Settings panel details
- Disk Selection panel details
- Hitachi TrueCopy Path Information panel details
- HTCSnap Resource Configuration panel details
- SRDFSnap Resource Configuration panel details
- Fire Drill Preparation panel details
- Running a fire drill
- Re-creating a fire drill configuration that has changed
- Restoring the fire drill system to a prepared state
- Deleting the fire drill configuration
- Considerations for switching over fire drill service groups
- Configuring SQL Server for failover
Campus cluster failover using the ForceImport attribute
Automated recovery is handled differently in a VCS campus cluster than with a VCS local cluster. The outcomes of failure situations depend on the settings for the ForceImport attribute of the VMDg resource. To ensure proper failover in a VCS campus cluster, you must verify the value of the ForceImport attribute.
You can set this attribute as follows:
ForceImport set to 1 automatically forces the import of the disk groups to the other node
ForceImport set to 0 does not force the import
The advantage of automatic failover in the event of site failure comes at the cost of potential data loss if all storage and network communication paths between the sites are severed. Choose an option that is suitable given your cluster infrastructure, uptime requirements, and administrative capabilities.
You can use the VCS Java Console or command line to modify the ForceImport attribute. For more information on modifying ForceImport:
See Setting the ForceImport attribute to 1 after a site failure.
The following table lists failure situations and the outcomes depending on the settings for the ForceImport attribute of the VMDg resource.
Table: Failure situations in a VCS campus cluster
Failure Situation | ForceImport set to 0 (import not forced) | ForceImport set to 1 (automatic forced import) |
|---|---|---|
1) Application fault May mean the services stopped for an application, a NIC failed, or a database table went offline. | Application automatically moves to another node. | Service Group failover is automatic on the standby or preferred system or node.Service Group failover is automatic on the standby or preferred system or node. |
2) Server failure May mean a power cord became unplugged or a failure caused the system to stop responding. | Application automatically moves to other node. 100% of the disks are still available. | Service Group failover is automatic on the standby or preferred system or node. 100% of the mirrored disks are still available. |
3) Failure of disk array or all disks Remaining disks in mirror are still accessible from the other site. | No interruption of service. Remaining disks in mirror are still accessible from the other node. | The Service Group does not failover. 50% of the mirrored disk is still available at remaining site. |
4) Zone failure Complete Site failure, all accessibility to the servers and storage is lost. | Manual intervention required to online the Service Group at remaining site. Can not automatically import 50% of mirrored disk. | Automatic failover of Service Group to online site. Force Import must be set to True before site failure to ensure VCS can import 50% of mirrored disk. |
5) Split-brain (loss of both heartbeats) If the public network link serves as a low-priority heartbeat, the assumption is made that the link is also lost. | No interruption of service. Can't import disks because the original node still has the SCSI reservation. | No interruption of service. Failover does not occur due to Service Group resources remaining online on the original nodes. Example: Online node has SCSI reservation to own disk. |
6) Storage interconnect lost Fibre interconnect severed. | No interruption of service. Disks on the same node are functioning. Mirroring is not working. | No interruption of service. Service Group resources remain online, but 50% of the mirror disk becomes detached. |
7) Split-brain and storage interconnect lost If a single pipe is used between buildings for the Ethernet and storage, this situation can occur. | No interruption of service. Cannot import with only 50% of disks available. Disks on the same node are functioning. Mirroring is not working. | Automatically imports 50% of mirrored disk to the alternate node. Disks online for a short period in both locations but offlined again due to IP and other resources being online on original node. No interruption of service. |