Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

Switchover / Failover of Async replication

Pre-requisits

Make sure both Rome and Lisbon Clusters are deployed using the Async Deployment manual!

Switchover (safe)

Assuming Rome is currently Primary and you want to promote Lisbon to be new primary
(Rome will be converted to StandBy member):


juju run -m lisbon db2/leader promote-to-primary

Failover (forced)

Warning: this is a dangerous operation which can cause the split-brain situation. It should be executed if Primary cluster is no longer exist (lost) ONLY! Otherwise please use safe switchover procedure above!

Assuming Rome was a Primary (before we lost the cluster Rome) and you want to promote Lisbon to be the new primary:


juju run -m lisbon db2/leader promote-to-primary force=True

Warning: The force will cause the old primary to be invalidated.

Last updated 2 months ago. Help improve this document in the forum.