Skip to content

Docs: update restore snapshot content #31231

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

Merged
brianshumate merged 1 commit into from
Jul 9, 2025
Merged

Docs: update restore snapshot content #31231

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
25 changes: 11 additions & 14 deletions website/content/docs/sysadmin/snapshots/restore.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>

Expand Down
Loading