Regional to global Upstash upgrade: export, import, cut over, no auto-upgrade
There is no auto-upgrade from regional to global. Export from the regional database and import into a new global one, then cut over.
Upgrading an Upstash regional database to global
The constraint
There is no in-place upgrade. A regional database cannot become a global one. You create a new global database and move the data.
The move
- Create the global database with the right primary region (where
your writes happen) and the read regions you need.
- Export from the regional database. RDB export or key-by-key
DUMP/RESTORE both work; pick by data size.
- Import into the global database.
- Verify: key counts, spot-checked values, TTLs.
- Cut over writes first, then reads. Keep the regional database
around until the global one has served clean traffic for a full TTL cycle.
What changes after the move
- Reads get faster worldwide; writes now travel to the primary
region, so measure write latency from your app region.
- Reads become eventually consistent across regions. If any flow
assumed read-your-writes, add the primary-region read or client-side hold for just-written values.
- Billing changes: replicated writes count as commands, and fixed
plans add per-read-region charges.
Verify
Same checks as any migration: key count parity, value spot checks, TTL preservation, and latency measurements from every region you serve before you delete the regional database.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.