Migrate Azure Database for PostgreSQL: Durable job state · Ample Computer
Migrate Azure Database for PostgreSQL: Durable job state
Move PostgreSQL data from Azure Database for PostgreSQL to Ample, one component at a time. Destination verified on Ample: a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true). Source procedure: Take a logical backup with pg_dump -Fc from an allowed network or private endpoint. Move separately: Microsoft Entra authentication, zone-redundant HA and PITR are Azure features; on Ample the app connects with injected credentials and backs up with pg_dump. Cutover: Freeze writes with the user's go-ahead, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep the Azure server until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.
What it runs on
- Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
You need
- Authorized access to the Azure Database for PostgreSQL source and its export tooling
- An inventory of every component in scope and out of scope
- A validated backup or copy before any cutover
- An Ample account token with servers:write, databases:read
Exact tested configuration
build npm run build --if-present
install npm install
runtime node
sizes-1vcpu-1gb
start npm run start
template node-22
Steps
Inventory the source. List what Azure Database for PostgreSQL provides beyond the component you are moving. Plan these separately: Microsoft Entra authentication, zone-redundant HA and PITR are Azure features; on Ample the app connects with injected credentials and backs up with
pg_dump.Source step 1. Take a logical backup with
pg_dump -Fcfrom an allowed network or private endpoint.Source step 2. Check the engine major version, extensions and server parameters the app depends on.
Source step 3. Restore into a scratch managed database first and compare row counts.
Provision and restore. Deploy the app once so a managed PostgreSQL 16 database exists (or create one with
ample database create --engine postgres), then restore the dump withpg_restoreusing its connection string; keep migrations idempotent.
$ ample database create --name <db-name> --engine postgres
Validate before cutover. Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/durable-job-state).
Cut over. Freeze writes with the user's go-ahead, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep the Azure server until confirmed.
Rollback. Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.
How it was checked
✓ destination app responds on its public URL · http get/ → “ample canary express patterns”
✓ durable-job-state check from the destination example · http get/p/durable-job-state → “see the pattern fixture checks”
✓ data or object counts and checksums match the source · manual → “operator comparison before cutover”
Evidence
- November 5, 2026 · canary run
Destination side verified: the Express pattern fixture deployed on Ample (npm install, npm run build --if-present, npm run start on the node-22 template) and its checks passed (a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true)). The source-side export from Azure Database for PostgreSQL uses the vendor's standard tooling.
Tested examples
- Express pattern fixture (destination). Verified destination basis: durable job state.
What it doesn’t cover
- A step-by-step guide: each stage is an ordinary
ample deploy,ample databaseorample bucketcommand you run. - The destination side was verified on Ample with the pattern fixture; the source-side steps use Azure Database for PostgreSQL's standard tooling.
- Plan separately: Microsoft Entra authentication, zone-redundant HA and PITR are Azure features; on Ample the app connects with injected credentials and backs up with
pg_dump. - Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector. Back up and restore with
pg_dumpandpg_restore.