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
- 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
- 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 Arctera 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
Configuring Volume Replicator replication and global clustering
After you complete the service group configuration task in the DR wizard, you configure Volume Replicator replication and global clustering.
Note:
The DR configuration wizard clubs the data and log volumes of one database in one RVG. It clubs the system database volumes and the RegRep volume in one RVG, and uses a separate RVG for each user-created database. For information about setting up Volume Replicator replication with VEA, see the Volume Replicator Administrator's Guide
Before you begin, ensure that you have met the following prerequisites:
Ensure that Volume Replicator Security Service (VxSAS) is configured at the primary and secondary site.
Verify whether the IP version preference is set before you configure replication.
If you specify host names when you configure replication, Volume Replicator resolves the host names with the IP addresses associated with them. This setting determines which IP version Volume Replicator uses to resolve the host names.
Use one of the following methods to set the IP preference:
Veritas Enterprise Administrator (VEA) GUI - select the appropriate options on the Control Panel > VVR Configuration > IP Settings tab.
Run the vxtune ip_mode [ipv4 | ipv6] command at the primary site as well as the secondary site.
Ensure that a minimum of one static IP address per site is available for each application instance running in the cluster.
Ensure that, for remote cluster configuration, you configure a VCS user with the same name and privileges in each cluster.
Use the following procedure to configure Volume Replicator replication and global clustering with the DR wizard.
To configure Volume Replicator replication and GCO
- Verify that the application server service group is online at the primary site and the appropriate disk groups are imported at the secondary site.
- If the DR wizard is still open after the previous wizard task, continue with the Replication Setup panel.
Otherwise, launch the wizard and proceed to the Replication Setup panel as follows:
Start the Solutions Configuration Center from the Apps menu on the Start screen.
Expand the Solutions for Microsoft SQL Server tab and click Disaster Recovery Configuration > Configure Disaster Recovery > Disaster Recovery Configuration Wizard.
- On the Welcome panel, click Next and continue through the wizard, providing the requested information.
- On the Replication Methods panel, click Configure Volume Replicator and the Global Cluster Option (GCO). Click Next.
- In the Internet Protocol panel, select IPv4 or IPv6 depending on which type of network you are using. (You must use the same on primary and secondary sites.) Click Next.
- In the Replication Setup panel, review the replication requirements. If you have met the requirements, click Next. If not, click Cancel and restart the wizard after meeting the requirements.
- In the Replication Settings for Replicated Volume Group panel, specify the requested information. If you are adding a DR site to an existing DR configuration, fields that must match the existing settings, such as the RVG or RDS name, are dimmed so that you cannot change them.
Disk Group
The left column lists the disk groups. By design, an RVG is created for each disk group.
RVG Name
Displays the default RVG name. If required, change this to a name of your choice.
RDS Name
Displays the default Replicated Data Set (RDS) name. If required, change this to a name of your choice.
Available Volumes
Displays the list of available volumes that have not been selected to be a part of the RVG.
Either double-click on the volume name or use the > button to move the volumes into the Selected RVG Volumes pane.
Selected RVG Volumes
Displays the list of volumes that have been selected to be a part of the RVG.
To remove a selected volume, either double-click the volume name or use the < button to move the volumes into the Available Volumes pane.
Arctera recommends excluding tempdb from replication. If you earlier moved tempdb to a separate volume in the same disk group as the system database volumes, you can exclude tempdb from replication by removing the tempdb volume from the Selected RVG Volumes pane.
Primary SRL
If you did not create a Replicator Log volume on the primary site, click Create New on the drop-down menu. On the New Volume dialog box, specify the name, size, and disk.
Otherwise, select the appropriate primary Replicator Log volume from the drop-down menu and enter an appropriate size.
Secondary SRL
If you did not create a Replicator Log volume on the primary site, click Create New on the drop-down menu. On the New Volume dialog box, specify the same name and size as you specified for the primary SRL.
Otherwise, select the appropriate secondary Replicator Log volume from the drop-down menu and enter an appropriate size.
Start Replication after the wizard completes
Select this check box to start replication automatically after the wizard completes the necessary configurations.
Once replication is configured and running, deselecting the checkbox does not stop replication.
Click Advanced Settings to specify some additional replication properties.
The options on the dialog box are described column-wise, from left to right:
Replication Mode
Select the required mode of replication; Synchronous, Asynchronous, or Synchronous Override (default).
Log Protection
Select the appropriate log protection from the list:
AutoDCM is the default selected mode for the Replicator Log overflow protection when all the volumes in the Primary RVG have a DCM log. The DCM is enabled when the Replicator Log overflows.
The Off option disables Replicator Log Overflow protection.
The Override option enables log protection. If the Secondary node is still connected and the Replicator Log is about to overflow then the writes are stalled until a predetermined amount of space, that is, 5% or 20 MB (whichever is lesser) becomes available in the Replicator Log.
If the Secondary becomes inactive due to disconnection or administrative action then Replicator log protection is disabled, and the Replicator Log overflows.
The Fail option enables log protection. If the log is about to overflow the writes are stalled until a predetermined amount of space, that is, 5% or 20 MB (whichever is lesser) becomes available in the Replicator Log. If the connection between primary and secondary RVG is broken, then, any new writes to the primary RVG are failed.
Primary RLINK Name
Enter a name of your choice for the primary RLINK. If you do not specify any name then the wizard assigns a default name.
Secondary RLINK Name
Enter a name of your choice for the Secondary RLINK. If you do not specify any name then the wizard assigns a default name.
Bandwidth
By default, Volume Replicator replication uses the maximum available bandwidth. You can select Specify to specify a bandwidth limit.
The default unit is Megabits per second (Mbps) and the minimum allowed value is 1 Mbps.
Protocol
Choose TCP or UDP. UDP/IP is the default replication protocol.
Packet Size (Bytes)
Default is 1400 Bytes. From the drop-down list, choose the required packet size for data transfer. The default unit for the packet size is Bytes. You can set the packet size only if the protocol is UDP/IP.
Latency Protection
By default, latency protection is set to Off.
When this option is selected the High Mark Value and the Low Mark Value are disabled. Select the Fail or Override option to enable Latency protection.
This Override option behaves like the Off option when the Secondary is disconnected and behaves like the Fail option when the Secondary is connected.
High Mark Value
This option is enabled only when Latency Protection is set to Override or Fail. It specifies the maximum number of pending updates by which the secondary site can be behind the primary site. The default value is 10000.
To ensure that latency protection is most effective the difference between the high and low mark values must not be very large.
Low Mark Value
This option is enabled only when Latency Protection is set to Override or Fail. When the updates in the Replicator log reach the High Mark Value, then the writes to the system at the primary site continues to be stalled until the number of pending updates on the Replicator log falls back to the Low Mark Value. The default is 9950.
Initial Synchronization
If you are doing an initial setup, then use the Auto Synchronous option to synchronize the secondary site and start replication. This is the default.
When this option is selected, Volume Replicator by default performs intelligent synchronization to replicate only those blocks on a volume that are being used by the file system. If required, you can disable intelligent synchronization.
If you want to use the Synchronize from Checkpoint method then you must first create a checkpoint.
If you have a considerable amount of data on the primary data volumes then you may first want to synchronize the secondary for existing data using the backup-restore method with checkpoint. After the restore is complete, use the Synchronize from Checkpoint option to start replication from the checkpoint to synchronize the secondary with the writes that happened when backup-restore was in progress.
To apply changes to advanced settings, click OK.
For additional information on Volume Replicator replication options, refer to the Volume Replicator Administrator's Guide.
Click Next.
- In the Replication Attribute Settings panel, specify required replication attribute information for the cluster at the primary and secondary site. Click the arrow icon to expand an RVG row and display the replication attribute fields. If you are configuring an additional secondary site (multiple DR sites), some fields are disabled.
Disk Group
Displays the list of disk groups that have been configured.
RVG Name
Displays the Replicated Volume Groups corresponding to the disk groups.
IP Address
For IPv4 networks, enter replication IPs that will be used for replication, one for the primary site and another for the secondary site.
For IPv6, select the network from the dropdown list. An IP address will be generated.
Subnet Mask
or
Prefix
For IPv4, enter the subnet mask for the system at the primary site and the secondary site.
For IPv6, enter the prefix.
Public NIC
Select the public NIC from the drop-down list for the system at the primary and secondary site.
For IPv6, available NICs are those belonging to the selected network.
Copy
Enables you to copy the above network settings to any additional RVGs that are listed on this screen. If there is only one RVG, this option does not apply.
After specifying the replication attributes for each of the RVGs, click Next.
- In the Global Cluster Settings panel specify the heartbeat information for the wide-area connector resource. You must specify this information for the primary and the secondary cluster. Any existing WAC resource information can be reused. If you are adding a DR site to an existing DR configuration, GCO is already configured at the primary site, so the primary site fields are dimmed.
Use existing settings
Allows you to use a WAC resource that already exists at either the primary or secondary site. Click Primary or Secondary, depending on the site at which the WAC resource already exists.
Resource Name
Select the existing WAC resource name from the resource name list box.
Create new settings
Select the appropriate site, primary or secondary, for which you want to create a new WAC resource.
IP Address
For IPv4, enter a virtual IP for the WAC resource.
For IPv6, select the network from the dropdown list. An IP address will be generated.
Subnet Mask
or
Prefix
For IPv4, enter the subnet mask for the system at the primary site and the secondary site.
For IPv6, enter the prefix.
Public NIC
Select the public NIC for each system from the drop-down list for the system at the primary and secondary site.
Start GCO after configuration
Select this check box to bring the cluster service group online and start GCO automatically after the wizard completes the necessary configurations. Otherwise, you must bring the service group online and start GCO manually, after the wizard completes.
Once GCO is configured and running, deselecting the checkbox does not stop GCO.
- In the Settings Summary panel, review the displayed information.
Click Back if you want to change any of the parameters. If you have a printer installed, you can click the printer icon at the bottom of the scrollable list to print the settings.
Otherwise, click Next to implement the settings.
- In the Implementation panel, wait till the wizard completes creating the replication configuration and the WAC resource required for global clustering. If a task could not be completed successfully, it is marked with an (x) symbol. For any critical errors, the wizard displays an error message. For less critical errors, the Information column displays a brief description about the task failure and the next screen displays additional information on what action you can take to remedy it. Click Next.
- In the Finish panel, review the displayed information. If a task did not complete successfully, the panel displays an error message, which will provide some insight into the cause for failure. Click Finish to exit the wizard.