# Rollback Mysql version after upgrade

**URL:** <https://forums.percona.com/t/rollback-mysql-version-after-upgrade/31613>\
**Category:** MySQL & MariaDB\
**Created:** [July 15, 2024, 12:05pm UTC](https://forums.percona.com/t/rollback-mysql-version-after-upgrade/31613 "2024-07-15T12:05:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bones52](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@Bones52](https://forums.percona.com/u/Bones52)\
**Post date:** [July 15, 2024, 12:05pm UTC](https://forums.percona.com/t/rollback-mysql-version-after-upgrade/31613/1 "2024-07-15T12:05:22Z")

</div>

Hi There  
Hope all is well.  
We have run into an issue after a mysql upgrade to 8.0.36-28 from 8.0.28-19. We seem to be having endless locks on the db’s.  
Would like to know the process for rolling back to the previous version. What are the options.

Thanks

---

<div class="post-metadata">

**Author:** ![kedarpercona](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/kedarpercona/32/809_2.png) [@kedarpercona](https://forums.percona.com/u/kedarpercona)\
**Post date:** [July 15, 2024, 12:48pm UTC](https://forums.percona.com/t/rollback-mysql-version-after-upgrade/31613/2 "2024-07-15T12:48:37Z")

</div>

Hi @Bones52,

I think it is well established that downgrade to a previous version is not supported in MySQL 8. It has been [documented](https://dev.mysql.com/doc/refman/8.0/en/downgrading.html) and also [blogged](https://www.percona.com/blog/mysql-8-minor-version-upgrades-are-one-way-only/).

> Downgrade from a MySQL 8.0 release to a previous MySQL 8.0 release, is not supported. The only supported alternative is to restore a backup taken _before_ upgrading.

So, the option you have would be to restore from your last backup OR try-dump-load the data from current to older version may be on a different server (probably excluding system tables). Suggest you to test but yes, no rollback; sorry.

Thanks,  
K

---

<div class="post-metadata">

**Author:** ![Bones52](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@Bones52](https://forums.percona.com/u/Bones52)\
**Post date:** [July 15, 2024, 12:52pm UTC](https://forums.percona.com/t/rollback-mysql-version-after-upgrade/31613/3 "2024-07-15T12:52:44Z")

</div>

Thank you so much for that prompt response. Will try that suggestion. 👍

---

<div class="post-metadata">

**Author:** ![CTutte](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ctutte/32/1341_2.png) [@CTutte](https://forums.percona.com/u/CTutte)\
**Post date:** [July 15, 2024, 1:38pm UTC](https://forums.percona.com/t/rollback-mysql-version-after-upgrade/31613/4 "2024-07-15T13:38:44Z")

</div>

Physical backups are not supported for upgrade so depending on the data set size you might find [mydumper](https://github.com/mydumper/mydumper) useful (multi threaded).

---

<div class="post-metadata">

**Author:** ![meyerder](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/meyerder/32/16994_2.png) [@meyerder](https://forums.percona.com/u/meyerder)\
**Post date:** [July 22, 2024, 1:09pm UTC](https://forums.percona.com/t/rollback-mysql-version-after-upgrade/31613/5 "2024-07-22T13:09:03Z")

</div>

> [@Bones52](#):
>
> 8.0.28-19

Good luck getting a working backup… 8.0.28-19 was known quite a bit to have backup issues I had a issue with one of the 5 in my cluster and could NOT get a backup restored. I was told someplace on this site that all the .26-30 versions in MySQL had issues and was strongly suggested to upgrade… After spending 2-3 days TRYING to get a backup restored I upgraded all the other nodes and had no issues… (This was in the Cluster version though)