Hello, have an old FAS3250 running ONTAP 9.1P20 - both of these (HW and ONTAP) are long past any support. It was used for secondary backups using SnapMirror (XDP, Async) from the primary system running newer ONTAP (started with 9.8 and was updated over the years to 9.13.1P7). Few days ago I have updated the primary system to 9.14.1P2 and since then the SnapMirror does not work. I cannot update the existing relationships and cannot initialize new ones. The error is reported on the 9.1 system smc.snapmir.update.fail: Snapmirror update from source volume 'xxx' to destination volume 'yyy' failed with error 'Failed to create Snapshot copy snapmirror.zzz.2024-04-21_090500 on volume xxx.(Failed to start operation on source.)'. Relationship UUID 'zzz'. There is no error on the 9.14 system (nothing in the event log, did not find anything in the other logs (maybe not looking properly). Weird thing is the "snapmirror list-destinations" on the 9.14 does not return anything (the old snapmirror snapshots exists in the volumes). The cluster and vserver peer relationships seems OK (available, healthy). I can replicate from the 9.14 system to another system with ONTAP 9.13.1P7 (tried just for the test). Found KB article and documentation page that states this is no longer supported (since a long time) - but according to that information it should not work even before. https://kb.netapp.com/onprem/ontap/dp/SnapMirror/How_to_check_SnapMirror_compatibility_between_ONTAP_versions https://docs.netapp.com/us-en/ontap/data-protection/compatible-ontap-versions-snapmirror-concept.html Funny thing is all the relationships (even between 9.14 and 9.13) state Relationship Capability: 8.2 and above Does anybody know what changed in 9.14 and if there is any workaround? (reverting the system to 9.13 would be really painful). Thanks Harry
... View more
Hi all, I was wondering, is there a possibility that snapcenter allows you to create a clone residing on another vserver? We have a mixed fc/iscsi environment. I think it would be nice if i could clone db's from the fc vserver to the iscsi vserver. Currently i use a powershell script to realize this as powershell has an option to change the destination vserver. The snapshots for the clones are restapi triggered. But, with lifecycle management in mind i would prefer the option complete in snapcenter itself.
... View more
I'm using Snapcenter 4.7 and 5.0 and the REST API. I'm looking to build a front end Web app to show clone details (and other things). Where can I find a schema reference for the JSON/XML returned by the APIs?
... View more
I'm using Snapcenter 4.7 production instance and looking to test upgrade to 5.0. The problem is I need the workloads/config of prod (clones etc.) to do a real test so I have attempted taking a backup of 4.6 and restoreing to a new server with the same name but in a different domain. I cannot restore to the same domain as this would impact produciton. After manipulating some of the XML files and folder name sof the backup I managed ot do the restore but now I cannot logon. I'm assuming this is because all the roles on the prod instance are targted at ADDS users/groups in the prod domain and my restore is to a member server in my test domain. Q: is there anyway to reset the access?
... View more
Hello, I am testing the snapshot copy locking feature. We're on OnTAP 9.12.1P11 and SnapCenter 5. Here is my understanding of limits I've discovered during testing thus far. Can someone verify whether my analysis is correct and/or provide insights into these issues? I'm starting to think this might only be a viable solution for the VMware plug-in. CIFS - you cannot restore an entire volume to an earlier snapshot unless it's the most recent locked snapshot copy. Of course you can restore individual files still via the hidden snapshot directory. SnapCenter Plug-In for SQL - any snapshot (locked or not) can be restored from, but the restore method is always single-file restore and can't be a full volume restore, unless it's the most recent locked snapshot. Best practice is to have very large databases on their own volume so the entire volume can be quickly restored, but this wouldn't be doable on anything but the latest locked snapshot. Restoring from any other snapshot would result in a lengthy outage. SnapCenter Plug-In for Windows - similar to SQL, I believe this would never be a full volume restore unless it's the most recent locked snapshot. If the volume contained significant amounts of data and we needed to restore from an older snapshot, this could cause a very large outage. SnapCenter Plug-In for VMware - I believe functionality is 100% the same with locked snapshots. Restoring a full VM creates a clone behind the scenes that is mounted, with the existing VM powered off and the backed up copy powered on and migrated, followed by unmounting the backup. You could mount a whole datastore snapshot if needed, detach the old datastore and attach the new, turning the snapshot into a separate cloned volume. Same process.
... View more
