Example 4 - Failing back to the original Primary using difference-based synchronization in a multiple Secondaries setup

This example shows how to fail back to the original Primary seattle using the difference-based synchronization feature, in an RDS with multiple Secondaries.

To fail back to the original Primary using difference-based synchronization in a setup with multiple Secondaries

  1. Fail back to the original Primary using difference-based synchronization as usual except do not restart the application on the original Primary yet.

    See Example 3 - Failing back to the original Primary using difference-based synchronization.

  2. On the original Primary seattle:

    • Synchronize the data volumes in the Secondary RVG hr_rvg on tokyo with the data volumes in the original Primary RVG hr_rvg using the difference-based synchronization and checkpoint. To do this, use the following command on any host in the RDS:

      # vradmin -g hrdg -c checkpt syncrvg hr_rvg tokyo

      The -c option when used with the vradmin syncrvg command automatically starts a checkpoint with the specified name, checkpt, in this example. After the data volumes are synchronized, the checkpoint is ended.

    • Start replication from seattle to tokyo using the command:

      # vradmin -g hrdg -c checkpt startrep hr_rvg tokyo
  3. Restart the application on the original Primary seattle. Because the application was stopped properly before the migration, an application recovery is not required.