InfoScale™ 9.0 Storage Foundation and High Availability Solutions Microsoft Clustering Solutions Guide for Microsoft SQL Server - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: Windows
  1. Introducing SFW solutions for a Microsoft cluster
    1.  
      About Microsoft clustering solutions with SFW
    2.  
      Advantages of using SFW in a Microsoft cluster
    3.  
      About high availability clusters
    4.  
      About campus clusters
    5.  
      About disaster recovery clusters
  2. Planning for deploying SQL Server with SFW in a Microsoft cluster
    1.  
      InfoScale requirements for Microsoft clustering solutions
    2. Planning your SQL Server high availability configuration
      1.  
        Sample high availability configuration for SQL Server with SFW
      2.  
        Configuring the quorum device for high availability
    3. Planning your campus cluster configuration
      1.  
        Microsoft campus cluster failure scenarios
      2. Microsoft cluster quorum and quorum arbitration
        1.  
          Quorum
        2.  
          Cluster ownership of the quorum resource
        3.  
          The vxclus utility
    4. Planning your disaster recovery configuration
      1.  
        Sample disaster recovery configuration for SQL Server with SFW and Volume Replicator
  3. Workflows for deploying SQL Server with SFW in a Microsoft cluster
    1.  
      Workflow for a high availability (HA) configuration
    2. Workflow for a campus cluster configuration
      1.  
        Campus cluster: Connecting the two nodes
    3.  
      Workflow for a disaster recovery configuration
    4.  
      Using the Solutions Configuration Center workflow
    5.  
      Configuring the storage hardware and network
  4. Configuring SFW storage
    1.  
      Tasks for configuring InfoScale Storage
    2. Planning for SFW cluster disk groups and volumes
      1.  
        Sample SQL Server high-availability cluster storage configuration
      2.  
        Sample campus cluster storage configuration
      3.  
        Sample SQL Server disaster recovery storage configuration
    3.  
      Considerations when creating disk groups and volumes for a campus cluster
    4.  
      Considerations when creating volumes for a DR configuration using Volume Replicator replication
    5.  
      Viewing the available disk storage
    6.  
      Creating dynamic cluster disk groups
    7.  
      Adding disks to campus cluster sites
    8.  
      Creating dynamic volumes for high availability clusters
    9.  
      Creating dynamic volumes for campus clusters
  5. Implementing a dynamic mirrored quorum resource
    1.  
      Tasks for implementing a dynamic mirrored quorum resource
    2.  
      Creating a dynamic cluster disk group and a mirrored volume for the quorum resource
    3.  
      Adding a Volume Manager Disk Group resource for the quorum
    4.  
      Changing the quorum resource to a dynamic mirrored quorum resource
  6. Installing SQL Server and configuring resources
    1.  
      Tasks for installing and configuring SQL Server
    2.  
      Creating the resource group for the SQL Server instance
    3.  
      Prerequisites for installing SQL Server
    4.  
      Installing SQL Server in an InfoScale Storage environment
    5.  
      Dependency graph for SQL Server
    6.  
      Verifying the SQL Server group in the Microsoft cluster
  7. Configuring disaster recovery
    1.  
      Tasks for configuring the secondary site for disaster recovery for SQL Server
    2.  
      Verifying the primary site configuration
    3.  
      Creating a parallel environment for SQL Server on the secondary site
    4.  
      Volume Replicator components overview
    5.  
      Setting up security for Volume Replicator
    6.  
      Creating resources for Volume Replicator
    7. Configuring Volume Replicator: Setting up an RDS
      1.  
        Prerequisites for setting up the RDS
      2.  
        Creating a Replicated Data Set (RDS)
    8.  
      Creating the RVG resource
    9.  
      Setting the SQL server resource dependency on the RVG resource
    10. Normal Volume Replicator operations and recovery procedures
      1.  
        Monitoring the status of the replication
      2.  
        Performing planned migration
      3. Replication recovery procedures
        1.  
          Bringing up the application on the secondary host
        2.  
          Restoring the primary host
  8. Appendix A. Configure InfoScale Storage in an existing Microsoft Failover Cluster
    1.  
      Configuring InfoScale Storage in an existing Microsoft Failover Cluster

Creating resources for Volume Replicator

Create the resources for Volume Replicator replication at the primary and secondary sites using the Failover Cluster Management tool. You create a network name resource and IP address resource to be used for Volume Replicator replication.

A separate valid IP address is necessary for Volume Replicator replication, because on the secondary cluster before a disaster, the application IP must be offline whereas the Volume Replicator IP must be online.

You create the resources for the primary site and then repeat the procedure to create the resources on the secondary site.

To create a Network Name resource and IP address resource for Volume Replicator replication

  1. Right-click on the application group and select Add a Resource > Client Access Point.

  2. In the Client Access Point panel of the New Resource Wizard, specify the following:

    • In the Name field, specify a name for the Network Name resource. The default is the name of the group you selected. Specify any name except the node and the virtual server name. The network name you assign when creating the resource for the secondary site must be different from the network name for the primary site.

    • Select the network and specify the IP address.

    Click Next.
  3. In the Confirmation panel, review the information and click Next.
  4. When configuration is complete, click Finish.
  5. Repeat the same procedure to create the IP and the Network Name resource at the secondary site.
  6. Bring the resources online.