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 volume...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.