The problem you're facing
Backups run in a server corner, never tested, with the same credentials as production. On ransomware day, the encryptors find the backups first. On disk-failure day, the restore fails halfway.
Our answer
We build a serious backup chain: 3-2-1 strategy (three copies, two media, one off-site), encryption, European replication on our infrastructure, anti-ransomware immutability : and documented restore tests.
What LaMeDuSe takes care of
- Audit of your current backups and risks
- 3-2-1 strategy sized by criticality
- Encrypted backups and European replication
- Anti-ransomware protection (immutable snapshots)
- Documented disaster recovery plan
- Regular, reported restore tests
- Backup monitoring with failure alerting
Our methodology
- 1
Audit & mapping
Complete inventory of your information system: servers, network, backups, access rights, technical debt.
- 2
Takeover plan
Risk prioritisation, documentation of the existing setup and monitoring in place from the first week.
- 3
Operations & automation
Day-to-day administration, automation of repetitive tasks, security patches and backup management.
- 4
Continuous improvement
Monthly review of incidents, capacity and costs, with a shared improvement roadmap.
Relevant technologies
Security
Hardened configurations, privileged access management, centralised logging, managed firewalls and a tested 3-2-1 backup plan.
Hosting & infrastructure
We administer your existing infrastructure as well as our own cloud: the people and the infrastructure can come from the same group.
Maintenance
Contracts with committed response times, 24/7 on-call for critical environments and a monthly operations report.
Why LaMeDuSe
Our own production backups flow through this architecture, with continuous restore testing: we don't sell a backup chain we don't use ourselves.
Frequently asked questions
Three copies of your data, on two different media, one off-site. It's the minimal base to survive hardware failure, site disaster or ransomware : each rule covers a distinct risk.
Through immutability: non-rewritable snapshots for a defined period, and isolated backup access. Even if your systems are compromised, backups stay intact and restorable.
By criticality: monthly to quarterly, with a documented test report. Each test restores a representative set to an isolated environment : the result is measured, not assumed.
The RTO (recovery time) and RPO (maximum data loss) are defined per application by your criticality, then validated by tests. These are measured commitments, not promises.