Table of ContentsView in Frames

Re-creating the SnapVault relationship

You can re-create the SnapVault relationship from the primary system to the tertiary system.

About this task

The original configuration in the following procedure is a SnapVault relationship between systemA:/vol/vol1/qtree3 and systemB:/vol/vol2/qtree3 with the SnapVault destination volume systemB:vol2 backed up to another volume on a third system, systemC:vol3.

Steps

  1. Break the volume SnapMirror relationship to the volume on the new secondary system (systemC) to make it writable.
    Example
    Perform the following steps from systemC.snapmirror quiesce vol3 snapmirror break vol3
  2. Check the status of the SnapMirror relationship on the new secondary system (systemC), by using the snapmirror status command.
    The SnapMirror relationship should be broken-off.
  3. Check the status of the SnapVault relationship on the new secondary system (systemC).
    Example
    snapvault status
    The SnapVault relationship should be snapvaulted.
  4. Add SnapVault configuration information to the new secondary system using the snapvault start command.
    Note: This does not start a new baseline, it updates the registry.
    Example
    Perform the following step from systemC (the new secondary system).snapvault start -S systemA:/vol/vol1/qtree3 systemC:/vol/vol3/qtree3
  5. Check that the new SnapVault configuration is present.
    Example
    Perform the following step from systemC.snapvault status -c
  6. Test the new SnapVault relationship by manually updating systemC.
    Example
    Perform the following step from systemC.snapvault update systemC:/vol/vol3/qtree3
  7. Re-create any schedules used on the old secondary system on the new secondary system, and ensure access permissions are in place.
  8. Release resources locked on systemA for the removed systemA to systemB SnapVault relationship.
    Example
    Perform the following step from systemA.snapvault release /vol/vol1/qtree3 systemB:/vol/vol2/qtree3