Skip to content

Activating a Standby Server

When a production server fails, this is how you put a standby in its place.

The principle

In Odizy, promoting an Odoo server from standby to production is driven by the database.

The production server is the one whose database cluster is the primary — the one open for writing. So changing which cluster is primary changes which Odoo server is in production.

Procedure

  1. Open Muppy / Databases / PostgreSQL / Replicated Cluster Set (RCS).
  2. Open the RCS you want to reconfigure. Its form lists the replicated clusters: the primary, and its standbys.
  3. On the line of the standby you want to promote, click Set as Primary.

Muppy promotes that cluster and reconfigures every member of the set around it — see Restructuring an RCS for what the operation does and for the other member-level actions.

  1. Wait for the end-of-failover notification.
  2. Open your Odoo server at the URL of the server that has just been activated — its fallback URL.

Note

On a set with High Availability activated, the promotion can also be triggered automatically by the pglookout daemons rather than by hand. See High Availability.