Scenario

Versioning is a bucket-level data protection feature. When versioning is enabled, deleted or overwritten data is preserved as historical versions. If you accidentally overwrite or delete an object, you can restore it to the latest version.

Restriction and Limitations

Enabling the compliance-based retention feature for a bucket automatically activates versioning, which cannot be suspended.

Enabling Versioning

• When versioning is enabled, ZOS automatically assigns a unique version number to each uploaded object. Objects with identical names are stored in ZOS with distinct version numbers.

• Objects uploaded to the bucket before versioning is enabled have empty version ID. Upon uploading objects with identical names, version numbers are assigned to the newly uploaded objects.

• Listing objects within a bucket will display both the current and historical versions of those objects.

• You can download or delete the current or any historical version of an object.

Version	Description
Latest Edition	When versioning is enabled, uploading an object with an identical name to an existing one, deleting, or restoring an object generates a new version. The version generated by the last operation becomes the current version.
History Edition	When versioning is enabled, uploading an object with an identical name to an existing one, deleting, or restoring an object generates a new version. All generated versions except the latest one are considered historical versions.

Description

When versioning is enabled, all historical versions of objects are preserved, consuming storage space in ZOS and incurring associated storage costs. Exercise caution when enabling versioning to prevent incurring unnecessary additional storage costs.

Suspending Versioning

You can suspend versioning when this feature is no longer needed.

• Once enabled, versioning can be suspended but not disabled.

• After suspension, uploaded objects will no longer have version numbers. This may lead to overwriting existing objects with identical names.

• Historical versions existing prior to suspension will not be deleted and can still be downloaded. If you no longer need them, manually delete them.

• Once suspended, deleted or overwritten objects cannot be restored.

Usage

Usage	Reference Documentation
Console	For more information, seeVersioning Management.
SDK	ZOS supports various SDKs. For more information about code examples, seeDeveloper Documentation.
API	For more information, seeEnable Versioning.

Zettabyte Object Storage

Multi-version Management