DRP and business continuity
A plan that sets what comes back first, how fast (RTO) and from which backup, when the servers go down, when there is ransomware or when the office is unavailable. We build it from the business’s needs, document it and test it in an exercise (DR test), so that on the day of the incident nobody has to improvise.
When something fails,
you know what to do
Every critical system has a recovery time target, a backup source and a role holder responsible for it. The plan is written down, kept outside the systems as well, and tested with a real restore.
- A BIA and RTO/RPO targets for every critical system
- Immutable backup and an air-gapped copy
- Tabletop exercises and actual restores
Who this is for
Businesses that depend on systems to work
Where a day without accounting, the CRM or the file server means work stops (downtime) and customers wait.
Organizations with servers in the office
Whose backup sits in the same room and on the same network, and has never been tested with a full restore (restore test).
Organizations that must present a plan
When a customer, an insurer, a regulator or an ISO 27001 audit asks for a documented continuity plan (BCP) and records of an exercise.
Sound familiar?
These are gaps that usually come to light only on the day you need to restore.
- There is a backup, but nobody knows how long it will take to restore from it (RTO)
- The backup sits on a NAS on the same network, with the same passwords
- Nobody has defined what comes back first (recovery order) if all the servers go down
- The plan, if there is one, is stored on the server that might fail
- It is not clear who decides, who updates customers and who talks to the vendors (crisis communication)
- A full restore exercise (DR test) has never been done
What DRP and continuity planning includes
The plan is built around what the business needs to keep working, and the technical solutions follow from that.
Business impact analysis (BIA)
Mapping the critical processes, the systems and vendors they depend on, and how long the business can work without them.
RTO and RPO targets
For each system: how quickly it must come back, and how much data may be lost.
A written recovery plan (DRP)
Restore order, dependencies between systems, contacts and vendor details, in a format that is available even when the systems are down.
DR site
A secondary site in the cloud or another location, to which the critical systems can be moved when the main site is unavailable.
Immutable and offline backup
A copy that cannot be changed or deleted for a defined period, and another copy outside the network (air-gapped), designed to hold up even against an attacker who has gained admin rights.
Ransomware recovery
A dedicated procedure (ransomware playbook): containment, identifying a clean point in time, restoring to an isolated environment (clean room) and resetting passwords before returning to work.
Roles and communication (crisis management)
Who declares an incident, who decides, who updates employees, customers and vendors, and when to report to outside bodies.
Exercises
Tabletop exercises with management and real restore exercises (DR tests), with a record of the actual times and fixes for whatever did not work.
What we take care of, in detail
Planning
- BIA: critical processes, systems, vendors and dependencies
- Defining RTO, RPO and maximum tolerable period of disruption (MTPD) for each process
- BCP: alternative ways of working when a system or the office is unavailable
- DRP: restore order (recovery order), technical dependencies and decision points
- Roles, an escalation path and contact lists
- Keeping the plan outside the systems too: a printed copy and an offline copy
Recovery infrastructure
- A DR site in the cloud or a secondary location, warm or cold according to the targets
- Replication of virtual machines for critical systems
- Backup by the 3-2-1-1-0 rule: three copies, two types of media, one copy off-site, one immutable or offline copy, and zero errors on verification
- Immutable backup and an offline or air-gapped copy
- Separate permissions and accounts between the backup system and production
- Full restore (bare metal) and Active Directory restore
Ransomware and exercises
- A ransomware recovery procedure: containment, a clean point in time, an isolated restore environment (clean room)
- Scanning backups before restoring, so the attacker is not brought back into the network (reinfection)
- Resetting passwords and admin accounts before returning to production (credential reset)
- Scenario-based tabletop exercises with management
- Real restore exercises (DR tests) and measuring the actual RTO
- An exercise report, gaps and an updated plan (lessons learned)
From the first conversation to an organized routine
- 1
Introductory call
Which systems the business needs in order to work, and what exists today for backup and recovery.
- 2
BIA and targets
Mapping processes and dependencies, and defining RTO and RPO for every critical system, approved by management.
- 3
Planning and setup
Matching the backup and the DR site to the targets, and writing the plan and the roles.
- 4
Exercise and update
A tabletop exercise and a real restore (DR test), closing the gaps and updating the plan when the environment changes.
Why a backup alone is not a recovery plan
A backup answers the question of whether the data exists somewhere else. A recovery plan (DRP) answers the question of how the business gets back to work, in what order and how fast.
The BIA sets the targets
Before choosing technology you need to know what matters to the business. The BIA identifies the critical processes, the systems they need and the damage caused by every hour of downtime. The RTO and RPO targets are derived from it, and they determine whether a nightly backup is enough or continuous replication to a DR site is needed.
RTO and RPO in plain language
RTO is the maximum time a system can be down until it comes back. RPO is the amount of data you can afford to lose, and it is measured in time: if the last backup ran last night, a whole day of work may be lost. Shorter targets cost more, so they are set separately for each system.
Immutable and offline
Ransomware attackers look for the backups and try to delete or encrypt them before they encrypt the servers. An immutable backup cannot be changed or deleted until its retention period ends, even with admin rights. An offline copy, not connected to the network, adds another layer in case the backup system itself was hit.
Recovering from ransomware is different from a regular restore
After an attack you cannot simply put back the last backup, because the attacker may have been in the network for days or weeks before the encryption (dwell time). You need to identify a clean point in time, restore to an isolated environment (clean room), scan, reset passwords and admin accounts, and only then reconnect to the network.
An exercise reveals what the document hides
In a tabletop exercise management walks through a scenario and discovers decisions nobody defined: who approves a shutdown, what to tell customers, when to report to the Privacy Protection Authority. In a real restore exercise (DR test) you find a missing password, an expired license or an undocumented dependency. It is better to find this in an exercise than on the day of the incident.
Guide: How to map critical suppliers: who brings the business to a halt if they go down
A BCP is the continuity plan for the whole business: how to keep serving customers when a system, an office or a vendor is unavailable, including alternative ways of working. A DRP is the technical part: how to restore the systems and data, in what order and how fast. Both rely on the same BIA.
Cloud backup is a good foundation, but you need to check how long it takes to download a whole server from it, whether it is protected from deletion (immutable) by someone who obtained the passwords, and what the restore order is. Without answers to these questions, the actual downtime may last much longer than the business can tolerate.
It depends on the RTO targets. If the business can work for a while without the systems, restoring from backup may be enough. If a quick return is required, or the office itself may be unavailable, a DR site in the cloud or another location lets you move the critical systems there.
Regularly, on a schedule set in the plan, and also after every significant change to the infrastructure (change management): a move to the cloud, a new server or a replacement of the backup system. An exercise that is not repeated quickly loses its value, because the environment changes.
Activate the ransomware procedure: disconnect what was affected (containment), preserve evidence (forensics) and declare an incident according to the escalation path. The restore is done from a clean point in time to an isolated environment, and at the same time reporting obligations are checked, for example to the Privacy Protection Authority when personal data was exposed.
Yes. ISO 27001, NIST CSF, customer security questionnaires and cyber insurers ask about a documented continuity plan and exercises. A written plan with exercise reports gives an answer backed by evidence instead of a declaration.
More you can centralize with us
Virtualization and Servers
Planning, setup and migration of virtualization environments in your own data center: Hyper-V, VMware and Proxmox.
Information security and cyber for organizations
An outsourced CISO, risk management and compliance, hardening, penetration tests, monitoring and response to cyber incidents (incident response).
Backup, recovery and continuity
Cloud and off-site backup for servers, workstations, websites and M365, with restore tests and DRP planning.
Want to know how long it would take your business to get back to work?
Tell us briefly about your business and what concerns you about your IT. We’ll get back to you to understand what you need and suggest a way of working that fits.
Business hours: Sunday to Thursday, 08:00 to 17:00
Existing client? Open a support ticket