mirror of
https://github.com/minio/docs.git
synced 2025-07-30 07:03:26 +03:00
DOCS-399: Resolve ILM related issues
This commit is contained in:
ravindk89
Ravind Kumar
@ -59,27 +59,6 @@ transition lifecycle management rules on any bucket in the cluster:.
|
||||
:language: json
|
||||
:class: copyable
|
||||
|
||||
Expire Objects after Calendar Date
|
||||
----------------------------------
|
||||
|
||||
Use :mc-cmd:`mc ilm add` with :mc-cmd-option:`~mc ilm add expiry-date` to
|
||||
expire bucket contents after a specific date.
|
||||
|
||||
.. code-block:: shell
|
||||
:class: copyable
|
||||
|
||||
mc ilm add ALIAS/PATH --expiry-date "DATE"
|
||||
|
||||
- Replace :mc-cmd:`ALIAS <mc ilm add TARGET>` with the
|
||||
:mc:`alias <mc alias>` of the S3-compatible host.
|
||||
|
||||
- Replace :mc-cmd:`PATH <mc ilm add TARGET>` with the path to the bucket on the
|
||||
S3-compatible host.
|
||||
|
||||
- Replace :mc-cmd:`DATE <mc ilm add expiry-date>` with the calendar date after
|
||||
which to expire the object. For example, specify "2021-01-01" to expire
|
||||
objects after January 1st, 2021.
|
||||
|
||||
Expire Objects after Number of Days
|
||||
-----------------------------------
|
||||
|
||||
|
||||
@ -49,15 +49,9 @@ objects. Object transition is *not* a replacement for backup/recovery
|
||||
strategies such as :ref:`minio-bucket-replication`.
|
||||
|
||||
Use the :mc-cmd:`mc admin tier` command to create a remote target for tiering
|
||||
data to a supported Cloud Service Provider object storage You can then use the
|
||||
:mc-cmd:`mc ilm add` command with one of the following commandline options to
|
||||
create new transition rules on a bucket:
|
||||
|
||||
- :mc-cmd-option:`mc ilm add transition-date` to transition objects after
|
||||
a specified calendar date.
|
||||
|
||||
- :mc-cmd-option:`mc ilm add transition-days` to transition object after
|
||||
a specified number of calendar days.
|
||||
data to a supported Cloud Service Provider object storage. You can then use the
|
||||
:mc-cmd-option:`mc ilm add transition-days` command to transition objects to the
|
||||
remote tier after a specified number of calendar days.
|
||||
|
||||
Versioned Buckets
|
||||
~~~~~~~~~~~~~~~~~
|
||||
@ -68,7 +62,8 @@ on :ref:`versioned buckets <minio-bucket-versioning>`. Specifically, MinIO by
|
||||
default applies the transition operation to the *current* object version.
|
||||
|
||||
To transition noncurrent object versions, specify the
|
||||
:mc-cmd-option:`~mc ilm add noncurrentversion-transition-days` option
|
||||
:mc-cmd-option:`~mc ilm add noncurrentversion-transition-days` and
|
||||
:mc-cmd-option:`~mc ilm add noncurrentversion-transition-storage-class` options
|
||||
when creating the transition rule.
|
||||
|
||||
.. _minio-lifecycle-management-expiration:
|
||||
|
||||
@ -141,7 +141,7 @@ The example above uses the following arguments:
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 40 60
|
||||
:widths: 30 70
|
||||
:width: 100%
|
||||
|
||||
* - Argument
|
||||
@ -153,7 +153,8 @@ The example above uses the following arguments:
|
||||
|
||||
* - :mc-cmd:`TIER_NAME <mc admin tier add TIER_NAME>`
|
||||
- The name to associate with the new :abbr:`Azure (Microsoft Azure)` blob
|
||||
remote storage tier. This value is required in the next step.
|
||||
remote storage tier. Specify the name in all-caps, e.g. ``AZURE_TIER``.
|
||||
This value is required in the next step.
|
||||
|
||||
* - :mc-cmd:`HOSTNAME <mc admin tier add endpoint>`
|
||||
- The URL endpoint for the :abbr:`Azure (Microsoft Azure)` storage
|
||||
@ -194,16 +195,16 @@ The example above uses the following arguments:
|
||||
3) Verify the Transition Rule
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Use the :mc-cmd:`mc ilm list` command to review the configured transition
|
||||
Use the :mc-cmd:`mc ilm ls` command to review the configured transition
|
||||
rules:
|
||||
|
||||
.. code-block:: shell
|
||||
:class: copyable
|
||||
|
||||
mc ilm list ALIAS/PATH --transition
|
||||
mc ilm ls ALIAS/PATH --transition
|
||||
|
||||
- Replace :mc-cmd:`ALIAS <mc ilm list TARGET>` with the :mc:`alias <mc alias>`
|
||||
- Replace :mc-cmd:`ALIAS <mc ilm ls TARGET>` with the :mc:`alias <mc alias>`
|
||||
of the MinIO deployment.
|
||||
|
||||
- Replace :mc-cmd:`PATH <mc ilm list TARGET>` with the name of the bucket for
|
||||
- Replace :mc-cmd:`PATH <mc ilm ls TARGET>` with the name of the bucket for
|
||||
which to retrieve the configured lifecycle management rules.
|
||||
|
||||
@ -130,7 +130,7 @@ The example above uses the following arguments:
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 40 60
|
||||
:widths: 30 70
|
||||
:width: 100%
|
||||
|
||||
* - Argument
|
||||
@ -142,7 +142,8 @@ The example above uses the following arguments:
|
||||
|
||||
* - :mc-cmd:`TIER_NAME <mc admin tier add TIER_NAME>`
|
||||
- The name to associate with the new :abbr:`GCS (Google Cloud Storage)`
|
||||
remote storage tier. This value is required in the next step.
|
||||
remote storage tier. Specify the name in all-caps, e.g. ``GCS_TIER``.
|
||||
This value is required in the next step.
|
||||
|
||||
* - :mc-cmd:`HOSTNAME <mc admin tier add endpoint>`
|
||||
- The URL endpoint for the :abbr:`GCS (Google Cloud Storage)` storage
|
||||
@ -180,16 +181,16 @@ The example above uses the following arguments:
|
||||
3) Verify the Transition Rule
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Use the :mc-cmd:`mc ilm list` command to review the configured transition
|
||||
Use the :mc-cmd:`mc ilm ls` command to review the configured transition
|
||||
rules:
|
||||
|
||||
.. code-block:: shell
|
||||
:class: copyable
|
||||
|
||||
mc ilm list ALIAS/PATH --transition
|
||||
mc ilm ls ALIAS/PATH --transition
|
||||
|
||||
- Replace :mc-cmd:`ALIAS <mc ilm list TARGET>` with the :mc:`alias <mc alias>`
|
||||
- Replace :mc-cmd:`ALIAS <mc ilm ls TARGET>` with the :mc:`alias <mc alias>`
|
||||
of the MinIO deployment.
|
||||
|
||||
- Replace :mc-cmd:`PATH <mc ilm list TARGET>` with the name of the bucket for
|
||||
- Replace :mc-cmd:`PATH <mc ilm ls TARGET>` with the name of the bucket for
|
||||
which to retrieve the configured lifecycle management rules.
|
||||
|
||||
@ -141,7 +141,7 @@ The example above uses the following arguments:
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 40 60
|
||||
:widths: 30 70
|
||||
:width: 100%
|
||||
|
||||
* - Argument
|
||||
@ -152,8 +152,9 @@ The example above uses the following arguments:
|
||||
the S3 remote tier.
|
||||
|
||||
* - :mc-cmd:`TIER_NAME <mc admin tier add TIER_NAME>`
|
||||
- The name to associate with the new S3 remote storage tier. This value
|
||||
is required in the next step.
|
||||
- The name to associate with the new S3 remote storage tier. Specify the
|
||||
name in all-caps, e.g. ``S3_TIER``. This value is required in the next
|
||||
step.
|
||||
|
||||
* - :mc-cmd:`HOSTNAME <mc admin tier add endpoint>`
|
||||
- The URL endpoint for the S3 storage backend.
|
||||
@ -198,16 +199,16 @@ The example above uses the following arguments:
|
||||
3) Verify the Transition Rule
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Use the :mc-cmd:`mc ilm list` command to review the configured transition
|
||||
Use the :mc-cmd:`mc ilm ls` command to review the configured transition
|
||||
rules:
|
||||
|
||||
.. code-block:: shell
|
||||
:class: copyable
|
||||
|
||||
mc ilm list ALIAS/PATH --transition
|
||||
mc ilm ls ALIAS/PATH --transition
|
||||
|
||||
- Replace :mc-cmd:`ALIAS <mc ilm list TARGET>` with the :mc:`alias <mc alias>`
|
||||
- Replace :mc-cmd:`ALIAS <mc ilm ls TARGET>` with the :mc:`alias <mc alias>`
|
||||
of the MinIO deployment.
|
||||
|
||||
- Replace :mc-cmd:`PATH <mc ilm list TARGET>` with the name of the bucket for
|
||||
- Replace :mc-cmd:`PATH <mc ilm ls TARGET>` with the name of the bucket for
|
||||
which to retrieve the configured lifecycle management rules.
|
||||
|
||||
Reference in New Issue
Block a user