Turn ad-hoc backup scripts into a recovery strategy
Fixed-price engagements for DACH-mid-market operators: audit what you have today, document what recovery should look like, prove it with a drill.
Backup Audit
We look at every backup path you have today — cron jobs, managed-DB snapshots, storage scripts — and write up what is sound, what is brittle, and what is flat-out dangerous.
You get
- Inventory of every backup pipeline
- Risk rating per pipeline
- RTO/RPO measured, not guessed
- Top-5 quick wins (usually ≤1 day)
- 30-min walkthrough call
Migration Consulting
Move from ad-hoc pg_dump cron jobs to a documented runbook: on-prem → resistro + Resistro Cloud, or managed DB → your own storage. Including Prometheus alerts and a tested restore path.
You get
- Documented backup + restore runbook
- Resistro agent installed, monitored, alerting
- Off-site encrypted storage (Hetzner, S3, or BYO)
- Hand-off session with your ops team
- 30-day follow-up included
Disaster-Recovery Drill
We restore one of your real backups into a throwaway target and prove RTO with a stopwatch. The number you report to your board is a measurement, not a hope.
You get
- Restore performed against a clean target
- Measured RTO, data-integrity check
- Failure-mode log (what broke, how fixed)
- 1-page summary for exec / board
- Replayable drill script for next time
How an engagement runs
30-min call
You describe what you run today, what hurts, and what a win looks like. Free, no pitch deck.
Written scope
Fixed price and exact deliverables in writing before anyone pays anything. No ambiguity.
Work
Done remotely out of my home office in Bavaria, or on-site if you prefer. Daily brief stays short.
Hand-off
You get the runbook, the fixes, the measurements. Your team owns it from there.
FAQ
Do I have to use Resistro Cloud?
No. The open-source resistro binary + your own storage is a perfectly valid outcome. About a third of engagements end that way. I'll recommend Resistro Cloud when the monitoring and retention layer is a real gap — not by default.
PostgreSQL, MySQL, MariaDB — what about the others?
Those three are where I can stand in front of your CTO and commit. For MongoDB, SQL Server, Oracle, I'll recommend someone specialised and bow out.
Do you sign NDAs?
Yes. Standard mutual NDA before the scoping call if you need one — send me yours or I'll send you mine.
On-site where?
Based in Krailling, near Munich. DACH-wide travel is fine; beyond that it's remote unless you really want me there.
How is this different from a generic DevOps consultancy?
Narrow scope, strong opinions. I've built the tool you might end up using, so the advice comes with the code to back it up. If your problem is broader than DB backups, I'll say so and not take the engagement.
Not sure which one?
Drop a line describing what hurts. I'll reply within one business day and suggest the shortest useful engagement — or tell you it's not a fit.
Email me