From cdddbbe31f528474c73ecd1e587618ce933dbcf2 Mon Sep 17 00:00:00 2001 From: Joao Fernandes Date: Mon, 21 Aug 2017 16:01:27 -0700 Subject: [PATCH] Fix broken link --- .../ucp/2.1/guides/admin/backups-and-disaster-recovery.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md b/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md index e464c2861c..e3f93687c0 100644 --- a/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md +++ b/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md @@ -148,9 +148,9 @@ manager failures, the system should be configured for [high availability](config `uninstall-ucp` command. 4. Perform a restore operation on the recovered swarm manager node. 5. Log in to UCP and browse to the nodes page, or use the CLI `docker node ls` - command. + command. 6. If any nodes are listed as `down`, you'll have to manually [remove these - nodes](../configure/scale-your-cluster.md) from the cluster and then re-join + nodes](configure/scale-your-cluster.md) from the cluster and then re-join them using a `docker swarm join` operation with the cluster's new join-token. ## Where to go next