Backup and disaster recovery that has been tested.
Every company has backups; fewer have restored from them. We design backup and recovery so that the questions — what is protected, how far back, how fast can we be working again — have written answers, and we test those answers on a schedule.
Both are planned per system, because a web shop, a file server and a mailbox have different needs — and different costs of being unavailable.
Backup of cloud applications
Microsoft and Google protect their platform, not your data from deletion, ransomware or a leaver’s mistake. Third-party backup of mailboxes, drives, SharePoint and Teams closes that gap.
- Daily backups with long retention
- Point-in-time restore of a mailbox, a file or a whole site
- Independent storage location in the EU
Backup of servers and databases
- Image backups of virtual and physical servers
- Application-consistent database backups (PostgreSQL, MySQL, SQL Server)
- Off-site copies in a second location or with a second provider
- Immutable, write-once storage against ransomware
- Encryption in transit and at rest, with keys under your control
Backup of devices
- Laptop backups for roles where local data matters
- Policies that keep working data in synced company storage instead of on the device
Recovery planning
- Business impact: which systems matter most and what an hour of outage costs
- Recovery objectives per system: RPO (data loss tolerated) and RTO (time to recover)
- Runbooks: step-by-step recovery instructions, kept current
- Alternative ways of working during an outage — mail, telephony, files
- A contact and decision-maker list that is not stored only on the systems that failed
Restore tests and reporting
- Scheduled test restores of files, mailboxes and whole servers
- An annual recovery exercise for critical systems
- A report after each test: what worked, how long it took, what was changed
Inventory and impact weeks 1–2
What exists, where it lives, who depends on it and what an outage costs. Existing backups are checked, including a test restore.
Design weeks 2–3
Targets per system, tooling, storage locations, retention and cost — written down and agreed.
Implementation weeks 3–5
Backup jobs, off-site and immutable copies, monitoring of every job, encryption and access control.
Test and hand-over weeks 5–6
A first full restore test, runbooks and a report. Then scheduled tests and monthly checks.
- Daily monitoring of every backup job, with failures handled the same day.
- Retention as agreed — typically 30 daily, 12 monthly and longer where the law requires.
- Off-site and immutable copies in EU data centres separate from the primary system.
- Restore tests quarterly for files and mailboxes, annually for whole systems.
- Runbooks for each critical system, reviewed after every change.
- Report every month: job status, storage used, tests performed.
- Restores carried out by us on request, within the agreed scope.
We use Microsoft 365. Isn’t that backed up already?
Microsoft keeps the service running and offers limited retention, such as recycle bins with time limits. It does not protect you against data deleted long ago, ransomware that encrypts synced files, or an account that has been closed. Microsoft’s own service terms recommend third-party backup.
How quickly can we be back after ransomware?
That is what the RTO is for. With image backups, immutable copies and a rehearsed runbook, a typical small server environment is rebuilt in hours to a day; without them, it takes days to weeks. The design step gives you the number for your systems and the cost of improving it.
Where are backups stored?
In EU data centres separate from the primary system — a second provider or region. Location and retention are written into the design.
Do you really test?
Yes, on a schedule, and you receive the report. An untested backup is a hope, not a control.
Cyber security
Assessment, the controls that stop most attacks, monitoring and incident response for SMEs.
Read more →ServicesHosting and internet infrastructure
Managed servers, websites and applications, DNS, certificates, e-mail and connectivity.
Read more →ServicesCloud management
Architecture, migration and operation on AWS, Microsoft Azure, Google Cloud and European providers, in EU regions.
Read more →When did you last restore something?
If the answer is “not sure”, start with the inventory. We reply within one business day.