Cluster Server 7.4 Agent for EMC SRDF Configuration Guide - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.1)
Platform: Windows
  1. Introducing the agent for EMC SRDF
    1.  
      About the agent for EMC SRDF
    2.  
      Supported hardware for EMC SRDF
    3.  
      Supported software
    4.  
      Typical EMC SRDF setup in a VCS cluster
    5. EMC SRDF agent functions
      1.  
        About the EMC SRDF agent's online function
      2.  
        About dynamic swap support for the EMC SRDF agent
    6.  
      Installing the agent for EMC SRDF
  2. Configuring the agent for EMC SRDF
    1. Configuration concepts for the EMC SRDF agent
      1.  
        Resource type definition for the EMC SRDF agent
      2. Attribute definitions for the SRDF agent
        1.  
          Required attributes
        2.  
          Optional attributes
        3.  
          Internal attributes
      3.  
        Sample configuration for the EMC SRDF agent
    2. Before you configure the agent for EMC SRDF
      1.  
        About cluster heartbeats
      2.  
        About configuring system zones in replicated data clusters
      3.  
        About preventing split-brain
    3. Configuring the agent for EMC SRDF
      1. Configuring the agent manually in a global cluster
        1.  
          Configuring the Symm heartbeat on each cluster
      2.  
        Configuring the agent manually in a replicated data cluster
      3.  
        Setting the OnlineTimeout attribute for the SRDF resource
      4.  
        Additional configuration considerations for the SRDF agent
  3. Testing VCS disaster recovery support with EMC SRDF
    1. How VCS recovers from various disasters in an HA/DR setup with EMC SRDF
      1.  
        Failure scenarios in global clusters
      2.  
        Failure scenarios in replicated data clusters
    2.  
      Testing the global service group migration
    3.  
      Testing disaster recovery after host failure
    4.  
      Testing disaster recovery after site failure
    5.  
      Performing failback after a node failure or an application failure
    6.  
      Performing failback after a site failure
  4. Setting up fire drill
    1.  
      About fire drills
    2.  
      Fire drill configurations
    3. About the SRDFSnap agent
      1.  
        SRDFSnap agent functions
      2.  
        Resource type definition for the SRDFSnap agent
      3.  
        Attribute definitions for the SRDFSnap agent
      4.  
        About the Snapshot attributes
      5.  
        Sample configuration for a fire drill service group
    4.  
      Additional considerations for running a fire drill
    5.  
      Before you configure the fire drill service group
    6. Configuring the fire drill service group
      1.  
        About the Fire Drill wizard
    7.  
      Verifying a successful fire drill

Configuring the agent manually in a global cluster

Configuring the agent manually in a global cluster involves the following tasks:

To configure the agent in a global cluster

  1. Start Cluster Manager (Java Console) and log on to the cluster.

  2. If the agent resource type (SRDF) is not added to your configuration, add it. From the Cluster Explorer File menu, choose Import Types, and select:

    systemdrive\Program Files\Veritas\cluster server\conf\
Sample_SRDF\SRDFTypes.cf
  3. Click Import.
  4. Save the configuration.
  5. Add a resource of type SRDF at the bottom of the service group.
  6. Configure the attributes of the SRDF resource.
  7. If the service group is not configured as a global service group, configure the service group using the Global Group Configuration Wizard.

    Refer to the Cluster Server Administrator's Guide for more information.

  8. Change the ClusterFailOverPolicy attribute from the default, if necessary. Veritas recommends keeping the default, which is Manual, to minimize the chance of failing over on a split-brain.
  9. Repeat step 5 through step 8 for each service group in each cluster that uses replicated data.
  10. Configure the Symm heartbeat on each cluster.

    See Configuring the Symm heartbeat on each cluster.

  11. The configuration must be identical on all cluster nodes, both primary and disaster recovery.