HIPAA data backup requirements establish how healthcare organizations must create and maintain recoverable copies of electronic protected health information (ePHI). These requirements apply to covered entities and business associates, including healthcare providers and vendors that maintain ePHI.Under 45 CFR §164.308(a)(7)(ii)(A), organizations must establish and implement procedures for creating and maintaining retrievable exact copies of ePHI.
Meeting this obligation requires more than scheduling backups. Organizations must identify the information they protect, maintain suitable backup procedures, secure recovery copies, and establish how protected information can be retrieved after data loss or disruption.
Quick Answer: What are the HIPAA Data Backup Requirements?
HIPAA requires covered entities and business associates to establish and implement a Data Backup Plan that creates and maintains retrievable exact copies of electronic protected health information (ePHI). This is a required specification under the HIPAA Security Rule’s Contingency Plan standard, 45 CFR §164.308(a)(7)(ii)(A).
A practical HIPAA data backup plan should address:
- ePHI coverage: Identify databases, applications, files, and systems containing protected health information.
- Backup procedures: Document backup frequency, methods, storage locations, and responsibilities.
- Security safeguards: Protect backup data against unauthorized access, modification, and loss.
- Retrievability: Maintain copies that authorized personnel can recover when needed.
- Verification: Evaluate backup integrity and restoration capabilities.
- Documentation: Maintain required procedures and appropriate records of backup operations and reviews.
HIPAA does not prescribe a universal backup frequency, storage technology, backup-data retention period, Recovery Time Objective (RTO), or Recovery Point Objective (RPO). These decisions must reflect the organization’s risk analysis and operational needs.
Does HIPAA Require Healthcare Data Backups?
Yes. HIPAA requires healthcare covered entities and business associates that maintain ePHI to establish and implement a Data Backup Plan.
The requirement applies to regulated organizations such as hospitals, medical practices, dental clinics, health plans, and qualifying healthcare technology or service providers.
Under 45 CFR §164.308(a)(7)(ii)(A), the required Data Backup Plan must establish procedures to create and maintain retrievable exact copies of ePHI.
Organizations cannot satisfy this obligation simply by purchasing backup software or assuming their cloud provider protects all stored information. They must establish procedures appropriate to their information systems and ensure that those procedures are implemented.
The backup requirement applies whether ePHI resides on local servers, cloud infrastructure, or a hybrid environment.
What are Retrievable Exact Copies of ePHI?
Retrievable exact copies are recoverable copies that preserve the protected information required for restoration without unintended alteration or loss.
A backup must support three essential outcomes:
- Completeness: Required ePHI is included in the protected dataset.
- Integrity: Recovered information remains accurate and protected against improper alteration.
- Retrievability: Authorized personnel can access and recover the protected information when necessary.
For example, a dental practice may store treatment notes in its practice management software and patient X-rays in a separate imaging system.

The three structural pillars required to satisfy HIPAA retrievable exact copy standards.
Backing up only the practice management database leaves the imaging records unprotected.
A complete backup plan must identify all relevant ePHI locations and account for the relationships between protected systems.
HIPAA Data Backup Plan: Required vs. Addressable Specifications
The Data Backup Plan is part of the HIPAA Security Rule’s Contingency Plan standard, established under 45 CFR §164.308(a)(7).
This standard contains five implementation specifications that collectively address data protection, restoration, emergency operations, testing, and recovery priorities.
What are the Five HIPAA Contingency Plan Requirements?
| Implementation specification | Classification | Purpose |
|---|---|---|
| Data Backup Plan | Required | Create and maintain retrievable exact copies of ePHI |
| Disaster Recovery Plan | Required | Establish procedures to restore lost data |
| Emergency Mode Operation Plan | Required | Continue critical processes protecting ePHI during emergencies |
| Testing and Revision Procedures | Addressable | Periodically test and revise contingency plans |
| Applications and Data Criticality Analysis | Addressable | Assess the relative importance of applications and data |
Required specifications must be implemented. Addressable specifications require evaluation to determine whether implementation is reasonable and appropriate.
When an addressable specification is reasonable and appropriate, the organization must implement it. Otherwise, it must document its determination and implement an equivalent alternative measure where reasonable and appropriate.
Addressable does not mean automatically optional.
The Data Backup Plan focuses on maintaining protected copies. The Disaster Recovery Plan focuses on restoring lost data. Emergency Mode Operation procedures support critical functions during disruptions.
For a broader explanation of these connected obligations, read the HIPAA Contingency Plan guide.
Is a HIPAA Data Backup Plan Mandatory?
Yes. The Data Backup Plan is a required implementation specification under the HIPAA Security Rule.
Organizations may choose backup technologies and procedures appropriate to their risks, size, and technical environment, but they cannot eliminate the backup obligation.
The plan must be implemented and maintained as part of the organization’s administrative safeguards for ePHI.
What Should a HIPAA Data Backup Plan Include?
A HIPAA Data Backup Plan should explain what data receives protection, how backup copies are maintained, who manages the process, and how recoverability is evaluated.
The following elements translate the regulatory requirement into an operational backup strategy.
1. Identify ePHI Sources and Backup Coverage

Mapping primary clinical repositories and dependencies into a unified backup plan.
Start by identifying systems that create, receive, maintain, or transmit ePHI.
Common healthcare data sources include:
- Electronic Health Records (EHR/EMR): Patient charts, treatment histories, prescriptions, clinical documentation, and diagnoses.
- Practice management systems: Scheduling, billing, insurance records, and administrative data containing ePHI.
- Picture Archiving and Communication Systems (PACS): Diagnostic imaging files, DICOM studies, X-rays, and related records.
- Laboratory Information Systems (LIS): Laboratory results, diagnostic information, and clinical testing records.
- Cloud and SaaS applications: Hosted patient portals, healthcare applications, and related storage.
- Additional repositories: File servers, email systems, document management platforms, and databases containing ePHI.
For each source, identify its owner, storage location, backup coverage, backup schedule, and responsible administrator.
This inventory helps prevent backup gaps caused by overlooked applications, disconnected databases, or information stored outside the primary EHR.
2. Account for Critical Systems and Recovery Dependencies
Backing up a database does not guarantee that its application can be restored.
Healthcare applications may rely on supporting components, including database servers, authentication services, network configurations, application settings, and encryption keys.
For example, restoring an EHR database without the application configuration or required encryption keys may leave the patient information inaccessible.
The backup plan should identify dependencies necessary to make recovered information usable.
Evaluate which systems support critical patient care, which components require protection, and which services must be restored before dependent applications can operate.
These findings also support Applications and Data Criticality Analysis, which evaluates the relative importance of applications and data when determining recovery priorities.
3. Define Backup Frequency, Methods, and Storage Locations
HIPAA does not mandate daily, hourly, or real-time backups for every healthcare organization.
Backup frequency should reflect the organization’s security risk analysis, how frequently its information changes, and the operational consequences of losing recent data.
Document the following:
- Backup frequency: How often each system produces recoverable copies.
- Backup method: Whether protection uses full, incremental, differential, or application-aware backups.
- Storage location: Where recovery copies reside and how they can be accessed.
- Retention: How long backup recovery points remain available.
- Monitoring: How administrators identify and address failed or incomplete backups.
Full backups capture complete datasets. Incremental backups generally capture changes since the preceding backup, while differential backups capture changes since the last full backup.
Snapshots can provide additional recovery points, but organizations should evaluate whether they are independent of the source system and suitable for the intended recovery scenario.
The appropriate method depends on application requirements, storage capacity, backup windows, and recovery needs.
For further technical comparisons, see Types of Backup Solutions in Healthcare.
4. Back Up ePHI Before Moving Equipment
The HIPAA Security Rule also contains an addressable Data Backup and Storage specification under 45 CFR §164.310(d)(2)(iv).
This specification addresses creating retrievable exact copies of ePHI, when needed, before equipment is moved.
Organizations should evaluate the specification when relocating servers, replacing storage hardware, or transferring devices containing protected health information.
5. Set Backup Schedules Based on RPO and Recovery Needs

How RPO and RTO determine data recovery schedules and acceptable downtime.
Backup schedules should support the organization’s acceptable level of data loss.
Two recovery metrics help define expectations:
- Recovery Point Objective (RPO): The maximum acceptable age of recovered data following a disruption.
- Recovery Time Objective (RTO): The targeted duration for restoring a system or service.
Consider a medical practice that establishes a one-hour RPO and a four-hour RTO for its EHR system.
The practice aims to recover information no more than one hour old and restore the affected EHR service within four hours.
A nightly backup would generally not support that one-hour RPO. More frequent backups or another suitable data-protection method would be needed.
However, running a backup every hour does not guarantee a one-hour RPO. Failed jobs, replication delays, incomplete backup sets, or unusable recovery points can increase actual data loss.
Likewise, a usable backup does not guarantee that an application can be restored within the target RTO.
These values are illustrative recovery objectives, not HIPAA-prescribed timeframes.
Organizations should establish recovery targets through risk analysis and operational impact assessments. See the RTO vs. RPO guide for a more detailed explanation.
6. Document Backup Security and Responsibilities
A documented plan must assign accountability for backup operations.
Identify who is responsible for:
- Configuring and maintaining backup schedules.
- Monitoring job completion and investigating failures.
- Managing backup access permissions and encryption keys.
- Authorizing recovery operations.
- Maintaining backup procedures, logs, and verification records.
- Reviewing backup coverage when systems or applications change.
Responsibilities should remain clear when an external service provider manages part or all of the backup environment.
Outsourcing backup operations does not eliminate the regulated organization’s own HIPAA obligations.
How to Protect HIPAA Backups Against Data Loss and Ransomware
Healthcare backups must remain protected when production systems experience hardware failures, cyberattacks, accidental deletion, or other disruptions.
A backup strategy that stores all recovery copies within the same compromised environment may fail when the organization needs recovery most.
Protect Backups With Appropriate Security Controls

Multi-layered safeguards essential for protecting ePHI recovery copies from targeted cyberattacks.
The HIPAA Security Rule establishes safeguards for protecting ePHI but does not mandate one universal backup architecture.
Organizations should evaluate controls such as:
- Encryption: Protect stored and transmitted ePHI and maintain appropriate encryption-key management.
- Role-Based Access Control (RBAC): Restrict backup administration and restoration privileges.
- Multifactor Authentication (MFA): Strengthen access to backup management systems.
- Immutable storage: Protect retained backup versions against unauthorized modification or deletion.
- Offline or isolated storage: Reduce exposure to attacks affecting production systems.
- Offsite copies: Reduce the risk of losing both production data and backups during a localized incident.
Encryption under the HIPAA Security Rule is addressed through relevant addressable specifications. Organizations must evaluate these specifications and implement appropriate safeguards or documented alternatives.
HIPAA does not explicitly mandate AES-256, immutable backups, air-gapped storage, or a specific number of backup copies.
These technologies can support risk reduction and recoverability, but their use should reflect the organization’s security assessment.
The 3-2-1-1-0 Backup Rule for Healthcare provides an additional framework for redundancy, isolation, and backup verification.
Verify Cloud and Third-Party Backup Responsibilities
Cloud storage does not automatically satisfy HIPAA data backup requirements.
Healthcare organizations must understand which data their cloud or Software-as-a-Service (SaaS) providers protect and which responsibilities remain with the customer.
Verify whether the provider:
- Maintains recoverable copies of the relevant ePHI.
- Protects associated databases, attachments, and necessary application configurations.
- Supports suitable data export and restoration procedures.
- Monitors backup failures and provides useful recovery evidence.
- Defines its responsibilities during incidents and service interruptions.
A cloud service provider that maintains ePHI on behalf of a covered entity or another business associate generally requires an appropriate Business Associate Agreement (BAA).
This can apply even when the provider stores encrypted ePHI without possessing the decryption key.
A BAA defines contractual responsibilities, but signing one does not independently establish HIPAA compliance.
Organizations should evaluate the provider’s actual controls, service capabilities, and recovery responsibilities.
How to Verify HIPAA Backup Integrity and Retrievability
Successful backup notifications do not prove that protected information can be restored.
A backup may complete while omitting important files, producing inconsistent application data, or storing copies that cannot be accessed during an emergency.
Verification should determine whether the recovered information is complete, accurate, and usable.
Verify Backup Integrity Through Restoration Testing

The essential four-stage verification process to ensure backups are truly recoverable.
A practical backup verification process includes four distinct checks:
- Backup execution: Confirm that scheduled backup operations completed and investigate failures.
- Backup integrity: Check protected datasets for corruption, missing information, or unexpected changes.
- Data restoration: Restore representative files, databases, or systems to a suitable test environment.
- Usability validation: Confirm that the restored information can be accessed and used as intended.
The final step matters because recovering files does not necessarily restore an operational healthcare application.
For example, a restored PACS archive may contain imaging files, but the system may remain unusable if its imaging database or application dependencies are missing.
Organizations should design appropriate tests around the protected workload and documented recovery objectives.
HIPAA identifies testing and revision of contingency plans as an addressable specification under §164.308(a)(7)(ii)(D). Organizations must evaluate and appropriately address this specification.
For assistance evaluating recoverability, explore CDS Backup Verification.
Maintain Backup Verification Records and Audit Evidence

Distinguishing the 6-year compliance record retention rule from operational backup life cycles.
Backup documentation should demonstrate that the organization implements and maintains its established procedures.
Useful evidence includes:
| Record | Purpose |
|---|---|
| Backup execution logs | Identify completed, missed, and failed backup jobs |
| Integrity verification results | Document checks for corruption or incomplete data |
| Restoration test reports | Demonstrate whether selected information was recovered |
| Recovery performance records | Compare measured recovery points and restoration times against targets |
| Corrective-action records | Document how identified problems were investigated and resolved |
For restoration tests, record the date, tested system, recovery point, restoration duration, outcome, reviewer, and corrective actions.
These records support internal oversight and can help demonstrate implementation during a compliance audit.
The HHS OCR Audit Protocol provides guidance on evaluating contingency planning, backup implementation, restoration evidence, and related safeguards.
HIPAA’s six-year documentation retention rule is different from backup-data retention.
Under 45 CFR §164.316(b)(2)(i), specified Security Rule documentation generally must be retained for six years from its creation or the date it was last in effect, whichever is later.
That provision does not establish a universal requirement to retain every backup copy of ePHI for six years.
Backup retention should reflect recovery requirements and any other applicable patient-record retention laws, contractual obligations, or legal holds.
HIPAA Data Backup Requirements Checklist
Use this checklist to assess backup procedures and identify gaps requiring further review.
- Identify all systems, applications, and repositories containing ePHI.
- Establish and implement written procedures for creating retrievable exact copies.
- Confirm backup coverage includes relevant clinical databases, imaging files, and other protected data.
- Identify application dependencies necessary for usable recovery.
- Define backup methods, schedules, storage locations, and retention.
- Establish RPO and RTO targets based on operational needs.
- Evaluate encryption, access controls, and protection against unauthorized deletion.
- Review offsite, isolated, or immutable backup options based on identified risks.
- Confirm vendor responsibilities and applicable BAAs.
- Monitor failed backups and incomplete recovery points.
- Perform appropriate integrity checks and restoration testing.
- Maintain required policies, procedures, reviews, and supporting evidence.
- Review backup procedures after significant system, operational, or risk changes.
This checklist supports backup planning. It does not replace a comprehensive HIPAA security risk analysis or assessment of all applicable Security Rule requirements.
How to Evaluate a HIPAA-Aligned Backup Provider
A healthcare backup provider should support the organization’s data protection and recovery needs, not simply offer storage capacity.
Evaluate potential providers using six questions:
- Will the provider execute an appropriate BAA? Confirm contractual responsibilities for maintaining and protecting ePHI.
- Which systems and data types are covered? Verify support for clinical databases, imaging systems, relevant cloud applications, and associated information.
- How are backups secured? Review encryption, access restrictions, storage isolation, and protection against unauthorized changes.
- How is recoverability verified? Ask about integrity checks, restoration testing, and recovery validation.
- Can the service support the organization’s recovery objectives? Assess backup schedules, recovery capabilities, system dependencies, and operational support.
- What documentation is available? Review reporting, recovery records, incident procedures, data portability, and service termination responsibilities.
No provider’s description of its services as “HIPAA compliant” replaces the customer’s responsibility to evaluate relevant safeguards and contractual arrangements.
Healthcare organizations comparing managed services can explore Central Data Storage’s HIPAA-Aligned Backup Services.
Strengthen Your HIPAA Backup Plan With Verified Recovery
HIPAA data backup requirements center on maintaining retrievable exact copies of ePHI. Effective implementation also depends on appropriate backup coverage, documented procedures, security controls, and reliable recovery processes.
Central Data Storage (CDS) provides managed backup, disaster recovery, and backup verification solutions for healthcare organizations.
Its UnisonBDR platform supports healthcare data protection and recovery readiness through managed backup and recovery capabilities.
Are your healthcare backups complete, secure, and recoverable?
Request a Data Assessment to evaluate potential gaps in backup coverage, recovery procedures, and verification.
You can also explore HIPAA-Aligned Backup Services to learn about managed healthcare backup solutions.
HIPAA Data Backup Requirements FAQs
How Often Does HIPAA Require Data Backups?
HIPAA does not specify one universal backup frequency. Healthcare organizations should establish backup schedules based on security risk analysis, how frequently ePHI changes, and acceptable data loss. Systems with frequently updated patient records may need more frequent protection than relatively static information.
Does HIPAA Require Encrypted or Offsite Backups?
HIPAA does not prescribe one universal offsite backup arrangement. Encryption is addressed through applicable addressable Security Rule specifications, which must be evaluated and appropriately addressed. Offsite storage, encryption, and backup isolation can help protect ePHI against loss, unauthorized access, and localized incidents.
How Long Must HIPAA Backup Data Be Retained?
HIPAA does not establish a universal backup-data retention period. Healthcare organizations should set retention periods based on recovery needs and applicable legal obligations. The Security Rule’s six-year documentation retention requirement applies to specified compliance documentation, not automatically to every backup copy of patient data.
Does Cloud Backup Automatically Meet HIPAA Requirements?
No. Cloud backup does not automatically satisfy HIPAA. Organizations must evaluate backup coverage, access controls, integrity, recoverability, and vendor responsibilities. Cloud providers maintaining ePHI on behalf of regulated entities generally require appropriate business associate arrangements.
What is the Difference Between a HIPAA Data Backup Plan and a Disaster Recovery Plan?
A HIPAA Data Backup Plan establishes procedures for creating and maintaining retrievable exact copies of ePHI. A Disaster Recovery Plan establishes procedures for restoring lost data. Both are required specifications under the HIPAA Security Rule’s Contingency Plan standard.
Does HIPAA Require Immutable Backups?
No. The current HIPAA Security Rule does not explicitly mandate immutable backup technology. Immutable storage can help prevent unauthorized modification or deletion of recovery copies, especially during ransomware incidents. Organizations should evaluate its suitability based on their risks and recovery requirements.
Does HIPAA Specify an RTO or RPO for Data Backup?
No. HIPAA does not establish universal numerical RTO or RPO values. Healthcare organizations should define recovery objectives based on data criticality, acceptable data loss, and operational impact. Backup schedules, recovery procedures, and verification methods should support those objectives.
Regulatory References
- 45 CFR §164.308 — Administrative Safeguards
- 45 CFR §164.310 — Physical Safeguards
- 45 CFR §164.312 — Technical Safeguards
- 45 CFR §164.316 — Policies, Procedures, and Documentation Requirements
- HHS — HIPAA Security Rule
- HHS — HIPAA Security Rule Audit Protocol
- NIST SP 800-66 Revision 2 — Implementing the HIPAA Security Rule
Regulatory note: This article describes the HIPAA Security Rule requirements discussed above and distinguishes them from recommended implementation practices. Organizations should verify current regulatory requirements and obtain appropriate compliance guidance for their circumstances.




