Skip to content
Engineer
Menu
Design
English

Engineer / Portfolio

Backup automation with an explicit restore method

Implemented restic backup automation with retention, integrity checks and a monthly restore‑test workflow; documented storage activation and live‑restore verification as separate operational steps.

Situation. Engineer ApS needed a recovery design that covered its own infrastructure beyond a provider snapshot. The work concerned backup automation, storage prerequisites and a way to test restoration.

Task. The implementation needed encrypted off‑host snapshots, retention rules, integrity checks and a repeatable restore test. Writing those controls and proving a live recovery are separate deliverables.

Action. An Ansible role installs restic scripts and systemd units. The backup path supports a database dump where configured, snapshot creation, pruning and integrity checks. A separate monthly workflow restores a known file to a scratch location and compares its bytes. Success signals are separate for backup and restore; timers depend on a configured repository. The passphrase is read from a protected file rather than a systemd‑parsed environment value.

Result. The repository contains the backup and restore‑test implementation and documents its activation prerequisites. The implementation record dated 2026‑10‑27 says the timers were disabled without a repository and records no completed live restore. That dated evidence supports the automation work, not a claim about current runtime state, successful disaster recovery or a recovery‑time commitment.

Cases · 2026

Backup and restore testing are separate workflows

  1. Configure the backup repository

    Timers require a configured backup repository; the passphrase is read from a protected file.

  2. Create and check snapshots

    The backup workflow creates encrypted snapshots, applies retention rules and checks repository integrity.

  3. Test a known-file restore

    A separate workflow restores a known file to a scratch location and compares its bytes. Backup and restore have separate success signals.

Logical overview of the backup and restore-test implementation. The dated case record describes activation prerequisites and does not record a completed restore run.

Contact

Still working out what you need?

Tell us what is going wrong, or what you are trying to build. We will tell you what it would take, roughly what it would cost, and whether we are the right people for it.

From 1,400 DKK an hour, excluding VAT — and less per hour on a longer booking.

welcome@engineer.company +45 50 10 61 84 Copenhagen, Denmark