Since years NetApp has the two different data protection mechanisms SnapMirror and SnapVault. SnapMirror is used to mirror the state of the volume to a secondary volume including all SnapShots and can be used to be a disaster recovery solution. SnapVault is used to build up a data protection (backup) solution based on SnapShots. With SnapVault you can define different numbers of SnapShots for primary and secondary volume. You can e.g. save 10 SnapShots on your production for instant recovery, primary volume and keep 200 SnapShots on you secondary volume for long-term retention.
With Data ONTAP 8.3 NetApp has extended the data protection relationships (type XDP) support by two more use cases, mirroring and mirror-vault. Mirror-Vault can be used to have one data protection relation for both, backup (SnapVault) and disaster recovery (SnapMirror). In previous versions you only had one data protection (type DP) relationship for async-mirror (SnapMirror) and one extended data protection relationship (type XDP) for SnapVault. The table below explains the current available types of data protection policies and their related results. The new flexible version SnapMirror is part of XDP as well.
As you can see, NetApp integrated the two new type into the XDP type. Veeam supports all four different types of data protection policies and relation types.
If you want to use any kind of secondary integration, you simply have to choose in our job settings.
Depending on your SnapMirror policy type you now have to select different options to get the update to a secondary ONTAP running.
Standard SnapMirror relation (async-mirror, DP)
To get a standard SnapMirror relation working you have to choose “Configure secondary destination for this job” in your Veeam Job in the section “Storage”.
Version Flexible SnapMirror (async-mirror, XDP)
To get a version flexible SnapMirror relation working you have to choose “Configure secondary destination for this job” in your Veeam Job in the section “Storage”.
As the version flexible SnapMirror is relation type is XDP Veeam recognizes them as a SnapVault relation. That means that you have to select “NetApp SnapVault” under “Add” in the “Secondary Target” window.
In the appearing window you can leave everything on default. As it is a mirror the number of SnapShot copies for secondary does not have any effect. The number of SnapShots that will be saved on the secondary volume is depending on what you’ve entered in the Job setting “Storage” section under “Restore points to keep on disks”.
Mirror and Vault combined (MirrorAndVault, XDP)
To get a version combined SnapMirror/SnapVault (mirror-vault) relation working you have to choose “Configure secondary destination for this job” in your Veeam Job in the section “Storage”.