Feature · External Backups

External Backups.

Push daily backups to your own S3-compatible bucket. Your bucket, your credentials, your retention policy. Works with Hetzner Object Storage, Backblaze B2, AWS S3, Wasabi, MinIO, or any other S3-API endpoint.
See pricing

7-day free trial · Cancel anytime · Pay with card, PayPal, or USDT

Feature

External Backups

BYO S3 destination. Your bucket, your retention, your keys.

More features
40smedian deploy time
99.94%fleet uptime · last 30d
6regions live
Auditedevery state change

What you get

The full external backups surface, end-to-end.

Every card below is a shipped capability. Hover for emphasis; click any matching feature for the deep page.

BYO S3 destination

Paste your bucket name, region, endpoint URL, access key, secret. We encrypt the credentials at rest and seal them in the DB. Test from the dashboard before saving.

Your retention, your rules

Set the lifecycle policy on the bucket — keep 30 days, keep 365 days, keep forever. The platform pushes; the bucket decides what to keep.

Database + recordings

Two streams: a daily MySQL dump (compressed, gzip-piped, single-transaction) and the recordings directory (incremental rsync to a date-partitioned prefix). Both run at 03:30, after the platform snapshot.

Restore-ready format

The DB dump is a regular mysqldump file — restore with `mysql < dump.sql.gz`. Recordings are stored at their original paths so you can rsync them back without rewriting metadata.

Any S3-compatible endpoint

AWS S3, Hetzner Object Storage, Backblaze B2, Wasabi, MinIO, Cloudflare R2, DigitalOcean Spaces — all tested. Custom S3-compatible endpoints work too; set the endpoint URL field.

Bandwidth throttle by default

20 MB/s default on the recordings rsync so your daily push does not saturate the line during a business hour. Tunable per server if your link can handle more.

Push verification

After each push we read back a manifest from the bucket and compare row + file counts. A mismatch pages the on-call before the customer sees it. The dashboard surfaces the last 30 days of push outcomes inline.

Cross-region for DR

Put the bucket in a different region (or different provider) from your VICIdial server. If the primary region has a bad day, your recordings + DB are recoverable elsewhere. We never write to a bucket we are not actively asked to.

Audit log entries

Every push (start, complete, fail) lands in AuditLog with byte counts + duration. Forensic teams that audit "did the backup actually run on day X" have proof in seconds.

FAQ

Questions worth answering

Push to your S3 bucket from day one.

Start the trial. Paste bucket credentials in the dashboard; the next 03:30 daily push lands offsite. Any S3-compatible endpoint, your retention rules.

All features