InfoScale™ 9.0 Cluster Server Agent for Hitachi TrueCopy/HP-XP Continuous Access Configuration Guide - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: Windows
  1. Introducing the agent for Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
    1.  
      About the agent for Hitachi TrueCopy/HP-XP Continuous Access
    2.  
      Supported software
    3.  
      Supported hardware
    4.  
      Typical Hitachi TrueCopy/Hewlett-Packard XP Continuous Access setup in a VCS cluster
    5. Hitachi TrueCopy/Hewlett-Packard XP Continuous Access agent functions
      1.  
        About the Hitachi TrueCopy/Hewlett-Packard XP Continuous Access agent's online function
  2. Configuring the agent for Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
    1. Configuration concepts for the Hitachi TrueCopy/Hewlett-Packard XP Continuous Access agent
      1.  
        Resource type definition for the Hitachi TrueCopy agent
      2. Attribute definitions for the TrueCopy/HP-XP-CA agent
        1. About the SplitTakeover attribute for the Hitachi TrueCopy agent
          1.  
            SplitTakeover attribute = 0
          2.  
            SplitTakeover attribute = 1
        2. About the FreezeSecondaryOnSplit attribute for the Hitachi TrueCopy agent
          1.  
            FreezeSecondaryOnSplit attribute = 0
        3.  
          About the HTC configuration parameters
        4.  
          Special consideration for fence level NEVER
        5.  
          Considerations for calculating the AllowAutoFailoverInterval attribute value
      3.  
        Sample configuration for the TrueCopy/HP-XP-CA agent
    2. Before you configure the agent for Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
      1.  
        About cluster heartbeats
      2.  
        About configuring system zones in replicated data clusters
      3.  
        About preventing split-brain
    3. Configuring the agent for Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
      1.  
        Configuring the agent manually in a global cluster
      2.  
        Configuring the agent manually in a replicated data cluster
  3. Testing VCS disaster recovery support with Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
    1. How VCS recovers from various disasters in an HA/DR setup with Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
      1.  
        Failure scenarios in global clusters
      2.  
        Failure scenarios in replicated data clusters
      3.  
        Replication link / Application failure scenarios
    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. About the HTCSnap agent
      1.  
        HTCSnap agent functions
      2.  
        Resource type definition for the HTCSnap agent
      3.  
        Attribute definitions for the HTCSnap agent
      4.  
        About the Snapshot attributes
      5.  
        Sample configuration for a fire drill service group
    3.  
      Additional considerations for running a fire drill
    4.  
      Before you configure the fire drill service group
    5. Configuring the fire drill service group
      1.  
        About the Fire Drill wizard
    6.  
      Verifying a successful fire drill

About preventing split-brain

Split-brain occurs when all heartbeat links between the primary and secondary hosts are cut. In this situation, each side mistakenly assumes that the other side is down. You can minimize the effects of split-brain by ensuring that the cluster heartbeat links pass through a similar physical infrastructure as the replication links. When you ensure that both pass through the same infrastructure, if one breaks, so does the other.

Sometimes you cannot place the heartbeats alongside the replication links. In this situation, a possibility exists that the cluster heartbeats are disabled, but the replication link is not. A failover transitions the original P-VOL to S-VOL and S-VOL to P-VOL. In this case, the application faults because its underlying volumes become write-disabled, causing the service group to fault. VCS tries to fail it over to another host, causing the same consequence in the reverse direction. This phenomenon continues until the group comes online on the final node. You can avoid this situation by setting up your infrastructure such that loss of heartbeat links also means the loss of replication links.