After upgrading to 9.11.1p8 my snap-diff integration with my Backup vendor (Rubrik) has stopped working. From the documentation, snap-diff v3 was implemented on 9.10 and v1/2 was removed. Since then (I assume after lots of complaining) it was added back in. I am still unable to get my backup to work with snap-diff. I have tickets open with support at both Netapp and Rubrik, but we have not been able to identify the problem. Does anyone have any insights into this issue?
#Help with Snap-Diff issues.
idle kite
wooden relic
re-enabling SnapDiff v1/v2 is a very convoluted process and involves both NetApp and the backup vendor exchanging and signing different forms and contracts before you are given the magic option to re-enable SnapDiff v1/v2. It seems strange that NetApp support is unable to identify the problem because this is apparently a well-documented process on their side
idle kite
according to the netapp KB's the protocol was added back in 9.11.1P7 and newer (I am running P8). But it doesn't seem to work. Rubrik just adds the Netapp with the svm backup user account and then discovers. I have not changed anything but the OnTap version (went from 9.9 to 9.11.1p8) so nothing should have changed.
wooden relic
yes it was added back but it must be enabled, it's not on by default
also, I know that at least in CommVault and Veeam you also need to enable a special flag in the software to be able to use it, I don't know if that's the same for Rubrik
I could send you the option to toggle it but I'm pretty sure I would be getting into legal trouble, as the document that describes it has large "strictly confidential" and "for customer XYZ only" background prints on it (yes, they made a separate PDF for every customer who wants this feature enabled)
seriously, I have seen a lot of "NetApp confidential" things before (NDA presentations, internal documents, etc.) but the wording on these SnapDiff documents makes them look like top secret CIA stuff in comparison 😄
idle kite
thanks, I will push this to my sales team. I have been waiting since Friday for someone at support to get a zoom call up and running on this P2 case.
what miff's me is if going from 9.9 (supported snapdiff) to 9.11.1p8 (supported snapdiff) causes that flag to turn off, WHY is it not in the release notes. 😉
idle kite
is there an internal document I can tell the engineer to look at?
quaint basin
::> set adv
::> vserver snapdiff-rpc-server on -vserver <svm_name>
::> vserver snapdiff-rpc-server-show
what is the output of that?
also what's your case number?
supple siren
Case 2009652680
idle kite
Hey Alex, the option to enable v2 is on for all the vservers I am backing up. note that last command is incorrect in the documentation (I assume you are reading from) the command is "vserver snapdiff-rpc-server show". Please note, this all was working prior to the 9.11.1p8 upgrade. From the Rubrik side, the config is showing that snapdiff is no longer enabled in the config. This is for both the existing host entries as well as a any new ones I add.
low laurel
@idle kite @quaint basin @wooden relic @supple siren or whoever knows,
Here is what it said in Upgrade Advisor:
SnapDiff Support in ONTAP If you use a third party backup utility that uses SnapDiff v1 or v2 APIs, be aware that it will not function after this upgrade. Please refer to CPC-00352 and SnapDiff Support in ONTAP for details, and work with your backup vendor to ensure you will not be impacted after upgrade.
We are planning to upgrade 9.9.1p16 to 9.11.1p16,
What is exactly re-enabling SnapDiff v1/v2 process? By following the process, will SnapDiff work then?
We are using SnapDiff v2 ZAPI a lot
idle kite
@low laurel First, there is no 9.11.1p16, I think 11 is the latest. If I understand this correctly, if you go from 9.9 to 9.11 and skip 9.10, you do not have to do anything to continue using snapdiff v2. It was added back in a version of 9.10 and is still in 9.11.
WIth regards to the backups, it ultimately turned out when I upgraded my backup software version is when things broke. I had to jump through hoops with both the backup vendor and Netapp to get a Variance approved. I then had to get the backup vendor to re-enable it and re-add support to every share. I am very very unhappy with how this was handled by both companies (and I have made my opinion known).
One thing to be clear on Snapdiff V3 is NOT an enhanced version of V2. It's a total replacement and deprication of function that no longer exist for backup users to use unless you use a Netapp compatible "snap target". This is not something I want or will support, so we won't be upgrading Ontap until there is a better solution to the problem.
To define what I think my backup vendor is using, they use snap diff to get a list of files that changed since the last snapshot and then use that list to do a CIFS/NFS based file scan and backup. They DO NOT want nor use snapmirror. If this functionality "is" in V3 then great. Can someone please provide me with the API call that can be made that is equal to the V2 call?
I recommend if your backup vendor says they can not support later ontap versions, you talk to your SE at netapp and talk to them about variences and approvals.