Back up Azure Database.
Azure Database runs PostgreSQL, MySQL with standard connectivity — which means encrypted, verified, off-platform backups take a connection string and three minutes.
Find your connection details
Azure Portal → your flexible server → Connect. Add a firewall rule for the worker's IP.
# host looks like:
myserver.postgres.database.azure.comTLS: Azure enforces TLS by default.
The manual way
PostgreSQL (port 5432):
pg_dump -h myserver.postgres.database.azure.com -U USER mydb | gzip > backup.sql.gzMySQL (port 3306):
mysqldump -h myserver.postgres.database.azure.com -u USER --single-transaction mydb | gzip > backup.sql.gzOne-shot and unencrypted. Scheduling, encryption, retention, verification and alerting are still on you — that's the part xbackupman automates.
The automated way
- 1. Add your Azure Database connection — the same host, user and password, encrypted at rest.
- 2. Point backups at storage you own (S3, R2, B2, MinIO, Drive…).
- 3. Pick a schedule — down to every 5 minutes; unchanged runs dedup to pointers.
FAQ
Does xbackupman support Azure Database?
Yes — Azure Database exposes standard PostgreSQL, MySQL connectivity, and xbackupman connects with the same credentials you use anywhere else. No special integration or agent is needed on the provider's side.
Are Azure Database backups encrypted?
Every dump is encrypted with AES-256-GCM using your organization's key before it leaves the worker, then stored in S3-compatible storage you own. Azure Database (and your storage provider) only ever see ciphertext.
Doesn't Azure Database already take backups?
Provider snapshots live inside the same account and platform as the database — one compromised credential or billing lapse can take both. Independent, encrypted, restore-verified copies in storage you control are what off-platform backups are for.