upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-02-18 18:38:08 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 7

Docs: update restore snapshot content (#31231)

Browse source 
- Correct unseal example for CLI
This commit is contained in:
Brian Shumate 2025-07-09 09:11:41 -04:00 committed by GitHub
parent baf4f84373
commit b2b237991e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 11 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
website/content/docs/sysadmin/snapshots/restore.mdx
View file

@ -106,34 +106,31 @@ $ curl \
</Tabs>
## Step 4: Unseal Vault
<Tabs>
<Tab heading="CLI" group="cli">
Run
[`vault operator raft snapshot restore`](/vault/docs/commands/operator/raft#snapshot-restore)
with the local snapshot file path and the `-force` flag:
Have each person with an unseal key share run
`vault operator unseal` with their original unseal
key until reaching the number of key shares required by your origial quroum
configuration to unseal your Vault cluster:
```shell-session
$ vault operator raft snapshot restore -force <local_file_path>
$ vault operator unseal
```
For example:
Enter the unseal key when prompted:
<CodeBlockConfig hideClipboard>
```shell-session
$ vault operator raft snapshot restore -force /tmp/snapshots/backup.snap
```plaintext
Unseal Key (will be hidden):
```
</CodeBlockConfig>
You must use the `-force` flag as the auto-unseal or Shamir keys are not
consistent with the snapshot data, which came from a different cluster.
</Tab>