docs/source/reference/deprecated/mc-ilm-add.rst

mc ilm add

minio

Table of Contents

mc ilm add

RELEASE.2022-12-24T15-21-38Z

mc ilm add replaced by mc ilm rule add.

Syntax

The mc ilm add command adds an object lifecycle management rule to a bucket.

The command supports adding both Transition (Tiering) <minio-lifecycle-management-tiering> and Expiration <minio-lifecycle-management-expiration> lifecycle management rules.

EXAMPLE

The following command adds new lifecycle management rules to the mydata bucket on the myminio deployment:

mc ilm add --expire-days 90 --noncurrent-expire-days 30 myminio/mydata

mc ilm add --expire-delete-marker myminio/mydata

mc ilm add --transition-days 30 --transition-tier "COLDTIER" myminio/mydata

mc ilm add --noncurrent-transition-days 7 --noncurrent-transition-tier "COLDTIER" 

The configured rules have the following effect:

• Delete objects more than 90 days old
• Delete objects 30 days after they become non-current
• Delete DeleteMarker tombstones if that object has no other versions remaining.
• Transition objects more than 30 days old to the COLDTIER remote tier.
• Transition objects 7 days after they become non-current to the COLDTIER remote tier.

SYNTAX

The command has the following syntax:

mc [GLOBALFLAGS] ilm add                                    \
                 [--prefix string]                          \
                 [--tags string]                            \
                 --expire-days "integer"                    \
                 [--expire-delete-marker]                   \
                 [--transition-days "string"]               \
                 [--transition-tier "string"]               \
                 [--noncurrent-expire-days "integer"]       \
                 [--noncurrent-expire-newer "integer"]      \
                 [--noncurrent-transition-days "integer"]   \
                 [--noncurrent-transition-tier "string"]    \
                 ALIAS

Parameters

ALIAS

The alias <alias> and bucket on the MinIO deployment to which to add the object lifecycle management rule.

For example:

mc ilm add myminio/mydata

--prefix

Restrict the management rule to a specific object prefix.

For example:

mc ilm add --prefix "meetingnotes/" myminio/mydata/ --expire-days "90"

The command creates a rule that expires objects in the mydata bucket of the myminio ALIAS after 90 days for any object with the meetingnotes/ prefix.

--tags

One or more ampersand &-delimited key-value pairs describing the object tags to use for filtering objects to which the lifecycle configuration rule applies.

This option is mutually exclusive with the following option:

• ~mc ilm add --expire-delete-marker

--expire-days

The number of days to retain an object after being created. MinIO marks the object for deletion after the specified number of days pass. Specify the number of days as an integer, e.g. 30 for 30 days.

For versioned buckets, the expiry rule applies only to the current object version. Use the ~mc ilm add --noncurrent-expire-days option to apply expiration behavior to noncurrent object versions.

MinIO uses a scanner process <minio-concepts-scanner> to check objects against all configured lifecycle management rules. Slow scanning due to high IO workloads or limited system resources may delay application of lifecycle management rules. See minio-lifecycle-management-scanner for more information.

Mutually exclusive with the following options:

• ~mc ilm add --expire-delete-marker

For more complete documentation on object expiration, see minio-lifecycle-management-expiration and minio-object-delete.

--expire-delete-marker

Specify this option to direct MinIO to remove delete markers for objects with no remaining object versions. Specifically, the delete marker is the only remaining "version" of the given object.

This option is mutually exclusive with the following option:

• ~mc ilm add --tags
• ~mc ilm add --expire-days

MinIO uses a scanner process <minio-concepts-scanner> to check objects against all configured lifecycle management rules. Slow scanning due to high IO workloads or limited system resources may delay application of lifecycle management rules. See minio-lifecycle-management-scanner for more information.

For more complete documentation on object expiration, see minio-lifecycle-management-expiration and minio-object-delete.

--transition-days

The number of calendar days from object creation after which MinIO marks an object as eligible for transition. MinIO transitions the object to the configured remote tier specified to the ~mc ilm add --transition-tier. Specify the number of days as an integer, e.g. 30 for 30 days.

For versioned buckets, the transition rule applies only to the current object version. Use the ~mc ilm add --noncurrent-transition-days option to apply transition behavior to noncurrent object versions.

Requires specifying ~mc ilm add --transition-tier.

MinIO uses a scanner process <minio-concepts-scanner> to check objects against all configured lifecycle management rules. Slow scanning due to high IO workloads or limited system resources may delay application of lifecycle management rules. See minio-lifecycle-management-scanner for more information.

For more complete documentation on object transition, see minio-lifecycle-management-tiering.

--transition-tier

The remote tier to which MinIO transition objects <minio-lifecycle-management-tiering>. Specify an existing remote tier created by mc admin tier.

Required if specifying ~mc ilm add --transition-days.

--noncurrent-expire-days

The number of days to retain an object version after becoming non-current (i.e. a different version of that object is now the HEAD). MinIO marks noncurrent object versions for deletion after the specified number of days pass.

This option has the same behavior as the S3 NoncurrentVersionExpiration action.

MinIO uses a scanner process <minio-concepts-scanner> to check objects against all configured lifecycle management rules. Slow scanning due to high IO workloads or limited system resources may delay application of lifecycle management rules. See minio-lifecycle-management-scanner for more information.

--noncurrent-transition-days

The number of days an object has been non-current (i.e. replaced by a newer version of that same object) after which MinIO marks the object version as eligible for transition. MinIO transitions the object to the configured remote tier specified to the ~mc ilm add --transition-tier once the system host datetime passes that calendar date.

This option has no effect on non-versioned buckets. Requires specifying ~mc ilm add --noncurrent-transition-tier.

This option has the same behavior as the S3 NoncurrentVersionTransition action.

MinIO uses a scanner process <minio-concepts-scanner> to check objects against all configured lifecycle management rules. Slow scanning due to high IO workloads or limited system resources may delay application of lifecycle management rules. See minio-lifecycle-management-scanner for more information.

--noncurrent-transition-tier

The remote tier to which MinIO transitions noncurrent objects versions <minio-lifecycle-management-tiering>. Specify a remote tier created by mc admin tier.

--noncurrent-expire-newer

The maximum number of non-current object versions to retain, ordered from newest to oldest.

Use this flag to retain a certain number of past versions of a file in a first in, first out fashion. After retaining the maximum number of non-current versions, MinIO marks any remaining older non-current object versions as eligible for expiration.

The following table lists a number of object versions and their expiration eligibility based on --noncurrent-expire-newer 3:

v5 (current version)	Current version not affected by ILM rules.
v4	retained
v3	retained
v2	retained
v1	marked for expiry

MinIO retains the current version, v5. MinIO also retains the next 3 non-current versions, starting with the newest. This means MinIO marks v4, v3, and v2 for the three non-current version to retain.

v1 would be a fourth non-current version, which falls outside the limit of non-current versions to retain, so MinIO marks v1 for expiration.

Updating the number for this flag only impacts the unmarked versions of objects. Any versions already marked for expiration do not change if you increase the number to retain.

MinIO uses a scanner process <minio-concepts-scanner> to check objects against all configured lifecycle management rules. Slow scanning due to high IO workloads or limited system resources may delay application of lifecycle management rules. See minio-lifecycle-management-scanner for more information.

Global Flags

Examples

Expire All Bucket Contents After Number of Days

Use mc ilm add with ~mc ilm add --expire-days to mark bucket contents for expiration after a number of days pass from the object's creation:

mc ilm add ALIAS/PATH --expire-days "DAYS" 

• Replace ALIAS <mc ilm add ALIAS> with the alias <mc alias> of the S3-compatible host.
• Replace PATH <mc ilm add ALIAS> with the path to the bucket on the S3-compatible host.
• Replace DATE <mc ilm add --expire-days> with the number of days after which to expire the object. For example, specify 30 to expire the object 30 days after creation.

Transition Non-Current Object Versions at a Prefix to a Different Tier

Use the mc ilm add with ~mc ilm add --prefix and ~mc ilm add --transition-tier to transition older non-current versions of an object to a different storage tier.

mc ilm add --prefix "doc/" --transition-days "90" --trasition-tier "MINIOTIER-1"                  \
       --noncurrent-transition-days "45" --noncurrent-transition-tier "MINIOTIER-2"  \
       myminio/mybucket/

This command looks at the contents with the doc/ prefix in the mybucket bucket on the myminio deployment.

• Current objects in the prefix older than 90 days move to the MINIOTIER-1 storage tier.
• Non-current objects in the prefix older than 45 days move to the MINIOTIER-2 storage tier.
• Both MINIOTIER-1 and MINIOTIER-2 have already been created with mc admin tier add.

Expire All Objects at a Prefix, Retain Current Object Versions Longer Than Non-Current Object Versions

Use the mc ilm add command with ~mc ilm add --prefix, ~mc ilm add --expire-days, and ~mc ilm add --noncurrent-expire-days to expire current and non-current versions of an object at different times.

mc ilm add --prefix "doc/" --expire-days "300" --noncurrent-expire-days "100" myminio/mybucket/

This command looks at the contents with the doc/ prefix in the mybucket bucket on the myminio deployment.

• Current objects expire after 300 days.
• Non-current objects expire after 100 days.

Behavior

Lifecycle Management Object Scanner

MinIO uses a scanner process <minio-concepts-scanner> to check objects against the configured lifecycle management rules. Slow scanning due to high IO workloads or limited system resources may delay application of lifecycle management rules. See minio-lifecycle-management-scanner for more information.

Expiry vs Transition

MinIO supports specifying both expiry and transition rules in the same bucket or bucket prefix. MinIO can execute an expiration rule on an object regardless of its transition status. Use mc ilm ls to review the currently configured object lifecycle management rules for any potential interactions between expiry and transition rules.

S3 Compatibility