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

68 lines
1.8 KiB
Plaintext

---
layout: docs
page_title: Rollback upgrade
description: >-
Basic process for rolling back a Vault upgrade.
---
> [!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.
# Rollback a Vault upgrade
Vault supports in-place upgrades but does not support automatic rollbacks.
## Before you start
- **You must have `sudo` permissions on the Vault server**. Make sure you have
can install binaries on the Vault server.
- **You must have admin permissions for Vault**. Make sure you can stop and
start the Vault process.
- **Identify unseal candidates**. Identify and notify enough people with unseal
shards to meet the unseal threshold after restart.
## Basic rollback process
To rollback a Vault upgrade:
1. Use `SIGINT` or `SIGTERM` to shut down Vault.
<Tabs>
<Tab heading="Bash">
```shell-session
$ kill <vault_pid>
```
</Tab>
<Tab heading="Powershell">
```powershell
Stop-Process <vault_pid>
```
</Tab>
</Tabs>
1. [Install your previous version of Vault](/vault/docs/get-vault) over your
existing instance.
1. Replace the upgraded Vault data store with your pre-upgrade snapshot.
1. Replace the upgraded Vault configuration with your pre-upgrade configuration.
1. Start Vault.
1. Verify the current version:
```shell-session
$ vault status | grep Version
```
1. Unseal Vault.
1. Test the rollback.