Improve what I have · Backup & Recovery

A change request is a bounded, pre-scoped change to something you already run — adding to it, upgrading it, or reconfiguring it. We scope it, agree a fixed price, make the change safely, and validate it.

Pre-scoped & fixed-price

You see exactly what changes and what it costs before we start — no open-ended hours.

Safe & reversible

Production changes are staged, backed up, and carry a rollback plan.

On your existing setup

We work within what you already have — anything brand-new is a project.

How it works

1
You tell us what to change
Pick the area and the counts, and add a note on exactly what you need changed.
2
We scope and price it
We confirm the change, its impact, and a fixed price — usually within 1 business hour.
3
We make the change and validate
We apply it in a planned window, test it, and confirm it’s working — with a rollback ready.

What you’re buying

The change implemented on your existing systems
A change and rollback plan for anything touched in production
Post-change validation and confirmation it’s working
A short record of exactly what changed

What this covers here

Adjust retention, policies, and tooling on your existing backup setup.

Retention / policy changes
Backup tool upgrades
Repository cleanup
Restore-test cycles
Resilience tuning

Turnaround & price

Scoping & quote: within 1 business hour
Delivery: typically 1–5 business days
Rollback: planned for every production change

Priced by how many items the change affects — you’ll see the estimate before you commit, and we confirm the final price at scoping.

What’s not included

Installing or building something new — that’s “Set up something new”
Day-to-day fixes, monitoring, and upkeep — that’s “Look after my IT”
Anything that redesigns your architecture — that’s a project

Not this? Not a brand-new build, and not everyday fixes. Adding a rule to your firewall is a change; installing a new firewall is “Set up something new”. Keeping it patched and running is “Look after my IT”.