跳转到主内容

MCC SnapLock Compliance 时钟重新初始化失败

Views:
Visibility:
Public
Votes:
0
Category:
snaplock
Specialty:
dp
Last Updated:

适用于

  • ONTAP 9.16.1x
  • SnapLock
  • Metro Cluster (MCC)

问题

SnapLock Compliance Clock 在 Metro Cluster (MCC) 上重新初始化失败,出现以下错误:
Cluster::> compliance-clock initialize -node *  
Warning: You are about to initialize the secure ComplianceClock of the node "cluster-01" to the current value of the node's system clock. ComplianceClock re-initialization requires all nodes in the cluster to be healthy, all volumes are in online state, no volumes are present in the volume recovery queue and there are no SnapLock volumes or volumes with "snapshot-locking-enabled" set to true or S3 buckets with object locking enabled. Ensure that the system time is set correctly before proceeding. The current node's system clock is: Mon Jan  1 12:22:17 CET 2026
Error: command failed on node "cluster-01": ComplianceClock re-initialization failed. ComplianceClock re-initialization requires all nodes in the cluster to be healthy, all volumes are in online state, no volumes are present in the volume recovery queue and there are no SnapLock volumes or volumes with "snapshot-locking-enabled" set to true or S3 buckets with object locking enabled 

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.