Free download · A4 PDF · CISO / CTO grade
Verified Backups
58% of backups fail when you try to restore them. Most companies only find out during the disaster.
One email. Confirmation by mail. Unsubscribe with one click.
What's inside
Inside: what it protects against and how it works. Which rules it helps you meet. The proof your auditor will want. About 10 to 14 dense pages.
- What you're really defending against, in plain terms
- How the system works, and why an attacker can't beat it
- What it stops, with real-world examples
- Which rules apply: fines, deadlines, exact wording
- The cost math, grounded in published numbers
- How we stack up against other vendors on the tech, not the price tag
- What setup looks like, and what we don't cover
- The evidence your auditor will ask for
Related solution pages
The same approach, framed for the questions you'll get asked:
Get your whole setup back in minutes
Not just files. Whole setups: your servers, configs, and databases. Back up and running in minutes.
Read moreKeep your data as long as the law requires
Set how long to keep your backups. Rediacc keeps them that long, then cleans up. HIPAA, SOC2, and GDPR rules are covered from day one.
Read moreEvery backup verified. Automatically.
Don’t wait for a disaster to find out your backup is corrupted. Rediacc checks every backup the moment it’s created.
Read moreQuestions readers asked
Who is this brief written for?
A CISO, CTO, or senior infrastructure engineer reviewing the design. It assumes you know how backups work, how storage works, and the rules your stack already has to follow.
Is there a non-technical version?
Yes. After you submit your email, the same page links to a five-minute executive PDF you can forward to a CFO, IT director, or board member.
What happens to my email?
One confirmation email. You're added to our newsletter (one short post per month, all-product). Unsubscribe with one click. Your email lives in the EU by default per Rediacc's data-residency policy.
Why btrfs?
The brief covers this in depth. Short version: btrfs puts write-once copies and instant clones into the storage layer itself. Not into an app on top. The send/receive feature ships those copies off-machine. So an attacker holding your top admin password can't change or delete them.
Does this apply to managed services like AWS RDS?
Not directly. The design covers your own servers running databases in Docker on btrfs storage. If your critical data lives in RDS or Aurora, the brief flags that. It then shows where the model fits and where it doesn't.
About this brief
Rediacc is a Tallinn-based company. We build backup and disaster recovery on btrfs and commodity Linux. Our engineering team wrote this brief. We edited it against an anti-slop style guide. Then we checked every claim before publishing.
Have a question we should add to this page? Tell us at hello@rediacc.com.
Download short brief (PDF)