You must initialize the ComplianceClock feature if you want to enforce WORM data retention on SnapLock volumes. If the ComplianceClock is not initialized, you cannot delete the files after their expiry date, even on SnapLock Enterprise volumes.
Ensure that a SnapLock Compliance or SnapLock Enterprise license is installed on the storage system. In addition, ensure that the system time and time zone are set correctly.
Data ONTAP checks the ComplianceClock when determining or enforcing retention periods.
For example, Data ONTAP checks the ComplianceClock when determining whether a file has expired; to enforce the volume's minimum, maximum, or default retention period when committed to the WORM state; or to determine whether a volume’s destroy date has expired and the volume can therefore be destroyed.
*** WARNING: YOU ARE INITIALIZING THE SECURE COMPLIANCE CLOCK *** You are about to initialize the secure Compliance Clock of this system to the current value of the system clock. This procedure can be performed ONLY ONCE on this system so you should ensure that the system time is set correctly before proceeding. The current local system time is: Wed Feb 4 23:38:58 GMT 2007 Is the current local system time correct? y Are you REALLY sure you want initialize the Compliance Clock? y Compliance Clock: Wed Feb 4 23:39:27 GMT 2007