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

Update e2e backup (#5087) 

* Update e2e backup
This commit is contained in:
Joao Fernandes 2017-10-25 10:50:22 -07:00 committed by GitHub
parent 51dd725ecc
commit 9c43b9ad8a
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
enterprise/backup.md
View File

@ -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