Skip to main content

snaplock compliance-clock initialize

Contributors
Suggest changes
PDFs

Initializes the node ComplianceClock

Availability: This command is available to cluster administrators at the admin privilege level.

Description

` snaplock compliance-clock initialize` command is used to initialize System ComplianceClock from the system clock. User should ensure that the system clock is correct before initializing the System ComplianceClock. System ComplianceClock can be initialized multiple times as long as all nodes in the cluster are 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" parameter set to true or S3 buckets with object locking enabled.

Parameters

-node {<nodename>|local} - Node

Specifies the name of the node on which System ComplianceClock needs to be initialized.

[-force <true>] - Forces Initialization

If you use this parameter, it will suppress the warning message during snaplock compliance-clock initialize operation.

Examples

cluster-1::> snaplock compliance-clock initialize -node node1

Warning: You are about to initialize the secure ComplianceClock of the node
         node1 to the current value of the node's system clock. This
         procedure can be performed only once on a given node, so you should
         ensure that the system time is set correctly before proceeding.
         The current node's system clock is: Wed Nov 26 16:18:30 IST 2014

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

cluster-1::>