#Snaplock Behaviour

1 messages · Page 1 of 1 (latest)

slender spoke
#

Hi All, Need some help in understanding Snaplock behaviour:

  1. Can we create a Flexclone from a destination volume (Vault in Compliance Mode) without breaking anything ?

  2. Can snaplock destination volumes be again replicated/cascaded to another NetAp system if we want to change the hardware ?

  3. What is the effect/behavior on space efficiency between source and destination (snaplock compliance using snapvault) ?

  4. Can we just go ahead and increase the retention period again for a destination volume once the period is over ?

onyx compass
#
  1. Yes, beginning with ONTAP 9.13.1 you can create a clone with another snaplock-type than the parent-volume. So you could create a non-snaplock clone and then delete it afterwards. (https://docs.netapp.com/us-en/ontap/volumes/create-flexclone-task.html#create-a-flexclone-of-any-snaplock-type)
  2. Yes, but the destination volume needs to have the same snaplock-type like the source-volumes. So all three volumes in your cascade would need to be of type snaplock-compliance for example.
  3. Efficiency features are supported on SnapLock volumes (since ONTAP 9.9.1), so I don't think there is any difference if you replicate a non-snaplock volume compared to a snaplock-volume.
  4. I did not try it but yes that should be possible with volume snapshot modify-snaplock-expiry-time (https://docs.netapp.com/us-en/ontap-cli-9161/volume-snapshot-modify-snaplock-expiry-time.html)