Skip to main content
NetApp Knowledge Base

CONTAP-812069: SnapLock Compliance Clock reinitialization fails on MetroCluster

Views:
5
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
DP
Last Updated:

Issue

  • On MetroCluster, snaplock compliance-clock initialize / compliance-clock initialize -node * fails even when data volumes are online
  • The error reports that Compliance Clock re-initialization requires all volumes to be online (and the usual SnapLock / snapshot-locking / S3 object-locking checks)
  • After an extended outage, the System Compliance Clock can remain behind wall-clock time and does not catch up automatically
  • Absolute -snaplock-expiry-time retention then lasts longer than wall-clock time by about the Compliance Clock skew

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.