Symantec logo

Transferring the role

This section explains how to transfer the Primary role. VVR enables you to transfer the Primary role from a healthy or failed Primary to a Secondary. It also enables you to fail back to the original or failed Primary. For details on transferring the role, see Transferring the Primary role.

Accessing the transfer role menu

 To access Transfer Role

  1. Select Replication Tasks > Transfer Role.

    The following screen displays:

Click the thumbnail above to view full-sized image.

  1. Make your selection from the Transfer Role screen, and then refer to the appropriate section:
Migrating the Primary and Secondary roles

Migration involves transferring the Primary role from a healthy Primary to a Secondary when the application is inactive and the RLINK is up to date.

 To migrate the Primary and Secondary roles

  1. Choose Replication Tasks > Transfer Role > Migrate Primary and Secondary Roles.
  2. Select the RVG from the list.

    After selecting the RVG, the following screen displays:

Click the thumbnail above to view full-sized image.

  1. If the RDS contains multiple Secondary hosts, press F4 to list and select the Secondary host in the Secondary Host entry field. If the RDS contains a single Secondary, the host name displays in the Secondary Host entry field.
  2. To initiate the task, press enter.

    The command status screen displays.

  3. Press F3 until you return to the main menu.
Taking over from a failed Primary

Takeover is an emergency procedure performed when disaster strikes the Primary. Takeover involves transferring the Primary role from a failed Primary to a Secondary.

 To take over from a failed Primary

This task can only be executed on the Secondary host that is to take over the Primary role.

  1. Choose Replication Tasks > Transfer Role > Take Over From Failed Primary.
  2. Select the RVG from the list.

    After selecting the RVG, the following screen displays:

Click the thumbnail above to view full-sized image.

  1. To disable Failback logging, press tab to select no in the Enable Failback Logging entry field; otherwise, keep the default setting to yes.
  2. To automatically synchronize the failed Primary when it becomes available press tab to select yes in the Automatically Synchronize the Failed Primary field; otherwise, keep the default setting to no.

      Note   Automatic synchronization of the failed Primary requires Failback logging to be enabled. If you set step 3 to no, and set step 4 to yes, this is an invalid option, and an error will occur when you press enter to initiate the task.

    To determine the appropriate settings for step 3 and step 4, press F1 to view help.


  1. To initiate this task, press enter. The command status screen displays.
  2. Press F3 until you return to the main menu.
Converting the original or failed Primary to a Secondary

Failback is the process of restoring the original Primary.

 To convert the original or failed Primary to a Secondary

This task can only be executed on the new Primary.

  1. Choose Replication Tasks > Transfer Role > Resynchronize Previous Primary Using Fast Failback Logging.
  2. Select the RVG from the list.

    After selecting the RVG, the following screen displays:

Click the thumbnail above to view full-sized image.

  1. To create a space-optimized snapshot of the old primary's data volumes, select yes. Otherwise, select no and go to step 6 to continue.

Click the thumbnail above to view full-sized image.

  1. To use a pre-existing cache object, select yes. Otherwise, select no.
  2. If you selected yes to use a pre-existing cache object, a screen displays with the Cache-Object Name field. Enter the name of the cache object.

    OR

    If you selected no to use a pre-existing cache object, a screen displays with the Cache Size field. Enter the cache size.

  3. To initiate the task, press enter.

    The command status screen displays.

  4. Press F3 until you return to the main menu.