Back up Aiven.
Aiven runs PostgreSQL, MySQL, Redis with standard connectivity — which means encrypted, verified, off-platform backups take a connection string and three minutes.
Find your connection details
Aiven Console → your service → Overview → Connection information (host, port and password are all there).
# host looks like:
pg-mydb-myproject.aivencloud.comTLS: Aiven enforces TLS on every service.
The manual way
PostgreSQL (port 5432):
pg_dump -h pg-mydb-myproject.aivencloud.com -U USER mydb | gzip > backup.sql.gzMySQL (port 3306):
mysqldump -h pg-mydb-myproject.aivencloud.com -u USER --single-transaction mydb | gzip > backup.sql.gzRedis (port 6379):
redis-cli -h pg-mydb-myproject.aivencloud.com --rdb - | 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 Aiven 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 Aiven?
Yes — Aiven exposes standard PostgreSQL, MySQL, Redis 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 Aiven 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. Aiven (and your storage provider) only ever see ciphertext.
Doesn't Aiven 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.