You can use the dump command to back up data from a SnapMirror destination volume. The dump command picks the most recent Snapshot copy and copies that to tape.
Note: The use of the dump command to copy data from a synchronous SnapMirror destination volume is not supported.
You can back up any Snapshot copy displayed by the snap list command on the destination. You can also create a Snapshot copy on the source volume, copy the Snapshot copy to the destination, and use the dump command to back up this Snapshot copy from the destination to tape.
Effect of the dump command on the SnapMirror destination update schedule
Running the dump command on a SnapMirror destination affects SnapMirror operations on that destination in several ways.
• Scheduled incremental SnapMirror updates of a destination volume can occur concurrently with a dump command operation to tape; however, if a scheduled SnapMirror update to the destination volume involves the deletion of a Snapshot copy that the dump command operation is currently
writing to tape, the SnapMirror update will be delayed until the dump command operation is complete.
Note: SnapMirror updates of a destination qtree are not affected by dump command operations under any circumstances.
• The operation of snapmirror break, snapmirror resync, and snapmirror migrate commands cannot be carried out concurrently with the operation of the dump command.
Protection of SnapVault secondaries using volume SnapMirror
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) system running Data ONTAP. SnapMirror provides an exact replica of the SnapVault secondary data on the tertiary system.
The advantage of protecting SnapVault secondaries using volume SnapMirror is that soft lock support enables you to continue SnapVault relationships between the original SnapVault primary system and the tertiary system, without initial baseline transfers.
Note: To deploy this solution, ensure that you have the appropriate licenses for SnapMirror and SnapVault. You cannot execute SnapVault commands on the new secondary system (which is also a SnapMirror destination) if you do not license sv_ontap_sec on this tertiary system.
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
You can migrate a volume that contains SnapVault destination qtrees from one secondary system to a tertiary system without having to perform a baseline transfer.
Before you begin
Ensure that you have Open Systems SnapVault baselines. For example, in the following procedure, consider a baseline of the bno:C:\500MB directory was backed up to system-old:/vol/
old_vol/bno_C_500MB. Steps
1. 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 system-old secondary system to the new_vol volume on the system-new secondary system, complete the following steps on the new secondary system (system-new).
a. Create the new_vol volume.
system-new> vol create new_vol 3 b. Mark the new_vol volume restricted.
system-new> vol restrict new_vol
c. Transfer the old_vol volume to the new_vol volume.
system-new> snapmirror initialize -S system-old:old_vol new_vol 2. 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 system-old and system-new, complete the following steps on system-new.
a. snapmirror quiesce new_vol b. snapmirror break new_vol
3. Check the SnapMirror status and SnapVault status on the new secondary system. 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 system-new. a. snapmirror status
Source Destination State
system-old:old_vol system-new:new_vol Broken-off b. snapvault status
Source Destination State
bno:C:\500MB system-new:/vol/new_vol/bno_C_500MB Snapvaulted 4. 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 system-new. snapvault status -c
Snapvault secondary is ON.
5. Enable access to the new SnapVault secondary system from the SnapVault primary system using the options snapvault.access command.
Example
Perform the following step from system-new. options snapvault.access host=system-old
Note: When using SnapVault, access needs to be specified on both the primary and secondary systems.
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 system-new.
snapvault start -S bno:C:\500MB system-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 system-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 system-new.
If you are using the CLI to manage your environment, continue to the next step; otherwise, you have completed the task.
Example
Perform the following step from system-new.
snapvault update system-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 system to the new secondary system and ensure access permissions are in place.