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

Before you configure the fire drill service group

Before you configure the fire drill service group, ensure that the following pre-requisites are met:

  • Make sure the application service group is configured with a SRDF resource.

  • Make sure the infrastructure to take appropriate snapshots (mirror/clone/snap) is properly configured on the target arrays.

  • If you plan to run a fire drill on SRDF/A devices, you must have a TimeFinder/CG license.

  • When you use the Gold or Silver configuration, make sure TimeFinder for SRDF is installed and configured at the target array.

  • When you take snapshots of R2 devices, consider the following:

    • For TimeFinder/Mirror, BCV devices must be associated with and attached to the RDF2 device group or composite group, and fully established and synchronised with the R2 devices.

    • For TimeFinder/Clone, BCV or target devices must be associated with the RDF2 device group or composite group.

    • For TimeFinder/Snap, or space-optimized snapshots, the VDEV and SAVE devices must be associated with the device group or composite group for which you want to run the fire drill using space-optimized snapshots. Ensure that the SAVE pool that is defined in the SavePoolName attribute exists and that the SAVE devices are enabled in the SAVE pool.

  • When you take snapshots of non-replicated VxVM disk groups residing on Symmetrix devices, create a Symmetrix device group with the same name as the VxVM disk group. The device group must contain the same devices as in the VxVM disk group and additionally, have the same number of BCVs or target devices associated.

  • For non-replicated devices:

    • You must use the Gold configuration without the option to run in the Bronze mode. Set the RequireSnapshot attribute to 1.

  • If you plan to run a fire drill using space-optimized snapshots, you must have a TimeFinder/Snap license.

  • Make sure that the VDEV devices and SAVE devices are associated with the device group or composite group for which you want to run fire drill using space-optimized snapshots.

  • Make sure that the SAVE pool as specified by SavePoolName attribute exists prior to running fire drill using space-optimized snapshots.

  • Make sure that the copy sessions are not created for the device or composite group prior to running fire drill with space-optimized snapshots.

  • Make sure that the SRDF mode of replication is set to Synchronous prior to running fire drill using space-optimized snapshots and clones. This is because EMC does not support creation of TimeFinder/Snap and TimeFinder/Clone copy sessions for RDF2 device, if the SRDF mode of replication is set to Asynchronous.

  • The secondary system where you plan to run the fire drill must have access to the replicated volumes.