In this example, the Primary host
seattle has restarted after an unexpected failure. After the failure, the Primary role was taken over by the Secondary host london. Each data volume on the Secondary
london has a Data Change Map (DCM) associated with it.
This example explains how to failback when fast failback is enabled on
london by selecting Auto fast failback in the Takeover wizard or when Fast failback was selected.
An application is running on
london and incoming writes are logged to its DCM. This example shows how to fail back to the original Primary seattle using the fast-failback feature.
To fail back to the original Primary using fast failback
The Replay Failback Log task synchronizes the data volumes in the new Secondary RVG hr_rvg on seattle with the data volumes in the new Primary RVG hr_rvg on london using the fast-failback feature. This step is not required if Auto fast failback was selected in the Takeover task when taking over from the original Primary.
londonto the original Primary host
seattleusing the Migrate task (Replication > Migrate). For instructions, see Migrating the Primary role.
Replication from the original Primary
seattle to the original Secondary
london is started by default after the migration is completed.