Table of ContentsView in Frames

Comparison between qtree SnapMirror and SnapVault

There are several similarities between qtree SnapMirror and SnapVault. However, there are differences in how they are used.

The following table compares qtree SnapMirror with SnapVault:
Qtree SnapMirror SnapVault
More suitable for providing immediate failover capability. More suitable where data availability is less critical, and immediate failover is not required.
Uses the same functionality and licensing on the source and destination systems. Uses SnapVault source system and SnapVault destination system, which provide different functionality.
Transfers can be scheduled at a maximum rate of once every minute. Transfers can be scheduled at a maximum rate of once every hour.
Every qtree within a source volume uses one Snapshot copy each on the source system. Only one Snapshot copy is used.
Snapshot copies are deleted by qtree SnapMirror when not required for replication. Snapshot copies are retained and deleted on a specified schedule.
Relationships can be reversed. This allows the source to be resynchronized with changes made at the destination. Relationships cannot be reversed. It provides the capability to transfer data from the destination to the source only to restore data. The direction of replication cannot be reversed.
Can be used to replicate data between systems running Data ONTAP only. Can be used to back up both NetApp systems and open systems. However, the destination system should be a NetApp system.