Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document --encryption_key_file option in dgraph restore command. #5638

Merged
merged 2 commits into from
Jun 12, 2020
Merged

Document --encryption_key_file option in dgraph restore command. #5638

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
96837c3
Document --encryption_key_file option in dgraph restore command.
martinmr Jun 12, 2020
b6d841f
address comments.
martinmr Jun 12, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions wiki/content/enterprise-features/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -273,6 +273,10 @@ backups built on top of it. Each time a new full backup is created, a new backup
series with a different ID is started. The backup series ID is stored in each
`manifest.json` file stored in every backup folder.

The `--encryption_key_file` argument is required if you took the backup in an
martinmr marked this conversation as resolved.
Show resolved Hide resolved
encrypted cluster and should point to the location of the same key used to
run the cluster.

The restore feature will create a cluster with as many groups as the original
cluster had at the time of the last backup. For each group, `dgraph restore`
creates a posting directory `p<N>` corresponding to the backup group ID. For
Expand Down