Business Data Backup Strategy: How to Build One You Can Restore From
Short answerBuild it system by system: list what the business cannot work without, set a recovery point and recovery time target for each, and keep 3 copies on 2 media types with 1 offsite and at least one offline or immutable. Then prove it with scheduled restore tests, because a backup is only as good as its last tested restore.

What is a business backup strategy?
A business backup strategy is a written plan for which data you copy, how often, where the copies are kept and how quickly each system must be restored, and it is only proven by a tested restore. Start with the systems the business cannot work without, set a recovery point and recovery time target for each, and keep at least one copy offline or immutable, because many ransomware strains try to delete or encrypt the backups they can reach. CISA's ransomware guidance is direct: keep offline, encrypted backups of critical data and test them regularly.
Need help applying this to your business? See data backup services in Dubai, or describe your requirements to GR IT.
What should you back up first?
Back up the systems that would stop the business if they disappeared, found through an inventory, not memory. NIST's contingency planning guide lists examples of the resources a business impact analysis should identify: "facilities, personnel, equipment, software, data files, system components, and vital records." For a typical office, the data side includes:
- Line-of-business data: accounting, ERP and CRM systems and their databases.
- Files: file servers, NAS devices and laptops holding the only copy of anything.
- Microsoft 365: Exchange mailboxes, OneDrive accounts and SharePoint sites.
- Servers: CISA recommends keeping up-to-date "golden images" of critical systems so they can be rebuilt quickly.
- Configurations and software: firewall and switch settings, installers, licence keys and the documentation needed to rebuild.
Cloud services belong on the list too. Microsoft's shared responsibility model is explicit: "For all cloud deployment types, you own your data and identities."
Is the 3-2-1 rule still enough?
The 3-2-1 rule is still the right baseline, but on its own it does not cover ransomware. A US-CERT paper on data backup options, published by CISA, sets it out: keep 3 copies of any important file (1 primary and 2 backups), on 2 different media types, with 1 copy offsite. The paper presents it as a way to improve your chances of recovering lost or corrupted data. Ransomware adds an attacker who goes looking for your backups: CISA's #StopRansomware Guide warns that "many ransomware variants attempt to find and subsequently delete or encrypt accessible backups." So add two things:
- One copy offline or immutable. Offline means disconnected from your network. CISA notes that some cloud vendors offer immutable storage that can protect stored data without a separate environment, but warns that it does not meet the compliance criteria of certain regulations and that misconfiguring it can be costly.
- Encryption. CISA's advice is offline, encrypted backups of critical data.
If every backup sits with one cloud vendor, CISA suggests considering a multi-cloud approach. Backups are the last layer of ransomware protection.
How do you set RPO and RTO for each system?
Set them system by system from a business impact analysis, not as one company-wide number. NIST SP 800-34 defines both:
- Recovery point objective (RPO): the point in time before the outage to which data can be recovered, set by how much data loss the business can tolerate. It drives backup frequency.
- Recovery time objective (RTO): the maximum time a system can stay unavailable before the impact becomes unacceptable. It drives the choice of recovery technology.
NIST describes three typical steps: identify the business processes each system supports and how critical they are, identify the resources needed to resume them, then set recovery priorities. The RTO must normally be shorter than the maximum tolerable downtime, the longest outage the business will accept. If finance can re-enter a day of invoices but not a week, its system needs at least a daily backup. A business impact analysis produces these targets, and our guide to RPO and RTO planning for UAE businesses goes further.
Full, incremental or differential: which fits which system?
Often a combination: NIST SP 800-34 notes that the types can be combined to suit each system's configuration and recovery requirements. It describes the trade-offs:
| Type | What it copies | Strength | Weakness |
|---|---|---|---|
| Full | All files in the selected scope | Finding a file is simple, as everything is in one backup set | Slow to run, and repeated full copies of unchanged files waste storage |
| Incremental | Files created or changed since the last backup of any type | Shorter backup times and more efficient use of storage | A restore can need the last full backup plus every incremental since |
| Differential | Files created or changed since the last full backup | A restore needs only the last full and the last differential | Slower than an incremental, and grows each day until the next full backup |
NIST's example: "a full backup can be conducted on the weekend with differential backups conducted each evening." Let the RPO set the frequency and the RTO set how much restore complexity you can accept.
Does Microsoft 365 need its own backup?
Usually yes, because Microsoft runs the service while you own the data. Two Microsoft features do different jobs:
- Retention policies in Microsoft Purview keep or delete content for compliance. The content "remains in its original location", and if someone edits or deletes it, a copy is retained.
- Microsoft 365 Backup is a separate product for restoring SharePoint sites, OneDrive accounts and Exchange mailboxes to an earlier point in time after ransomware, or an accidental or malicious deletion or overwrite.
Microsoft 365 Backup starts when you create a protection policy that selects what to cover. Microsoft lists recovery points every 10 minutes for the previous two weeks for OneDrive and SharePoint, and a recovery window of 3 months, 6 months, 1 year or 2 years. The backups are created within the protected services' data boundaries, on append-only storage, so decide whether you also need a copy outside the tenant. See Microsoft 365 backup and our Office 365 backup options guide.
How often should you test a restore, and what counts as a pass?
Test on a schedule in your backup policy, most often for critical systems, and after any major change. CISA's guidance is to "regularly test the availability and integrity of backups in a disaster recovery scenario", and NIST's guide says backup tapes should be tested regularly so that files "may be retrieved without errors or lost data". A successful job proves data was copied; only a restore proves you can use it. Count a test as a pass only when:
- the right data came back complete, from the expected point in time;
- the restore finished inside the system's RTO;
- the application opens and a user can work with the restored data;
- some tests use the offline or immutable copy, not only the nearest one;
- steps, timings and failures are recorded, and failures are fixed and retested.
In a real ransomware recovery, CISA warns that care must be taken to identify dropper malware before rebuilding from backups. If you have never run a full restore test, a backup audit or a disaster recovery audit is a practical place to start.
What should backup monitoring catch?
Monitoring should tell you the same day that a backup failed, was skipped or was tampered with. Watch for failed or partial jobs, new servers, mailboxes or sites missing from every backup policy, storage running low, and retention settings changed without a ticket. CISA's threat-hunting checklist also includes "Endpoint modifications that may impair backups, shadow copy, disk journaling, or boot configurations", such as unusual use of vssadmin.exe and wbadmin.exe.
Each alert needs an owner and a response target. On GR IT AMC packages, a backup job that failed overnight is P2: a 10 minute response in support hours (24/7 on GR IT AMC Scale) and a one business day resolution target. Ransomware is P1: a 5 minute response 24/7 and a 4 hour resolution target.
How long should UAE businesses keep backups?
Keep backups long enough to restore from a point before an incident was noticed, and records as long as the law requires, and set both with legal advice. Two federal laws shape the decision:
- Personal data. The Personal Data Protection Law, Federal Decree-Law No. 45 of 2021, came into force on 2 January 2022. It obliges companies that hold personal data to secure it and keep it confidential. A backup of customer or staff records holds personal data, so protect it like the live system.
- Tax records. Federal Decree-Law No. 47 of 2022 on the Taxation of Corporations and Businesses (the Corporate Tax law) requires a taxable person to keep the records and documents that support its tax returns for seven years after the end of the tax period they relate to.
Backup and records retention are different jobs. Microsoft 365 Backup's longest recovery window is two years, so on its own it is not a seven-year archive. Businesses in the DIFC should also check the DIFC Data Protection Law, DIFC Law No. 5 of 2020.
What are the most common backup mistakes?
Not testing restores is the mistake that hides all the others. Three more to check:
- Every copy online. If ransomware can reach the backups with the same access as the live systems, it can delete or encrypt them.
- Plans stored only on the network. A runbook on the failed server is no use. CISA advises a hard copy and an offline version of your incident response plan.
- Unchecked providers. If a provider maintains your backups, CISA says to make sure it follows the same practices and to put your security requirements in the contract.
Sources
- SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems, NIST. Checked 2026-11-03.
- #StopRansomware Guide, CISA. Checked 2026-11-03.
- Data Backup Options, US-CERT, published by CISA. Checked 2026-11-03.
- Shared responsibility in the cloud, Microsoft Learn. Checked 2026-11-03.
- Overview of Microsoft 365 Backup, Microsoft Learn. Checked 2026-11-03.
- Learn about retention policies and retention labels, Microsoft Learn. Checked 2026-11-03.
- Data protection laws, The Official Platform of the UAE Government (u.ae). Checked 2026-11-03.
- Federal Decree-Law No. 47 of 2022 on the Taxation of Corporations and Businesses, with amendments (unofficial English translation), UAE Ministry of Finance. Checked 2026-11-03.
Related Articles
Microsoft 365 Backup in Dubai: How to Protect Office 365 Data
Comprehensive Office 365 backup guide for Dubai businesses. Learn Exchange backup, SharePoint backup, OneDrive backup, compliance, recovery, retention policies, and data protection strategies.
Phishing Simulation for Staff: How to Run One That Works
Run phishing simulations as practice, not as a trap. Tell staff a programme exists, base lures on attacks you really receive, never name or shame anyone, and teach at the moment someone clicks. Then measure how many people report the message, not only how many click it.
What Should a UAE Company Do After a Personal Data Breach?
Contain the breach, work out what personal data was exposed and whose, report it, record it and fix the cause. Article 9 of the UAE PDPL requires the controller to report such a breach to the UAE Data Office and to tell the people affected, within a period the Executive Regulations set. The DIFC and ADGM have their own rules.