Skip to main content
NetApp Knowledge Base

CONTAP-267640: SnapLock Volume Compliance Clock can get set to an older value

  1. Last updated
  2. Save as PDF
Views:
15
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Issue

Under certain conditions, the SnapLock volume compliance clock of a SnapMirror destination volume can get set to an older value. The following are some of the scenarios when this can happen:

* Replicating a snapshot to the destination that was created prior to snapshot locking being enabled on a volume 

* Performing a resync of a SnapMirror relationship where the destination is a SnapLock Compliance volume. 

In either of the scenarios, the volume compliance clock of the destination volume can get set to the value that was captured in the snapshot being used. This can cause the VCC to be set to an older value.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.