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

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: Windows
  1. Section I. Getting started with Storage Foundation and High Availability Solutions for SQL Server
    1. Introducing SFW HA and the VCS agents for SQL Server
      1.  
        About the Veritas InfoScale solutions for monitoring SQL Server
      2.  
        How application availability is achieved in a physical environment
      3. How is application availability achieved in a VMware virtual environment
        1.  
          How the VMwareDisks agent communicates with the vCenter Server instead of the ESX/ESXi host
        2.  
          Typical VCS cluster configuration in a virtual environment
      4.  
        Managing storage using VMware virtual disks
      5.  
        Modifying the ESXDetails attribute
      6. How VCS monitors storage components
        1.  
          Shared storage - if you use NetApp filers
        2.  
          Shared storage - if you use SFW to manage cluster dynamic disk groups
        3.  
          Shared storage - if you use Windows LDM to manage shared disks
        4.  
          Non-shared storage - if you use SFW to manage dynamic disk groups
        5.  
          Non-shared storage - if you use Windows LDM to manage local disks
        6.  
          Non-shared storage - if you use VMware storage
      7.  
        What must be protected in an SQL Server environment
      8.  
        About the VCS agents for SQL Server
      9.  
        About the VCS agent for SQL Server Database Engine
      10.  
        About the VCS agent for SQL Server FILESTREAM
      11.  
        About the VCS GenericService agent for SQL Server Agent service and Analysis service
      12.  
        About the agent for MSDTC service
      13.  
        About the monitoring options
      14.  
        Typical SQL Server configuration in a VCS cluster
      15.  
        Typical SQL Server disaster recovery configuration
      16.  
        SQL Server sample dependency graph
      17.  
        MSDTC sample dependency graph
    2. Deployment scenarios for SQL Server
      1.  
        Workflows in the Solutions Configuration Center
      2. Reviewing the active-passive HA configuration
        1.  
          Sample Active-Passive configuration
      3.  
        Reviewing the prerequisites for a standalone SQL Server
      4. Reviewing a standalone SQL Server configuration
        1.  
          Sample standalone SQL Server configuration
      5.  
        Reviewing the MSDTC configuration
      6.  
        VCS campus cluster configuration
      7. Reviewing the campus cluster configuration
        1.  
          Campus cluster failover using the ForceImport attribute
        2.  
          Reinstating faulted hardware in a campus cluster
      8.  
        VCS Replicated Data Cluster configuration
      9. Reviewing the Replicated Data Cluster configuration
        1.  
          Sample replicated data cluster configuration
      10. About setting up a Replicated Data Cluster configuration
        1.  
          About setting up replication
        2.  
          About configuring and migrating the service group
      11. Disaster recovery configuration
        1.  
          DR configuration tasks: Primary site
        2.  
          DR configuration tasks: Secondary site
        3.  
          Supported disaster recovery configurations for service group dependencies
      12. Reviewing the disaster recovery configuration
        1.  
          Sample disaster recovery configuration
      13. Notes and recommendations for cluster and application configuration
        1.  
          IPv6 support
        2.  
          IP address requirements for an Active-Passive configuration
        3.  
          IP address requirements for a disaster recovery configuration
      14.  
        Configuring the storage hardware and network
      15. Configuring disk groups and volumes for SQL Server
        1.  
          About disk groups and volumes
        2.  
          Prerequisites for configuring disk groups and volumes
        3.  
          Considerations for a fast failover configuration
        4.  
          Considerations for converting existing shared storage to cluster disk groups and volumes
        5.  
          Considerations when creating disks and volumes for campus clusters
        6.  
          Considerations for volumes for a Volume Replicator configuration
        7.  
          Considerations for disk groups and volumes for multiple instances
        8.  
          Sample disk group and volume configuration
        9.  
          MSDTC sample disk group and volume configuration
        10.  
          Viewing the available disk storage
        11.  
          Creating a dynamic disk group
        12.  
          Adding disks to campus cluster sites
        13.  
          Creating volumes for high availability clusters
        14.  
          Creating volumes for campus clusters
      16. About managing disk groups and volumes
        1.  
          Importing a disk group and mounting a volume
        2.  
          Unmounting a volume and deporting a disk group
        3.  
          Adding drive letters to mount the volumes
      17. Configuring the cluster using the Cluster Configuration Wizard
        1.  
          Configuring notification
        2.  
          Configuring Wide-Area Connector process for global clusters
        3.  
          Adding nodes to a cluster
    3. Installing SQL Server
      1.  
        About installing and configuring SQL Server
      2.  
        About installing multiple SQL Server instances
      3.  
        Verifying that the SQL Server databases and logs are moved to shared storage
      4.  
        About installing SQL Server for high availability configuration
      5.  
        About installing SQL Server on the first system
      6.  
        About installing SQL Server on additional systems
      7.  
        Creating a SQL Server user-defined database
      8. Completing configuration steps in SQL Server
        1.  
          Moving the tempdb database if using Volume Replicator for disaster recovery
        2.  
          Assigning ports for multiple SQL Server instances
        3.  
          Enabling IPv6 support for the SQL Server Analysis Service
  2. Section II. Configuring SQL Server in a physical environment
    1. Configuring SQL Server for failover
      1.  
        Tasks for configuring a new server for high availability
      2.  
        Tasks for configuring an existing server for high availability
      3. About configuring the SQL Server service group
        1.  
          Service group requirements for Active-Active configurations
        2.  
          Prerequisites for configuring the SQL Server service group
        3.  
          Creating the SQL Server service group
      4. Configuring the service group in a non-shared storage environment
        1.  
          Assigning privileges to the existing SQL Server databases and logs
        2.  
          Enabling fast failover for disk groups (optional)
      5.  
        Verifying the SQL Server cluster configuration
      6.  
        About the modifications required for tagged VLAN or teamed network
      7.  
        Tasks for configuring MSDTC for high availability
      8. Configuring an MSDTC Server service group
        1.  
          Prerequisites for MSDTC configuration
        2.  
          Creating an MSDTC Server service group
      9.  
        About configuring the MSDTC client for SQL Server
      10.  
        About the VCS Application Manager utility
      11.  
        Viewing DTC transaction information
      12.  
        Modifying a SQL Server service group to add VMDg and MountV resources
      13.  
        Determining additional steps needed
    2. Configuring campus clusters for SQL Server
      1.  
        Tasks for configuring campus clusters
      2.  
        Modifying the IP resource in the SQL Server service group
      3.  
        Verifying the campus cluster: Switching the service group
      4.  
        Setting the ForceImport attribute to 1 after a site failure
    3. Configuring Replicated Data Clusters for SQL Server
      1.  
        Tasks for configuring Replicated Data Clusters
      2.  
        Creating the primary system zone for the application service group
      3.  
        Creating a parallel environment in the secondary zone
      4.  
        Setting up security for Volume Replicator
      5. Setting up the Replicated Data Sets (RDS)
        1.  
          Prerequisites for setting up the RDS for the primary and secondary zones
        2.  
          Creating the Replicated Data Sets with the wizard
      6. Configuring a RVG service group for replication
        1.  
          Creating the RVG service group
        2. Configuring the resources in the RVG service group for RDC replication
          1.  
            Configuring the IP and NIC resources
          2. Configuring the VMDg or VMNSDg resources for the disk groups
            1.  
              Modifying the DGGuid attribute for the new disk group resource in the RVG service group
            2.  
              Configuring the VMDg or VMNSDg resources for the disk group for the user-defined database
            3.  
              Adding the Volume Replicator RVG resources for the disk groups
            4.  
              Linking the Volume Replicator RVG resources to establish dependencies
            5.  
              Deleting the VMDg or VMNSDg resource from the SQL Server service group
        3. Configuring the RVG Primary resources
          1.  
            Creating the RVG Primary resources
          2.  
            Linking the RVG Primary resources to establish dependencies
          3.  
            Bringing the RVG Primary resources online
        4.  
          Configuring the primary system zone for the RVG service group
      7.  
        Setting a dependency between the service groups
      8. Adding the nodes from the secondary zone to the RDC
        1.  
          Adding the nodes from the secondary zone to the RVG service group
        2.  
          Configuring secondary zone nodes in the RVG service group
        3.  
          Configuring the RVG service group NIC resource for fail over (VMNSDg only)
        4.  
          Configuring the RVG service group IP resource for failover
        5.  
          Configuring the RVG service group VMNSDg resources for fail over
        6.  
          Adding nodes from the secondary zone to the SQL Server service group
        7.  
          Configuring the zones in the SQL Server service group
        8.  
          Configuring the application service group IP resource for fail over (VMNSDg only)
        9.  
          Configuring the application service group NIC resource for fail over (VMNSDg only)
      9. Verifying the RDC configuration
        1.  
          Bringing the service group online
        2.  
          Switching online nodes
      10.  
        Additional instructions for GCO disaster recovery
    4. Configuring disaster recovery for SQL Server
      1.  
        Tasks for configuring disaster recovery for SQL Server
      2.  
        Tasks for setting up DR in a non-shared storage environment
      3.  
        Guidelines for installing Arctera InfoScale Enterprise and configuring the cluster on the secondary site
      4.  
        Verifying your primary site configuration
      5. Setting up your replication environment
        1. Requirements for EMC SRDF array-based hardware replication
          1.  
            Software requirements for configuring EMC SRDF
          2.  
            Replication requirements for EMC SRDF
        2. Requirements for Hitachi TrueCopy array-based hardware replication
          1.  
            Software requirements for Hitachi TrueCopy
          2.  
            Replication requirements for Hitachi TrueCopy
      6.  
        Assigning user privileges (secure clusters only)
      7. About configuring disaster recovery with the DR wizard
        1.  
          Configuring disaster recovery with the DR wizard
      8.  
        Cloning the storage on the secondary site using the DR wizard (Volume Replicator replication option)
      9.  
        Creating temporary storage on the secondary site using the DR wizard (array-based replication)
      10.  
        Installing and configuring SQL Server on the secondary site
      11.  
        Cloning the service group configuration from the primary site to the secondary site
      12.  
        Configuring the SQL Server service group in a non-shared storage environment
      13. Configuring replication and global clustering
        1.  
          Configuring Volume Replicator replication and global clustering
        2. Configuring EMC SRDF replication and global clustering
          1.  
            Optional settings for EMC SRDF
        3. Configuring Hitachi TrueCopy replication and global clustering
          1.  
            Optional settings for HTC
        4.  
          Configuring global clustering only
      14.  
        Creating the replicated data sets (RDS) for Volume Replicator replication
      15.  
        Creating the Volume Replicator RVG service group for replication
      16. Configuring the global cluster option for wide-area failover
        1.  
          Linking clusters: Adding a remote cluster to a local cluster
        2.  
          Converting a local service group to a global service group
        3.  
          Bringing a global service group online
      17.  
        Verifying the disaster recovery configuration
      18.  
        Adding multiple DR sites (optional)
      19.  
        Recovery procedures for service group dependencies
      20.  
        Configuring DR manually without the DR wizard
    5. Testing fault readiness by running a fire drill
      1.  
        About disaster recovery fire drills
      2. About the Fire Drill Wizard
        1.  
          About Fire Drill Wizard general operations
        2. About Fire Drill Wizard operations in a Volume Replicator environment
          1.  
            Preparing the fire drill configuration
          2.  
            About running the fire drill
          3.  
            About restoring the fire drill configuration
          4.  
            About deleting the fire drill configuration
        3.  
          About Fire Drill Wizard operations in a Hitachi TrueCopy or EMC SRDF environment
      3.  
        About post-fire drill scripts
      4.  
        Tasks for configuring and running fire drills
      5. Prerequisites for a fire drill
        1.  
          Prerequisites for a fire drill in a Volume Replicator environment
        2.  
          Prerequisites for a fire drill in a Hitachi TrueCopy environment
        3.  
          Prerequisites for a fire drill in an EMC SRDF environment
      6. Preparing the fire drill configuration
        1.  
          System Selection panel details
        2.  
          Service Group Selection panel details
        3.  
          Secondary System Selection panel details
        4.  
          Fire Drill Service Group Settings panel details
        5.  
          Disk Selection panel details
        6.  
          Hitachi TrueCopy Path Information panel details
        7.  
          HTCSnap Resource Configuration panel details
        8.  
          SRDFSnap Resource Configuration panel details
        9.  
          Fire Drill Preparation panel details
      7.  
        Running a fire drill
      8.  
        Re-creating a fire drill configuration that has changed
      9.  
        Restoring the fire drill system to a prepared state
      10. Deleting the fire drill configuration
        1.  
          Fire Drill Deletion panel details
      11.  
        Considerations for switching over fire drill service groups

Adding nodes to a cluster

To add a node to a VCS cluster

  1. Start the VCS Cluster Configuration wizard.

    Click Start > All Programs > Veritas > Veritas Cluster Server > Configuration Tools > Cluster Configuration Wizard.

    Run the wizard from the node to be added or from a node in the cluster. The node that is being added should be part of the domain to which the cluster belongs.

  2. Read the information on the Welcome panel and click Next.
  3. On the Configuration Options panel, click Cluster Operations and click Next.
  4. In the Domain Selection panel, select or type the name of the domain in which the cluster resides and select the discovery options.

    To discover information about all the systems and users in the domain, do the following:

    • Clear the Specify systems and users manually check box.

    • Click Next.

      Proceed to step 8.

    To specify systems and user names manually (recommended for large domains), do the following:

    • Check the Specify systems and users manually check box.

      Additionally, you may instruct the wizard to retrieve a list of systems and users in the domain by selecting appropriate check boxes.

    • Click Next.

      If you chose to retrieve the list of systems, proceed to step 6. Otherwise proceed to the next step.

  5. On the System Selection panel, complete the following and click Next:
    • Type the name of an existing node in the cluster and click Add.

    • Type the name of the system to be added to the cluster and click Add.

    If you specify only one node of an existing cluster, the wizard discovers all nodes for that cluster. To add a node to an existing cluster, you must specify a minimum of two nodes; one that is already a part of a cluster and the other that is to be added to the cluster.

    Proceed to step 8.

  6. On the System Selection panel, specify the systems to be added and the nodes for the cluster to which you are adding the systems.

    Enter the system name and click Add to add the system to the Selected Systems list. Alternatively, you can select the systems from the Domain Systems list and click the right-arrow icon.

    If you specify only one node of an existing cluster, the wizard discovers all nodes for that cluster. To add a node to an existing cluster, you must specify a minimum of two nodes; one that is already a part of a cluster and the other that is to be added to the cluster.

  7. The System Report panel displays the validation status, whether Accepted or Rejected, of all the systems you specified earlier.

    A system can be rejected for any of the following reasons:

    • The system does not respond to a ping request.

    • WMI access is disabled on the system.

    • The wizard is unable to retrieve information about the system's architecture or operating system.

    • VCS is either not installed on the system or the version of VCS is different from what is installed on the system on which you are running the wizard.

    Click on a system name to see the validation details. If you wish to include a rejected system, rectify the error based on the reason for rejection and then run the wizard again.

    Click Next to proceed.

  8. On the Cluster Configuration Options panel, click Edit Existing Cluster and click Next.
  9. On the Cluster Selection panel, select the cluster to be edited and click Next.

    If you chose to specify the systems manually in step 4, only the clusters configured with the specified systems are displayed.

  10. On the Edit Cluster Options panel, click Add Nodes and click Next.

    In the Cluster User Information dialog box, type the user name and password for a user with administrative privileges to the cluster and click OK.

    The Cluster User Information dialog box appears only when you add a node to a cluster with VCS user privileges (a cluster that is not a secure cluster).

  11. On the Cluster Details panel, check the check boxes next to the systems to be added to the cluster and click Next.

    The right pane lists nodes that are part of the cluster. The left pane lists systems that can be added to the cluster.

  12. The wizard validates the selected systems for cluster membership. After the nodes have been validated, click Next.

    If a node does not get validated, review the message associated with the failure and restart the wizard after rectifying the problem.

  13. On the Private Network Configuration panel, configure the VCS private network communication on each system being added and then click Next. How you configure the VCS private network communication depends on how it is configured in the cluster. If LLT is configured over Ethernet, you have to use the same on the nodes being added. Similarly, if LLT is configured over UDP in the cluster, you have use the same on the nodes being added.

    Do one of the following:

    • To configure the VCS private network over Ethernet, do the following:

      • Select the check boxes next to the two NICs to be assigned to the private network.

        Arctera recommends reserving two NICs exclusively for the private network. However, you could lower the priority of one NIC and use the low-priority NIC for public and private communication.

      • If you have only two NICs on a selected system, it is recommended that you lower the priority of at least one NIC that will be used for private as well as public network communication.

        To lower the priority of a NIC, right-click the NIC and select Low Priority from the pop-up menu.

      • If your configuration contains teamed NICs, the wizard groups them as "NIC Group #N" where "N" is a number assigned to the teamed NIC. A teamed NIC is a logical NIC, formed by grouping several physical NICs together. All NICs in a team have an identical MAC address. Arctera recommends that you do not select teamed NICs for the private network.

      The wizard configures the LLT service (over Ethernet) on the selected network adapters.

    • To configure the VCS private network over the User Datagram Protocol (UDP) layer, do the following:

      • Select the check boxes next to the two NICs to be assigned to the private network. You can assign maximum eight network links. Arctera recommends reserving at least two NICs exclusively for the VCS private network. You could lower the priority of one NIC and use the low-priority NIC for both public and private communication.

      • If you have only two NICs on a selected system, it is recommended that you lower the priority of at least one NIC that will be used for private as well as public network communication. To lower the priority of a NIC, right-click the NIC and select Low Priority from the pop-up menu.

      • Specify a unique UDP port for each of the link. Click Edit Ports if you wish to edit the UDP ports for the links. You can use ports in the range 49152 to 65535. The default ports numbers are 50000 and 50001 respectively. Click OK.

      • For each selected NIC, verify the displayed IP address. If a selected NIC has multiple IP addresses assigned, double-click the field and choose the desired IP address from the drop-down list. In case of IPv4, each IP address can be in a different subnet.

        The IP address is used for the VCS private communication over the specified UDP port.

      • For each selected NIC, double-click the respective field in the Link column and choose a link from the drop-down list. Specify a different link (Link1 or Link2) for each NIC. Each link is associated with a UDP port that you specified earlier.

      The wizard configures the LLT service (over UDP) on the selected network adapters. The specified UDP ports are used for the private network communication.

  14. On the Public Network Communication panel, select a NIC for public network communication, for each system that is being added, and then click Next.

    This step is applicable only if you have configured the ClusterService service group, and the system being added has multiple adapters. If the system has only one adapter for public network communication, the wizard configures that adapter automatically.

  15. Specify the credentials for the user in whose context the VCS Helper service runs.
  16. Review the summary information and click Add.
  17. The wizard starts running commands to add the node. After all commands have been successfully run, click Finish.