Servers, Backup & Disaster Recovery
Business Backup Solutions
We design and operate backup against agreed RTO and RPO, meaning how fast you come back and how much data you can afford to lose. We keep offsite copies and run a restore test: a backup that has never been tested is not a backup, it is an assumption. The first restore is measured.
Who it is for
- Businesses with data on a server, NAS or Microsoft 365
- Companies that have backups but have never tested them
- Organisations running ERP or WMS that cannot lose data
- Boards wanting a written answer on how fast they recover
When we are NOT the right choice
- If critical data cannot be identified
- If the agreed RTO and RPO are not accepted
- If connectivity is inadequate for offsite copies
PROCESS
The process
Indicative times from signature of the proposal, subject to hardware availability. Every project is shaped to the size and the needs of the client.
01Data and criticality inventory
We record where data lives, which of it is critical to operations, and which simply occupies space.Time: 2-5 working daysDeliverable: Data map with priority
02Defining RTO and RPO
We agree how long you can be down and how many hours of work you can lose. Those two define the solution and the cost.Time: Alongside the studyDeliverable: Written targets agreed per system
03Implementation
We implement a local copy for speed and an offsite copy for protection against ransomware and physical loss.Time: 1-2 weeksDeliverable: Live backup locally and offsite
04First restore test
We restore real data into a controlled environment and measure how long it took, so the RTO is measured rather than promised.Time: After implementationDeliverable: Restore test report
05Recurring verification
We verify job success daily and repeat the restore test periodically, with reporting to management.Time: Ongoing, under agreementDeliverable: Test schedule and status reporting
| What is included | What is not included |
|---|---|
| Data inventory and criticality definition | Storage capacity and cloud subscription costs |
| Backup plan with agreed RTO and RPO | Laboratory recovery from physically damaged media |
| Local copy and offsite copy | Archiving for legal purposes |
| Microsoft 365 data backup | Data in third party systems that do not permit access |
| First restore test with a measured duration | |
| Daily verification and periodic restore testing |
Technology and equipment
- Veeam
- Synology
- Microsoft 365
- Proxmox
- Windows Server
From practice
The question is not whether you take backups. It is whether they have been tested. The daily success report states that a copy was taken, nothing more. Whether it restores, and how quickly, only becomes visible when you need it, which is the worst possible moment to find out.
That is why the first restore test is part of the project rather than an extra service. The number it produces, the real recovery time, is usually the most useful piece of information in the whole engagement.
Prerequisites
- A decision on which data is critical
- Acceptance of the agreed RTO and RPO
- Adequate connectivity for offsite copies
- Access to the systems being protected
Cost
Charged monthly based on data volume and protected systems, with verification and restore testing included. Storage capacity and cloud subscriptions are billed separately, at cost.
We do not publish a price list. Every proposal follows a site survey and separates hardware from labour.
What moves the cost
- Data volume and rate of change
- RTO and RPO requirements per system
- How long copies must be retained
- Whether Microsoft 365 backup is included
Frequently asked questions
What do RTO and RPO mean, and how do I set them?
Does Microsoft 365 back up my email?
Why does a restore test matter?
Is an external drive enough?
NEXT STEP
Ask us to test your restore
The fastest way to find out whether your backup works is to restore from it. We measure the real recovery time too.
GET IN TOUCH
Tell us what you need
Four fields. An engineer replies, not a sales desk.