Failover and failback in an active-passive chained topology

In an active/passive chained replication topology, one HCP system replicates to a second HCP system, which replicates to a third HCP system. For an explanation of this topology, see Active-passive chained replication.

The way you manage failover and failback in an active/passive chained replication topology depends on which system or systems have failed. The links from the first system in the chain to the second system and from the second system to the third system function independently of each other, but order matters when you fail them over or restore and perform data recovery on them.

The following sections outline the steps you need to take to return an active/passive replication chain to normal operation after the failure of any one or two of the systems in the chain. These sections assume a replication topology in which, when all three systems are healthy:

System A replicates to system B on link AB.

Link AB includes HCP tenant T1 and default-namespace directory D1, both of which were originally created on system A.

System B replicates to system C on link BC.

Link BC includes link AB and HCP tenant T2, which was originally created on system B.

T1 and D1 are read-write on system A and read-only on systems B and C.

T2 is read-write on system B and read-only on system C.

The figure below shows this topology.

Trademarks and Legal Disclaimer

© 2017 Hitachi Data Systems Corporation. All rights reserved.