InfoScale™ 9.0 Cluster Server Agent for Hitachi TrueCopy/HP-XP Continuous Access Configuration Guide - Windows
- Introducing the agent for Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
- Configuring the agent for Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
- Configuration concepts for the Hitachi TrueCopy/Hewlett-Packard XP Continuous Access agent
- Attribute definitions for the TrueCopy/HP-XP-CA agent
- Before you configure the agent for Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
- Configuring the agent for Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
- Configuration concepts for the Hitachi TrueCopy/Hewlett-Packard XP Continuous Access agent
- Testing VCS disaster recovery support with Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
- How VCS recovers from various disasters in an HA/DR setup with Hitachi TrueCopy/Hewlett-Packard XP Continuous Access
- Setting up fire drill
About cluster heartbeats
In a replicated data cluster, ensure robust heartbeating by using dual, dedicated networks over which the Low Latency Transport (LLT) runs. Additionally, you can configure a low-priority heartbeat across public networks.
In a global cluster, VCS sends ICMP pings over the public network between the two sites for network heartbeating. To minimize the risk of split-brain, VCS sends ICMP pings to highly available IP addresses. VCS global clusters also notify the administrators when the sites cannot communicate.
Hitachi TrueCopy/HP-XP arrays do not support a native heartbeating mechanism between the arrays. The arrays send a support message on detecting replication link failure. You can take appropriate action to recover from the failure and to keep the devices in a synchronized state. The TrueCopy/HP-XP-CA agent supports those actions that can automate the resynchronization of devices after a replication link outage is corrected.