Skip to main content
NetApp Knowledge Base

Can files in a SnapLock volume be deleted before the volume expiry time?

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

Applies to

  • ONTAP 9
  • SnapLock

Answer

Yes. SnapLock retention is enforced at the file level. A volume's expiry time is based on its file(s) with the longest retention.
 
Example:
File "f12" can be deleted because it has expired(2015), even though the volume expiry time is 2025.
 

cluster1::> volume file retention show -vserver vs1 -file /vol/vol_slc/f12

                                   Vserver : vs1
                                      Path : /vol/nfs_slc/f12
          Retention Time (Secs from Epoch) : 1439111404
                  Formatted Retention Time : Sun Aug  9 09:10:04 GMT 2015
              Is Retention Time Wraparound : false
              
cluster1::> volume snaplock show -vserver vs1 -volume vol_slc

                 Vserver Name: vs1
                  Volume Name: vol_slc
                SnapLock Type: compliance
     Minimum Retention Period: 1 years
     Default Retention Period: max
     Maximum Retention Period: 30 years
            Autocommit Period: 12 hours
Is Volume Append Mode Enabled: false
            Privileged Delete: permanently-disabled
                  Expiry Time: Thu May 11 14:37:2 GMT 2025
 ............

Additional Information

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.