After upgrading our main and one of the snapmirror destinations to 9.14.1 the snapmirror relationships are no longer found by the snapcenter hosts (after the SMCore service had been restarted).
We have had this issue with other customes and fix it with adding this "<add key="IsRestEnabledForStorageConnection" value="false" />" to the smcore.config file on the SnapCenter server and the host. But for whetever reason it does not work 100%... We have two snapmirror destinations.. one is running ONTAP 9.11 (and works) the other is running 9.14.1 as well if the source storage system... The newer snapmirror destination system isn't updated by SnapCenter as the backup job runs... and it doesn't even report an error or warning about it... kinda scary behaviour right there... has anyone run into this issue, and managed to fix it?
#SnapCenter issues after ONTAP upgrade...
tight gate
tight gate
Update... apparently SnapCenter version 5.0 has some quite nasty bugs in it which are solved in 5.0P1... We got hit with the MySQL database corrupting (fixed this by a very slow dump and restore) then we noticed the above issue where only one of the snapmirror relationships was updated, which is also a known issue when the destination volume has the same name across destination clusters...