Scenario

The versioning feature enables you to retain multiple versions of an object within a bucket. This feature allows you to easily retrieve objects and restore data quickly in the event of inadvertent operations or application faults.

Note:

By default, the versioning feature is disabled for a bucket. Consequently, if you upload an object with the same name as an existing one, the new object will overwrite that one.

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.

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.

Zettabyte Object Storage