Managed backups
Local and off-site copies
Regularly tested restorations
Retention defined in writing
Business continuity plan
RTO and RPO agreed in writing
Replication and disaster recovery in the cloud
Recovery tests with logging
RPO and RTO in writing
Fixed system by system based on the actual cost of an hour of downtime.
Immutable copies
Against ransomware: not even a compromised administrator can delete them.
Scheduled tests
One full report per year and quarterly partials, with a real-time recovery time report.
Disaster recovery and business continuity for businesses
Backups answer the question “did we lose the data?”. Disaster recovery answers “when are we back to work?”. They are different questions, with different answers. A company can have perfect copies and be out of action for three days because no one knows where to restore them, in what order, or with which server. DataRoad designs, maintains and tests disaster recovery plans for companies that cannot afford to stop, and writes them with two numbers on the first page: how much you can afford to lose (RPO) and how quickly everything has to be back up and running (RTO).
Backup and disaster recovery are not the same thing
| Backups | Disaster recovery | |
|---|---|---|
| Question answered | Are the data securely stored elsewhere? | How long until the company resumes operations? |
| What protects | Files, databases, email mailboxes | Complete servers, network, accesses, applications, people and procedures |
| Measure of success | Yesterday's backup restores without errors | The RTO was met in the latest test |
| When it fails | There is no copy, or it is corrupted | There is a copy, but there is nowhere to restore it to nor anyone who knows how to do it |
| Typical scenario | Deleted file, corrupted database | Ransomware, fire, flood, theft, destroyed server, prolonged power or internet failure |
As managed backups they are the foundation; the disaster recovery plan is what is built on top of them.
The two numbers that matter: RPO and RTO
RPO — how much can be lost
O Recovery Point Objective it is the maximum amount of work that the business is willing to lose, measured in time. An RPO of 24 hours means that, in the worst case, one day's worth of work is lost; an RPO of 15 minutes requires almost continuous replication. There is no single correct value — there is only the value the business is willing to pay. A clinic that books 80 appointments a day and an accountancy firm at month-end have very different RPOs.
RTO — how long until you go back to work
O Recovery Time Objective It is the time between the disaster and the moment when critical systems are up and running again. It determines the architecture: with a two-day RTO, it is enough to have somewhere to restore to; with a two-hour RTO, you need replicas ready to boot up. The RTO is written into the contract and is measured during every test.
What does a DataRoad disaster recovery plan include
- Impact assessment. Which systems stop the business if they go down, for how long is it tolerable, and how much does each hour of downtime cost. This is where the RPO and RTO of each system come from — they do not have to be the same for all of them.
- Backups using the 3-2-1 rule. Three copies, on two different media, one off-site and, for critical systems, an immutable version that not even a compromised administrator can delete.
- Replicas of critical servers. In a data centre in Portugal or in the cloud, according to the required RTO, ready to start without waiting for new hardware.
- Communications plan. How does the company continue to answer phones and receive email while the main infrastructure is down — includes the switchboard and Microsoft 365.
- Written, step-by-step procedure. Who decides to declare the disaster, who is notified, in what order systems are recovered, what passwords and contacts are needed. Kept outside the systems you may need to recover.
- Tests scheduled. At least one full test per year and quarterly partial tests. Each test produces a report showing the actual recovery time compared with the agreed RTO and the corrections to be made.
- A return to normality. The plan does not end when the company is working on the replica; it includes the process of returning to the main infrastructure without losing the work carried out in the meantime.
The most frequent case: ransomware
In Portugal, the most common disaster is no longer fire or flood — it is an encrypted file that spreads through the network overnight. A disaster recovery plan prepared for ransomware has three characteristics that a generic plan does not: immutable copies, which the attacker cannot encrypt or delete even with administrator credentials; a network isolation procedure, to prevent the replica from becoming infected upon boot; and a securely identified restoration point prior to the infection, because restoring yesterday's copy may mean restoring the ransomware itself. In cases where we are called without a prior plan, the job is one of data recovery — slower, more expensive and with no guarantees.
Who it makes sense for
For any business where a single day without systems costs more than the annual subscription fee. The clients who need it most are hotels whose bookings and check-ins depend on the management system, clinics with appointment schedules and medical imaging, law firms and accountants with legal deadlines, embassies and organisations with availability requirements, and logistics firms where invoicing and dispatches grind to a halt simultaneously. Smaller businesses benefit from a simplified version: off-site backups, a one-page written procedure and one test per year.
Inside IT Unlimited
Managed backups and monitoring are included in all plans IT Unlimited. The comprehensive disaster recovery plan — including replicas, a written procedure and recovery tests — is included in the IT Unlimited Premium 365, the plan for businesses that cannot afford downtime, and can be contracted as a project for clients on the other plans.
How we got started
We start with the impact analysis, together with company management and not just with IT: it is management that knows how much an hour of downtime costs. From there, the RPO and RTO are established for each system, the solution is designed and the procedure is written. The first complete test takes place within the first three months. If you already have backups and just want to know if you would be able to recover from them, that test can be carried out in isolation, as consultancy work, with a written report.
A real-life case: server, UPS and backups in a local authority
The Union of Parishes of Massamá and Monte Abraão awarded to DataRoad, for public contract in 2022, the installation and configuration of a new server, a UPS system and corporate backups — the three foundational layers of any business continuity plan: processing capacity, power that can withstand a failure, and recoverable data. In a local authority that provides services to the public, a system outage is not just a cost; it means services cannot be provided; the ongoing management contract, renewed through a tender, combines monitoring and 24x7 support for that base so that incidents are detected before they affect the front desk.
What is put in writing
A disaster recovery plan that isn't written down does not exist. The document that the client receives includes:
- The impact analysis, system by system, with the RPO and RTO agreed for each one and the estimated cost of one hour of downtime.
- The architecture of copies and replicas: where each copy is located, how often it is created, which one is immutable, and how far back it is possible to go.
- The activation procedurewho declares the disaster, who is notified, the system recovery order and the necessary contacts and credentials, stored outside the infrastructure.
- The communications plan — how the company continues to answer phones and receive emails while the core systems are down.
- The test reports, including the actual recovery time relative to the RTO and the corrections decided upon after each test.
Frequently Asked Questions
We already take backups every day. Is that not enough?
It is the foundation, but it is not a plan. A backup tells you that data exists; it does not tell you where you are going to restore it to if the server has burnt down, who is going to do it, in what order, or how long it takes. The disaster recovery plan answers those questions before they are urgent.
What RTO should we require?
What the business can withstand without serious harm, neither more nor less. Short RTOs require hot standbys ready to go and cost more; RTOs of one to two days can be handled with off-site copies and spare hardware. Impact analysis serves precisely to pin down this figure based on actual costs, not fear.
Where are the replicas?
In a data centre in Portugal, in the cloud, or both, depending on the required RTO and the customer's data localisation requirements. This is defined in writing in the plan.
How often do you test?
At least one full test per year and quarterly partial tests, as a minimum. Each test is documented with the actual recovery time, compared with the agreed RTO. A plan that is not tested is merely an intention.
Does the policy cover ransomware?
Yes, and it is the scenario we design for first: immutable copies, network isolation before booting the replica, and identifying the pre-infection recovery point.
And business continuity, is it the same thing?
Business continuity is the broader concept — it includes people, facilities and processes, not just systems. Disaster recovery is the technological part of that plan. We handle the technological part and coordinate with whoever handles the rest, where applicable.
How long does it take to get a plan ready?
In a company with 20 to 50 workstations and one or two servers, the impact analysis and design take two to four weeks; the implementation of replicas and immutable backups, another two to four; the first full test takes place within the first three months. Environments with multiple sites or industrial production require more time, as defined in the assessment.
Who activates the plan in a disaster?
It is defined in the procedure: normally, company management declares the disaster, based on the written criteria, and DataRoad performs the recovery. In plans with 24×7×365 coverage, execution can begin at any time, without waiting for working hours.
Disaster recovery is one of IT services for businesses by DataRoad, in collaboration with the managed backups, a 24/7 monitoring and a cybersecurity.
Where we operate
We design and test disaster recovery plans for clients across the country; our on-site support mainly covers Greater Lisbon. We have dedicated pages for Lisbon, Cascais, Oeiras, Sintra, Leiria, Coimbra e Porto. See all areas of expertise.
Contact us
If you want to know how quickly your business would be back up and running after a disaster — rather than how quickly you would like it to be — the initial conversation is free. Call 211 459 950 (weekdays, 09:30–13:00 and 14:00–18:30) or write to [email protected].
Some of the companies that entrust their infrastructure to DataRoad, sectors where downtime costs far more than IT support
