Migrating SnapVault data using volume SnapMirror

To migrate a volume that contains SnapVault destination qtrees from one secondary storage system to a tertiary storage system without having to perform a baseline transfer, complete the following steps.

Before You Begin

Steps

1. Using SnapMirror, replicate the volume from the present secondary storage system to a volume on the new secondary storage system.

   Example

   To replicate the old_vol volume from the r200-old secondary storage system to the new_vol volume on the r200-new secondary storage system, complete the following steps on the new secondary storage system (r200-new).

   1. Create the new_vol volume.r200-new> vol create new_vol 3
   2. Mark the new_vol volume restricted.r200-new> vol restrict new_vol
   3. Transfer the old_vol volume to the new_vol volume.r200-new> snapmirror initialize -S r200-old:old_vol new_vol
2. Quiesce and break the SnapMirror relationship between the old secondary storage system and the new secondary storage system.

   Example

   To quiesce and break the SnapMirror relationship between r200-old and r200-new, complete the following steps on r200-new.

   1. snapmirror quiesce new_vol
   2. snapmirror break new_vol
3. Check the SnapMirror status and SnapVault status on the new secondary storage system. SnapMirror status should be Broken-off. SnapVault status should be Snapvaulted to the new volume on the new secondary storage system.

   Example

   Perform the following steps from r200-new.

   1. snapmirror status

      Source             Destination        State
      r200-old:old_vol   r200-new:new_vol   Broken-off

   2. snapvault status

      Source         Destination                         State
      bno:C:\500MB   r200-new:/vol/new_vol/bno_C_500MB   Snapvaulted

4. Confirm that SnapVault configuration information is not present on the new secondary storage system by using the snapvault status -c command.

   Example

   Perform the following step from r200-new. snapvault status -c

   Snapvault secondary is ON.

5. Enable access to the new SnapVault secondary storage system from the SnapVault primary storage system using the options snapvault.access command.

   Example

   Perform the following step from r200-new. options snapvault.access host=r200-old

   Note: When using SnapVault, access needs to be specified on both the primary and secondary storage systems.

6. Add SnapVault configuration information to the registry on the new secondary storage system using the snapvault start command.
   Note: This does not start a new baseline, it updates the registry.

   Example

   Perform the following step from r200-new.snapvault start -S bno:C:\500MB r200-new:/vol/new_vol/bno_C_500MB

   SnapVault configuration for the qtree has been set.
   Qtree /vol/new_vol/bno_C_500MB is already a replica.

7. Confirm that SnapVault configuration information is present on the new secondary storage system using the snapvault status -c command.

   Example

   Perform the following step from r200-new.snapvault status -c

   SnapVault secondary is ON.
   /vol/new_vol/bno_C_500MB source=bno:C:\500MB

8. Test the new SnapVault relationship by manually updating r200-new.

   If you are using the command line to manage your environment, continue to the next step; otherwise, you are finished.

   Example

   Perform the following step from r200-new.snapvault update r200-new:/vol/new_vol/bno_C_500MB

   Transfer started.
   Monitor progress with ‘snapvault status’ or the snapmirror log.

9. Re-create any schedules used on the old secondary storage system to the new secondary storage system and ensure access permissions are in place.