Skip to main content
NetApp Knowledge Base

Snaplock Compliance Clock not in Sync with Local Cluster time

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

Applies to

  • ONTAP 9.X
  • Snaplock
  • ONTAP S3 with object locking enabled

Issue

  • Snaplock Compliance Clock is not in Sync with Local Cluster Date. 
  • Unable to delete objects from Veeam and getting access denied error.
  • Below is the error from Veeam application logs:

[06.11.2024 00:31:29.805] < 22836> aws      | Amazon REST exception with status=403, error code=AccessDenied.
[06.11.2024 00:31:29.805] < 20448> cli      |     Deleting checkpoint [2784] from checkpoints tree... Failed.
[06.11.2024 00:31:29.805] < 21840> cli      | Thread finished. Role: 'Cloud exclusive lock /Veeam/Backup/New Folder/Clients/{xxxx-xxxxxx-xxxxxxx}/xxxx-xxxx-xxxxxxx/Metadata/Lock/delete.checkpoint'.

 

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.