All Products
Search
Document Center

Object Storage Service:Why does the storage usage of the objects in the storage class of the source objects remain the same after the storage class of the source objects is converted?

Last Updated:Mar 25, 2024

This topic describes the causes of and solutions to the issue that the storage usage of objects in the storage class of the destination objects increases but the storage usage of the objects in the storage class of the source objects remains the same after the storage class of the source objects is converted. You can use the provided solutions to resolve the issue.

Problem description

The storage usage of objects in the storage class of the destination objects increases but the storage usage of the objects in the storage class of the source objects remains the same after the storage class of the source objects is converted.

Causes

When you call CopyObject to convert the storage class of the source objects, the storage usage of objects in the storage class of the destination objects increases but the storage usage of the objects in the storage class of the source objects remains the same if one of the following conditions is met:

  • Versioning is not enabled for the bucket, and the names of the source and destination objects are different.

  • Versioning is enabled for the bucket, and the names of the source and destination objects are the same or different.

Solutions

You can use one of the following methods to convert the storage class of source objects. After storage class conversion, the storage usage of objects in the storage class of the destination objects increases and the storage usage of the objects in the storage class of the source objects decreases.

  • Configure a lifecycle rule to convert the storage class of the source objects.

  • Call CopyObject to convert the storage class of the source objects. One of the following conditions must be met:

    • Versioning is not enabled for the bucket, and the names of the source and destination objects are the same.

    • Versioning is not enabled for the bucket, and you delete the source objects if the names of the source and destination objects are different.

    • Versioning is enabled for the bucket, and you delete the source objects regardless of whether the names of the source and destination objects are the same.

    Important
    • If the storage class of the source objects or the specified version of the objects is Infrequent Access (IA), Archive, Cold Archive, or Deep Cold Archive, and the objects are deleted before their minimum storage duration ends, you are charged for the storage usage of the objects that are stored for less than the minimum storage duration. For more information, see How am I charged for objects whose storage duration is less than the minimum storage duration?

    • After the source objects or the specified version of the objects are deleted, they cannot be restored. Exercise caution when you perform this operation.