From 9c43b9ad8a326af7075eecaa79d4f30f69f13b06 Mon Sep 17 00:00:00 2001 From: Joao Fernandes Date: Wed, 25 Oct 2017 10:50:22 -0700 Subject: [PATCH] Update e2e backup (#5087) * Update e2e backup --- enterprise/backup.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/enterprise/backup.md b/enterprise/backup.md index 6c649d6ea8..f0f4e9c840 100644 --- a/enterprise/backup.md +++ b/enterprise/backup.md @@ -8,15 +8,18 @@ keywords: enterprise, backup, restore To backup Docker Enterprise Edition you need to create individual backups for each of the following components: -1. Docker Engine. [Learn more](/engine/swarm/admin_guide/#back-up-the-swarm). -2. Universal Control Plane (UCP). [Learn more](/datacenter/ucp/2.2/guides/admin/backups-and-disaster-recovery/#backup-command). -3. Docker Trusted Registry (DTR). [Learn more](/datacenter/dtr/2.3/guides/admin/backups-and-disaster-recovery/#backup-dtr-data). +1. Docker Swarm. [Backup Swarm resources like service and network definitions](/engine/swarm/admin_guide.md#back-up-the-swarm). +2. Universal Control Plane (UCP). [Backup UCP configurations](/datacenter/ucp/2.2/guides/admin/backups-and-disaster-recovery.md). +3. Docker Trusted Registry (DTR). [Backup DTR configurations and images](/datacenter/dtr/2.3/guides/admin/backups-and-disaster-recovery.md). Before proceeding to backup the next component, you should test the backup you've created to make sure it's not corrupt. One way to test your backups is to do a fresh installation in a separate infrastructure and restore the new installation using the backup you've created. +If you create backups for a single component, you won't be able to restore your +deployment to its previous state. + ## Restore Docker Enterprise Edition You should only restore from a backup as a last resort. If you're running Docker