# Upgrading Foundationdb 7.0.0+

**URL:** <https://forums.foundationdb.org/t/upgrading-foundationdb-7-0-0/3361>\
**Category:** Using FoundationDB\
**Created:** [June 7, 2022, 1:41pm UTC](https://forums.foundationdb.org/t/upgrading-foundationdb-7-0-0/3361 "2022-06-07T13:41:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stefan-kiss](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/stefan-kiss/32/1359_2.png) [@stefan-kiss](https://forums.foundationdb.org/u/stefan-kiss)\
**Post date:** [June 7, 2022, 1:41pm UTC](https://forums.foundationdb.org/t/upgrading-foundationdb-7-0-0/3361/1 "2022-06-07T13:41:12Z")

</div>

With the release of the 7.0.0 (and following versions)

Did the recommended upgrade procedure remain the same ?

- overwrite binaries (or symlink to binaries)
- kill all processes from fdbcli
- wait for fdbmonitor to restart them

Also another question - in regards to multi-region setup - do we also have to atomically restart processes on all the region at the same time or we can stage this operation ?

(example restart process in region 1, then after everything is done restart in second region?

Link to the known procedure below.

> [@Upgrading FoundationDB](https://forums.foundationdb.org/t/upgrading-foundationdb/191/2):
>
> You are correct that major/minor releases of FoundationDB are always protocol incompatible, and patch releases are always protocol compatible. This means that rolling upgrades are not an option between major/minor versions. Hopefully I can provide a little bit of insight into why we made this choice. The first consideration is that the master, proxies, resolvers, and transaction logs are a unit in FoundationDB. If any process recruited as any of those roles fail, we recruit all new versions of …

---

<div class="post-metadata">

**Author:** ![johscheuer](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@johscheuer](https://forums.foundationdb.org/u/johscheuer)\
**Post date:** [June 8, 2022, 5:10am UTC](https://forums.foundationdb.org/t/upgrading-foundationdb-7-0-0/3361/2 "2022-06-08T05:10:34Z")

</div>

The procedure to upgrade your cluster to 7.0.0 or 7.1+ is still the same as before. If you want to upgrade you cluster you should make use of 7.1.6 (or newer) since the older version had a bug in `fdbcli kill` ([revert "kill" command to previous 7.0 behavior by sfc-gh-etschannen · Pull Request #7149 · apple/foundationdb · GitHub](https://github.com/apple/foundationdb/pull/7149)) that could lead to some issues during the kill command.

In a multi-region setup you have to upgrade all processes “at once” otherwise the other region is not able to communicate with the upgraded processes.