[Company name]
Data Backup Plan and Policy
| Organization | [Company name] |
|---|---|
| Document | Data Backup Plan and Policy |
| Document owner | [Owner name], [Owner title] |
| Approved by | [Approver name], [Approver title] |
| Effective date | [Effective date] |
| Version | [Version] |
| Review frequency | Reviewed [Review frequency] and after any significant change |
| Classification | Internal use |
1. Purpose
This policy establishes how [Company name] backs up its data and systems, how long backup copies are kept, how they are protected, and how the ability to restore them is tested. Its purpose is to make sure that business data can be recovered after hardware failure, accidental deletion, cyberattack, natural disaster, or any other event that destroys or corrupts information.
This policy supports the IT Disaster Recovery Plan and the Incident Response Plan. Where those plans rely on backups, the requirements in this document apply.
2. Scope
This policy applies to all data created, received, or stored by [Company name], regardless of where it is stored, including:
- On-premises servers, network storage (NAS), and virtual machines at [Primary office address]
- Cloud services, including [Email / productivity platform] and [Main line-of-business application]
- Company laptops and desktops, where business data is stored locally
- Configuration of network equipment such as firewalls, switches, and wireless controllers
- Documentation, passwords, and encryption keys needed to perform a recovery
This policy applies to all employees, contractors, and service providers, including [IT provider / MSP], who manage or have access to company data or backup systems.
3. Policy Statement: The 3-2-1-1-0 Rule
[Company name] follows the widely used 3-2-1 backup rule, strengthened for modern ransomware threats:
| Element | Requirement | How we meet it |
|---|---|---|
| 3 copies | Keep at least three copies of important data: the live production data plus two backups. | Production data, local backup, off-site backup |
| 2 media types | Store backups on at least two different types of storage or platforms. | Local backup appliance or NAS, plus cloud storage |
| 1 off-site | At least one copy is stored in a different physical location, far enough away to survive a local disaster. | [Offsite / cloud backup location] |
| 1 immutable or offline | At least one copy cannot be changed or deleted, even by an administrator account, for a set period (immutable), or is disconnected from the network (air-gapped). | Immutable cloud storage or backup vendor retention lock |
| 0 errors | Backups are monitored and restores are tested so that recovery is verified, not assumed. | Daily monitoring and scheduled restore tests (Section 10) |
Drafting note: For Florida businesses, "off-site" should mean outside the same storm impact area. A second copy at the owner's home five miles from the office may be lost in the same hurricane. A cloud region in another part of the country is usually the simplest answer.
4. Data and System Inventory
The backup administrator maintains an inventory of systems and data that must be backed up. Any new server, application, or cloud service must be added to this inventory, and to the backup schedule, before it is used for business data.
| System / data | Location | Data owner | Contains sensitive data? | Backup method |
|---|---|---|---|---|
| File server / shared drives | On-premises server | [Owner name] | Yes | Image-based backup via [Backup solution / provider] |
| [Main line-of-business application] | Server or vendor cloud | Department manager | Yes | Application-aware backup or vendor export |
| Email, calendars, contacts | [Email / productivity platform] | [Owner name] | Yes | Third-party SaaS backup |
| Cloud file storage (OneDrive, SharePoint, Google Drive) | [Email / productivity platform] | Each user / department | Yes | Third-party SaaS backup |
| Accounting data | Server or cloud | Finance lead | Yes | Included in server backup or vendor export |
| Firewall and switch configurations | Network devices | [IT provider / MSP] | No | Configuration export after changes |
| Laptops with local data | Endpoints | Each user | Possibly | Redirect to cloud storage; endpoint backup if required |
Drafting note: Employees should store business files in approved shared or cloud locations, not only on a laptop desktop. The simplest endpoint backup strategy is to make sure there is nothing on the endpoint that exists nowhere else.
5. Backup Schedule and Retention
Backups run on the schedule below. Retention is set long enough to recover from problems discovered late, such as ransomware that sat quietly for weeks or a file deleted months ago, while respecting legal and contractual retention requirements.
| Data / system | Backup frequency | Backup type | Local retention | Off-site retention |
|---|---|---|---|---|
| Servers (file, application, domain) | Every 1-4 hours during business hours; nightly | Image-based incremental | 14-30 days | 30 daily, 12 monthly, 7 yearly |
| [Main line-of-business application] database | Hourly, or per vendor guidance | Application-aware | 14 days | 90 days minimum |
| [Email / productivity platform] mail and cloud files | 2-4 times per day | SaaS backup | n/a | 1 year minimum, or as required |
| Network device configurations | After every change, and monthly | Configuration export | Last 5 versions | Last 5 versions |
| Endpoints (if used) | Daily | File-level | n/a | 30 days |
Records that the business must keep for legal, tax, or regulatory reasons are retained according to the company's record retention schedule. Backups are not a substitute for a records management system, but retention must never be shorter than what the business is required to be able to produce.
Drafting note: Check with your accountant, attorney, or industry regulator for how long specific record types must be kept. Healthcare, legal, financial, and tax records often have their own retention rules.
6. Backup Security and Encryption
- All backups are encrypted in transit and at rest using strong, industry-standard encryption (for example, AES-256) provided by [Backup solution / provider].
- Encryption keys and passphrases are stored in [Company password manager] and are accessible to at least two authorized people. Losing the key means losing the backup.
- Local backup storage is kept in a locked, access-controlled area and is not shared with general-purpose file storage.
- Backup systems are patched and kept on supported versions like any other critical system.
- Where supported, backup appliances are placed on a separate network segment that ordinary workstations cannot reach.
7. Access to Backup Systems
Attackers target backups first, because deleting them makes a ransom demand more effective. Access is therefore restricted:
- Only the backup administrator, [Backup administrator], and named staff at [IT provider / MSP] may administer backup systems.
- Backup consoles use unique named accounts, never shared logins, and require multi-factor authentication (MFA).
- Backup administrator accounts are separate from normal email and domain administrator accounts, so a single stolen password cannot reach both production and backups.
- Deleting backups, shortening retention, or disabling immutability requires approval from [Approver name] and is logged.
- Access is reviewed at least quarterly and removed immediately when a person leaves or changes roles.
8. Cloud and SaaS Data (Microsoft 365, Google Workspace)
Cloud platforms such as [Email / productivity platform] keep services running, but they operate under a shared responsibility model: the provider protects its infrastructure, while the customer is responsible for its own data. Built-in features like the recycle bin and version history have limited retention and do not protect against every scenario, such as a compromised account deleting data, a sync error spreading corruption, or an employee purging files before they leave.
For this reason, [Company name] uses a third-party backup service to back up:
- All user mailboxes, including shared mailboxes
- OneDrive / Google Drive for every licensed user
- SharePoint sites and Microsoft Teams files (or Google shared drives)
- Calendars and contacts
- Mailboxes and files of departed employees, for the retention period in Section 11
New users are added to the SaaS backup automatically or as part of the onboarding checklist. The backup administrator confirms monthly that the number of protected users matches the number of licensed users.
9. Monitoring and Alerting
- Every backup job sends success, warning, and failure notifications to [Backup alert email], which is monitored by [IT provider / MSP].
- Failed or missed backups are investigated and corrected within one business day. Two consecutive failures of any Priority 1 system are escalated to [Owner name].
- Off-site replication status is checked at least weekly to confirm the off-site copy is current.
- Available storage capacity is reviewed monthly so backups do not stop because a disk or quota is full.
- A short monthly backup report (jobs, failures, storage, tests performed) is provided to [Owner name].
10. Restore Testing
A backup is only as good as the last successful restore. [Company name] tests restores on the following schedule:
| Test type | Frequency | Scope | Pass criteria |
|---|---|---|---|
| File / folder restore | Monthly | Random files from the file server and cloud storage | Files open correctly and match the expected version |
| Mailbox item restore | Quarterly | Deleted email or folder from a sample mailbox | Items restored to the mailbox intact |
| Full server / VM restore | Quarterly | One Priority 1 server, rotating | Server boots, applications run, restore completed within RTO |
| Off-site / immutable copy restore | Twice a year | Restore from the off-site copy, not the local one | Data retrievable within the time the DR plan assumes |
| Full recovery exercise | Annually | Restore critical systems as in a real disaster | All Priority 1 systems restored and verified |
Restore test procedure
- Select the test items, rotating systems so every critical system is tested at least once a year.
- Restore to an isolated location (test folder or isolated virtual network) so production data is not overwritten.
- Record the start and finish time to measure actual recovery time.
- Have the data owner confirm the restored data is complete and usable.
- Record the result in the restore testing log below. Any failure is treated as an incident and fixed promptly.
- Delete test restores when finished so sensitive data is not left in extra locations.
Restore testing log
| Date | System / data tested | Backup copy used (local / off-site) | Time to restore | Result (pass / fail) | Verified by | Notes / follow-up |
|---|---|---|---|---|---|---|
11. Offboarding and Departed-Employee Data
When an employee leaves, their data is preserved before accounts are removed:
- Confirm the departing user's mailbox and cloud files are included in a current backup.
- Convert the mailbox to a shared mailbox or transfer ownership to the manager, as appropriate.
- Transfer files needed by the business to a shared location.
- Retain the departed employee's backup data for [Departed-employee data retention], or longer if subject to a legal hold or records requirement.
- Collect company laptops and confirm no business data exists only on the device before it is wiped.
Backup data subject to a legal hold must not be deleted until [Legal counsel] or management releases the hold in writing.
12. Secure Disposal of Backup Media
Backup drives, tapes, NAS devices, and appliances that are retired or fail are wiped using a recognized secure erasure method or physically destroyed. Disposal is recorded (device, serial number, method, date, and who performed it). Cloud backup data is deleted according to the retention schedule when a service is terminated, and written confirmation is requested from the provider where available.
13. Roles and Responsibilities
| Role | Assigned to | Responsibilities |
|---|---|---|
| Policy owner | [Owner name] | Maintains this policy, receives monthly reports, approves exceptions. |
| Backup administrator | [Backup administrator] | Configures and monitors backups, maintains the inventory, performs restore tests. |
| IT provider | [IT provider / MSP] | Monitors alerts, resolves failures, performs restores, reports on status. |
| Data owners / managers | Department leads | Tell IT about new systems and data; verify restore test results. |
| All employees | Everyone | Store business data in approved locations; report lost or deleted data promptly to [IT contact email]. |
14. Exceptions and Enforcement
Any exception to this policy (for example, a system that cannot be backed up as described) must be documented, including the risk and any compensating measures, and approved by [Approver name]. Exceptions are reviewed at least [Review frequency].
Employees who intentionally disable backups, delete backup data without authorization, or store business data in unapproved locations may be subject to disciplinary action.
15. Revision History
| Version | Date | Description of change | Author |
|---|---|---|---|
| [Version] | [Effective date] | Initial adoption of this Data Backup Plan and Policy | [Owner name] |
16. Approval
This Data Backup Plan and Policy has been reviewed and approved by the undersigned and is effective as of [Effective date]. It will be reviewed [Review frequency], after any significant incident, and whenever there is a material change to our systems, staff, or legal obligations.
| Signature: | Name / title: [Approver name], [Approver title] | Date: |
| Signature: | Name / title: [Owner name], [Owner title] | Date: |
Template adapted from the free Data Backup Plan and Policy template by PinellasIT (pinellasit.com/templates). Review with your legal counsel and insurer before adoption.
