minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-28 19:42:10 +03:00
Code Activity

DOCS-677: Update site replication recovery procedure (#694)

Browse Source 
Closes #677 

Updates the site replication recovery tutorial with slight tweaks to the multi-site expansion tutorial to account for the latest changes to MinIO/MC

Co-authored-by: Poorna <poornas@users.noreply.github.com>
This commit is contained in:
Ravind Kumar
2023-01-06 18:03:59 -05:00
committed by GitHub
parent c2dacd93f2
commit dbbfce1aeb
2 changed files with 84 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -346,12 +346,10 @@ The new site must meet the following requirements:
.. tab-item:: Command Line
:sync: cli
#. Deploy three or more separate MinIO sites, using the same external IDP
#. Deploy the new MinIO peer site(s) following the stated requirements.
Only one site can have any buckets or objects on it.
The other sites must be empty.
#. Configure an alias for each site
#. Configure an alias for the new site
.. include:: /includes/common-replication.rst
:start-after: start-mc-admin-replicate-load-balancing
@ -359,34 +357,28 @@ The new site must meet the following requirements:
To check the existing aliases, use :mc:`mc alias list`.
For example, for three MinIO sites, you might create aliases ``minio1``, ``minio2``, and ``minio3``.
Use :mc:`mc alias set` to define the hostname or IP of the load balancer managing connections to the site.
Use :mc:`mc alias set` to define the hostname or IP of the load balancer managing connections to the new site(s).
.. code-block:: shell
mc alias set minio1 https://minio1.example.com:9000 adminuser adminpassword
mc alias set minio2 https://minio2.example.com:9000 adminuser adminpassword
mc alias set minio3 https://minio3.example.com:9000 adminuser adminpassword
mc alias set minio4 https://minio4.example.com:9000 adminuser adminpassword
or define environment variables
.. code-block:: shell
export MC_HOST_minio1=https://adminuser:adminpassword@minio1.example.com
export MC_HOST_minio2=https://adminuser:adminpassword@minio2.example.com
export MC_HOST_minio3=https://adminuser:adminpassword@minio3.example.com
export MC_HOST_minio4=https://adminuser:adminpassword@minio4.example.com
#. Add site replication configuration
List all existing replicated sites first, then list the new site(s) to add.
In this example, ``minio1``, ``minio2``, and ``minio3`` are already configured for replication.
The command adds ``minio4`` and ``minio5`` as new sites to add to the replication.
``minio4`` and ``minio5`` must be empty.
Use the :mc-cmd:`mc admin replicate add` command to expand the site replication configuration with the new peer site.
Specify the alias of any existing healthy peer site as the first parameter and the alias of the new site as the second parameter.
For example, the following command adds the new peer site ``minio4`` to an existing site replication configuration on ``minio1``.
.. code-block:: shell
mc admin replicate add minio1 minio2 minio3 minio4 minio5
mc admin replicate add minio1 minio4
#. Query the site replication configuration to verify
@ -494,11 +486,15 @@ You can re-add the site at a later date, but you must first completely wipe buck
.. code-block:: shell
mc admin replicate remove <ALIAS> --all --force
mc admin replicate remove ALIAS PEER_TO_REMOVE --force
The ``-all`` flag removes the site as a peer from all participating sites.
- Replace ``ALIAS`` with the :ref:`alias <ref>` of any peer site in the replication configuration.
The ``--force`` flag is required to removes the site from the site replication configuration.
- Replace ``PEER_TO_REMOVE`` with the alias of the peer site to remove.
All healthy peers in the site replication configuration update to remove the specified peer automatically.
MinIO requires the ``--force`` flag to remove the peer from the site replication configuration.
.. _minio-site-replication-status-tutorial: