Skip to main content
NetApp Knowledge Base

Why does a rename operation create a duplicate object instead of renaming it when Lifecycle Policy is enabled?

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

Applies to

  • Ontap S3
  • Buckets with Lifecycle Policy enabled

Answer

This behavior is expected in object storage environments
Object storage does not support a true rename operation. A rename request is internally processed as:
  • Copy the object to a new name
  • Delete the original object
Lifecycle Policies can impact delete operations by preventing or delaying object deletion in order to enforce retention or compliance requirements. As a result, while the copy operation succeeds and creates a new object with the updated name, the delete operation may not complete, causing the original object to remain.

Additional Information

additionalInformation_text
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.