Blog
By Lucas Flores, IT Systeme Flores UG. Last updated
Plain explanations of the questions an IT admin actually asks before committing to a backup product: pricing, lock-in, restore testing and GoBD archiving. Every number is sourced to an official page and dated, or marked as illustrative where no official price is public. Vendor comparisons use the same standard.
-
The subscription trap in backup pricing
Why per-user, per-year backup subscriptions rarely go down, and what a one-time license with optional update years does and does not change.
-
Per-user backup pricing over 5 years, calculated
A worked, sourced example of what metered and per-seat backup pricing compounds to, against a one-time license plus update years.
-
Exit costs and vendor lock-in in backup software
What it actually costs to leave a backup vendor: proprietary formats, egress, and re-onboarding.
-
Bring your own storage: why it matters for backup
Why writing to storage you already control changes the economics and the trust model, not just the price.
-
Why restore tests matter more than backups
A backup that has never been restored is a theory. How verified, automated restore testing changes that.
-
GoBD and email archiving, explained
What GoBD actually requires for email archiving in Germany, and what the Restow archive does since 0.1.0.
-
EWS retirement in Exchange Online: what backup tools need now
Microsoft is switching off Exchange Web Services in phases. What changes, why Graph-based tools are unaffected, and what to check with your current backup tool.
-
How to prove that a backup can be restored
Restore tests, sample read-back, hash comparison, a fixed rhythm and written results: a method that works with any backup tool, and how Restow does it.
-
Why German law is a good yardstick for data protection and backup quality
German rules on data protection, business records and IT security are detailed, public and enforced. Why that makes them a useful benchmark for backup and archive software, and where the argument ends.