SnapLock Compliance meets the following requirements needed to enforce WORM data retention:
SnapLock Compliance meets the requirements by using a secure compliance clock. The compliance clock is implemented in software and runs independently of the system clock. Although running independently, the compliance clock tracks the regular system clock and remains very accurate with respect to the system clock.
To initialize the compliance clock, complete the following steps.
Caution
The compliance clock can be initialized only once for the system. You should exercise extreme care when setting the compliance clock to ensure that you set the compliance clock time correctly.
system> date -c initialize
*** WARNING: YOU ARE INITIALIZING THE SECURE COMPLIANCE CLOCK ***
You are about to initialize the secure Compliance Clock of this
system to the current value of the system clock. This procedure
can be performed ONLY ONCE on this system so you should ensure
that the system time is set correctly before proceeding.
The current local system time is: Wed Feb 4 23:38:58 GMT 2004
Is the current local system time correct? y
Are you REALLY sure you want initialize the Compliance Clock? y
Compliance Clock: Wed Feb 4 23:39:27 GMT 2004
To view the compliance clock time, complete the following step.
| 1 |
date -c Exampledate -c Compliance Clock: Wed Feb 4 23:42:39 GMT 2004 |
Copyright © 1994-2005, Network Appliance, Inc. All rights
reserved.
Part No. 210-01081_B0
File: snaploc4.htm
Last updated: 01-Dec-2005 16:36:23