Plexivo MySQL standby and read replicas

A standby keeps your Plexivo MySQL serving when its primary fails, at the same address. Read replicas keep more live copies of your data.

Standby and automatic failover#

A standby is a second copy of your database, kept up to date by replication and placed on a different server whenever one is available. If the primary fails, Plexivo promotes the standby automatically, and your app keeps the same address throughout.

• Business: every database includes a standby.
• Developer, Startup and Enterprise: tick Standby with automatic failover when you create the database.

With a standby, updates are applied to the standby first and then switched over, so patching does not stop your database.

Read replicas#

Read replicas keep live copies of the database, slightly behind the primary. Your connections use the database’s usual address.

Add them when you create the database, or later on the Replicas tab with the Read replicas stepper. Each replica is one more instance of the database at its size, charged by the day.

By default, each plan allows:

Maintenance#

Updates arrive in your weekly maintenance window, after an email telling you what and when. See Maintenance and patches; it works the same way for Plexivo MySQL.

Next steps#