# Reverting version after problematic update

**URL:** <https://meta.discourse.org/t/reverting-version-after-problematic-update/240656>\
**Category:** Self-hosting\
**Created:** [October 1, 2022, 5:51pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656 "2022-10-01T17:51:29Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [October 2, 2022, 2:37pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/8 "2022-10-02T14:37:45Z")

</div>

To avoid any database issues you will need to pinpoint the exact version in the backup and build a fresh instance on that, then restore your database.

The issue here is that you upgraded a production site without testing it first, if your site is important then you need to reduce the risk of these updates by first testing it on a representative staging copy.

---

_[View the full topic](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656)._