mirror of
https://github.com/minio/docs.git
synced 2025-07-30 07:03:26 +03:00
DOCS-404: Improve documentation around tiering and replication
Adding Poorna's suggestions Co-authored-by: Poorna K <poornas@users.noreply.github.com> CR fixups KP suggestions Co-authored-by: Krishnan Parthasarathi <krisis@users.noreply.github.com> More fixups Final fixups
This commit is contained in:
ravindk89
Ravind Kumar
@ -36,23 +36,30 @@ following public cloud storage services:
|
||||
- :ref:`Microsoft Azure Blob Storage
|
||||
<minio-lifecycle-management-transition-to-azure>`
|
||||
|
||||
MinIO object transition supports use cases like moving aged data from
|
||||
MinIO clusters in private or public cloud infrastructure to low-cost
|
||||
public cloud storage solutions.
|
||||
|
||||
MinIO manages retrieving tiered objects on-the-fly without any additional
|
||||
application-side logic. MinIO retains the minimum object metadata required to
|
||||
support retrieving objects transitioned to a remote tier. MinIO therefore
|
||||
*requires* exclusive access to the data on the remote storage tier. Object
|
||||
retrieval assumes no external mutation, migration, or deletion of stored
|
||||
objects. Object transition is *not* a replacement for backup/recovery
|
||||
strategies such as :ref:`minio-bucket-replication`.
|
||||
MinIO object transition supports use cases like moving aged data from MinIO
|
||||
clusters in private or public cloud infrastructure to low-cost private or public cloud
|
||||
storage solutions. MinIO manages retrieving tiered objects on-the-fly without
|
||||
any additional application-side logic.
|
||||
|
||||
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-option:`mc ilm add transition-days` command to transition objects to the
|
||||
remote tier after a specified number of calendar days.
|
||||
|
||||
Exclusive Access to Remote Data
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. include:: /includes/common-minio-tiering.rst
|
||||
:start-after: start-transition-bucket-access-desc
|
||||
:end-before: end-transition-bucket-access-desc
|
||||
|
||||
Availability of Remote Data
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. include:: /includes/common-minio-tiering.rst
|
||||
:start-after: start-transition-data-loss-desc
|
||||
:end-before: end-transition-data-loss-desc
|
||||
|
||||
Versioned Buckets
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
||||
@ -78,25 +78,12 @@ permissions.
|
||||
Considerations
|
||||
--------------
|
||||
|
||||
Lifecycle Management Object Scanner
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
Exclusive Access to Remote Data
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
MinIO uses a scanner process 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 :ref:`minio-lifecycle-management-scanner` for more information.
|
||||
|
||||
Exclusive Bucket Access
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
MinIO retains the minimum object metadata required to
|
||||
support retrieving objects transitioned to a remote tier. MinIO therefore
|
||||
*requires* exclusive access to the data on the remote storage tier. Object
|
||||
retrieval assumes no external mutation, migration, or deletion of stored
|
||||
objects.
|
||||
|
||||
MinIO also ignores any objects in the remote bucket or bucket prefix not
|
||||
explicitly managed by MinIO.
|
||||
.. include:: /includes/common-minio-tiering.rst
|
||||
:start-after: start-transition-bucket-access-desc
|
||||
:end-before: end-transition-bucket-access-desc
|
||||
|
||||
.. important::
|
||||
|
||||
@ -108,6 +95,13 @@ explicitly managed by MinIO.
|
||||
Please contact `MinIO Support <https://min.io/pricing?ref=docs>`__ if you need
|
||||
situation-specific guidance around configuring Azure remote tiers.
|
||||
|
||||
Availability of Remote Data
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. include:: /includes/common-minio-tiering.rst
|
||||
:start-after: start-transition-data-loss-desc
|
||||
:end-before: end-transition-data-loss-desc
|
||||
|
||||
Procedure
|
||||
---------
|
||||
|
||||
@ -166,7 +160,16 @@ The example above uses the following arguments:
|
||||
|
||||
* - :mc-cmd:`PREFIX <mc admin tier add prefix>`
|
||||
- The optional bucket prefix within which MinIO transitions objects.
|
||||
Omit this argument to transition objects to the bucket root.
|
||||
|
||||
MinIO stores all transitioned objects in the specified ``BUCKET`` under a
|
||||
unique per-deployment prefix value. Omit this argument to use only that
|
||||
value for isolating and organizing data within the remote storage.
|
||||
|
||||
MinIO recommends specifying this optional prefix for remote storage tiers
|
||||
which contain other data, including transitioned objects from other MinIO
|
||||
deployments. This prefix should provide a clear reference back to the
|
||||
source MinIO deployment to faciliate ease of operations related to
|
||||
diagnostics, maintenance, or disaster recovery.
|
||||
|
||||
* - :mc-cmd:`ACCOUNT <mc admin tier add account-name>`
|
||||
- The account name MinIO uses to access the bucket. The account name
|
||||
@ -192,7 +195,7 @@ The example above uses the following arguments:
|
||||
:end-before: end-create-transition-rule-desc
|
||||
|
||||
|
||||
3) Verify the Transition Rule
|
||||
4) Verify the Transition Rule
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Use the :mc-cmd:`mc ilm ls` command to review the configured transition
|
||||
|
||||
@ -86,17 +86,19 @@ lifecycle management rules. Slow scanning due to high IO workloads or
|
||||
limited system resources may delay application of lifecycle management
|
||||
rules. See :ref:`minio-lifecycle-management-scanner` for more information.
|
||||
|
||||
Exclusive Bucket Access
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
Exclusive Access to Remote Data
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
MinIO retains the minimum object metadata required to
|
||||
support retrieving objects transitioned to a remote tier. MinIO therefore
|
||||
*requires* exclusive access to the data on the remote storage tier. Object
|
||||
retrieval assumes no external mutation, migration, or deletion of stored
|
||||
objects.
|
||||
.. include:: /includes/common-minio-tiering.rst
|
||||
:start-after: start-transition-bucket-access-desc
|
||||
:end-before: end-transition-bucket-access-desc
|
||||
|
||||
MinIO also ignores any objects in the remote bucket or bucket prefix not
|
||||
explicitly managed by MinIO.
|
||||
Availability of Remote Data
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. include:: /includes/common-minio-tiering.rst
|
||||
:start-after: start-transition-data-loss-desc
|
||||
:end-before: end-transition-data-loss-desc
|
||||
|
||||
Procedure
|
||||
---------
|
||||
@ -122,7 +124,7 @@ service as the remote storage tier:
|
||||
mc admin tier add gcs TARGET TIER_NAME \
|
||||
--endpoint https://HOSTNAME \
|
||||
--bucket BUCKET \
|
||||
--prefix PREFIX
|
||||
--prefix PREFIX \
|
||||
--credentials-file CREDENTIALS \
|
||||
--region REGION
|
||||
|
||||
@ -155,7 +157,16 @@ The example above uses the following arguments:
|
||||
|
||||
* - :mc-cmd:`PREFIX <mc admin tier add prefix>`
|
||||
- The optional bucket prefix within which MinIO transitions objects.
|
||||
Omit this argument to transition objects to the bucket root.
|
||||
|
||||
MinIO stores all transitioned objects in the specified ``BUCKET`` under a
|
||||
unique per-deployment prefix value. Omit this argument to use only that
|
||||
value for isolating and organizing data within the remote storage.
|
||||
|
||||
MinIO recommends specifying this optional prefix for remote storage tiers
|
||||
which contain other data, including transitioned objects from other MinIO
|
||||
deployments. This prefix should provide a clear reference back to the
|
||||
source MinIO deployment to faciliate ease of operations related to
|
||||
diagnostics, maintenance, or disaster recovery.
|
||||
|
||||
* - :mc-cmd:`CREDENTIALS <mc admin tier add credentials-file>`
|
||||
- The `credential file
|
||||
@ -178,7 +189,7 @@ The example above uses the following arguments:
|
||||
:end-before: end-create-transition-rule-desc
|
||||
|
||||
|
||||
3) Verify the Transition Rule
|
||||
4) Verify the Transition Rule
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Use the :mc-cmd:`mc ilm ls` command to review the configured transition
|
||||
|
||||
@ -95,17 +95,19 @@ lifecycle management rules. Slow scanning due to high IO workloads or
|
||||
limited system resources may delay application of lifecycle management
|
||||
rules. See :ref:`minio-lifecycle-management-scanner` for more information.
|
||||
|
||||
Exclusive Bucket Access
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
Exclusive Access to Remote Data
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
MinIO retains the minimum object metadata required to
|
||||
support retrieving objects transitioned to a remote tier. MinIO therefore
|
||||
*requires* exclusive access to the data on the remote storage tier. Object
|
||||
retrieval assumes no external mutation, migration, or deletion of stored
|
||||
objects.
|
||||
.. include:: /includes/common-minio-tiering.rst
|
||||
:start-after: start-transition-bucket-access-desc
|
||||
:end-before: end-transition-bucket-access-desc
|
||||
|
||||
MinIO also ignores any objects in the remote bucket or bucket prefix not
|
||||
explicitly managed by MinIO.
|
||||
Availability of Remote Data
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. include:: /includes/common-minio-tiering.rst
|
||||
:start-after: start-transition-data-loss-desc
|
||||
:end-before: end-transition-data-loss-desc
|
||||
|
||||
Procedure
|
||||
---------
|
||||
@ -165,7 +167,16 @@ The example above uses the following arguments:
|
||||
|
||||
* - :mc-cmd:`PREFIX <mc admin tier add prefix>`
|
||||
- The optional bucket prefix within which MinIO transitions objects.
|
||||
Omit this argument to transition objects to the bucket root.
|
||||
|
||||
MinIO stores all transitioned objects in the specified ``BUCKET`` under a
|
||||
unique per-deployment prefix value. Omit this argument to use only that
|
||||
value for isolating and organizing data within the remote storage.
|
||||
|
||||
MinIO recommends specifying this optional prefix for remote storage tiers
|
||||
which contain other data, including transitioned objects from other MinIO
|
||||
deployments. This prefix should provide a clear reference back to the
|
||||
source MinIO deployment to faciliate ease of operations related to
|
||||
diagnostics, maintenance, or disaster recovery.
|
||||
|
||||
* - :mc-cmd:`ACCESS_KEY <mc admin tier add access-key>`
|
||||
- The S3 access key MinIO uses to access the bucket. The
|
||||
@ -196,7 +207,7 @@ The example above uses the following arguments:
|
||||
:end-before: end-create-transition-rule-desc
|
||||
|
||||
|
||||
3) Verify the Transition Rule
|
||||
4) Verify the Transition Rule
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Use the :mc-cmd:`mc ilm ls` command to review the configured transition
|
||||
|
||||
Reference in New Issue
Block a user