InfoScale™ 9.0 Storage Foundation and High Availability Solutions Microsoft Clustering Solutions Guide for Microsoft SQL Server - Windows
- Introducing SFW solutions for a Microsoft cluster
- Planning for deploying SQL Server with SFW in a Microsoft cluster
- Workflows for deploying SQL Server with SFW in a Microsoft cluster
- Configuring SFW storage
- Planning for SFW cluster disk groups and volumes
- Implementing a dynamic mirrored quorum resource
- Installing SQL Server and configuring resources
- Configuring disaster recovery
- Configuring Volume Replicator: Setting up an RDS
- Normal Volume Replicator operations and recovery procedures
- Appendix A. Configure InfoScale Storage in an existing Microsoft Failover Cluster
Prerequisites for setting up the RDS
Before creating an RDS, check whether your setup meets the following prerequisites:
Verify that the disk groups and volumes for the SQL user database files and log files have been created. You can create the Replicator Log volume while you run the wizard if not created earlier.
Verify that VxSAS has been configured.
Verify that the SQL virtual server Network Name resource is offline on the secondary site. This would also bring all the dependent SQL resources offline. If on the same subnet, ensure that the SQL IP address resource is also offline.
Verify that the intended Primary host is connected to VEA, if you configure the RDS from a remote client or from a host that is not the Primary.
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.
Verify that the data volumes and Replicator Log volume that intended to be a part of the RDS are not of the following types, as Volume Replicator does not support the following types of volumes:
Storage Foundation (software) RAID-5 volumes
Volumes with the Dirty Region Log (DRL)
Volumes with a comma in their names
Secondary volume of a size smaller or greater than that on the Primary
Volume that is under replication
For the Replicator Log volume, in addition to these types, make sure that the volume does not have a DCM.