Cluster Server 8.0 Implementation Guide for Microsoft SQL Server - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (8.0)
Platform: Windows
  1. Section I. Introducing Veritas InfoScale solutions for application high availability
    1. Understanding the InfoScale solutions for application high availability
      1.  
        About the Veritas InfoScale solutions for monitoring SQL Server
      2. About the VCS agents for SQL Server
        1.  
          About the VCS agent for SQL Server Database Engine
        2.  
          About the VCS agent for SQL Server FILESTREAM
        3.  
          About the VCS GenericService agent for SQL Server Agent service and Analysis service
        4.  
          About the agent for MSDTC service
        5.  
          About the monitoring options
      3. 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
      4. How application availability is achieved in a physical environment
        1.  
          Typical SQL Server cluster configuration using shared storage
        2.  
          Typical SQL Server disaster recovery cluster configuration
        3.  
          SQL Server sample dependency graph
        4.  
          MSDTC sample dependency graph
      5. 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
    2. Managing storage and installing the VCS agents
      1. Managing storage using NetApp filer
        1.  
          Connecting virtual disks to the cluster node
        2.  
          Disconnecting virtual disks from the cluster nodes
      2. Managing storage using Windows Logical Disk Manager
        1.  
          Reserving disks (if you use Windows LDM)
        2.  
          Creating volumes (if you use Windows LDM)
        3.  
          Mounting volumes (if you use Windows LDM)
        4.  
          Unassigning a drive letter
        5.  
          Releasing disks (if you use Windows LDM)
      3.  
        Managing storage using VMware virtual disks
      4.  
        About installing the VCS agents
    3. Installing SQL Server
      1.  
        About installing SQL Server for a high availability (HA) configuration
      2.  
        Configuring Microsoft iSCSI initiator
      3.  
        About installing SQL Server on the first system
      4.  
        About installing SQL Server on additional systems
      5.  
        Assigning ports for multiple SQL Server instances
      6.  
        Enabling IPv6 support for the SQL Server Analysis Service
  2. Section II. Configuring SQL Server in a physical environment
    1. Overview
      1.  
        About configuring SQL Server in physical environment
    2. Configuring the VCS cluster
      1.  
        Configuring the cluster using the Cluster Configuration Wizard
      2.  
        Configuring notification
      3.  
        Configuring Wide-Area Connector process for global clusters
    3. Configuring the SQL Server service group
      1.  
        About configuring the SQL Server service group
      2.  
        Before configuring the SQL Server service group
      3. Configuring a SQL Server service group using the wizard
        1.  
          Configuring detail monitoring for a SQL Server instance
        2.  
          Assigning privileges to the existing SQL Server databases and logs
      4.  
        Configuring the service group in a non-shared storage environment
      5.  
        Running SnapManager for SQL Server
      6.  
        About the modifications required for tagged VLAN or teamed network
      7. Making SQL Server user-defined databases highly available
        1.  
          Create volumes or LUNs for SQL Server user-defined databases
        2.  
          Creating SQL Server databases
        3.  
          Adding storage agent resources to the SQL service group
      8. Verifying the service group configuration
        1.  
          Bringing the service group online
        2.  
          Taking the service group offline
        3.  
          Switching the service group
      9. Administering a SQL Server service group
        1.  
          Modifying a SQL service group configuration
        2.  
          Deleting a SQL service group
    4. Configuring an MSDTC service group
      1.  
        About configuring the MSDTC service group
      2.  
        Typical MSDTC service group configuration using shared storage
      3.  
        Before configuring the MSDTC service group
      4.  
        Creating an MSDTC service group
      5.  
        About configuring an MSDTC client
      6.  
        Configuring an MSDTC client
      7.  
        Verifying the installation
    5. Configuring the standalone SQL Server
      1. Typical high availability configuration for a standalone SQL Server setup
        1.  
          Sample configuration
      2. Configuring a standalone SQL Server for high availablility
        1.  
          Moving the existing SQL Server data files and user databases
    6. Configuring an Active/Active cluster
      1. About running SQL Server in an active-active clustered environment
        1.  
          Sample configuration
      2.  
        Setting up the Active/Active cluster
    7. Configuring a disaster recovery setup
      1. Setting up the disaster recovery cluster
        1.  
          Why implement a disaster recovery solution
        2.  
          Understanding replication
        3.  
          What needs to be protected in a SQL Server environment
      2. Configuring a disaster recovery set up for SQL Server
        1.  
          Configuring replication using NetApp SnapMirror
        2.  
          Configuring SnapMirror resources at the primary site
      3. Configuring the Global Cluster Option for wide-area failover
        1.  
          Prerequisites
        2.  
          Linking clusters: Adding a remote cluster to a local cluster
        3.  
          Converting a local service group to a global service group
        4.  
          Bringing a global service group online
      4. Administering global service groups
        1.  
          Taking a remote global service group offline
        2.  
          Switching a remote service group
        3.  
          Deleting a remote cluster
  3. Section III. Configuring SQL Server in a VMware environment
    1. Configuring application monitoring using the Veritas High Availability solution
      1.  
        Deploying the Veritas High Availability solution for configuring application monitoring
      2. Notes and recommendations
        1. Assigning privileges for non-administrator ESX/ESXi user account
          1.  
            Creating a role
          2.  
            Integrating with Active Directory or local authentication
          3.  
            Creating a new user
          4.  
            Adding a user to the role
      3. Configuring application monitoring
        1.  
          Configuring the VCS cluster
        2.  
          Configuring the application
      4.  
        Modifying the ESXDetails attribute
    2. Administering application monitoring
      1.  
        About the various interfaces available for performing application monitoring tasks
      2. Administering application monitoring using the Veritas High Availability tab
        1.  
          Understanding the Veritas High Availability tab work area
        2.  
          To view the status of configured applications
        3.  
          To configure or unconfigure application monitoring
        4.  
          To start or stop applications
        5.  
          To suspend or resume application monitoring
        6.  
          To switch an application to another system
        7.  
          To add or remove a failover system
        8.  
          To clear Fault state
        9.  
          To resolve a held-up operation
        10.  
          To determine application state
        11.  
          To remove all monitoring configurations
        12.  
          To remove VCS cluster configurations
      3.  
        Administering application monitoring settings
      4. Administering application availability using Veritas High Availability dashboard
        1. Understanding the dashboard work area
          1.  
            Aggregate status bar
          2.  
            ESX cluster/host table
          3.  
            Taskbar
          4.  
            Filters menu
          5.  
            Application table
        2.  
          Monitoring applications across a data center
        3.  
          Monitoring applications across an ESX cluster
        4.  
          Searching for application instances by using filters
        5.  
          Selecting multiple applications for batch operations
        6.  
          Starting an application using the dashboard
        7.  
          Stopping an application by using the dashboard
        8.  
          Entering an application into maintenance mode
        9.  
          Bringing an application out of maintenance mode
        10.  
          Switching an application
  4. Section IV. Appendixes
    1. Appendix A. Troubleshooting
      1.  
        VCS logging
      2.  
        VCS Cluster Configuration Wizard (VCW) logs
      3.  
        VCWsilent logs
      4.  
        NetApp agents error messages
      5. Error and warning messages from VCS agent for SQL Server
        1.  
          Messages from the VCS agent for SQL Server Database Engine
        2.  
          Messages from the VCS agent for SQL Server FILESTREAM
        3.  
          Messages from the VCS agent for SQL Server Agent service and Analysis service
        4.  
          SQL Server Analysis service (MSOLAP) service fails to come online with "invalid context of address" error
        5.  
          Messages from the VCS agent for MSDTC
      6. Troubleshooting application monitoring configuration issues
        1.  
          Running the 'hastop - all' command detaches virtual disks
        2.  
          Validation may fail when you add a failover system
        3.  
          Adding a failover system may fail if you configure a cluster with communication links over UDP
      7. Troubleshooting Veritas High Availability view issues
        1.  
          Veritas High Availability tab not visible from a cluster node
        2.  
          Veritas High Availability tab does not display the application monitoring status
        3.  
          Veritas High Availabilitytab may freeze due to special characters in application display name
        4.  
          Veritas High Availability view may fail to load or refresh
        5.  
          Operating system commands to unmount resource may fail
    2. Appendix B. Using the virtual MMC viewer
      1.  
        About using the virtual MMC viewer
      2.  
        Viewing DTC transaction information

Creating an MSDTC service group

MSDTC is a global resource and is accessed by more than one SQL Server service group. VCS recommends configuring one MSDTC service group in per cluster. VCS provides a configuration wizard that guides you through the process of configuring an MSDTC service group. You can also use this wizard to modify an MSDTC service group configuration.

Note:

Veritas recommends that you create only one MSDTC Server service group in a cluster.

You must use the MSDTC Configuration Wizard to configure the MSDTC Server service group. You cannot use the SQL Server Configuration Wizard to perform this task.

To create an MSDTC service group

  1. Start the MSDTC Configuration Wizard from the Apps menu on the Start screen.
  2. In the Select Configuration Option panel, click MSDTC Server - Service Group Configuration, click Create, and then click Next.
  3. Review and verify that you have met the prerequisites for configuring an MSDTC Server service group and then click Next.
  4. On the Service Group Configuration panel, specify the service group name and select the systems for the service group as follows:
    • Type a name for MSDTC service group.

    • In the Available Cluster Systems box, select the systems on which to configure the service group and click the right-arrow to move the systems to the Systems in Priority Order box. The systems listed in the Systems in Priority Order box represent the SystemList attribute of the service group. While selecting systems, make sure to select the systems that are not in the SystemList attribute for an Exchange service group configured in the cluster.

      To remove a system from the service group's system list, select the Systems in Priority Order list and click the left arrow.

      To change a system's priority in the service group's system list, select the system from the Systems in Priority Order and click the up and down arrows. The system at the top of the list has the highest priority while the system at the bottom of the list has the lowest priority.

    • To enable the service group to automatically come online on one of the systems, select the Include selected systems in the service group's AutoStartList attribute checkbox.

      For information about the AutoStartList attribute, see the Cluster Server Administrator's Guide.

    • Click Next. If the cluster configuration is in read-only mode, the wizard prompts you before changing it to read-write mode. The wizard starts validating your configuration. Various messages indicate the validation status.

  5. On the Virtual Server Configuration panel, specify the information related to the virtual server as follows:
    • Type a virtual name for the MSDTC Server. This is the name that is used by MSDTC clients to connect to the MSDTC Server. The DTC service runs under this virtual name. Ensure that the virtual server name is unique in the cluster.

    • Select IPv4 to configure an IPv4 address for the virtual server.

      • In the Virtual IP Address field, type a unique virtual IPv4 address for the MSDTC server.

      • In the Subnet Mask field, type the subnet to which the virtual IPv4 address belongs.

    • Select IPv6 to configure an IPv6 address for the virtual server. The IPv6 option is disabled if the network does not support IPv6.

      • Select the network from the drop-down list. The wizard uses the network prefix and automatically generates an IPv6 address that is valid and unique on the network.

    • For each system, select the public network adapter name. The Adapter Display Name field displays the TCP/IP enabled adapters on a system, including the private network adapters, if they are TCP/IP enabled. To view the adapters associated with a system, click the Adapter Display Name field and then click the arrow. Make sure that you select the adapters assigned to the public network, not the private.

    • Click Advanced Settings to configure the Lanman agent to perform Windows Active Directory (AD) update. These settings are applicable to the Lanman resource in the service group. On the Lanman Advanced Configuration dialog box, complete the following:

      • Check the Active Directory Update required check box to enable the Lanman agent to update the Active Directory with the virtual name. This sets the Lanman agent attributes ADUpdateRequired and ADCriticalForOnline to true.

      • In the Organizational Unit field, type the distinguished name of the Organizational Unit for the virtual server in the format CN=containername,DC=domainname,DC=com. To browse for an OU, click the ellipsis (...) button and search for the OU using the Windows Find Organization Units dialog box. By default, the Lanman resource adds the virtual server to the default container "Computers."

      • Click OK.

        The user account for VCS Helper service must have adequate privileges on the specified container to create and update computer accounts.

    • Click Next.

  6. On the Specify Data Path panel, specify the drive letter for the MSDTC log and registry replication directory and click Next. If the directory does not exist, the wizard creates it. Veritas recommends using different paths for these directories.

    Clear the Configure NetApp SnapMirror Resource(s) check box. This option is applicable only in case of a disaster recovery configuration. The SnapMirror resource is used to monitor replication between filers at the primary and the secondary site, in a disaster recovery configuration. If you are setting up a disaster recovery environment, check this check box to configure the SnapMirror resource at the primary site. The SnapMirror resource must be configured only after you have configured the cluster at the secondary site.

  7. On the Initiator Selection panel, select the initiator for the virtual disk from the list of available initiators displayed for each cluster node, and then click Next.

    If you are configuring Multipath I/O (MPIO) over Fibre Channel (FC), you must select at least two FC initiators for each cluster node. Note that the node from which you run this wizard already has an initiator selected by default. This is the initiator that was specified when you connected the LUNs to this cluster node.

  8. On the Service Group Summary panel, review the service group configuration and change the resource names if desired and then click Next.
    • The Resources box lists the configured resources. Click on a resource to view its attributes and their configured values.

    • The wizard assigns unique names to resources. Change names of the resources, if desired.

      To edit a resource name, select the resource name and either click it or press the F2 key. Press the Enter key after editing each resource name. To cancel editing a resource name, press the Esc key.

  9. Click Yes on the message that informs you that the wizard will run commands to create the service group.

    Various messages indicate the status of these commands.

  10. In the Completing the MSDTC Configuration Wizard panel, check Bring the service group online check box if you wish to bring the configured service group online on the local system. To bring the service group online later, clear this check box.
  11. Click Finish to exit the wizard.

    This completes the MSDTC Server service group configuration. You can now proceed to configure the MSDTC client manually.