Managed disaster recovery from DataRoad - IT Services and Consulting, a premium IT partner in Portugal, answers the only question that matters after a disaster: how soon the company is invoicing again. We set in writing how much work can be lost (RPO) and how quickly operations resume (RTO), and we prove those numbers in real tests. It is a service for organisations that cannot stop — hotels, clinics, offices with legal deadlines, embassies, logistics, international companies with operations in Portugal — built on immutable backups, replicas of critical servers and a procedure any authorised person can follow, with support in English, Spanish and French.
Why having backups is not having a plan
A backup guarantees that the data exists somewhere else. It does not say where it will be restored if the server has burnt down, who does it, in what order or how long it takes. Some companies with perfect backups stay down for three days because they lack those answers.
| Criterion | Backups | Disaster recovery |
|---|
| Question | Is the data safe? | When are we back at work? |
| Scope | Files, databases, email | Servers, network, access, applications, people and procedures |
| Success | Yesterday's backup restores without errors | The RTO was met in the last test |
| Typical failure | Backup missing or corrupted | There is a backup, but nowhere to restore it and nobody who knows how |
| Scenarios | Deleted file, corrupted database | Ransomware, fire, flood, theft, prolonged power or internet failure |
Managed backups, with local and off-site copies and tested restores, are the foundation. The recovery plan is what is built on top.
Which numbers go into the contract
RPO — how much work you can lose
The Recovery Point Objective measures, in time, the work the company accepts losing. With an RPO of 24 hours you lose, in the worst case, a day; with 15 minutes you need near-continuous replication. A clinic with 80 appointments a day and an accountant at month-end need very different values.
RTO — how quickly you are operating again
The Recovery Time Objective is the time between the disaster and critical systems working again. It defines the architecture: with two days, it is enough to have somewhere to restore; with two hours, you need replicas ready to go. It goes into the contract and is measured in every test.
Both are set system by system, based on the real cost of an hour of downtime, and do not have to be the same for everything.
How the plan stops ransomware
The most likely scenario in Portugal is not fire: it is encryption spreading across the network overnight. A plan designed for ransomware has three defences that a generic plan does not.
- Immutable backups Not even an attacker with administrator credentials can encrypt or delete them.
- Isolation before start-up The network is segmented so the replica is not infected when it comes up.
- A clean restore point Identified with certainty, because yesterday's backup may already contain the ransomware.
Without a plan in advance, the job becomes business data recovery: slower, more expensive and with no guarantees. This scenario overlaps with managed cybersecurity and with the obligations of NIS2 for companies in Portugal.
What a DataRoad plan includes
- Impact analysis — which systems stop the business, how long is tolerable and what each hour costs.
- Reinforced 3-2-1 rule — three copies, two media, one off site and an immutable version for critical systems.
- Replicas of critical servers — in a datacentre in Portugal or in the cloud, ready to start without waiting for hardware.
- Contingency communications — phones and email working while the main infrastructure is down, including the cloud or on-premises phone system and Microsoft 365.
- Written procedure — who declares the disaster, who is notified, recovery order, contacts and credentials, stored outside the systems to be recovered.
- Tests with a report — one full test a year and quarterly partial tests, with the actual time compared with the RTO.
- Return to normal — the path back from the replica to the main infrastructure, without losing the work done in the meantime.
What management receives in writing
- Impact per system RPO, RTO and the estimated cost of an hour of downtime.
- Map of copies and replicas Where each copy is, frequency, which is immutable and how far back you can go.
- Activation procedure Owners, recovery order and credentials stored outside the infrastructure.
- Communications plan How to keep serving clients during the outage.
- Test reports Measured times and corrections agreed after each rehearsal.
DataRoad IT Unlimited
Talk to DataRoad. We assess your operation and propose the right plan.
Request a proposal →Where we have already applied it
The União das Freguesias de Massamá e Monte Abraão, a local authority near Lisbon, awarded DataRoad a 2022 public contract for a new server, a UPS system and corporate backups: processing power, power that survives an outage and recoverable data. With a public service counter, downtime means a service that is not delivered.
The ongoing management contract, renewed through tender, adds monitoring and support under the Premium 365 regime (24×7) to detect incidents before they reach the counter.
How long it takes to implement
Four to eight weeks, for a company with 20 to 50 workstations and one or two servers. Analysis and design take two to four weeks; replicas and immutable copies, another two to four. The first full test takes place within the first three months.
We start with the impact analysis with management, because it is management that knows what an hour of downtime costs. If you already have backups and only want to know whether you could recover from them, the test can be done on its own, as an IT consultancy project with a written report.
Questions about disaster recovery
Aren't daily backups enough?
No. They are the foundation, not the plan: the plan defines the destination, owners, order and timing of recovery before it becomes urgent.
What RTO should we ask for?
Whatever the company can withstand without serious damage. Short RTOs require ready replicas and cost more; one to two days can be achieved with off-site copies and spare hardware. The impact analysis sets the value using real costs.
Where are the replicas stored?
In a datacentre in Portugal, in the cloud or both, depending on the RTO and data location requirements. It is written into the plan.
How often do you test the plan?
At least one full test a year and quarterly partial tests, always documented. A plan without a test is only an intention.
Are business continuity and disaster recovery the same thing?
No. Business continuity covers people, premises and processes; disaster recovery is the technology part. We handle that part and coordinate with whoever manages the rest.
Who activates the plan?
Management declares the disaster according to written criteria and DataRoad carries out the recovery. On Premium 365, with 24×7 cover, execution can start at any hour.
Next step: find out how quickly you would be back at work
Not how quickly you would like to be — how quickly you actually could be. The first analysis carries no commitment. Service provided exclusively under an IT Unlimited contract; we do not carry out one-off interventions or sell standalone equipment.
More than 10 workstations · support contract · remote, on-site and phone support.
+351 211 459 950* (working days, 9:30–13:00 and 14:00–18:30, Lisbon time) · sales@dataroad.pt
*Call to a Portuguese landline.