A few opportunistic text updates: - `mc mirror` recommends `mc replicate` and `mc admin replicate` for other use cases. Mention what they are for. - Clarify that `mc version` creates a null version id for existing unversioned objects when bucket versioning is enabled. http://192.241.195.202:9000/staging/mc-mirror-clarification/linux/reference/minio-mc/mc-mirror.html http://192.241.195.202:9000/staging/mc-mirror-clarification/linux/reference/minio-mc/mc-version.html#bucket-versioning-with-existing-data --------- Co-authored-by: Ravind Kumar <ravind@min.io>
2.3 KiB
mc version
minio
Table of Contents
mc version
Description
The mc version
commands enable, disable, and retrieve the versioning <minio-bucket-versioning>
status for
a MinIO bucket.
For more information about object versioning in MinIO, see minio-bucket-versioning
.
mc version
includes
the following subcommands:
Subcommand | Description |
---|---|
~mc version enable |
|
~mc version info |
|
~mc version suspend |
Behavior
Object Locking Enables Bucket Versioning
While bucket versioning is disabled by default, configuring object
locking on a bucket or an object in that bucket automatically enables
versioning for the bucket. See mc retention
for more information on configuring object
locking.
Bucket Versioning with Existing Data
Enabling bucket versioning on a bucket with existing data immediately creates a null value version ID for each unversioned object.
Disabling bucket versioning on a bucket with existing versioned data
does not remove any versioned objects. Applications can
continue to access versioned data after disabling bucket versioning. Use
mc rm --versions ALIAS/BUCKET/OBJECT <mc rm --versions>
to delete an object and all its versions.
S3 Compatibility
/reference/minio-mc/mc-version-enable /reference/minio-mc/mc-version-info /reference/minio-mc/mc-version-suspend