Skip to content

Leadership guide · for CIOs, IT directors and CFOs

Disaster recovery planning for UAE businesses: RPO, RTO, DR site options and testing

Most companies have backups. Far fewer can say how long it would take to run the business again after losing their server room or being hit by ransomware, and have tested it. This guide covers the numbers, the DR site options and the tests that turn backups into a plan.

Reviewed by Abu Amir, CEO, Missan Global · Updated

Start with the business, not the backup software

A disaster recovery plan answers one question: after a serious failure, how quickly can each part of the business work again, and how much data will be missing? Those are decisions for leadership. IT's job is to show what each answer costs and then deliver it.

The National Emergency Crisis and Disaster Management Authority (NCEMA) publishes AE/SCNS/NCEMA 7000:2021, the UAE national standard for business continuity management. It is mandatory for designated entities, mostly government and critical sectors, and a sound reference for everyone else. If you supply government or regulated customers, expect their questionnaires to borrow from it or from ISO 22301.

Step 1: list and tier your systems

List every system the business uses and give each a tier:

  • Tier 1: the business stops without it. Usually ERP, email, the main file store, telephony, and sector systems such as a hospital information system or warehouse management.
  • Tier 2: painful but survivable for a day or two. CRM, HR, intranet.
  • Tier 3: can wait a week or run manually.

Include the dependencies people forget: Active Directory or Entra ID, DNS, the firewall, internet links, licence servers and the backup system itself.

Step 2: set RPO and RTO per tier

TierTypical RPOTypical RTO
Tier 115 minutes to 4 hours2 to 8 hours
Tier 224 hours1 to 2 days
Tier 324 to 48 hoursup to a week

These are typical ranges, not targets. A trading company that loses an afternoon of orders has a different answer from a professional services firm. Put the cost of an hour of downtime next to each system; our downtime cost calculator helps. Then have the CFO and the CEO sign the numbers. That signature is what stops the plan being an IT wish list.

Step 3: choose a DR site approach

Cold: backups only

Data is backed up off-site; after a disaster you restore it onto new or rented hardware. Cheapest to run. Recovery takes days, mostly waiting for hardware and restoring large data sets. Fine for Tier 3, rarely for Tier 1.

Warm: replicated, not running

Virtual machines are replicated to a second site or a private cloud at intervals, ready to be started. Recovery in hours. This is the most common choice for mid-sized UAE companies, and where a hosted Sangfor private cloud or FortGrid DR fits.

Hot: running in parallel

Systems run in two locations with near-continuous replication and automatic or fast manual failover. Minutes of downtime, highest cost. Justified for systems where an hour offline costs more than a year of the second site.

Public cloud DR

Replicate on-premises workloads to Azure or another cloud and pay mostly for storage until you fail over. Good economics for some workloads; check data location requirements, licensing and how your users would connect if the office network is the thing that failed.

Most companies end up with a mix: hot or warm for two or three Tier 1 systems, cold for the rest.

Step 4: design for ransomware first

Floods and fires happen. Ransomware happens far more often, and it is built to find and encrypt your backups before it announces itself. Your design needs:

  • At least one immutable or offline copy that admin credentials cannot delete.
  • Backup systems on separate credentials, ideally a separate identity domain, with MFA.
  • Retention long enough to go back before the attacker arrived, often weeks.
  • A clean recovery environment, so you are not restoring onto infected machines.
  • An independent backup of Microsoft 365. Deletion and encryption sync to the cloud too.

Our ransomware recovery guide goes deeper.

Step 5: write the runbook

  1. Header: owner, version, last test date, next review.
  2. Signed RPO and RTO per system.
  3. Invocation criteria: who can declare a disaster, and on what evidence.
  4. Contacts: named people and deputies, IT provider, ISP, key vendors, insurer.
  5. Recovery order: identity and network first, then Tier 1 in agreed sequence.
  6. Step-by-step procedures per Tier 1 system, written so someone other than the author can follow them.
  7. Communications: how staff, customers and suppliers are told, if email is down.
  8. Test log.

Keep a printed and an offline copy. A plan stored only on the server that failed is no help.

Step 6: test it, and keep the evidence

  • Monthly: restore a random sample of files, a mailbox and a database. See why untested backups fail.
  • Twice a year: tabletop exercise with leadership. Walk through a ransomware morning, minute by minute.
  • Once a year: fail over at least one Tier 1 system and measure the actual RTO against the signed one.
  • After every major change: new ERP, office move, new site. Update and re-test.

DR readiness checklist

  • System inventory with tiers and dependencies.
  • RPO and RTO per system, signed by leadership.
  • Immutable or offline backup copy; separate backup credentials with MFA.
  • Independent Microsoft 365 backup.
  • DR site approach chosen per tier, with costs approved.
  • Written runbook, stored offline, with named roles.
  • Monthly restore tests logged; annual failover test completed.
  • Cyber insurer and key customers' requirements mapped to the plan.

Where Missan helps

We design and run backup and DR for UAE organisations: FortGrid backup cloud, Sangfor HCI and hosted private cloud in the UAE, Microsoft 365 backup, and the runbooks and tests that go with them. We are a Sangfor Gold Partner and have 22+ years of infrastructure work behind us. You get fixed quotes after a site survey, and staged migrations with a way back when we move systems onto new DR infrastructure. Start with the backup, DR and cloud page.

Download the checklist (PDF)

DR readiness checklist, ready to print

The checklist from this guide on one or two A4 pages, with tick boxes, for your next planning meeting.

Our team may contact you about this topic. We reply within one business day if you ask us anything, and you can tell us to stop at any time. See ourprivacy policy.

Related Missan services

Frequently asked questions

What is the difference between RPO and RTO?

RPO (recovery point objective) is how much data you can afford to lose, measured in time: a four-hour RPO means you can lose at most four hours of work. RTO (recovery time objective) is how long a system can be down before the damage is unacceptable. Both are business decisions; IT designs to meet them.

Is there a UAE standard for business continuity?

Yes. AE/SCNS/NCEMA 7000:2021 is the UAE national standard for business continuity management, published by the National Emergency Crisis and Disaster Management Authority. It is mandatory for designated entities, mainly government and critical sectors. Private companies often use it, or ISO 22301, as a reference even when not required to.

Can Microsoft 365 or Azure be our disaster recovery?

Cloud services are resilient against hardware failure, but they do not protect you from deletion, ransomware that syncs into OneDrive, or a compromised admin account. You still need an independent backup of Microsoft 365 data, and a plan for what happens if your identity platform is unavailable.

How often should we test disaster recovery?

At minimum, restore a sample of data every month, run a tabletop exercise twice a year and do a full failover test of your most critical systems once a year. Regulated organisations usually test more often. Keep a record of every test: insurers and auditors ask for it.

What does a DR site cost?

It depends on your RTO more than anything else. A cold site with backups you restore on demand costs little to run but takes days. A warm site with replicated systems costs more but recovers in hours. A hot standby is the most expensive. We give fixed quotes after a site survey and an agreed RPO and RTO per system.

Can our DR copy stay in the UAE?

Yes. Our hosted private cloud runs on a UAE-based Sangfor HCI cluster, and FortGrid, our backup platform, is run and supported by our team in the UAE. Where data must stay in the country, we design the backup and DR targets around that and confirm the storage location in writing.

This guide is general information for planning, not legal or tax advice. Regulations and deadlines change; confirm the current position with the official source linked in the text and with your own advisers. Last reviewed 17/10/2026.

Tell us what you need

A short note is enough. We reply within one business day.

4.6★ from 200+ Google reviews We reply within one business day
Add country and company size (optional)

No newsletter and no sales sequence. We only use this to answer you. See our privacy policy. Prefer to talk? +971 6 562 6006 or WhatsApp us

Get a DR design with RPO and RTO you can sign off

We map your critical systems, agree targets with you and design a DR option that meets them, with a fixed quote after a site survey. We reply within one business day.