Add screenshot for backup warning, minor edits

This commit is contained in:
Maria Bermudez 2019-01-14 19:36:09 -08:00
parent 46145f7bf9
commit c48ecb4bad
2 changed files with 12 additions and 10 deletions

View File

@ -25,33 +25,35 @@ Docker Trusted Registry maintains data about:
This data is persisted on the host running DTR, using named volumes. This data is persisted on the host running DTR, using named volumes.
[Learn more about DTR named volumes](../../architecture.md). [Learn more about DTR named volumes](../../architecture.md).
To perform a backup of a DTR node, run the `docker/dtr backup` command. This To perform a backup of a DTR node, run the [docker/dtr backup](/reference/dtr/2.6/cli/backup/) command. This
command backups up the following data: command backups up the following data:
| Data | Backed up | Description | | Data | Backed up | Description |
|:-----------------------------------|:----------|:---------------------------------------------------------------| |:-----------------------------------|:----------|:---------------------------------------------------------------|
| Configurations | yes | DTR settings | | Configurations | yes | DTR settings |
| Repository metadata | yes | Metadata like image architecture and size | | Repository metadata | yes | Metadata such as image architecture and size |
| Access control to repos and images | yes | Data about who has access to which images | | Access control to repos and images | yes | Data about who has access to which images |
| Notary data | yes | Signatures and digests for images that are signed | | Notary data | yes | Signatures and digests for images that are signed |
| Scan results | yes | Information about vulnerabilities in your images | | Scan results | yes | Information about vulnerabilities in your images |
| Certificates and keys | yes | TLS certificates and keys used by DTR | | Certificates and keys | yes | TLS certificates and keys used by DTR |
| Image content | no | Needs to be backed up separately, depends on DTR configuration | | Image content | no | Needs to be backed up separately, depends on DTR configuration |
| Users, orgs, teams | no | Create a UCP backup to backup 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 | | Vulnerability database | no | Can be redownloaded after a restore |
## Backup DTR data ## Back up DTR data
To create a backup of DTR you need to: To create a backup of DTR you need to:
1. Backup image content 1. Back up image content
2. Backup DTR metadata 2. Back up DTR metadata
You should always create backups from the same DTR replica, to ensure a smoother You should always create backups from the same DTR replica, to ensure a smoother
restore. restore. If you have not previously performed a backup, the web interface displays a warning for you to do so:
### Backup image content ![](/ee/dtr/images/backup-warning.png)
### Back up image content
Since you can configure the storage backend that DTR uses to store images, Since you can configure the storage backend that DTR uses to store images,
the way you backup images depends on the storage backend you're using. the way you backup images depends on the storage backend you're using.
@ -71,7 +73,7 @@ If you're using a different storage backend, follow the best practices
recommended for that system. recommended for that system.
### Backup DTR metadata ### Back up DTR metadata
To create a DTR backup, load your UCP client bundle, and run the following To create a DTR backup, load your UCP client bundle, and run the following
command, replacing the placeholders for the real values: command, replacing the placeholders for the real values:

Binary file not shown.

After

Width:  |  Height:  |  Size: 50 KiB