Backup & Disaster Recovery
Getting everything back after a bad day
Backups that are tested rather than assumed, and a written plan for the morning a server does not come back on.

Photo: GulArt / Pixabay 
Photo: AbouYassin / Pixabay
Selected work demonstrating this service.
-
Automated 100 critical data backups using Barman
Automated 100 critical data backups using Barman, Google Cloud, Bash, and Python, ensuring data integrity across databases.
-
Managed 30 Ubuntu Linux VPS instances
Managed 30 Ubuntu Linux VPS instances, implementing disaster recovery strategies and ensuring optimal network configurations.
-
Implemented backups and disaster recovery as code
Configured database backup retention as infrastructure‑as‑code, then audited the recovery position and documented the restore procedure — naming the remaining gaps rather than leaving them to be found during an incident.
-
Backups that have actually been restored
Built encrypted off‑host backups on restic with retention pruning, an integrity check and a monthly automated restore drill, then audited the recovery position and wrote down the gaps rather than leaving them to be found during an incident.
-
Split every operational secret per host
Split the four per‑host operational secrets after establishing that two hosts sharing one dead‑man's switch alert less than two switches, not more, and that a shared backup passphrase makes two hosts one repository.
If this is the work you need done, the next step is a conversation.
Tell us the problem and we will tell you honestly whether we are the right people.

