Protecting SnapVault secondaries using volume SnapMirror

How SnapMirror protects SnapVault secondaries

Volume SnapMirror protects SnapVault secondaries by creating SnapMirror relationships to migrate data from the volumes on the SnapVault secondary system to volumes on a remote (tertiary) Data ONTAP storage system. SnapMirror provides an exact replica of the SnapVault secondary data on the tertiary system.

Advantage of SnapMirror protection

The advantage of protecting SnapVault secondaries using volume SnapMirror is that softlock support enables you to continue SnapVault relationships between the original SnapVault primary system and the tertiary system, without initial baseline transfers.

For example, if your SnapVault secondary system becomes unusable because of a disaster, you can manually redirect your next SnapVault transfers to the tertiary system instead of the unusable secondary system. Your tertiary system becomes the new SnapVault secondary system, and your SnapVault transfers continue, using the latest Snapshot copy common to both the primary and the tertiary systems.

Migrating SnapVault data using volume SnapMirror

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

Step

Action

1
Ensure that you have Open Systems SnapVault baselines of the directory you are migrating.

Example

In this procedure, assume a baseline of the bno:C:\500MB directory was backed up to r200-old:/vol/old_vol/bno_C_500MB.

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

Example

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

Create the new_vol volume.
r200-new> vol create new_vol 3

Mark the new_vol volume restricted.
r200-new> vol restrict new_vol

Transfer the old_vol volume to the new_vol volume.
r200-new> snapmirror initialize -S r200-old:old_vol new_vol

3
Quiesce and break the SnapMirror relationship between the old secondary system and the new secondary system.

Example

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

snapmirror quiesce new_vol
snapmirror break new_vol

4
Check the SnapMirror status and SnapVault status on the new secondary. SnapMirror status should be Broken-off. SnapVault status should be Snapvaulted to the new volume on the new secondary system.

Example

Perform the following steps from r200-new.

snapmirror status

Source             Destination          State

r200-old:old_vol   r200-new:new_vol     Broken-off

snapvault status

Source         Destination                           State

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

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

Example

Perform the following step from r200-new.

snapvault status -c

Snapvault secondary is ON.

6
Add SnapVault configuration information to the registry on 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 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 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
Recreate any schedules used on the old secondary system to the new secondary system and ensure access permissions are in place.

Step	Action
1	Ensure that you have Open Systems SnapVault baselines of the directory you are migrating. Example In this procedure, assume a baseline of the bno:C:\500MB directory was backed up to r200-old:/vol/old_vol/bno_C_500MB.
2	Using SnapMirror, replicate the volume from the present secondary system to a volume on the new secondary system. Example To replicate the old_vol volume from the r200-old secondary system to the new_vol volume on the r200-new secondary system, complete the following steps on the new secondary system (r200-new): Create the new_vol volume. `r200-new> vol create new_vol 3` Mark the new_vol volume restricted. r200-new> vol restrict new_vol Transfer the old_vol volume to the new_vol volume. r200-new> snapmirror initialize -S r200-old:old_vol new_vol
3	Quiesce and break the SnapMirror relationship between the old secondary system and the new secondary system. Example To quiesce and break the SnapMirror relationship between r200-old and r200-new, complete the following steps on r200-new: `snapmirror quiesce new_vol` `snapmirror break new_vol`
4	Check the SnapMirror status and SnapVault status on the new secondary. SnapMirror status should be `Broken-off`. SnapVault status should be `Snapvaulted` to the new volume on the new secondary system. Example Perform the following steps from r200-new. `snapmirror status` Source Destination State r200-old:old_vol r200-new:new_vol Broken-off `snapvault status` Source Destination State bno:C:\500MB r200-new:/vol/new_vol/bno_C_500MB Snapvaulted
5	Confirm that SnapVault configuration information is not present on the new secondary system by using the `snapvault status -c` command. Example Perform the following step from r200-new. snapvault status -c Snapvault secondary is ON.
6	Add SnapVault configuration information to the registry on 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 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 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	Recreate any schedules used on the old secondary system to the new secondary system and ensure access permissions are in place.