From ff4d39fa90c2fc5abb063b3e858f257b785830e9 Mon Sep 17 00:00:00 2001 From: Joao Fernandes Date: Tue, 12 Sep 2017 16:35:51 -0700 Subject: [PATCH] Improve DTR backup and restore (#4602) --- .../dtr/2.2/guides/admin/backups-and-disaster-recovery.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/datacenter/dtr/2.2/guides/admin/backups-and-disaster-recovery.md b/datacenter/dtr/2.2/guides/admin/backups-and-disaster-recovery.md index d2f96da773..0d14a58cd5 100644 --- a/datacenter/dtr/2.2/guides/admin/backups-and-disaster-recovery.md +++ b/datacenter/dtr/2.2/guides/admin/backups-and-disaster-recovery.md @@ -39,7 +39,7 @@ command backs up the following data: | Scan results | yes | | | Certificates and keys | yes | | | Image content | no | Needs to be backed up separately, depends on DTR configuration | -| Users, orgs, teams | no | Create a UCP backup to back up this data | +| Users, orgs, teams | no | Create a UCP backup to back up this data | | Vulnerability database | no | Can be re-downloaded after a restore | @@ -125,9 +125,6 @@ dtr-backup-v2.2.3/rethink/layers/ And the backup of the DTR metadata should look like: ```none -tar -tf /tmp/backup-metadata.tar - -# The archive should look like this dtr-backup-v2.2.1/ dtr-backup-v2.2.1/rethink/ dtr-backup-v2.2.1/rethink/properties/