クローンボリュームを作成できませんでした理由：WORMコンプライアンスクロックが実行されていません

最後の更新
PDFとして保存

Views:: 22

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: dp

Last Updated:

環境

ONTAP 9
SnapLock

問題

ボリュームのクローンの作成が次のエラーで失敗します。

volume clone create -flexclone vol_clone -s none -b vol_parent -parent-snapshot snapshot_name

[Job 463945] Job is queued: Create vol_clone

Error: command failed: [Job 463945] Job failed: Failed to create the clone volume on node. Reason: WORM - Compliance clock is not running.

SnapLock Complianceクロックの初期化も次のエラーで失敗しました。

cluster::>snaplock compliance-clock initialize -node node8

Warning: You are about to initialize the secure ComplianceClock of the node "node8" to the current value of the node's system clock. ComplianceClock reinitialization 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: Thu Jan  9 20:46:04 PST 2025

Do you want to continue? {y|n}: y

Error: command failed: 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.

ボリュームクローンの作成が失敗するのは、1つの特定のノードにあるボリュームだけです。