File-Level Continuous Data Protection via Write Interception

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional data archiving methods, such as full backups and incremental backups, are inefficient and costly due to the need for large storage space and time-consuming processes, and they often result in data loss during system failures, especially when trying to restore data to specific points in time.

Innovation Solution

A system and method for continuous data protection that allows for efficient viewing and restoration of previous file versions by intercepting write commands and redirecting them to a backup storage, using a combination of file-level monitoring and snapshot techniques to create incremental backups in real-time, enabling data to be restored to any point in time without interrupting the system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full backup of entire hard drive is performed, then complete data protection is achieved, but storage space requirements and archiving time increase significantly

Engineering Contradiction:

Improvedata protection completenessVSAvoidstorage space for archived data

Core Design Contradiction:

ReliabilityVSVolume of stationary object

Solution Approach 1:

The patent extracts only the changed data sets from the full backup, storing only the differences in the incremental backup storage. This allows complete data protection to be achieved while minimizing storage space requirements by storing only what has changed since the last backup.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The backup process is segmented into identifying changed data sets, copying only those changes to incremental backup storage, and maintaining references to the full backup. This segmentation allows the system to achieve complete protection with minimal incremental storage space.

Inventive Principle:

Principle #1Segmentation

2Volume of stationary object

If incremental backup is used to reduce storage space, then storage requirements decrease, but data recovery complexity increases due to merging requirements

Engineering Contradiction:

Improvestorage space for archived dataVSAvoiddata recovery process complexity

Core Design Contradiction:

Volume of stationary objectVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms where the system automatically tracks which data sets have changed since the last backup, using this information to determine what needs to be backed up next. This automated tracking simplifies the recovery process by maintaining organized, sequential backup chains that can be automatically reconstructed.

Inventive Principle:

Principle #23Feedback

3Volume of stationary object

If traditional incremental backup is performed, then storage space is optimized, but data loss occurs between backup points during system failure

Engineering Contradiction:

Improvestorage space for archived dataVSAvoiddata recovery completeness

Core Design Contradiction:

Volume of stationary objectVSReliability

Solution Approach 1:

The patent implements continuous monitoring of data sets between incremental backups, tracking changes in real-time. This continuous action ensures that when a system failure occurs, the system can recover to the most recent backup point without losing data that changed after the last backup, thus maintaining both space efficiency and data completeness.

Inventive Principle:

Principle #20Continuity of useful action

4Measurement precision

If file-level monitoring is implemented for continuous protection, then data recovery precision improves, but system overhead and processing time increase

Engineering Contradiction:

Improvedata restoration point precisionVSAvoidbackup processing time

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies partial monitoring by focusing only on identifying changed data sets rather than monitoring all file system activity. This selective approach achieves precise restoration points by tracking only relevant changes, reducing the processing overhead compared to comprehensive file-level monitoring of all system operations.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS8005797B1File-level continuous data protection with access to previous versions

Publication Date: 2011.08.23 ACRONIS INT

AI summary

A system for continuous data protection includes a storage device and a backup storage device. The continuous data protection procedure is performed as two parallel processes: creating an initial backup by copying a data as a file/directory from the storage device into the backup storage device, and copying the data to be written to the data storage as a part of a file/directory into the incremental backup. When a write command is directed to a file system driver, it is intercepted and redirected to the backup storage, and the data to be written in accordance with the write request, is written to the incremental backup on the backup storage. If the write command is also directed to a data (a file/directory) that has been identified for backup, but has not yet been backed up, the identified data (a file/directory) is copied from the storage device to the intermediate storage device. Then, the write command is executed on the identified file/directory on the storage device and the file/directory is copied from the intermediate storage device.