Table of ContentsView in Frames

Operations that might affect volume ComplianceClock time

When the source and destination storage systems are running the same or different Data ONTAP versions, operations such as Volume SnapMirror, aggr copy, or vol copy might affect the volume ComplianceClock time.

Source and destination storage system running different Data ONTAP versions

You should be aware of the following points when performing volume SnapMirror, aggr copy or vol copy operations on the source storage system running Data ONTAP 7.3 and the destination storage system running Data ONTAP 8.1:
  • If the source and destination are SnapLock volumes, the destination volume ComplianceClock time is updated as per the source ComplianceClock time.
  • If the source is a non-SnapLock volume or aggregate and destination is a SnapLock volume or aggregate, the destination volume ComplianceClock time is updated as per the source ComplianceClock value when the SnapMirror relationship is broken.

Source and destination storage system running the same Data ONTAP version

You should be aware of the following points when performing Volume SnapMirror or vol copy operations on a source and destination storage system running Data ONTAP 8.1:
  • If the source and the destination is SnapLock volume, the volume ComplianceClock time of the destination volume is updated as per the source volume.
  • If the source is a non-SnapLock volume and the destination is SnapLock volume, the volume ComplianceClock time of the destination volume is re-initialized according to the destination system ComplianceClock.