This topic describes problems you may encounter when you use the versioning feature and provides troubleshooting methods and solutions.
Storage costs
If you enable versioning for a bucket, you are charged for the storage of the current versions and previous versions of all objects in the bucket. The following example is used to describe the storage costs incurred in a 30-day month for a versioning-enabled bucket.
Assume that on the first day of the month, you upload an object that is 20 GB in size by calling the PutObject operation and set the storage class of the object to Standard (locally redundant storage).
On the sixteenth day of the month, you write 40 GB of data to the object by calling the PutObject operation.
When you calculate storage costs for the month, be aware that the object (20 GB) uploaded on the first day is not deleted from the bucket when you write 40 GB of data to the object on the sixteenth day. The initial object uploaded on the first day is stored as a previous version in the bucket for 30 days, and the 40 GB of data uploaded on the sixteenth day is stored as the latest version of the object in the bucket for 15 days.
The storage costs of the object for the month is calculated based on the following equation: (20 GB - 5 GB) × USD 0.016 per GB per month + 40 GB × USD 0.016 per GB per month ÷ 30 days × 15 days = USD 0.56.
For more information about storage costs for different storage classes, see Storage fees.
Low response speed
Problem description: The response to a GetBucket (ListObjects) operation on a versioning-enabled bucket significantly slows down.
Cause: One or more objects in your bucket have a large number of previous versions or expired delete markers.
Troubleshooting:
Call the GetBucketVersions (ListObjectVersions) operation to check whether objects in your bucket have a large number of versions. For more information, see ListObjectVersions (GetBucketVersions).
Use the bucket inventory feature to view information about objects in your bucket and check whether the objects have previous versions or expired delete markers. For more information, see Bucket inventory.
Solution: Configure lifecycle rules that expire previous versions by using the NonCurrentVersionExpiration operation and remove expired delete markers by using the ExpiredObjectDeleteMarker operation. For more information, see Configuration elements.
Data size exception
Problem description: The total object size shown on the Objects page of a bucket is inconsistent with the total storage capacity on the Overview page of the bucket.
Cause: Versioning is enabled for the bucket and not all versions are displayed on the Objects page. To display all versions of objects on the Objects page, click Show in the upper right corner of the object list. This ensures that the object size shown on the Objects page is always consistent with the bucket storage usage on the Overview page.