Example: Failing back using automatic synchronization
In this example, the Primary host
seattle has restarted after an unexpected failure. After the failure, the Secondary host
london has manually taken over the Primary role. This example shows how to fail back to the original Primary
seattle using automatic synchronization.
To fail back using automatic synchronization
From the tree view, select the name of original Primary host, seattle, which has restarted and whose role you want to convert to Secondary.
Choose Replication > Make Secondary. To use the pop-up menu, right-click the name of the RDS.
In the Make Secondary box, select or enter london in the New Primary box. For detailed instructions, see Converting a Primary to a Secondary.
The Make Secondary task converts the original Primary RVG hr_rvg on seattle to the Secondary RVG of the new Primary
Select the Secondary host name seattle from the tree view.
Choose Replication > Synchronize RVG. For detailed instructions, see Synchronize the Secondary RVG with the Primary RVG.
The Synchronize RVG task synchronizes the data volumes in the RVG hr_rvg on
seattle with the data volumes on the new Primary RVG hr_rvg on
london using automatic synchronization.
Stop the applications on the new Primary london.
Migrate the Primary role from the new Primary host london to the original Primary host seattle using the Migrate wizard (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.