# Problems upgrading PMM server from 2.28 to 3 **URL:** \ **Category:** PMM 3.x\ **Created:** [March 26, 2025, 11:03am UTC](https://forums.percona.com/t/problems-upgrading-pmm-server-from-2-28-to-3/37368 "2025-03-26T11:03:24Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![DavidHarper](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/davidharper/32/20582_2.png) [@DavidHarper](https://forums.percona.com/u/DavidHarper)\ **Post date:** [March 26, 2025, 11:03am UTC](https://forums.percona.com/t/problems-upgrading-pmm-server-from-2-28-to-3/37368/1 "2025-03-26T11:03:24Z")
I’m running PMM Server v2.28 in a Docker container. I want to upgrade to PMM 3, but when I follow the official upgrade instructions headed “Migrate PMM 2 to PMM 3” at the Percona docs web site, it fails at the first step, “Upgrade PMM 2 Server to the latest version”. Looking at the logs, I see “Could not resolve host: [mirrorlist.centos.org](http://mirrorlist.centos.org); Unknown error” and when I dig into this, I find it’s because [centos.org](http://centos.org) no longer provides a Yum repo for Centos 7. My PMM Server installation was completely broken at this point and I had to restore it from a backup of the Docker volume. I then tried upgrading directly from 2.28 to 3, but that also failed. Has anyone found an upgrade procedure that works for Docker installations that are using Centos 7 as the base image? If there’s no in-place upgrade path, then is it possible to export the data from my PMM 2.28 server and import it into an empty PMM 3 server? ---
**Author:** ![Abhinav\_Gupta](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/abhinav_gupta/32/6262_2.png) [@Abhinav\_Gupta](https://forums.percona.com/u/Abhinav_Gupta)\ **Post date:** [March 26, 2025, 2:01pm UTC](https://forums.percona.com/t/problems-upgrading-pmm-server-from-2-28-to-3/37368/2 "2025-03-26T14:01:43Z")
To upgrade PMM 2.28 to the latest PMM 2.xx version, follow the staged approach mentioned in the documentation below. > **[Percona Monitoring and Management - Upgrade](https://docs.percona.com/percona-monitoring-and-management/2/how-to/upgrade.html#staged-upgrade-approach)** > > Documentation Once you have the latest PMM 2.xx version available, you can proceed with the upgrade to PMM 3 as per the documentation. > **[Percona Monitoring and Management - Migrate PMM 2 to PMM 3](https://docs.percona.com/percona-monitoring-and-management/3/pmm-upgrade/migrating_from_pmm_2.html)** > > PMM 3 introduces significant architectural changes that require gradual transition from PMM 2. About “`Could not resolve host: [mirrorlist.centos.org](http://mirrorlist.centos.org/); Unknown error`” you could check the solution mentioned here to update the repo manually as [mirrorlist.centos.org](http://mirrorlist.centos.org) doesn’t exist anymore after 2024. > ---
**Author:** ![DavidHarper](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/davidharper/32/20582_2.png) [@DavidHarper](https://forums.percona.com/u/DavidHarper)\ **Post date:** [March 27, 2025, 7:58am UTC](https://forums.percona.com/t/problems-upgrading-pmm-server-from-2-28-to-3/37368/3 "2025-03-27T07:58:23Z")
Hi Abhinav, Thank you for the suggestions. I appreciate you taking the time to reply. The CentOS Yum repo fix now allows the PMM-initiated upgrade to the latest 2.xx release to proceed without trashing the system, but I am left with a PMM 2.42.0 server that has “forgotten” all of the hosts and services and their histories. I presume this is because an upgrade from 2.28 directly to 2.42 hits the bug whose fix is a staged upgrade, first to 2.33 and then to 2.42. However, the instructions for performing a staged upgrade are – unusually for Percona documentation – not very clear. None of the issues listed under the heading “Upgrade issues” seems to apply in my case, so I don’t know whether any of the fixes would help me. I would be grateful for pointers to further advice on performing a staged upgrade 2.28 =\> 2.33 =\> 2.42. David ---
**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\ **Post date:** [March 28, 2025, 8:36am UTC](https://forums.percona.com/t/problems-upgrading-pmm-server-from-2-28-to-3/37368/4 "2025-03-28T08:36:48Z")
Hello @DavidHarper , let me look into it with the team and get back to you with the answer. We will find a way. ---
**Author:** ![DavidHarper](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/davidharper/32/20582_2.png) [@DavidHarper](https://forums.percona.com/u/DavidHarper)\ **Post date:** [March 28, 2025, 9:02am UTC](https://forums.percona.com/t/problems-upgrading-pmm-server-from-2-28-to-3/37368/5 "2025-03-28T09:02:13Z")
Hi Sergey, Thanks for your kind reply. I have a copy of my live PMM system where I can test any solutions that you and your team propose. David ---
**Author:** ![DavidHarper](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/davidharper/32/20582_2.png) [@DavidHarper](https://forums.percona.com/u/DavidHarper)\ **Post date:** [April 8, 2025, 7:19am UTC](https://forums.percona.com/t/problems-upgrading-pmm-server-from-2-28-to-3/37368/6 "2025-04-08T07:19:09Z")
Hi Sergey, Have the team been able to find a solution? Best regards David