H2MHuczyńskiSystems you own
Contact

Service 05 / 05 · Recovery · all services

Production failing? The data secured first, then the cause fixed while you keep selling

When the shop, the CRM or the system your company runs on is failing: the data secured first, the cause measured on live production, small reversible fixes. The business keeps selling while it happens.

  • Off-site backup before any change, proven by a restore
  • The cause measured on live production, not guessed
  • Reversible fixes, each with a written rollback
  • A written report: what broke, what changed, what is left

A system that crashes several times a day usually gets one of two answers: a bigger server, or a rewrite. Both are slow and neither starts with the cause. I start with the data: a full copy off the failing machine, with no maintenance mode, restored into a working clone so we know it is real. Then I measure on production, because a faster clone hides the bottleneck, and fix the cause with changes small enough to undo in one line. You get the system back, a written record of every change, and an honest list of what is still fragile. If a rebuild is the right next step, the report says so and prices it.

This is the right call when

  1. 01

    Your shop or system goes down several times a week and nobody can say why.

  2. 02

    The admin panel is so slow the team cannot do its daily work.

  3. 03

    There is no backup you have ever restored, and the person who built it is gone.

What you get

What lands on your account

  • A full off-site backup, restored and checked before any fix
  • The root cause, measured and written down
  • Fixes on production, each with a one-line rollback
  • A report with before and after numbers, and what is still fragile

How it runs

Three steps. The six-step version, with the brief and the video request, is on the home page.

  1. 01

    Scoping call

    30 min, free

    You describe what fails and since when; I ask what I need to look read-only, and we agree the start, usually the same or the next business day.

  2. 02

    Recovery triage

    €1,900 / $2,200 net, 3 business days

    A full off-site backup, restored and checked before anything changes; the cause measured on live production; the first fix when it is small and safe; and a written report with every remaining fix priced. It starts the same or the next business day, the report comes within 3 business days, and the fee is credited in full against the fixes or the first 3 months of a plan ordered within 30 days.

  3. 03

    Fix, then a plan

    fixed price from the triage

    The fixes from the report at the price it names, each with a rollback, then Care or Lane keeps the system up. The triage fee is credited against them.

Case studies

The systems behind this service, with the numbers their owners cleared for publication.

  1. Auto-parts shop

    An e-commerce shop with ~100k products whose database crashed three times a day, stabilised on live production without planned downtime.

    Backup first, proven by a restore; the cause was one missing index, found by measuring on production.

    19.5 → 2.8
    server load
    90 s → 1.3 s
    search
    −82%
    server errors a day

    Read the case

Runs on

  • Linux
  • Docker
  • Ansible
  • Cloudflare
  • Git
  • Claude

Questions I get about this

Tap a question to see the answer.

Scoping calls · most weeks

€1,900 / $2,200 net, a fixed price. A full off-site backup, restored and checked before anything changes; the cause measured on live production; the first fix when it is small and safe; and a written report with every remaining fix priced. It starts the same or the next business day, the report comes within 3 business days, and the fee is credited in full against the fixes or the first 3 months of a plan ordered within 30 days.

Usually the same or the next business day. The first hours go to read-only inspection and the off-site backup, so nothing changes on the system until there is a copy we have restored.

Server or hosting-panel access and the database credentials. Everything is inspected read-only first; secrets stay out of the repository, and I list what should be rotated when the work is done.

Every change has a backup and a one-line rollback written before it goes in, is tried on a restored clone first, and is measured on production afterwards. If a change does not help, it comes out.

The system keeps running on Cloudflare with no servers to babysit, and a monthly plan starts on launch day. Care (€590 / $690 a month) keeps it monitored and backed up and takes up to 2 small changes a month; Lane (€2,090 / $2,400) keeps one change always in progress. On top, every plan takes more changes in a relaxed queue, from 4 small ones a month on Care to 8 on Lane: no deadline, done when there is capacity. The code and the docs stay yours, so you can also run it yourself or hand it to another engineer. Plans and SLA

Something else? Ask it on the call

A 30-minute call, free

Thirty minutes, then a fixed price for the triage

Pick a free time in my calendar. Or leave an email: I reply within one business hour with three questions and a proposed time for the call, not a deck.