Backup & continuity
If it breaks tomorrow, we know what to restore. And how fast.
Reply within 1 business day · No commitment
What this avoids
- A backup exists. Nobody has ever restored it.
- Nobody listed what is critical: mail, client files, the till, the assistant’s index.
- After ransomware or a dead disk, people improvise. Lost hours are not in the contract.
How it runs
Interview, audit, a written deadline. Not an 80-page binder.
Interview
We sit down together. Which files, which mail, which business app — what would stop Monday morning. Not an inventory of every disk.
- Data that actually matters
- Where it lives today
- What you can lose vs what you cannot
Audit
Remote first. An on-site visit if you want one — a forgotten NAS, a cupboard, a till PC. Not a mandatory trip to bill a call-out.
- Remote first
- On site if you wish
- Scope inventory
Plan and RTO
Written scope: what is backed up, where, how often, tested when. The RTO — how long until you are back — sits in the contract, set on what is truly critical. Not a two-hour promise for everything.
- Backups and retention
- Restore tests
- RTO by criticality
What we put in place
Backups, RTO, DR. Three words, one thread.
Backups
Copies, retention, restore tests. A backup nobody has ever opened is not a backup.
- Scope and frequency
- Off-site copy
- Restore tested
RTO
The written recovery time, by criticality. Mail and client files are not the same contract as a 2019 archive.
- Deadline per data type
- Written in the contract
- No 2-hour / 24/7 slogan
SME DR plan
A short, readable plan. Who calls whom, in which order we restore. Enough that someone other than you can follow it.
- Recovery order
- Contacts and access
- A few pages, not theatre
AroBox option
Save your box’s intelligence with us.
If you have an AroBox, its “intelligence” — the index, the documents it knows — can have a cold copy with us. We do not use it day to day. The day the box is gone, we have something to rebuild from.
- A cold copy, not a second workstation
- On servers in France
- Scoped restore, after the incident
Option on quote, separate from the managed-IT run. Not a “zero bytes leaving” claim.
Raise it at the auditIncluded
- +Scoping interview (critical data)
- +Remote audit; on site if you ask
- +Written plan: backups, tests, RTO
- +AroBox cold-storage option (on quote)
Out of scope
- −24/7 on-call, unless an addendum
- −Restore outside the scope — what was not in the inventory
- −ISO / HDS certification
The RTO is set after the audit, on what is truly critical. It is not a generic two-hour promise, nor default 24/7 on-call.
Already an estate to run?
Backups in the managed-IT contract cover the signed scope. The DR audit and written RTO are the framing — often before, or as an addendum.
See managed ITScope recovery before the incident.
No commitment. Interview first, RTO next. On quote — not a managed-IT retainer in disguise.
Reply within 1 business day · No commitment