#SMas volumes does not have the same snapshots?

1 messages · Page 1 of 1 (latest)

gaunt ibex
#

Hi there... I setup a SMas setup for month ago, and by chance I can see that the "destination system has more older snapshots than the source volumes... and when I try to delete them from the destination, I am of cause denied because it's a snapmirror sync relationship.... is this normal?

Also today the customer started some load on the system (svmotion from one datastore to another (inside the SMas datastores) which seems to have "kicked" one of the datastore volume out of sync, and is it now running a "normal" resync.. which seems to take quite awhile to complete... Systems are two C800 HA's connected with two 40Gb links would it be that the links got saturated by the svmotion and dropped one of the datastores, or is this not supossed to happen? ... we are on ONTAP 9.16.1P7 which I think have some issues in this regard?

summer echo
gaunt ibex
# summer echo Probably unrelated, but have you see the bulletin about that release and SMas? h...

Yeah that's the one I think we have hit while updating to 9.16.1P7 som time ago... (maybe) anyway I vcan see that it should be fixed in 9.16.1P8 so the question is, if it's just to give it a go and upgrade, or ask support for their assistance? Seems like they have some kind of workaround... I will try to give then a yell tomorrow... but still don't link the fact that the snapshot count are now the same on source/destination...

summer echo
#

Upgrading does not fix the problem if you've already on an impacted release. So if you haven't already I'd have Support review your config to check if you need to use the workaround or not.

gaunt ibex
#

We had a supporter help us fix the database to reflect the correct number of CG members... so the issue in 9.16.1P7 should not be a "problem"... yet we would like to update soon to 9.16.1P8... also the older snapshots on the destination have been deleted as they didn't have any relation to the active snapmirror relations...