...and just to make it interresting, the destination has currently NVE enabled... We do remote backup using SnapMirror, and we do not want to have the snapshots explode if a customer enables NVE on their side....
Can someone confirm that the NVE is "transparent" to the data and snapshots in the volume? My guess is that it actually is, because I seem to remember that when we enabled NVE back in the day, we didn't do anything special in the regard of snapshots etc.. Another curveball might be that on the destination we have some snaplock on the snapshots going on as well... 🙂
#Does enabling NVE on a source volume have any negative effect on a SnapMirror relation?
drifting plank
wind hill
the destination is configured separately - FYI - https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/NetApp_Volume_Encryption_NVE_considerations_with_SnapMirror_relationships_and_SnapLock_volumes
If the customer enables Tamper Proof (snaplock) snapshots you will have to re-configure your end and allow for the Compliance clock to be enabled.
drifting plank
OK, the destination snapmirror volumes have snaplock enabled, and they have volume encryption enabled. The source volume does not have any of this enabled. So as I can understand from the KB we need to quiesce the snapmirror relationship, then do a volume encryption, once done we can resume the snapmirror. But it does not state anywhere if this volume encryption has any effect on the existing snapshots? My guess it that is has not (but would like to be sure). Actually the scenario we have is not really described in the KB 🙂 Thankfully we do not yet have snaplock enabled on the source. I am aware that if we do the retention set there will be carried over to the destination, and as far as I remember, you are able to set the retention on the destination, as long as it is longer than the existing one... (correct?)