Skip to main content
NetApp Knowledge Base

Snaplock snapshots get created with expiry time wrapping around to 2038

  1. Last updated
  2. Save as PDF
Views:
74
Visibility:
Public
Votes:
0
Category:
snaplock
Specialty:
dp
Last Updated:

Applies to

ONTAP 9.13.1

Issue

Snaplock snapshots get created with expiry time wrapping around to 2038. The customer might not be able to delete the volume/snapshot until the expiry time (2038)

cluster::> volume snaplock show -vserver svm -volume SLvol -instance

                         Vserver: svm
                          Volume: SLvol
                   SnapLock Type: compliance
        Minimum Retention Period: 0 days
        Default Retention Period: min
        Maximum Retention Period: 0 days
               Autocommit Period: none
   Is Volume Append Mode Enabled: false
               Privileged Delete: permanently-disabled
                     Expiry Time: Mon Jan 25 12:17:10 GMT 2038
            ComplianceClock Time: Thu Jan 08 00:51:07 GMT 1970 +00:00
                Litigation Count: 0
    Is SnapLock Audit Log Volume: false
Unspecified Retention File Count: 0

 

 

 

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.