docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update back-up-swarm.md (#9496) 

- Typo on symbol
- Added word "manager" to clarify the type of nodes where the procedure will be repeated.
This commit is contained in:
Jose J. Escobar 2019-09-23 09:50:50 -07:00 committed by Olly P
parent af803ce80d
commit 64c8e6c6ed
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ee/admin/backup/back-up-swarm.md
View File

@ -30,7 +30,7 @@ You must perform a manual backup on each manager node, because logs contain node
[Lock your swarm to protect its encryption key](/engine/swarm/swarm_manager_locking.md). [Lock your swarm to protect its encryption key](/engine/swarm/swarm_manager_locking.md).
2. Because you must stop the engine of the manager node before performing the backup, having three manager 2. Because you must stop the engine of the manager node before performing the backup, having three manager
nodes is recommended for high availability [HA]). For a cluster to be operational, a majority of managers nodes is recommended for high availability (HA). For a cluster to be operational, a majority of managers
must be online. If less than 3 managers exists, the cluster is unavailable during the backup. must be online. If less than 3 managers exists, the cluster is unavailable during the backup.
> **Note**: During the time that a manager is shut down, your swarm is more vulnerable to > **Note**: During the time that a manager is shut down, your swarm is more vulnerable to
@ -76,7 +76,7 @@ You must perform a manual backup on each manager node, because logs contain node
``` ```
systemctl start docker systemctl start docker
``` ```
7. Except for step 1, repeat the previous steps for each node. 7. Except for step 1, repeat the previous steps for each manager node.
### Where to go next ### Where to go next