All Products
Search

This Product

    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?

    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 07, 2025

    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.

    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.

    Possible 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 to increase the storage usage of objects in the storage class of the destination objects while reducing that of the source storage class.

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

    • Call CopyObject to convert the storage class of the source objects.

      • In an unversioned bucket: If the names of the source and destination objects are the same, no additional configuration is required. If the names of the source and destination objects are different, you need to delete the source object manually after the object is copied.

      • In a versioned bucket: You need to delete the source object manually after the object is copied 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 extra fees. 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.