How version management works
1) INTRODUCTION TO VERSION MANAGEMENT
Version management is a way of keeping several variants of an object in the same bucket, and allows each version of each object to be stored, retrieved and restored.
This option must be activated if you set up object locking.
2) THE BENEFITS OF VERSION MANAGEMENT
Version management has many benefits:
To recover a version in the event of unintentional user actions or application failures.
For data preservation and archiving.
In the event of several simultaneous write requests for the same object, a version is created for each request.
3) HOW VERSIONING WORKS
When versioning is enabled, the bucket can never revert to an unversioned state: all objects deposited after the option has been enabled will be versioned, and will receive a unique version identifier.
You can, however, stop versioning, and all new objects placed will not be versioned.
When deleting an object, a deletion marker is inserted instead of permanently deleting the object. The deletion marker becomes the current version of the object. If you replace an object, this creates a new object version in the bucket.
By default, GET requests retrieve the most recent version. Older versions of an overwritten or deleted object can be retrieved by specifying the version in the request.
4) ADDITIONAL RESOURCES
Create a bucket
Create an object storage identifier
How object locking works
Version management is a way of keeping several variants of an object in the same bucket, and allows each version of each object to be stored, retrieved and restored.
This option must be activated if you set up object locking.
2) THE BENEFITS OF VERSION MANAGEMENT
Version management has many benefits:
To recover a version in the event of unintentional user actions or application failures.
For data preservation and archiving.
In the event of several simultaneous write requests for the same object, a version is created for each request.
3) HOW VERSIONING WORKS
When versioning is enabled, the bucket can never revert to an unversioned state: all objects deposited after the option has been enabled will be versioned, and will receive a unique version identifier.
You can, however, stop versioning, and all new objects placed will not be versioned.
When deleting an object, a deletion marker is inserted instead of permanently deleting the object. The deletion marker becomes the current version of the object. If you replace an object, this creates a new object version in the bucket.
By default, GET requests retrieve the most recent version. Older versions of an overwritten or deleted object can be retrieved by specifying the version in the request.
4) ADDITIONAL RESOURCES
Create a bucket
Create an object storage identifier
How object locking works
Updated on: 05/01/2024
Thank you!