Back up Azure Database for PostgreSQL, and prove it restores
Restore-tested backups of your Azure Database for PostgreSQL Flexible Server, written to storage you control. Add one firewall rule, use a read-only role, 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 Azure
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 Azure, 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 Azure, step by step
The Azure-specific settings, from the connection string to network access. Everything after that is the standard Protect form: schedule, retention and restore testing.
Copy the server name
In the Azure portal, open your flexible server. On Overview, copy the Server name (
<server-name>.postgres.database.azure.com) and note the admin username. Use this name rather than an IP, because Azure's underlying IP can change.Create a read-only role
The admin user belongs to
azure_pg_admin, which is more than a backup needs. Sign in once and create a role such asnorcube_backupwithCONNECT, schemaUSAGEandSELECT.Add a firewall rule for Norcube
Under Settings → Networking → Firewall rules, add a rule with both start and end IP set to
18.196.207.101, then save. Changes can take up to five minutes. You don't need Allow public access from any Azure service.Paste it into Norcube with SSL required
Choose Protect a database, pick PostgreSQL and enter the host, port
5432, database and the read-only role. Azure enforces encrypted connections, so set SSL mode torequire. Don't add client certificates.
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.
Azure backups, answered
The questions that come up when backing up Azure Database for PostgreSQL. The full guide is in the docs.
Does this work with Single Server?
Can Norcube reach a server with private access (VNet)?
Why does a restore test mention azure_ai or azure_storage?
azure_storage, azure_ai, pg_diskann), they only exist on Azure's platform. A restore test notes their absence as expected and still records a clean Passed. Common extensions like pgvector or postgis restore normally.Is verify-full supported?
require is enough to satisfy Azure's encryption requirement.Your Azure data, backed up and tested
Start on the Free plan. No credit card required. Connect Azure, pick a schedule and let the first restore test prove it.
- Free plan
- No credit card
- Standard formats
- Restore-tested