Maintenance and versions

Plexivo keeps your databases and caches patched for you. You choose when updates happen, you hear about them well ahead, and you can apply them early or, within limits, later.

Your maintenance window#

Each Plexivo Postgres, Plexivo MySQL and Plexivo Cache resource has a weekly window. Set it on the resource’s Maintenance tab, under Maintenance window: choose the Day, the start time in your organisation’s time zone, and the Length: 1, 2, 3, 4, 6 or 8 hours. Choose Save window. Anything already scheduled moves into the new window.

Until you choose, the window is by default Monday at 02:30 India Standard Time, for three hours.

Notice#

Plexivo emails your owners and admins when an update is scheduled, and again 24 hours before it starts. By default, updates are announced:

These announcements and reminders are always sent: they cannot be switched off in Settings → Notifications. Maintenance counts as announced only when the email reached every owner and admin. By default, maintenance announced at least five days ahead does not count against the SLA while it stays inside its window, for up to four hours.

Apply now or postpone#

The Scheduled list on the Maintenance tab shows each update, when it will run and the latest you can postpone it to.

• Apply now starts the update within a minute or two.
• Postpone a week moves it to your window at least seven days later, up to its limit.

What happens during an update#

• A database with a standby is updated standby first, then switches over to the updated standby instead of stopping.
• A single-instance database or a cache restarts once, so it is briefly unavailable.
• Backups keep running.
• If an update is not healthy within 45 minutes, Plexivo puts the previous version back automatically and tells you.

Plexivo App Runner apps and Plexivo Kubernetes workloads do not have a maintenance window.

Major version upgrades#

Moving Plexivo Postgres from 17 to 18 is your decision, made when you are ready.

1. Check. Plexivo runs pre-upgrade checks, such as extensions, replication slots, disk space and backups, and tells you anything to fix first.
2. Choose when. Now, or in your maintenance window. Type the database’s name to confirm.
3. Upgrade. Plexivo takes a backup, upgrades, checks the result and takes another backup. The database is offline while the upgrade itself runs.

If the upgrade fails, the database comes back on its old version, unchanged. You can cancel a scheduled upgrade until it starts. After a successful upgrade, the way back is the backup taken before it, restored into a new database.

Supported versions#

Plexivo MySQL and Plexivo Cache each run one major version and receive patch updates. The console marks a version that reaches the end of support within six months.