Restoring the primary host

After a disaster, if the original primary becomes available again, you may want to revert the role of the Primary back to this host.

To restore the primary host

  1. Depending on whether you performed Takeover with or without the fast-failback option, do one of the following:
    • For Takeover with the Fast-failback option:

      The original primary, after it has recovered, will be in the Acting as secondary state. If the original Primary is not in the Acting as secondary state, verify whether your network connection has been restored.

      To synchronize this original Primary and the new Primary, use the Resynchronize Secondaries option from new Primary's context menu.

    • For Takeover without the Fast-failback option:

      After performing a takeover without fast-failback, you must convert the original Primary to a Secondary by using the Make Secondary option.


      Before performing the Make Secondary operation, the original Primary's RVG and the new Primary's RVG will be shown in separate RDSs. However, after this operation, they will be merged under a single RDS.

      After the Make Secondary operation, the original primary will be converted to a secondary. Right-click on this Secondary RVG and select Start Replication with the Synchronize Automatically option.

  2. Take the application resource offline and stop the application.

    After the sychronization is complete, perform a migrate operation to transfer the primary role back to the original Primary. To do this, right-click on the Primary RVG and select Migrate from the menu that appears.

  3. Make sure that the volumes have retained the same drive letters as they had before the disaster.
  4. Bring the application group online on the original Primary.