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

Clarify image restore topic (#2923) 

* restore doc updated

* changed the text a little bit

* changed the text according to requirement
This commit is contained in:
Prashant 2017-04-21 01:18:33 +05:30 committed by Misty Stanley-Jones
parent d9797820ca
commit c5d9a28bcc
5 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
datacenter/dtr/2.0/high-availability/backups-and-disaster-recovery.md
View File

@ -86,10 +86,9 @@ $ tar -tf /tmp/backup.tar
## Restore DTR data ## Restore DTR data
You can restore a DTR node from a backup using the `docker/dtr restore`
command.
This command performs a fresh installation of DTR, and reconfigures it with This command performs a fresh installation of DTR, and reconfigures it with
the configuration created during a backup. the configuration created during a backup.
When restoring, make sure you use the same version of the `docker/dtr` image that you've used to create the backup.
The command starts by installing DTR, restores the configurations stored on The command starts by installing DTR, restores the configurations stored on
etcd, and then restores the repository metadata stored on RethinkDB. You etcd, and then restores the repository metadata stored on RethinkDB. You

3
datacenter/dtr/2.1/guides/high-availability/backups-and-disaster-recovery.md
View File

@ -81,10 +81,9 @@ $ tar -tf /tmp/backup.tar
## Restore DTR data ## Restore DTR data
You can restore a DTR node from a backup using the `restore`
command.
This command performs a fresh installation of DTR, and reconfigures it with This command performs a fresh installation of DTR, and reconfigures it with
the configuration created during a backup. the configuration created during a backup.
When restoring, make sure you use the same version of the `docker/dtr` image that you've used to create the backup.
The command starts by installing DTR, restores the configurations stored on The command starts by installing DTR, restores the configurations stored on
etcd, and then restores the repository metadata stored on RethinkDB. You etcd, and then restores the repository metadata stored on RethinkDB. You

1
datacenter/ucp/1.1/high-availability/backups-and-disaster-recovery.md
View File

@ -63,6 +63,7 @@ Enter passphrase: secret
The example below shows how to restore a UCP controller node from an existing The example below shows how to restore a UCP controller node from an existing
backup. backup.
When restoring, make sure you use the same version of the `docker/dtr` image that you've used to create the backup.
First find out the Id of the UCP replica you want to restore: First find out the Id of the UCP replica you want to restore:

2
datacenter/ucp/2.0/guides/high-availability/backups-and-disaster-recovery.md
View File

@ -59,6 +59,8 @@ $ docker run --rm -i --name ucp \
docker/ucp restore --passphrase "secret" < backup.tar docker/ucp restore --passphrase "secret" < backup.tar
``` ```
When restoring, make sure you use the same version of the `docker/dtr` image that you've used to create the backup.
## Restore your cluster ## Restore your cluster
The restore command can be used to create a new UCP cluster from a backup file. The restore command can be used to create a new UCP cluster from a backup file.

1
datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md
View File

@ -77,6 +77,7 @@ $ gpg --decrypt /tmp/backup.tar | tar --list
## Restore your cluster ## Restore your cluster
The restore command can be used to create a new UCP cluster from a backup file. The restore command can be used to create a new UCP cluster from a backup file.
When restoring, make sure you use the same version of the `docker/dtr` image that you've used to create the backup.
After the restore operation is complete, the following data will be recovered After the restore operation is complete, the following data will be recovered
from the backup file: from the backup file: