Erica Thompson 0660ea6fac
Update README (#31244)
* Update README

Let contributors know that docs will now be located in UDR

* Add comments to each mdx doc

Comment has been added to all mdx docs that are not partials

* chore: added changelog

changelog check failure

* wip: removed changelog

* Fix content errors

* Doc spacing

* Update website/content/docs/deploy/kubernetes/vso/helm.mdx

Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>

---------

Co-authored-by: jonathanfrappier <92055993+jonathanfrappier@users.noreply.github.com>
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
2025-07-22 08:12:22 -07:00

38 lines
1.3 KiB
Plaintext

---
layout: docs
page_title: recover - Command
description: |-
Use the recover command to pull data from a loaded snapshot and restore it at
the specified path.
---
> [!IMPORTANT]
> **Documentation Update:** Product documentation, which were located in this repository under `/website`, are now located in [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs), colocated with all other product documentation. Contributions to this content should be done in the `web-unified-docs` repo, and not this one. Changes made to `/website` content in this repo will not be reflected on the developer.hashicorp.com website.
# recover
@include 'alerts/enterprise-only.mdx'
The `recover` command pulls data at the specified path from a loaded snapshot
and restores it to the cluster, overwriting newer data on the same path.
@include 'recover/deletedmounts.mdx'
## Examples
Recover the KV version 1 secret at the path `my-secret` from the loaded snapshot with ID `2403d301-94f2-46a1-a39d-02be83e2831a`:
```shell-session
$ vault recover -snapshot-id=2403d301-94f2-46a1-a39d-02be83e2831a secret/my-secret
```
## Usage
The following flag is available in addition to the [standard set of
flags](/vault/docs/commands) included on all commands.
### Command options
- `snapshot-id` `(string: "")` - Specifies a loaded snapshot ID to recover
the data from.