<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Snaplock Compliance Clock in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Snaplock-Compliance-Clock/m-p/46254#M10859</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Yes, the ComplianceClock is separate from the system clock.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;The only catch here is bounded drift correction (&lt;EM&gt;can only change by one week per year&lt;/EM&gt;) -- so if the system is shut down for a very long period (like a month), it will take several years for the ComplianceClock to catch up to "real" time. This means that if the customer has a disastrous outage, at the end of the retention period, the customer may need to wait slightly longer to delete expired files. However, this is a safe implementation from a compliance perspective, assuring that files under SnapLock protection can never be prematurely deleted.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Read TR-3618 for more details:&amp;nbsp; &lt;A href="http://media.netapp.com/documents/tr-3618.pdf" target="_blank"&gt;http://media.netapp.com/documents/tr-3618.pdf&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;STRONG&gt;Brian&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt; Geek ONTAP: &lt;A href="http://www.netappgeek.com" target="_blank"&gt;www.netappgeek.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Apr 2011 20:35:35 GMT</pubDate>
    <dc:creator>netappgeek</dc:creator>
    <dc:date>2011-04-21T20:35:35Z</dc:date>
    <item>
      <title>Snaplock Compliance Clock</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Snaplock-Compliance-Clock/m-p/46241#M10852</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Straight forward question I can't seem to find an answer to in the blogs here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I have a snaplock compliance volume running and have to take it offline and literally move it somewhere else, where power will be lost.&amp;nbsp; Or I simply lose power to the server room.&amp;nbsp; What happens with the compliance clock...&amp;nbsp; Can I still resync it when the power is reapplied, say a week later?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Presti &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:56:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Snaplock-Compliance-Clock/m-p/46241#M10852</guid>
      <dc:creator>jon_presti</dc:creator>
      <dc:date>2025-06-05T06:56:17Z</dc:date>
    </item>
    <item>
      <title>Re: Snaplock Compliance Clock</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Snaplock-Compliance-Clock/m-p/46246#M10855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no way to manually resync it.&amp;nbsp; The ComplianceClock is a software clock (independent from the system clock), so it will not run during the outage, but its last state will be persistently stored before shutdown.&amp;nbsp; The ComplianceClock will drift forward to the system clock at the rate of one week per year. This prevents any tampering with the retention date.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Answer your question?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;STRONG&gt;Brian&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt; Geek ONTAP: &lt;A href="http://www.netappgeek.com" target="_blank"&gt;www.netappgeek.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Apr 2011 19:43:57 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Snaplock-Compliance-Clock/m-p/46246#M10855</guid>
      <dc:creator>netappgeek</dc:creator>
      <dc:date>2011-04-21T19:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: Snaplock Compliance Clock</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Snaplock-Compliance-Clock/m-p/46250#M10857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Then phase two of the question is, are there any ramifications if the clock is off by lets say a month?&amp;nbsp; Does it care, since there is a seperate clock running there? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Apr 2011 19:58:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Snaplock-Compliance-Clock/m-p/46250#M10857</guid>
      <dc:creator>jon_presti</dc:creator>
      <dc:date>2011-04-21T19:58:31Z</dc:date>
    </item>
    <item>
      <title>Re: Snaplock Compliance Clock</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Snaplock-Compliance-Clock/m-p/46254#M10859</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Yes, the ComplianceClock is separate from the system clock.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;The only catch here is bounded drift correction (&lt;EM&gt;can only change by one week per year&lt;/EM&gt;) -- so if the system is shut down for a very long period (like a month), it will take several years for the ComplianceClock to catch up to "real" time. This means that if the customer has a disastrous outage, at the end of the retention period, the customer may need to wait slightly longer to delete expired files. However, this is a safe implementation from a compliance perspective, assuring that files under SnapLock protection can never be prematurely deleted.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Read TR-3618 for more details:&amp;nbsp; &lt;A href="http://media.netapp.com/documents/tr-3618.pdf" target="_blank"&gt;http://media.netapp.com/documents/tr-3618.pdf&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;STRONG&gt;Brian&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt; Geek ONTAP: &lt;A href="http://www.netappgeek.com" target="_blank"&gt;www.netappgeek.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Apr 2011 20:35:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Snaplock-Compliance-Clock/m-p/46254#M10859</guid>
      <dc:creator>netappgeek</dc:creator>
      <dc:date>2011-04-21T20:35:35Z</dc:date>
    </item>
    <item>
      <title>Re: Snaplock Compliance Clock</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Snaplock-Compliance-Clock/m-p/46261#M10860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for the information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the best,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Presti &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Apr 2011 22:56:38 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Snaplock-Compliance-Clock/m-p/46261#M10860</guid>
      <dc:creator>jon_presti</dc:creator>
      <dc:date>2011-04-21T22:56:38Z</dc:date>
    </item>
  </channel>
</rss>

