trio.so
Templates

Data Backup and Recovery Policy Template (Free Word + Excel)

Free data backup and recovery policy template in Word and PDF, with backup and restore procedures, a restore test form and an Excel log of RPO and RTO.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

A data backup and recovery policy sets the rules for backing up your systems and data and getting them back: what is backed up, how often, where the copies are kept, who checks them and how restores are tested. This free template gives you the full policy in Word and PDF, with a step-by-step backup procedure, a restore procedure, a restore test record and a worked example, plus an Excel backup schedule and restore test log.

It works for a one-person IT team at a 20-person company and for an IT lead at a company of 1,000. Fill in the brackets, set your system tiers, and it is ready to approve.

In short

  • Put every system in a tier. The tier sets its RPO (how much data you can lose), its RTO (how long it can be down) and how often you test a restore.
  • Keep three copies on two kinds of storage, one of them offsite, and one copy isolated from your everyday admin accounts.
  • Check backup results every working day. A failed job nobody notices turns up during the next restore, which is too late.
  • Test restores on a schedule and time them. Until you have restored from a backup, you don't know that it works.
  • SaaS data and laptops count too: read your providers' terms, and keep company files in storage that is backed up.

What Is a Data Backup and Recovery Policy?

A data backup and recovery policy (also called a data backup policy, backup policy or data recovery policy) is a short, approved document that says how your organization protects its data with backups and how it gets that data back. It names the systems in scope, sets recovery targets for each one, and says how backups are run, protected, kept, checked and tested, and who is responsible for each part.

It is not the same as a disaster recovery plan. The backup policy is the standing set of rules. The disaster recovery plan is the playbook for getting the whole business working again after a major outage, and it depends on the backups the policy produces. A data retention policy is a third document: it decides how long records are kept, and backup retention should follow it.

Backup and recovery policyDisaster recovery planData retention policy
AnswersHow data is copied, protected and restoredHow the business gets back to work after a major outageHow long each kind of record is kept
CoversEvery system and data set, every dayPeople, sites, suppliers, communications and the order systems come backRecords, from creation to disposal
Usual ownerIT leadOperations or continuity lead, with ITLegal, compliance or records owner
Tested byRestore testsRecovery exercises and tabletop testsRetention reviews

If you need the other two, start with our disaster recovery plan template and data retention policy template.

What to Include in a Backup Policy

A good backup policy is specific enough that a new IT hire could follow it. The template has 12 sections; these are the parts that do the work.

Scope and data classification

List what the policy covers: servers, virtual machines and databases on site and in the cloud, business apps and their configuration, file shares, SaaS data such as email and documents, laptops and phones that hold company data, network device configurations and system documentation. Each system goes into a register with an owner and a data class (restricted, confidential, internal or public). If you don't have classes yet, our data classification policy template sets them up.

Recovery targets: RPO and RTO by tier

The recovery point objective (RPO) is the most data, measured in time, you can afford to lose. The recovery time objective (RTO) is how long a system can be down before it must be back in service. Setting them per system gets messy, so the template groups systems into four tiers:

RPO and RTO on one timeline, and the template's four default tiers
RPO and RTO on one timeline, and the template's four default tiers
TierRPORTOBackup frequencyRestore testTypical systems
Tier 1: Critical1 hour4 hoursHourly or continuous, plus a daily full or synthetic fullEvery 3 monthsFinance and ERP, customer database, identity systems, core line-of-business apps
Tier 2: Important1 day1 dayDailyEvery 6 monthsFile shares, email, CRM, HR and payroll
Tier 3: Standard1 day3 daysDailyEvery 12 monthsIntranet, wiki, ticketing, website
Tier 4: Rebuildable7 days5 daysWeekly, or none if it can be rebuilt from sourceEvery 12 monthsTest systems, laptop and kiosk images, anything you can rebuild

These are starting points. Agree each system's tier with its owner, and have leadership approve the targets, because shorter targets cost more. If a system's backups can't keep up with its RPO, that is a gap to fix or a risk someone accepts in writing.

Backup types and frequency

Backups run automatically on a schedule that fits the RPO. A common pattern is a weekly full backup with daily incremental or differential backups, plus transaction log backups for databases with a short RPO.

TypeWhat it copiesTrade-off
FullA complete copy of the selected data every time.Simplest restore; slowest to run and uses the most storage.
IncrementalOnly what changed since the last backup of any type.Fast and small; a restore needs the last full plus every incremental since.
DifferentialEverything that changed since the last full backup.Grows until the next full; a restore needs the last full plus the latest differential.
SnapshotA point-in-time copy taken by the storage, hypervisor or cloud platform.Quick to take and restore; on the same storage it is not a separate copy.
ImageA copy of a whole machine, including the operating system.Rebuilds a server in one step; large.
Transaction logThe database's change log, copied between full backups.Lets you restore a database to a point in time, which keeps the RPO short.
SaaS backupA copy of SaaS data (mail, files, records) kept outside the provider's own service.Covers deletion and account loss that the provider's retention may not.
ExportA scheduled export from an app that has no backup feature.Better than nothing; check that you can actually import it back.

The 3-2-1 approach and an isolated copy

The 3-2-1 approach is a long-standing practice: keep three copies of your data (the original and two backups), on two kinds of storage, with one copy offsite. Ransomware added a fourth line, because attackers who get admin access try to delete backups first: keep one copy isolated, meaning offline, immutable or in a separate account that your production admins can't change.

The 3-2-1 approach with one isolated copy
The 3-2-1 approach with one isolated copy

Two things that look like backups but aren't: file sync, because a file deleted or encrypted on one device is deleted or encrypted everywhere it syncs, and snapshots kept on the same storage as the live data, because one storage failure takes both.

Encryption and access to backups

  • Encrypt backups in transit and at rest, and keep the keys apart from the backups. Our data encryption policy template covers the key rules.
  • Give backup admin rights only to named people, using accounts separate from their daily and server admin accounts, with MFA.
  • Require a second person to approve deleting backups or shortening retention.
  • Review who can reach the backup console and storage every six months.

Retention

Backup setKept for (template default)
Daily backups30 days
Weekly backups12 weeks
Monthly backups12 months
Yearly backups[7] years, only where law or contract needs it
Legal holdUntil the hold is lifted in writing

Legal, regulatory and contract rules win over these defaults, so check them with whoever owns your data retention policy. Delete expired backups on schedule and wipe or destroy backup media before disposal.

Roles

RoleResponsibilities
Policy ownerOwns this policy, approves exceptions, reviews it every year, reports backup and restore test results to leadership.
Backup operatorConfigures and runs backup jobs, reviews results every working day, fixes failures, runs restore tests and keeps the logs.
System and data ownersSet each system's tier with IT, approve restores of their data and confirm restored data is correct.
Security leadApproves who can reach and delete backups, checks encryption and the isolated copy, joins restore decisions after a security incident.
LeadershipApproves the policy and the recovery targets, and accepts in writing any risk that will not be fixed.
Service providersDo what their contract says about backups and restores; the contract names it.
All staffSave company data in approved storage, not only on a laptop or phone, and report lost devices and lost data at once.

In a small company one person may hold three of these roles. Write the names in anyway, plus a backup person for the backup operator.

Monitoring and failed jobs

  • Review every backup job result each working day and log it.
  • Open a ticket for a failed or missed job within one working day, re-run it and confirm it succeeds.
  • Escalate a job that fails twice in a row, or a system past its RPO, to the policy owner.
  • Check storage capacity monthly, with an alert before it runs out.
  • Report RPO breaches, failed jobs and restore test results to leadership every quarter.

SaaS data: Microsoft 365, Google Workspace and other apps

SaaS providers run the service and keep it available. Getting back data that your users deleted, that an attacker encrypted, or that sat in an account you closed is often your job, and the provider's retention may be shorter than you need. For each SaaS app in scope, read the provider's terms on retention and restore, write down what they cover, and decide whether you need a separate backup. Treat a monthly export as a stopgap, and test that you can import it back.

Endpoints and laptops

  • Company data is saved to storage that is backed up (a file server, OneDrive, SharePoint or Google Drive), not only on a laptop or phone.
  • Laptops and phones are encrypted, and staff report a lost or stolen company device within 24 hours so IT can wipe it.
  • Laptops are rebuilt from a standard setup rather than restored, so the time it takes to set up a replacement is part of the RTO.
  • Device backup settings, such as iCloud backup on iPhones or Time Machine on Macs, are allowed or blocked on purpose by device policy.

Backup Procedure Template, Step by Step

The policy says what must happen; the procedure says how. Here is the backup procedure from Appendix A of the Word file. Add your backup tool's job names and screens to it.

The backup procedure in six steps, from the register to a tested restore
The backup procedure in six steps, from the register to a tested restore
  1. Register the system. Add it to the system register with its owner, data class and tier. The tier sets its RPO, RTO and restore test interval.
  2. Configure the job. Choose what to back up (data, configuration, system state), the backup type and a schedule that fits the RPO. Point it at the primary backup storage.
  3. Add the other copies. Copy each backup to a second kind of storage and offsite, and keep one copy isolated: offline, immutable or in a separate account.
  4. Protect the backups. Encrypt backups in transit and at rest, keep the keys apart from the backups, and give backup admin rights only to named people, with MFA and accounts separate from daily and server admin accounts.
  5. Prove the first backup. Run the first full backup, check it completed, and restore a few files or records to show it can be read.
  6. Check results every working day. Review every job result and log it. Open a ticket for any failed or missed job within [1] working day, re-run it and confirm it succeeds. Escalate a job that fails [2] times in a row to the policy owner.
  7. Apply retention. Let old copies expire on schedule. Keep copies under legal hold until the hold is lifted in writing.
  8. Review every month. Compare the register with reality: new systems, retired systems, storage capacity, jobs that keep warning. Update the register and the jobs.

Restore Procedure and Restore Testing

Restores go wrong when they are rushed: the wrong restore point, live data overwritten, or a request from someone who shouldn't have it. The restore procedure in Appendix B slows down the parts that matter:

  1. Log the request. Open a ticket that says what to restore, to which point in time, where to, and why. Confidential and restricted data needs the data owner's approval.
  2. Check who is asking. Confirm the requester's identity and authority before restoring anything, especially for a request that arrives by email or chat.
  3. Pick the restore point. Use the latest good copy before the loss. After ransomware or a compromise, choose a point before the attack and scan it before use.
  4. Restore to a safe place first. Restore to an alternate place where you can, and never overwrite live data without the owner's approval.
  5. Check the data with the owner. Open files, compare record counts, start the app. The owner confirms the data is complete and correct.
  6. Put it back into service. Move the data or system into production, and record the time taken against the RTO and the data lost against the RPO.
  7. Close and learn. Record what was restored, from which copy, how long it took and what went wrong. Fix gaps in jobs, runbooks or targets.

How to test restores

  1. Pick the systems due for a test from the restore test log, at least one per tier each cycle, and rotate through the rest.
  2. Choose the test type: a file or record restore, a full system or database restore to a test environment, a SaaS item restore, or a device rebuild.
  3. Note the restore point used and time the restore from start to a working system.
  4. Have the data owner check the result, then compare the time with the RTO and the age of the restore point with the RPO.
  5. Record pass, partial or fail with any issues, give each issue an owner and a date, and schedule the next test.

How often: the template tests Tier 1 every 3 months, Tier 2 every 6 months and Tiers 3 and 4 every 12 months, and again after a major change. CIS Controls v8.1 Safeguard 11.5 asks for recovery tests quarterly or more often on a sample of assets (it sits in Implementation Group 2).

What to record

Each test record holds the system, test type, restore point used, start and finish times, time to restore against the RTO, age of the restored data against the RPO, the data owner's check, the result, the issues and their fixes, and the next test date. The workbook's Restore Test Log calculates the times, flags tests outside the RTO and shows which systems are overdue. These records are what an auditor or a cyber insurer asks for, and what tells you whether your targets are real.

Backup Policy Example

Here is one Tier 1 system filled in, from the template's worked example. The company and the details are made up.

ItemExample entry
SystemAccounting system on an on-site SQL Server (fictional)
Data class and ownerConfidential · Finance manager
Tier and targetsTier 1 (Critical) · RPO 1 hour · RTO 4 hours · restore test every 3 months
Backup scheduleTransaction log backup every 15 minutes; full backup every night at 01:00; image of the server every Sunday
Copies1) the live database; 2) the backup appliance in the server room (disk); 3) cloud object storage in another region, immutable for 30 days, in a separate account the server admins can't sign in to
3-2-1 check3 copies · 2 kinds of storage · 1 offsite · 1 isolated: OK
ProtectionEncrypted in transit and at rest; backup console uses separate admin accounts with MFA; keys held outside the backup storage
RetentionLog backups 7 days · nightly 30 days · monthly 12 months · year-end 7 years (tax records)
MonitoringBackup operator (Sam, IT) checks results every working day; failures ticketed and re-run the same day
Last restore test14 Oct 2026 · full database restore to a test server · 2 h 40 min (RTO 4 h) · restore point 12 minutes old (RPO 1 h) · Pass
Issue and fixThe runbook missed the step that reconnects the reporting service; Sam added it on 15 Oct 2026
Next test due12 Jan 2027

The workbook's Example tab has 12 made-up systems, including what gaps look like: a customer database with a failing job and no offsite copy, SaaS files whose restore has never been tested, and an HR app backed up only by a monthly export.

What ISO 27001, NIST, CIS and HIPAA Say About Backups

Most frameworks ask for the same things: a written backup approach, backups on a schedule tied to recovery targets, protected copies and tested restores. Here they are by ID, with our short summaries:

FrameworkReferenceWhat it covers
ISO/IEC 27001:2022Annex A 8.13 Information backupKeep backup copies of information, software and systems, and test them regularly, in line with an agreed backup policy (our paraphrase). Related: 5.30 ICT readiness for business continuity.
NIST SP 800-53 Rev. 5CP-9 System BackupBack up user-level and system-level information and system documentation at a frequency consistent with recovery time and recovery point objectives, and protect the backups. Enhancements in the moderate baseline: CP-9(1) test backups for reliability and integrity, CP-9(8) cryptographic protection.
NIST SP 800-53 Rev. 5CP-10 System Recovery and ReconstitutionRecover the system to a known state within a time consistent with its recovery time and recovery point objectives. CP-4 covers testing the contingency plan.
CIS Controls v8.1Control 11 Data Recovery (11.1 to 11.5)11.1 documented data recovery process, reviewed yearly; 11.2 automated backups, weekly or more often; 11.3 protect recovery data like the original; 11.4 an isolated instance of recovery data. These four are in IG1. 11.5 (IG2): test recovery quarterly or more often for a sample of assets.
HIPAA Security Rule45 CFR 164.308(a)(7)(ii)(A) Data backup plan (Required)Procedures to create and maintain retrievable exact copies of electronic protected health information. The same standard has a disaster recovery plan (B, Required) and testing and revision procedures (D, Addressable). 164.310(d)(2)(iv) covers a retrievable copy before equipment is moved.

ISO 27001 backup policy. ISO/IEC 27001:2022 Annex A 8.13 is the control behind the backup policy. The standard leaves the frequency and retention to you, so your policy sets them from your risk assessment. Expect to show the approved policy, records that backups ran, and restore test results. Our ISO 27001 checklist shows where 8.13 fits in the wider project.

The other references: NIST SP 800-53 Rev. 5 (see also our NIST 800-53 checklist), CIS Controls v8.1 Control 11, and the HIPAA Security Rule at 45 CFR 164.308 (see our HIPAA compliance checklist). A policy built from this template covers these themes, but an assessment looks at how you run it, not only at the document. This is a guide, not an audit mapping.

What's in the Download

The data backup and recovery policy template: cover, system tiers and the backup procedure
The data backup and recovery policy template: cover, system tiers and the backup procedure
  • Word policy template (Data-Backup-and-Recovery-Policy-Template-trio.so.docx): 12 policy sections with owners and fill-in fields, the backup procedure, the restore procedure, a restore test record, a worked example, framework references and related guides.
  • PDF of the policy, ready to print.
  • Excel workbook (Backup-Schedule-and-Restore-Test-Log-trio.so.xlsx): Start Here, Settings (tiers with RPO and RTO, lists), a System Register with the 3-2-1 check, an Example tab with 12 made-up systems, a Backup Job Log that flags RPO breaches, a Restore Test Log that times each restore against the RTO, a Dashboard and Sources. Formulas only, no macros.
The workbook's Example tab: 12 made-up systems with their 3-2-1 check, RPO status and restore test status
The workbook's Example tab: 12 made-up systems with their 3-2-1 check, RPO status and restore test status

Where trio.so Fits

trio.so does not back up or restore data. Your backup tool, your cloud or SaaS provider's backup service or your MSP does that, and this policy names who.

Where trio.so fits is the device side of the policy: the laptops, desktops, phones and tablets that hold company data, and how fast you can replace one. trio.so is mobile device management for Windows, macOS, Linux, iOS/iPadOS and Android, from one console. For the backup policy, it gives you:

  • A device inventory for Windows, macOS, Linux, iOS/iPadOS and Android with each device's owner and serial number, so you know every endpoint that holds company data.
  • Disk encryption enforcement, with each device's encryption status, so a lost laptop and any files on it stay protected.
  • Policies for backup settings on Apple devices: Time Machine settings on company-owned Macs, and a restriction that allows or blocks iCloud backup on iPhone and iPad.
  • Quick setup of a replacement device: Windows Autopilot and Apple Business enrollment configure a new device at first start, and its assigned apps install on it.
  • Remote wipe, a full factory reset, for lost or stolen company-owned Windows, macOS, iOS/iPadOS and Android devices.
  • Policy status for each device (applied, failed or pending) and evidence export, as records for a review or an audit.

See how the device inventory works, or how compliance automation exports evidence. Plans start at $5 per device.

Start free trial Book a demo

14-day free trial. No credit card required.

Related Templates

Sources. Last reviewed November 2026. Framework names and IDs identify their publishers' documents; descriptions are our own summaries. trio.so is not affiliated with or endorsed by ISO, NIST, CIS, HHS, Microsoft, Google or Apple. This template is a guide, not legal or audit advice. The tiers, targets and retention periods are our suggestions, not the requirements of any framework.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Know every device that holds company data

trio.so does not back up data. It shows every managed device with its owner, serial number and encryption status, and wipes lost company-owned devices.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

A data backup policy is an approved document that sets how an organization backs up its systems and data and how it restores them: what is in scope, how often backups run, where the copies are kept, how they are protected and kept, who checks them and how restores are tested.

Scope and data classes, system tiers with RPO and RTO targets, backup types and frequency, copies and where they are kept (the 3-2-1 approach with one isolated copy), encryption and access to backups, retention, roles, monitoring of failed jobs, restore requests, restore testing, exceptions and review. This template covers all of them and adds backup and restore procedures.

As often as each system's RPO needs. A system that can lose no more than an hour of data needs a backup at least every hour; daily backups suit data you could recreate a day of. CIS Controls v8.1 Safeguard 11.2 says to run automated backups weekly or more often, depending on how sensitive the data is.

RPO (recovery point objective) is the most data, measured in time, you can afford to lose: an RPO of 4 hours means a backup at least every 4 hours. RTO (recovery time objective) is how long a system can be down before it must be back in service. RPO drives how often you back up; RTO drives how you restore and what you test.

A backup policy is the standing set of rules for copying, protecting and restoring data. A disaster recovery plan is the playbook for getting the whole business working after a major outage: people, sites, suppliers, communications and the order systems come back. The plan depends on the backups the policy produces.

ISO/IEC 27001:2022 Annex A control 8.13 Information backup covers keeping backup copies of information, software and systems and testing them regularly, in line with an agreed backup policy. The standard leaves frequency and retention to you, so your policy sets them from your risk assessment.

On a schedule tied to each system's tier, and after major changes. This template tests critical systems every 3 months, important ones every 6 months and the rest every 12 months. CIS Controls v8.1 Safeguard 11.5 says to test recovery quarterly or more often for a sample of assets.

Related

From the blog

The related industry news, interviews, technologies, and resources.