Symantec logo

Updating the Secondary from the bunker

When disaster strikes and the Primary host goes down, the Secondary can be updated using the bunker. as described in this section.

  Note   If the Primary SRL has overflowed for a Secondary, or if the Secondary is inconsistent because it is resynchronizing, you cannot use the corresponding bunker SRL to recover the Secondary. Because the bunker does not have data volumes, it cannot use DCM to track overflows.

VVR commands relating to bunker replication can be issued on any VVR host associated to the RDS, except where indicated. The activatebunker and deactivatebunker commands must be issued on the bunker host.

 To update the Secondary from the bunker

  1. If the bunker is using the STORAGE protocol, import the disk group containing the bunker SRL onto the bunker host and then recover it. Issue the following commands on the bunker host:

    # vxdg -C import hrdg2

    # vxrecover -g hrdg2 -ns

  2. Activate the bunker, by issuing the following command on the bunker host:

    # vradmin -g hrdg2 activatebunker hr_rvg

    This command converts the bunker RVG from receiving mode (Secondary) to replicating mode (Primary).

    You only need to issue the activatebunker command once, even if you are updating multiple Secondaries.

  3. Start replication from the bunker host to the Secondary:

    # vradmin -g hrdg2 -b startrep hr_rvg london

    This command connects the RLINKs that were created when the bunker was added to the RDS and begins replaying the bunker SRL.

    If you have more than one Secondary using this bunker, repeat the vradmin startrep command for each Secondary.

  4. Monitor the status of the replication from bunker to Secondary:

    # vradmin -g hrdg2 repstatus hr_rvg

  5. When the Secondary is up-to-date, stop replication to the Secondary. You can also stop the replication before the replay is finished, for example, if the Primary is restored.

    # vradmin -g hrdg2 stoprep hr_rvg london

  6. After the bunker has been used to do the replay and it is not needed for any more replays, the bunker must be deactivated.

      Note   Deactivate the bunker only after all the replays from the bunker have been stopped.

    To deactivate the bunker, issue the following command on the bunker host:

    # vradmin -g hrdg2 deactivatebunker hr_rvg

    You only need to issue this command once.

The Secondary is now up-to-date and can take over as Primary. For details on the take over process, see Taking over from an original Primary.