Storage and backups
In preview
Connect the storage you already pay for, or run an S3-compatible store on your own server. Backups are encrypted restic repositories, one per account and target.
Built and lab-tested
- Connections to S3, Backblaze B2, Wasabi, Cloudflare R2, DigitalOcean Spaces, Azure Blob, Google Cloud Storage, SFTP, FTP(S) and WebDAV, tested on save and rechecked every 15 minutes.
- A built-in S3-compatible store (SeaweedFS): buckets, scoped access keys, versioning, object lock, CORS, lifecycle rules, quotas and presigned URLs. Standard AWS SDKs work with it.
- restic backups to a local folder, any connection or the built-in store. Databases are exported first, so a backup is never silently partial.
- Schedules, retention policies, and immutable backups with S3 object lock.
- Restore files beside the originals, in place or into another account; restore a database by replacing it (after a safety dump), as a new one or as a download; restore a whole account with a 24-hour rollback.
- Weekly integrity checks and monthly test restores run on their own.
- One-mailbox backup and restore.
- Whole-server recovery, run for real: a server was backed up, destroyed and rebuilt on a blank machine in 312 seconds, with every item verified identical. The recovery guide lists what does not come back.
Not there yet
- Google Drive, Dropbox and OneDrive connections, and mounts.
- Container volumes in the account's backup, and point-in-time recovery.
Every action in this area is in the panel, one keystroke away in the command palette (Ctrl K), on the command line and in the API, and most changes can be previewed as a plan first. Built and tested in our lab; RespireCloud is not released yet.