minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-30 07:03:26 +03:00
Code Activity

Patching replication docs for version match requirement (#825)

Browse Source
This commit is contained in:
Ravind Kumar
2023-04-20 10:36:31 -04:00
committed by GitHub
parent 579540ae5c
commit e7db29ff03
4 changed files with 13 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
source/administration/bucket-replication.rst
View File

@ -45,7 +45,7 @@ Server-Side Bucket Replication
------------------------------ ------------------------------
MinIO server-side bucket replication is an automatic bucket-level configuration that synchronizes objects between a source and destination bucket. MinIO server-side bucket replication is an automatic bucket-level configuration that synchronizes objects between a source and destination bucket.
MinIO server-side replication *requires* the source and destination bucket be two separate MinIO clusters. MinIO server-side replication *requires* the source and destination bucket be two separate MinIO clusters running the same MinIO Server version.
For each write operation to the bucket, MinIO checks all configured replication rules for the bucket and applies the matching rule with highest configured priority. For each write operation to the bucket, MinIO checks all configured replication rules for the bucket and applies the matching rule with highest configured priority.
MinIO synchronizes new objects *and* object mutations, such as new object versions or changes to object metadata. MinIO synchronizes new objects *and* object mutations, such as new object versions or changes to object metadata.

2
source/includes/common-replication.rst
View File

@ -17,7 +17,7 @@ MinIO does *not* support replicating client-side encrypted objects (SSE-C).
.. start-replication-minio-only .. start-replication-minio-only
MinIO server-side replication only works between MinIO deployments. MinIO server-side replication only works between MinIO deployments.
Both the source and destination deployments *must* run MinIO. Both the source and destination deployments *must* run MinIO Server with matching versions.
To configure replication between arbitrary S3-compatible services, use :mc:`mc mirror`. To configure replication between arbitrary S3-compatible services, use :mc:`mc mirror`.

5
source/operations/data-recovery/recover-after-site-failure.rst
View File

@ -65,8 +65,9 @@ This procedure assumes a *total loss* of one or more peer sites versus replicati
2. Deploy a new MinIO site following the :ref:`site replication requirements <minio-expand-site-replication>`. 2. Deploy a new MinIO site following the :ref:`site replication requirements <minio-expand-site-replication>`.
Do not upload any data or otherwise configure the deployment beyond the stated requirements. - Do not upload any data or otherwise configure the deployment beyond the stated requirements.
Validate that the new MinIO deployment functions normally and has bidirectional connectivity to the other peer sites. - Validate that the new MinIO deployment functions normally and has bidirectional connectivity to the other peer sites.
- Ensure the new site matches the server version on the existing peer sites
.. warning:: .. warning::

8
source/operations/install-deploy-manage/multi-site-replication.rst
View File

@ -105,6 +105,14 @@ All Sites Must Use the Same IDP
All sites must use the same :ref:`Identity Provider <minio-authentication-and-identity-management>`. All sites must use the same :ref:`Identity Provider <minio-authentication-and-identity-management>`.
Site replication supports the included MinIO IDP, OIDC, or LDAP. Site replication supports the included MinIO IDP, OIDC, or LDAP.
All Sites Must use the Same MinIO Server Version
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
All sites must have a matching and consistent MinIO Server version.
Configuring replication between sites with mismatched MinIO Server versions may result in unexpected or undesired replication behavior.
You should also ensure the :mc:`mc` version used to configure replication closely matches the server version.
Access to the Same Encryption Service Access to the Same Encryption Service
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~