Skip to main content

Initializing the ComplianceClock

The SnapLock ComplianceClock ensures against tampering that might alter the retention period for WORM files. You must initialize the system ComplianceClock on each node that hosts a SnapLock aggregate. Once you initialize the ComplianceClock on a node, you cannot initialize it again.

Before you begin

  • You must be a cluster administrator to perform this task.

  • The SnapLock license must be installed on the node.

About this task

The time on the system ComplianceClock is inherited by the volume ComplianceClock, which controls the retention period for WORM files on the volume. The volume ComplianceClock is initialized automatically when you create a new SnapLock volume.

Important
The initial setting of the ComplianceClock is based on the current system clock. For that reason, you should verify that the system time and time zone are correct before initializing the ComplianceClock. Once you initialize the ComplianceClock on a node, you cannot initialize it again.
  1. Initialize the system ComplianceClock: snaplock compliance-clock initialize -node node_name

    Example

    The following command initializes the system ComplianceClock on node1 :

    cluster1::> snaplock compliance-clock initialize -node node1
  2. When prompted, confirm that the system clock is correct and that you want to initialize the ComplianceClock:

    Example

    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: Mon Apr 25 06:04:10 GMT 2020

    Do you want to continue? (y|n): y

  3. Repeat this procedure for each node that hosts a SnapLock aggregate.