3.7 KiB
mc ilm restore
minio
Table of Contents
mc ilm restore
Syntax
The mc ilm restore
command creates a temporary copy of an object archived on a remote tier.
The copy automatically expires after 1 day by default.
Use this command to allow applications to access a tiered object
through the MinIO deployment (e.g. "hot tier"). The archived object
remains on the remote tier, while the temporary copy becomes
HEAD
for that object.
EXAMPLE
The following command restores a copy of a transitioned object from
the remote tier back to the myminio
MinIO deployment:
mc ilm restore myminio/mybucket/object.txt
SYNTAX
The command has the following syntax:
mc [GLOBALFLAGS] ilm restore \
[--days "int" ] \
[--recursive] \
[--vid "string"] \
[--versions] \
ALIAS
Parameters
ALIAS
Required The MinIO alias <alias>
, bucket, and path to the archived
object to restore.
mc ilm restore myminio/mybucket/object.txt
--days
Optional The number of days after which MinIO expires the restored copy of the archived object.
--recursive, r
Optional Restores all objects under the specified prefix.
--versions
Optional Restores all versions of the object on the remote tier.
--version-id, vid
Optional Restores the specified version of the object on the remote tier.
Global Flags
Examples
Restore an Archived Object
The following command restores an object archived to a remote tier:
mc ilm restore myminio/mybucket/object.txt
Restore a Specific Archived Object Version
The following command restore a specific object version archived to a remote tier:
mc ilm restore --vid "VERSIONID" myminio/mybucket/object.txt
Restore All Archived Objects at a Bucket Prefix
The following command restores all objects archived under a specified prefix on the remote tier:
mc ilm restore --recursive myminio/mybucket/data/
Behavior
Restored Objects Expire Automatically
MinIO automatically expires the restored object copy after the specified number of days (Default: 1 day).
Restored Objects Become HEAD
The restored object copy becomes HEAD for that object namespace regardless of it's versioning history. This can result in applications returning "stale" data while the local copy exists.