Upload without visibility
A manual sync to the bucket broke and only shows up when someone needs the file.
Cloudflare R2 backup
Cloudflare R2 (S3-compatible) destination with preflight, monitoring, and retention under your control.
Use R2 as the BYOS destination for your database backups. Zault sends files to the bucket you control — with policies, monitored jobs, and restore with a destination snapshot.
Cloudflare R2 destination
Preflight
Schedule
Health
Restore
R2
The real risk
Backup without a clear destination is risk
Scripts that leave dumps on local disk or improvised folders fail quietly and make retention and ownership hard.
Object in R2 ≠ rehearsed restore
Having the object in the bucket does not guarantee a safe recovery into the target database.
Credentials and scripts everywhere
Every server keeps its own keys and cron — hard to audit destination and retention.
How Zault helps
R2 as storage for the Zault routine
Connect the R2 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 R2 — 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 Cloudflare R2
Files in your S3-compatible bucket — retention and ownership under your Cloudflare account.
Positioning
Local scripts vs R2 destination on Zault
The difference is not only pointing at a bucket — it is operating backup and restore predictably into R2.
Traditional approach
- Local dump + ad hoc upload to R2
- File logs or occasional email
- Improvised download under pressure
- Little visibility into upload failures
With Zault
- Policies, preflight, and validated R2 destination
- Dashboard, jobs, and health map
- Restore with preflight and destination snapshot
- BYOS in your R2 bucket with retention
Common questions
Cloudflare R2 in practice
Why not just a script that uploads to R2?+
Upload is only one step. Without preflight, monitoring, and rehearsed restore, failures show up late. Zault treats R2 as the destination of a full operational routine.
How does restore from R2 work?+
The flow includes pre-checks and an automatic snapshot of the target database before changing data, with explicit confirmation in the dashboard.
Do files stay on Zault?+
No. In the BYOS model, files stay in your Cloudflare R2 bucket (or another supported destination), with retention aligned to your policy.
Which databases send to R2?+
PostgreSQL, MySQL, MariaDB, MongoDB, Redis, and SQL Server — each with the same operational model and BYOS destination.
Send backups to your Cloudflare R2
Create an account, connect the bucket, and start with the plan that fits your operation.