Version Upgrades
Miabi supports in-place version upgrades for managed database engines, so you can move to a newer release without rebuilding the database or rewiring your apps.
Before you upgrade
Take a backup first. A version upgrade migrates the on-disk data format. Always create a fresh backup before starting — see Storage & Backups. For Redis, note that backups are not yet supported, so plan accordingly.
Also worth doing ahead of time:
- Check your app's compatibility with the target engine version.
- Pick a low-traffic window — the database is briefly unavailable during the upgrade.
Performing the upgrade
From the database's detail page, open Upgrade, choose the target version, and confirm. Miabi then:
- Stops the database container cleanly.
- Migrates the data directory to the new engine version in place.
- Starts the database on the new version and re-checks health.
Credentials, the connection string, and the attached apps' injected environment variables stay the same — apps reconnect once the engine is healthy again.
What to expect
- Brief downtime — the database is offline for the duration of the migration.
- Same endpoint — host, port, and credentials are unchanged.
- One step at a time — for large version jumps, Miabi may guide you through intermediate versions where the engine requires it.
If anything looks wrong after the upgrade, your pre-upgrade backup is the safety net — restore it to roll back to the previous version.
Upgrades are available to Owners, Admins, and Developers. Because they involve downtime, coordinate with anyone relying on the database first.