Bucket versioning

Bucket versioning enables keeping a history of an object through its versions. Each version is a complete copy of an object and occupies space in Object Storage. Using version control protects your data from both accidental user actions and application faults.

Versioning is enabled at the bucket level and applies to every object in the bucket.

For more information on how to enable versioning, see Managing bucket versioning.

• After you enable this feature, each uploaded object will get the version_id parameter. This will allow you to manage specific object versions.

• Before versioning is enabled, each bucket object is assigned a version_id equal to null.

  When versioning is paused, the version_id of existing objects does not change. Each new object gets a null version ID. If the null version already exists, it will be overwritten.

  Note

  With object version lock on, versioning cannot be paused.

• Overwriting an object version results in a new object with the same ID and a randomly generated version_id.

  To access a previous version of an object, use the object ID and the version_id you need.

• If versioning is enabled, you can restore previous object versions by following this guide.

When you delete an object version, it is marked as delete and no longer takes up any storage space.

You can remove irrelevant or deleted object versions from a bucket manually or by setting up an object lifecycle.