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

I have snapcenter plug-in for VMware and the underlying protocol is FC for the storage connectivity. 

I want to retain more snapcenter snapshots at the secondary storage and hence planning to use “mirror-vault” policy for SM relation and update snapvault after back up option in plugin. 

To restore a VM from vault backup what is the connectivity requirement from secondary storage to snapcenter plugin/vcenter/host. Do I need any fc connectivity as primary is based on FC protocol ?

Hello,

Can I achieve the following retention plan for my VM datastores, where the primary (AFF) only keeps 7 daily snapshots, secondary (FAS) keeps 30 daily snapshots and tertiary (FAS remote) keeps 60 daily snapshots? The only tool (apart from ONTAP 9.11) is SnapCenter plugin for VMware vSphere. My concern is that SCV backup policy will only tag snapshots if it's configured to initiate SnapVault to secondary after backup and the policy also defines the number of snapshots to keep. Does this number refers to the local snapshots, remote (secondary) snapshots or both?

Hello,

for increasing inodes I use the following command: volume modify <volume_name> -files <number_of_files>

On a Data Protection Volume (Snapvault Destination) I get the following error when using this command:

Error: command failed: Modification of the following fields: files not allowed
for volumes of the type "Flexible Volume - DP read-only volume".

Is there another way to increase inodes on these volumes?

Regards,

Christian

Hello All,

We have got 15 new NetApp Arrays under our managed services. We want to start billing for NAS so as to bring the loading revenue.  How to go about this.  What are the steps and models available.  Please suggest.

Thank You.

Hello,

setting as below, but SnapVault did not auto delete old snapshot refer retention count

- primary storage vol1 with LUN did not setup snapshot schedule copy

- SnapCenter create Policy hourly and "Total Snapshot copies to keep" 3, Secondary policy label Select Customer Label "hourly", select "Update SnapVault after creating a local Snapshot copy"
- SnapCenter create Windows host Resource Group, select "Use custom name format for Snapshot copy" $Policy
- secondary storage create Protection policy name svtest with Asyn Vault, SnapMirror label "hourly" and Destination Retention Count 3
- seconday storage create volume relationship, Relationship Type Vault, Vault Policy select svtest, Schedule None
- SnapCenter primary snapshot backup and snapshot transfer to secondary successful

but secondary storage did not keep retention to 3, it did not auto delete old backup snapshot, is normal? How can setup auto delete the old backup snapshot?

Best regards,

Chung

Hi to all

The customer has a old filer, with snapvault destination volumes and aggrs inside that.They bought a new controller with new disks.We will ,first configure the new filer for future snapvault destinatinon.Then they want us to connect the old filers shelves to the new controller.

My question is about the snapvault volumes, they have been in place for the last 5 years, and lots of data inside them.

If we connect the old shelves to new filer, and assign the disks to this new filer, do we have the old structure of aggrs and volumes with snapshots?.Or do we loose snapshots or something else,

In my opinion, all the aggr, volume and snapshots must retain ,but i havent tried something like that.

what is your opinion?

regards

When we were running 9.7 we were able to create SnapVault/Mirror relationships in System Manager from the source cluster by selecting a volume and clicking the "Protect" button.

We upgraded to OnTap 9.8P1 and we can still click on a volume, click Protect, and then create the relationship however if we click on the "More Options" button in the dialog to change the settings associated with the relationship, the options page comes up but there is a rotating spinner that never goes away so we can't specify any of the other options.  Has anyone else seen this?

Hi all,

I have two 2520 in two seperate locations. They both are running 8.3.2.
In 7-mode I created several setups with a small number of snapshots on the primary and a larger number on the snapvault side.

I am trying to recreate this in C-mode.

So I have one volume on SAS disks on the primary.

I created a schedule for hourly, daily and a few weekly snapshots. I labeled them hourly, daily and weekly.

I can create a snapvault policy using these labels and assign a different (longer) retention.

Now, here is my question, Can I also create monthly and even yearly backups on the snapvault side?

I do not have the space on the primary to keep monthly and yearly backups.

Retention overview:

Primary: 48 hourly; 7 daily; 2 weekly

Snapvault: 14 daily; 8 weekly; 6 monthly; 2 yearly

Thanks for your thoughts and answers!

Regards,

Martijn

Dear Community,

does somebody know a usefull Process to migrate existing Snapvault realationships from a old enviroment to a new enivroment, is it possible to bypass a new intial Copy?

Old:

9.1 4 Node + 2 Node Backup

NEW

9.3 4 Node + 2 Node Backup

Regards

Fabian

Recently during the nightly Snapvault I have been receiving the following error: Transfer failed. (Out of memory).

I have searched here and on the internet, there doesn't seem to be an answer. I have 5 other vaults that have no issue. 

I am running OnTap 9.2 on a FAS 2554. Any help would be appriciated. 

Hi All, I have problem refer SnapVault restore as below:

- SiteA OnTap 9.7 vserver svm1 volume vol1 SnapMirror to SiteB OnTap 9.7 vserver sm1 volume vol1_mirror

- SiteB OnTap 9.7 cluster cmode97sm vserver sm1 volume vol1_mirror SnapVault to SiteC OnTap 9.3 vserver svmdrd2d volume vol1_mirror_vault

- all SnapMirror and SnapVault replication successful and healthy

When SiteC cluster drd2d relationship select restore from Destination: drd2d://svmdrd2d/vol1_mirror_vault to Source cmode97sm://sm1/vol1_mirror with Latest Snapshot copy:snapmirror.xxxxxxxxxxx, it was display "Data ONTAP API Failed: Relationship with destination sm1:vol1_mirror already exists. (Error: 17122)".

I try select another Snapshot restore and it was display same error, I try use command line and it was same problem

I try break the SiteB Snapmirror and let the SiteB vserver sm1 volume vol1_mirror change from DP to RW, and try SiteC restore to SiteB and it was same error

But I try SiteC restore to SiteB other volume and it was successful

Is SnapVault did not allow restore to original Source volume in this setup?

Hi All

Just a quick question about removing snapmirrored/vaulted volumes as I have had an issue in the past and just wanted to confirm the correct steps to be taken.

The previous issue I had was related to deleting a snapvault relationship after clearing an old relationship. This relationship sat on our destination filer and vaults from a snapmirror relationship which is also replicated to this filer. It had originally removed from view but reappeared. When trying to release the relationship I was getting a message saying "no releaseable destination found that matches those parameters".

We have 2 NetApp filers at 2 separate sites, snapmirror occurs on the volumes from Site A to Site B, on Site B we then use SnapVault to a separate volume for retention backups. We are using 7-mode 8.2.3P3 on both filers.

I normally follow the below steps when removing volumes. All of our volumes are fibre channels LUNs presented to VMware for serving datastores to our virtual machines.

1. Perform VMware tasks such as unmounting and deleting the datastores in the vSphere web client
2. Break snapmirror relationship for volume being decommissioned by doing a quiesce followed by a break, I normally do this from the source filer. Check relationship is removed from view in Production and DR filers using On command system manager.
3. On Source NetApp filer, go to LUNs, and offline the LUN in question, followed by deletion of LUN.
4. On source NetApp filer, go to volumes, offline the volume and then delete the volume.
5. On destination filer remove any schedules for the snapvault relationship to be removed.
6. On destination filer stop the related snapvault relationship, followed by release.
7. Once snapvault relationship deleted, remove snapvault source and destination volume once sufficient snaps have built up by offline LUN, delete LUN, offline volume and delete volume.

Any steps I have missed of any advice if there is a better way to do this would be much appreciated.

Many Thanks in advance for your help.

Hello,

We are on cdot 9.3 and are looking to possibly convert some of our SnapMirror jobs to Mirror + Vault jobs. Can they be easily converted? Just to clarify, I'm not referring to converting DP to XDP. These jobs are already XDP. I'm talking about taking XDP SnapMirror jobs and converting them to Mirror + Vault. Only purpose would be to possibly archive some of the snapshots longer than we currently do. I would still want to be able to activate the destination volumes in a disaster. Thanks in advance for your help!