Back up DigitalOcean Managed PostgreSQL, and prove it restores
Restore-tested backups of your DigitalOcean managed PostgreSQL, written to storage you control. Use the direct database on port 25060, add one trusted source, and every backup can prove it restores.
- Spin up a throwaway database
- Restore the backup
- Check the data came back 48 of 48 tables
- Delete the throwaway database
A second copy, outside DigitalOcean
An off-site backup is the one you can still reach when something goes wrong with the platform or the account. Norcube keeps it outside DigitalOcean, in storage you control, and proves it restores.
Off-site, in storage you control
Norcube runs a full pg_dump on your schedule and writes the encrypted archive to Norcube-managed storage in Frankfurt or to your own S3-compatible bucket.
Proven to restore
Every backup can be restore-tested: Norcube restores it into a throwaway database and confirms your schemas, tables and rows come back.
Yours, in a standard format
Download any backup and restore it with standard Postgres tools, independent of Norcube. No proprietary format, no lock-in.
Connect DigitalOcean, step by step
The DigitalOcean-specific settings, from the connection string to network access. Everything after that is the standard Protect form: schedule, retention and restore testing.
Open the connection details
In the DigitalOcean control panel, open Databases, select your cluster, and find Connection details on the Overview tab. Keep the network selector on Public network.
Pick the database, not a pool
Leave the Database/Pool selector on your database (for example
defaultdb). Connection pools run PgBouncer on port25061, and a transaction-mode pool breakspg_dump. The direct database listens on25060.Copy the connection string
Switch the format to Connection string. It looks like
postgresql://doadmin:<password>@<cluster>-do-user-000000-0.k.db.ondigitalocean.com:25060/defaultdb?sslmode=require. For least privilege, use a read-only role instead ofdoadmin.Add Norcube as a trusted source
On the Settings tab, edit Trusted Sources and add
18.196.207.101as an IP address. Once any trusted source exists, the cluster only accepts connections from the list.Paste it into Norcube with SSL required
Choose Protect a database, pick PostgreSQL and paste the details with port
25060and SSL moderequire. You don't need DigitalOcean's CA certificate.
What Norcube adds
Restore testing
Prove each backup restores, not just that the dump ran. A Passed badge per backup and a restore-health score per database show recoverability at a glance.
Failure and missed-backup alerts
Get notified when a backup fails, a restore test can't confirm your data, or a schedule silently stops. By email, Slack or a signed webhook, on every plan.
Your own bucket
Keep backups in Norcube-managed storage in Frankfurt, or in your own Amazon S3, Cloudflare R2, Backblaze B2, Wasabi or MinIO bucket.
Standard archives
Every backup is a standard pg_dump archive, gzip-compressed by default. Download it any time.
DigitalOcean backups, answered
The questions that come up when backing up DigitalOcean Managed PostgreSQL. The full guide is in the docs.
Why port 25060 and not 25061?
25060 is the direct database. 25061 is a connection pool running PgBouncer, and a transaction-mode pool breaks pg_dump.Will restore tests flag DigitalOcean-specific extensions?
pgvector or pgcrypto, so restore tests run clean.What if my database uses PostGIS or TimescaleDB?
Should I use the VPC network connection?
Your DigitalOcean data, backed up and tested
Start on the Free plan. No credit card required. Connect DigitalOcean, pick a schedule and let the first restore test prove it.
- Free plan
- No credit card
- Standard formats
- Restore-tested