UNIX Shadow Backup With Storage-Stack Change Detection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data backup and anti-malware protection systems in LINUX systems face challenges due to differences in storage stacks compared to Windows, leading to resource-intensive operations and difficulties in identifying file movements or copies within the system, necessitating a universal and efficient solution.

Innovation Solution

A shadow backup system is implemented that intercepts system calls and storage stack operations to create a universal mapping structure, allowing efficient tracking of file changes and detecting malicious patterns, with minimal resource impact, supporting network and cloud backups.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data backup and anti-malware protection are implemented in LINUX systems using traditional methods, then protection capability is provided, but resource consumption increases significantly

Engineering Contradiction:

Improvedata protection capabilityVSAvoidresource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system segments backup operations by file system type and operating system platform, implementing separate handling paths for LINUX, WINDOWS, and network file systems. This allows optimized resource usage for each segment rather than applying a resource-intensive universal approach across all file systems.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer that intercepts storage stack operations and system calls between the application and the actual file system. This intermediary monitors and tracks file changes efficiently without requiring deep integration into each specific file system implementation, reducing overall resource consumption while maintaining protection capability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If traditional backup methods are used in LINUX systems, then data backup is achieved, but the system complexity increases due to storage stack differences

Engineering Contradiction:

Improvedata backup functionalityVSAvoidstorage stack complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system implements a universal backup mechanism that can operate across multiple file systems and operating systems (LINUX, WINDOWS, network file systems) through a unified interface. The patent creates mapping structures that are format-universal, allowing the same backup logic to handle different storage stacks without requiring separate complex implementations for each platform.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Instead of adapting the backup system to each specific file system implementation, the patent inverts the approach by having the file system operations adapt to a standardized monitoring interface. The system intercepts and standardizes storage stack operations, allowing the backup mechanism to remain simple while handling diverse file systems through consistent interception points.

Inventive Principle:

Principle #13The other way round (Inversion)

3Reliability

If all file changes are tracked at the operating system level, then complete backup coverage is achieved, but the cost of tracking operations increases significantly

Engineering Contradiction:

Improvebackup coverageVSAvoidtracking operation cost

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The system implements partial tracking by focusing only on the specific storage stack operations that indicate actual file changes, rather than monitoring all operating system-level file operations. By intercepting only the critical storage stack calls that represent genuine data modifications, the system achieves sufficient backup coverage with reduced tracking overhead.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The patent creates shadow copies or mapping structures that replicate only the essential file change information needed for backup purposes. Instead of tracking and storing all operating system change operations, the system creates simplified copies of the critical change data through intercepted storage stack operations, reducing the computational cost of tracking while maintaining backup integrity.

Inventive Principle:

Principle #26Copying

4Productivity

If file system-specific implementations are used for backup, then optimization for each system is achieved, but adaptability across different operating systems decreases

Engineering Contradiction:

Improvebackup efficiencyVSAvoidcross-platform compatibility

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS12430435B2Shadow backup and anti-malware protection for UNIX-based machines

Publication Date: 2025.09.30 ACRONIS INT

AI summary

Systems and methods for embedding into a storage stack of a UNIX based computing device. A method includes building a file storage map for a file stored in computing device data storage, intercepting a system call associated with the file, intercepting a storage stack operation, and analyzing the system call and the storage stack operation using the file storage map to determine a change to a data block of the file. The method further includes building a shadow copy of the file on backup storage. The method further includes detecting a malicious operation based on the change to the data block.