Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Rollback Process

Description

If there is an issue with a PMM upgrade, there should be a rollback process to recover the server back to the starting point.  As a DBA, every upgrade will normally have a documented process for rolling back all changes.  The same would be very useful for PMM upgrades.

If the user presses the upgrade button in the GUI, the system can be broken with no means to recover without working with Support.  This can become a critical issue for users using PMM for alerting in a Production environment.

At the very minimum, a well documented recovery process would be useful.  Ideally, the system should automatically rollback in the event of a failure.

How to test

None

How to document

None

Activity

Show:

Michal November 30, 2022 at 8:09 AM

Sounds good - we already add a date of backup but shall add the pmm version as well https://jira.percona.com/browse/PMM-11162

 

Denys Kondratenko November 29, 2022 at 9:06 PM

btw, we probably should default to do backup while doing upgrade, so if user wants to roll back there is a backup for it. somehow we probably need to track metadata for those backups to know what version it was taken from, or have that data inside the volume.

duygu.aksoy November 2, 2022 at 12:37 PM

OK, but we still need the documentation even if we get rid of upgrade from UI

Denys Kondratenko November 2, 2022 at 11:03 AM

As I understand there is no way to rollback from UI upgrade (CC   ). The only way to rollback (which is documented) is to get Backup (which was created before update) and start it with old image, that method available only for "image" replacement update.

this is another point to get rid from the package upgrade.

duygu.aksoy November 2, 2022 at 9:18 AM

who can help   this request? 

Details

Assignee

Reporter

Priority

Components

Labels

Needs QA

Needs Doc

Smart Checklist

Created October 31, 2022 at 4:04 PM
Updated December 11, 2024 at 10:57 AM