Versioning

Scenarios

OBS can store multiple versions of an object. You can quickly search for and restore different versions or restore data in the event of accidental deletions or application faults.

By default, versioning is disabled for a new OBS bucket. New objects will overwrite existing objects in the bucket in case they have the same names.

Constraints

When you enable WORM for a bucket, OBS automatically enables versioning and versioning cannot be suspended later for that bucket.

Enabling Versioning

• Enabling versioning does not change the version ID (null) and content of any existing object in a bucket. After versioning is enabled for a bucket, if you upload a new object with the same name as an existing object, a version ID will be assigned to this new object, as shown in Figure 1.
  Figure 1 Versioning (with existing objects)
  
• In a versioning-enabled bucket, OBS automatically assigns a unique version ID to each newly uploaded object. Objects with the same name are stored in OBS with different version IDs, as shown in Figure 2.
  Figure 2 Versioning (for new objects)
  

  Table 1 Version description

  Version	Description
  Latest version	After versioning is enabled, each operation on an object will result in saving of the object with a new version ID. The version ID generated upon the latest operation is called the latest version.
  Historical version	After versioning is enabled, each operation on an object will result in saving of the object with a new version ID. Version IDs generated upon operations other than the latest operation are called historical versions.

• The latest objects in a bucket are returned by default after a GET Object request.
• Objects can be downloaded by version IDs. By default, the latest object is downloaded if the version ID is not specified. For details, see Related Operations in Versioning.
• You can select an object and click Delete on the right to delete the object. After the object is deleted, OBS inserts a delete marker. After Historical Versions is enabled, the object with a delete marker appears in the object list. For details, see Deleting an Object. If you try to access the deleted object, a 404 error will be returned.
  Figure 3 Object with a delete marker
  
• After enabling Historical Versions above the object list, you can permanently delete any object version.
• All object versions except those with Delete Marker stored in OBS are charged.

Suspending Versioning

Once versioning is enabled for a bucket, it cannot be disabled, but it can be suspended. When versioning is suspended, a null, not a specific version ID, will be allocated to a newly uploaded object. If the newly uploaded object has the same name as an existing object with a null version ID, the new object will overwrite the existing object.

Figure 4 Object versions in the scenario when versioning is suspended

If versioning is no longer needed, you can suspend it. After versioning is suspended:

• Existing object versions are still retained in OBS. If you no longer desire these versions, manually delete them.
• Objects can be downloaded by version IDs. By default, the latest object is downloaded if the version ID is not specified.
• All historical object versions except those with Delete Marker stored in OBS are charged.

Differences Between Scenarios When Versioning Is Suspended and Disabled

If you delete an object from a versioning-suspended bucket, a delete marker with a null version ID will be generated, no matter whether the object has historical versions. But, if versioning is disabled, the same operation will not generate a delete marker.

In a versioning-enabled bucket, each historical version of an object is stored and you will be billed for the storage of all object versions. Therefore, enable versioning when necessary.

Ways to Configure Versioning

You can use OBS Console, APIs, or SDKs to configure versioning.

Related Operations

After versioning is configured for a bucket, you can delete, share, and download object versions, and extend the retention period of an object version.

1. In the navigation pane of OBS Console, choose Object Storage.
2. In the bucket list, click the bucket you want to operate. The Objects page is displayed.
3. In the object list, view all versions of the object.
4. Perform the following operations on object versions:
   1. Download a desired version of the object by clicking Download in the Operation column.
      

      If the version you want to download is in the Archive or Deep Archive storage class, restore it first.

   2. Share a version of the object by clicking Share in the Operation column.
   3. Permanently delete a version of the object by choosing More > Delete in the Operation column. The deleted object version cannot be recovered. If you delete the latest version, the most recent version will become the latest version.
      

      In a WORM-enabled bucket, if an object has no retention policy configured or its retention policy has expired, you can delete a desired object version on the object's Versions tab page. If an object version is within the retention period, it cannot be deleted.

   4. Locate the object version for which you want to extend the retention period, choose More > Extend Retention Period, and select a date. A retention period can only be extended, but not shortened.