From dd86217b3fc012a6eeb2e2e015b5a40e25232497 Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Thu, 27 Apr 2017 04:43:59 +0800 Subject: [PATCH] Update backup.md (#3075) --- datacenter/dtr/2.2/reference/cli/backup.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/datacenter/dtr/2.2/reference/cli/backup.md b/datacenter/dtr/2.2/reference/cli/backup.md index 32ad02d724..3f5ea2c6ad 100644 --- a/datacenter/dtr/2.2/reference/cli/backup.md +++ b/datacenter/dtr/2.2/reference/cli/backup.md @@ -17,16 +17,16 @@ docker run -i --rm docker/dtr \ This command creates a tar file with the contents of the volumes used by -DTR, and prints it. You can then use the 'restore' command to restore the data +DTR, and prints it. You can then use the `restore` command to restore the data from an existing backup. Note: * This command only creates backups of configurations, and image metadata. - It doesn't backup users and organizations. Users and organizations can be + It doesn't back up users and organizations. Users and organizations can be backed up when performing a UCP backup. - It also doesn't backup the Docker images stored in your registry. + It also doesn't back up the Docker images stored in your registry. You should implement a separate backup policy for the Docker images stored in your registry, taking in consideration whether your DTR installation is configured to store images on the filesystem or using a cloud provider.