Skip to main content
NetApp Knowledge Base

Why an object is gone after delete request even when object lock is enabled ?

  1. Last updated
  2. Save as PDF
Views:
142
Visibility:
Public
Votes:
0
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

  • NetApp StorageGRID
  • Object Lock

Answer

This is the default behaviour and is compliant with Amazon S3.

Although a protected object version cannot be deleted, a delete marker can still be created for an object when only the object key is profided instead of the key + version id (as seen in s3 versioning definition):

Diagram depicting how S3 Versioning works when you DELETE an object that is in a versioning-enabled bucket.

Placing a delete marker on an object doesn't delete the object or its object versions but marks the version as non-current which hides the object from normal listing operations. Object version can be made current (visable) again with a S3 client as long as retention has not expired.

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.