Re: What is snap vault?what is the difference between Snap mirror and snap vault?

prabuvediappa · ‎2009-10-27

What is snap vault?what is the difference between Snap mirror and snap vault?

yong_fuk86 · ‎2009-10-27

From my knowledge. snapvault is actually a snapshot but not in the box or controller, but outside the box. so you need 2 n series to do snapvault. the diffrence between snapvault and snapmirror is almost the same both using snapshot technology, but snapmirror is replication from primary controller and secondary controller and snap mirror use the snap update to compare the snapshot between secondary and the primaryif there are any changes at the block then snapmirror will update the snapshot at the secondary site. and snapvault is actually the same with snapshot but the location where the snapshot was taken is at the secondary controller.

i hope it answer your question, sorry for my messy english, and just CMIIW

damaru · ‎2009-10-27

short answer:

snapmirror is a DR application whereas snapvault is a backup application.

long answer:

When you setup snapmirror schedule, snapmirror creates a (incremental) snapshot on the primary as part of the update and mirrors it to the secondary. This incremental snapshot becomes the base snapshot for the next update. The data being updated is always the delta between the base and the incremental. This way, snapmirror ends up replicating only the data that is changed beteween base and incremental snapshots. At the end of every update, the old base snapshot is removed on both primary and secondary and new incremental snapshot is marked as the base of next update. So, alwayes a snapmirror relationship retains one snapshot as the base of next update.

SnapVault uses the same engine as qtree snapmirror to replicate snapshot data. But there are some key differences.

- You need an independent snapshot schedule on the primary. snapshots are not takes as part of snapvailt update.

- snapvault snapshot schedules are per volume unlke snapmirror schedules which were per relationship

When the snpavault schedule on the secondary kicks in, it initiates an update to *every* qtree on the secondary volume. The primary of all those qtrees can come from different volumes/storage controllers etc. Once all qtrees are updated, snapvault will create one archive snapshot for the volume and keeps this snapshot till the retention count specifed in the schedule is reached. Hence snapvault will keep retention count number of snapshots in the volume - unlike snapmirror which keeps only one. This way, with snapvault, you can theoretically have more than 256 number of relationships per volume.

hth,

Damaru

RAVI_PALADUGU · ‎2013-05-13

http://hippodata.blogspot.com/2013/05/snapvault-data-archiving-solution.html?q=vault

BALAJI_VENKATRAMAN · ‎2013-09-04

In Simple words

Snapmirror ==> Replication technology used for setting up a DR solution for a source volume/filer.Also it is the best tool for performing Data Migrations from one Netapp filer to another.

Snapvault ==> Backup Technology used for taking backup of source and has "retention period " attached to it..which means you can maintain multiple snapshots on the source.

Balaji

AaronLim · ‎2016-05-10

can we used the destination snap mirror copy as the baseline for the SnapVault? thus, save space required on the destination array?

aborzenkov · ‎2016-05-10

If the question is whether you can use the same volume both as snapmirror and snap vault destination at the same time - no, you can not. You can use different qtrees on the same volume for QSM and SV, but this won't achieve space savings you mean.

TechopsVendor · ‎2019-01-30

setting up my first cdot snapvault trying to add rules to my snapmirror policy for snapvault but dont understand this

says i need at least 1 rule without a schedule but wont let me create one ?

nlc1-sys-ash1-cloudsys::> snapmirror policy add-rule -vserver t500_0_fls2 -policy RDB-daily -snapmirror-label ora_daily -keep 14 -prefix sv -schedule nightly-2:30AM

Error: command failed: Policy "RDB-daily" must have at least one rule without a "schedule".

nlc1-sys-ash1-cloudsys::> snapmirror policy add-rule -vserver t500_0_fls2 -policy RDB-daily -snapmirror-label ora_daily -keep 14 -prefix sv

Error: command failed: Field "-schedule" must be specified.

nlc1-sys-ash1-cloudsys::>

TechopsVendor · ‎2019-01-30

setting up my first cdot snapvault trying to add rules to my snapmirror policy for snapvault but dont understand this

says i need at least 1 rule without a schedule but wont let me create one ?

nlc1-sys-ash1-cloudsys::> snapmirror policy add-rule -vserver t500_0_fls2 -policy RDB-daily -snapmirror-label ora_daily -keep 14 -prefix sv -schedule nightly-2:30AM

Error: command failed: Policy "RDB-daily" must have at least one rule without a "schedule".

nlc1-sys-ash1-cloudsys::> snapmirror policy add-rule -vserver t500_0_fls2 -policy RDB-daily -snapmirror-label ora_daily -keep 14 -prefix sv

Error: command failed: Field "-schedule" must be specified.

lc1-sys-ash1-cloudsys::> snapmirror policy show -vserver t500_0_fls2 -policy RDB-daily -instance

Vserver: t500_0_fls2
SnapMirror Policy Name: RDB-daily
SnapMirror Policy Type: vault
Policy Owner: vserver-admin
Tries Limit: 8
Transfer Priority: normal
Ignore accesstime Enabled: false
Transfer Restartability: always
Network Compression Enabled: true
Create Snapshot: false
Comment: -
Total Number of Rules: 0
Total Keep: 0
Rules:
SnapMirror Label Keep Preserve Warn Schedule Prefix
----------------------------- ---- -------- ---- -------- ----------
- - - - - -

nlc1-sys-ash1-cloudsys::>

Ashun

SnapMirror is disaster recovery technology, designed for failover from primary storage to secondary storage at a geographically remote site. SnapVault is archiving technology designed for disk-to-disk Snapshot copy replication for standards compliance and other governance-related purposes.

These objectives account for the different balance each technology strikes between the goals of backup currency and backup retention:

SnapMirror stores only the Snapshot copies that reside in primary storage, because, in the event of a disaster, you need to be able to fail over to the most recent version of primary data you know to be good. Your organization, for example, might mirror hourly copies of production data over a ten-day span. As the failover use case implies, the equipment on the secondary system needs to be equivalent or nearly equivalent to the equipment on the primary system to serve data efficiently from mirrored storage.
SnapVault, in contrast, stores Snapshot copies whether or not they currently reside in primary storage because, in the event of an audit, access to historical data is likely to be as important as access to current data. You might want to keep monthly Snapshot copies of your data over a 20-year span (to comply with government accounting regulations for your business, for example). Since there is no requirement to serve data from secondary storage, you can use slower, less expensive disks on the vault system.

Of course, the different weights SnapMirror and SnapVault give to backup currency and backup retention ultimately derive from the 255-Snapshot copy limit for each volume. Where SnapMirror retains the most recent copies, SnapVault retains the copies taken over the longest period of time.