Managed IT services / Backup & disaster recovery
When something fails,
you're back in minutes.
Automatic backups and a tested recovery plan. We protect your data against ransomware, failures and mistakes, and define in advance how long it takes you to be operating again. A disaster stops being an open-ended outage and becomes a controlled interruption.
What it is
A copy of your data
and a plan to recover.
A backup is a copy of your data, kept separately, so you can recover it if the originals are lost, corrupted or encrypted by someone. It answers a simple question: "do I have another copy of this?". It is the raw material of any recovery.
Disaster recovery (DR) is the plan and the means to resume operations after a serious incident. It is not just about recovering files, but about restoring the whole operation—servers, applications, access and data— within an agreed time. It answers a different question: "how long until I am working again?".
The two need each other. A backup with no DR plan leaves your data safe but with no idea how or how quickly you come back. A DR plan without good copies is an intention with no raw material. Together, they are what turns a disaster into a controlled interruption. It is part of ourmanaged IT services, and the safety net everything else rests on.
Problems it solves
What you discover
on the worst day.
Backups that never restore
The copy exists, but it is corrupted, incomplete or has never been tested. On the day of the incident you discover it does not recover what you thought it would.
Ransomware
Malicious encryption locks your files and demands a ransom. If the attack also reaches your backups, you are left with no last line of defence.
Accidental deletion
Someone deletes or overwrites a file, a mailbox or a shared folder by mistake. Without previous versions, that data simply disappears.
A single backup location
If the copy lives next to the original data, a fire, a theft or a flood takes both at once. There is nowhere left to turn.
No recovery plan
You have backups, but nobody knows what gets restored first, who does it or how long it takes. Recovery is improvised under pressure.
Long downtime
Restoring terabytes over a slow link can take days. Every hour of downtime has a cost, and without failover that cost spirals.
What it includes
A backup that truly
covers you.
It is not just "making copies". It is a complete system, designed so that recovery works on the day you need it:
- Automatic, encrypted backups, with no reliance on anyone remembering
- The 3-2-1 rule: three copies, on two media, one of them offsite
- Immutable backups, shielded against ransomware
- Backup of servers, endpoints, Microsoft 365 and Google Workspace
- Regular restore testing, not just copies
- A recovery (DR) plan with defined RTO and RPO
- Documentation and runbooks to recover without improvising
Disaster scenarios
For every failure,
a response.
| Scenario | What happens | How we respond |
|---|---|---|
| Ransomware | Files are encrypted and systems are locked while a ransom is demanded. | We restore from an immutable copy taken before the attack. You are back without paying. |
| Hardware failure | A disk, a server or a storage array suddenly stops working. | Failover to the secondary copy or system and rebuild of the affected machine. |
| Human error | Someone deletes or overwrites files, mailboxes or records by mistake. | Granular restore of the specific item to its previous version, in minutes. |
| Fire or flood | The physical site and every device it holds are destroyed. | The offsite or cloud copy lets you recover operations in another location. |
| Cyberattack | Intrusion, sabotage or malicious deletion of critical data and systems. | Recovery from isolated copies and step-by-step execution of the DR plan. |
The core idea
A backup is only worth it if it's been proven to restore.
Benefits and outcomes
What you gain when
it's done right.
Business continuity
An incident stops being an open-ended outage. Work resumes within the time we have defined, not whenever it happens to be possible.
Ransomware protection
With immutable copies, malicious encryption does not destroy your last line of defence. You restore instead of negotiating.
Defined recovery times
You know in advance how long it takes you to come back (RTO) and how much data you could lose at most (RPO). No surprises.
Compliance and GDPR
Encrypted copies, controlled retention and logs that help demonstrate diligence in audits and under the GDPR.
Granular recovery
You do not need to restore a whole server to get back a file or a mailbox: we recover exactly what was lost.
Peace of mind
Someone is watching that the backups run, are tested and actually work. You stop crossing your fingers every time something fails.
Key concepts
The vocabulary
of backup.
You do not need to master these terms: that is our job. But knowing what they mean helps you understand what your backup protects, and what it does not.
The CPPA method
From "I have copies" to
"I know I recover."
Analyse critical data and objectives
We identify which data and systems are vital, how long you can afford to be down (RTO) and how much data you could lose at most (RPO). Those answers shape the entire design.
Design the strategy
We define what is backed up, how often, where it is stored (the 3-2-1 rule, offsite and cloud), how long it is retained and how it is protected against ransomware with immutable copies.
Deploy and encrypt
We roll out backups of servers, endpoints, Microsoft 365 and Google Workspace, encrypted end to end, with monitoring and automatic alerts if a backup ever fails.
Test restores and maintain
An untested backup does not count. We run real restores, simulate disasters, measure whether we meet the RTO and RPO and keep the plan up to date as your IT changes.
Recovery examples
How it looks
in practice.
Recovery after ransomware
- Encryption detected and machines isolated
- Last clean, immutable copy identified
- Affected systems and data restored
- Integrity verified
- Back in production without paying a ransom
Restoring a deleted file
- Report from the user or the team
- File or mailbox located in the backup
- Correct version selected
- Granular restore in minutes
Server failover
- Failure of the primary server detected
- Secondary copy or server activated
- Service continues while the fault is fixed
- Rebuild and return to the original machine
Scheduled DR test
- Agreed test schedule
- Restore into an isolated environment
- Real RTO and RPO measured
- Report with findings and adjustments
Risks and mitigation
Why a backup
fails.
Almost no backup fails for lack of copies, but because of how they are set up. These are the failures we see most, and how we prevent them:
A backup that never restores
The copy exists but is corrupted, incomplete or has never been tested. We solve it with regular restore testing: if it has not been restored, it does not count as a backup.
Ransomware that encrypts the backups
Many attacks go after the backups first. With immutable, isolated copies, the attacker cannot delete or encrypt them, not even with administrator credentials.
A single backup location
If the copy lives next to the original data, a fire or a theft takes both. We apply the 3-2-1 rule with an offsite and cloud copy.
An RTO that is too long
Restoring terabytes can take days. For anything critical we design a DR plan with failover that resumes operations in minutes, not days.
Unencrypted backups
A stolen or lost copy is a data breach. We encrypt in transit and at rest, so that a misplaced device does not turn into a GDPR incident.
Unprotected 365 or Workspace
The cloud is not a backup: Microsoft and Google will not recover your data if you delete it or it gets encrypted. We add a dedicated backup with its own retention.
Frequently asked questions
How do I know if my current backup is reliable?
What are RTO and RPO?
Does backup protect against ransomware?
Do I need to back up Microsoft 365 or Google Workspace?
How often are backups taken?
Do you test that restores actually work?
Related services
Keep exploring.
Cybersecurity
Backup is your last line of defence; cybersecurity is the first. Layered protection so the disaster never happens in the first place.
View →
IT infrastructure
Well-designed servers, networks and storage are the foundation any reliable recovery plan rests on.
View →
IT support
When something fails, someone has to respond. Managed helpdesk with clear SLAs that runs the recovery when it is needed.
View →Do you know for certain that your backup restores?
Request a proposal →Want to see how we think about the continuity of an operation end to end? Read ourCPPA X-RAY on 100 Montaditos.