# Help with rolling Upgrade

**URL:** <https://forums.percona.com/t/help-with-rolling-upgrade/4881>\
**Category:** Percona Server for MySQL 5.6\
**Created:** [May 6, 2016, 6:14am UTC](https://forums.percona.com/t/help-with-rolling-upgrade/4881 "2016-05-06T06:14:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![OS\_DBA](https://avatars.discourse-cdn.com/v4/letter/o/c2a13f/32.png) [@OS\_DBA](https://forums.percona.com/u/OS_DBA)\
**Post date:** [May 6, 2016, 6:14am UTC](https://forums.percona.com/t/help-with-rolling-upgrade/4881/1 "2016-05-06T06:14:31Z")

</div>

Architecture:  
MySQL 5.6.24 two node active-passive cluster managed by Pacemaker (with MySQL replication), with DRDB mirrored file system for the Magento application tier.

What we need to do:  
Rolling upgrade to 5.6.29, with no interruption to service and no data loss.

High Level Plan: [LIST=1]  
[_]Put Pacemaker in maintenance mode  
[_]Shutdown the slave database (database B).  
[_]Upgrade the MySQL binary packages for database B.  
[_]Start database B.  
[_]Run the upgrade script  
[_]Restart MySQL replication and let the Slave (B) resync with the master (A). Check DRBD is up to date.  
[_]Promote B to Master.  
[_]Shutdown the old master database (A)  
[_]Upgrade the MySQL binary packages for database A  
[_]Start database A.  
[_]Run the upgrade script  
[_]Restart MySQL replication and let it sync with database B. Check DRBD is up to date  
[_]Promote A to master  
[_]Turn Pacemaker maintenance mode off.  
[\*]Ensure Slave (B) resyncs with the master (A).  
[/LIST]

---

<div class="post-metadata">

**Author:** ![tsolodov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/tsolodov/32/1120_2.png) [@tsolodov](https://forums.percona.com/u/tsolodov)\
**Post date:** [May 23, 2016, 3:35am UTC](https://forums.percona.com/t/help-with-rolling-upgrade/4881/2 "2016-05-23T03:35:25Z")

</div>

Hi,

What file system are you using ? Is it distributed (GFS)?