We get a hell of a lot of these errors in the event log of the primary storage system (A300): (ontap 9.12.1) (SnapCenter version 5.0)
5/24/2024 11:31:08 host ERROR smc.snap.upd.retention.fail: The SnapMirror relationship with relationship UUID "e0a30162-4df5-11ec-b7b0-00a098d3fb6c" will not copy the retention period of a Snapshot copy from the source volume "3915ca88-462a-11e3-98a9-123478563412:sqlclu_c02_snapinfo01" to the destination volume "fc314ab7-3e41-11e8-878a-00a098d3fb5e:sqlclu_c02_snapinfo01_mv" because the ONTAP version of the destination cluster does not support copying the retention period.
The SM destination is a FAS2620 with ontap 9.11.1 (which we cannot upgrade to 9.12 because of old hardware) (but the system is still in support)
On the SM destination we have policies in place that catch the SM-labels and apply retention, so not sure why we even get this error? Is there a way to get rid of it?
#ONTAP Errors with "older" ONTAP SM destinations...
mighty widget
fallen dagger
The message is most likely about Tamperproof Snapshots which are only available with 9.12.1.
Looks like you have that feature enabled on the source cluster. So your snapshots might not be protected anymore with SnapLock on the destination cluster.
If everything else works fine I would ignore it. The FAS2620 is EOS next month anyways.
mighty widget
The 2620 might be EOS, but we have it in service for another 2 years (because if a PVR).. it makes no sense to me why this error has to be displayed on the primary system and for every snapmirror update, of which there are many because we do quarterly snapshots of many databases.. it makes the eventlog pretty much useless because it is just filled with these errors... also... it is "really" an error... I would think it should be a note or maybe warning.. but I guess there is no way to filter this out like in the old syslogs ?
radiant cipher
It is an important error because it impacts your security against accidental or deliberate deletion of backups.
And you can filter the event log to exclude these events by using event log show -event !smc.snap.upd.retention.fail so I wouldn't say it makes the event log useless
fallen dagger
You know what Tamperproof Snapshots are and you have them enabled by choice? (https://docs.netapp.com/us-en/ontap/snaplock/snapshot-lock-concept.html)
If not disable them and the errors should be gone.
pliant stag
Maybe ask for a RFE?
mighty widget
I will see if I can find the time to start an RFE...
I forgot that it was possible to add the -event !smc... to filter out lines in the event log... still cannot understand why they don't add features like grep, awk etc.. would make some things a lot faster some for someone like me, who mostly use the cmd-line... but then again, I think it took about 10 years before we got command completion 😉
radiant cipher
I forgot that it was possible to add the -event !smc... to filter out lines in ...
because ngsh is not a POSIX shell. If they added all that stuff in it would probably be a nightmare to maintain and bugfix. Also why bother when the APIs are all there, I mean you can use PowerShell to do even more than what grep and awk can do
mighty widget
because ngsh is not a POSIX shell. If they added all that stuff in it would prob...
well my world is normally via VPNs and SSH Tunnels etc.. to reach the storage system ssh... not always a host there that can do PS or REST and SSL can be locked down as well... 🙂 but that's just "security" for you...
radiant cipher
you can do noninteractive SSH and grep on the client, like ssh admin@1.2.3.4 event log show | grep -v retention.fail
pliant stag
That's a pain...