Upload without useful alerts
The put to the bucket failed overnight and only shows up when someone needs the backup.
S3 backup
Backup to Amazon S3 or S3-compatible storage with preflight and monitoring.
Send database dumps to the S3 bucket you control (BYOS). Zault runs policies, monitored jobs, and restore with a destination snapshot — without leaving files only on the server disk.
Amazon S3 destination
Preflight
Schedule
Health
Restore
S3
The real risk
Local dumps without predictable S3 destination
Scripts that write to disk or upload to S3 without monitoring fail quietly and make retention hard.
Object in S3 ≠ rehearsed restore
Having the file in the bucket does not guarantee a safe recovery into the target database.
IAM and cron everywhere
Every server keeps its own credentials and scripts — hard to audit destination and retention.
How Zault helps
S3 as storage for the Zault routine
Connect the bucket, validate the destination, schedule routines, and track jobs — ownership and retention under your control.
Destination preflight
Validates bucket access and permissions before the first run.
Controlled schedule and triggers
Manual or scheduled routines in the dashboard, with a clear history for every upload.
Health map and success rate
Continuous visibility for jobs writing to S3 — without relying on scattered server logs.
Restore with confirmation and snapshot
Restore flow from storage, with pre-checks and an automatic destination snapshot.
BYOS on Amazon S3
Files in your bucket — or supported S3-compatible storage — with retention and ownership under your control.
Positioning
Local scripts vs S3 destination on Zault
The difference is not only pointing at a bucket — it is operating backup and restore predictably into S3.
Traditional approach
- Local dump + aws s3 cp on cron
- File logs or occasional email
- Improvised download under pressure
- Little visibility into upload failures
With Zault
- Policies, preflight, and validated S3 destination
- Dashboard, jobs, and health map
- Restore with preflight and destination snapshot
- BYOS in your bucket with retention
Common questions
S3 backup in practice
Why not a script with aws s3 cp?+
Upload is only one step. Without preflight, monitoring, and rehearsed restore, failures show up late. Zault treats S3 as the destination of a full operational routine.
How does restore from S3 work?+
The flow includes pre-checks and an automatic snapshot of the target database before changing data, with explicit confirmation in the dashboard.
Amazon S3 only?+
You can use Amazon S3 or supported S3-compatible storage — in the BYOS model, files stay in the bucket you configure.
Which databases send to S3?+
PostgreSQL, MySQL, MariaDB, MongoDB, Redis, and SQL Server — each with the same operational model and BYOS destination.
Send backups to your S3
Create an account, connect the bucket, and start with the plan that fits your operation.