File System Dependency Policies for Complete Application Backups

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data protection systems fail to account for complex dependencies between file systems, leading to incomplete backups and potential data loss due to user errors in configuring backups for applications with interlinked data across multiple file systems.

Innovation Solution

A method for managing dynamic dependencies of file systems through a data protection manager that identifies and updates protection policies based on user dependency rules and user inputs, ensuring comprehensive data protection across interconnected file systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data protection systems backup individual file systems independently, then the backup process is simple and straightforward, but dependencies between file systems are not accounted for leading to incomplete backups

Engineering Contradiction:
Improvecompleteness of backupVSAvoidcomplexity of dependency management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a data protection manager as an intermediary component that coordinates between multiple file system backups. This manager identifies dependencies between file systems and orchestrates their backup in a specific sequence, ensuring that dependent file systems are backed up after their dependencies are resolved. The intermediary resolves the contradiction by adding coordination logic that maintains backup completeness without requiring fundamental changes to the backup mechanism itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by identifying and analyzing dependencies between file systems before the actual backup process begins. The data protection manager scans the system to map out dependency relationships, determines the correct backup sequence, and prepares a backup plan in advance. This preliminary analysis ensures that when backups are executed, all dependencies are already understood and properly ordered, preventing incomplete backups.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If users manually configure backup policies for each file system, then the configuration process is straightforward, but user errors lead to incomplete data protection

Engineering Contradiction:
Improveaccuracy of protection policyVSAvoidease of policy configuration
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements self-service by enabling automatic discovery and configuration of backup policies based on detected dependencies. The data protection manager autonomously identifies file system relationships, determines appropriate backup sequences, and generates protection policies without requiring manual user input. This self-configuration capability eliminates user errors while maintaining ease of operation, as the system does the complex work automatically based on observed system state.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system incorporates feedback mechanisms where the data protection manager continuously monitors file system states and dependency relationships. Based on this feedback, the system dynamically adjusts backup policies to ensure completeness. The feedback loop allows the system to learn from the actual system configuration and correct any policy deficiencies automatically, improving reliability without burdening users with complex configuration tasks.

Inventive Principle:
Principle #23Feedback

3Reliability

If the system performs comprehensive dependency analysis for all file systems, then all dependencies are identified ensuring complete protection, but the time and resources required increase significantly

Engineering Contradiction:
Improvecompleteness of dependency coverageVSAvoidtime for policy confirmation
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system applies partial action by focusing dependency analysis on file systems that are actually selected for backup in the current operation. Rather than analyzing all file systems in the system universally, the data protection manager identifies dependencies only for the subset of file systems included in the backup request. This partial analysis approach maintains complete protection for the targeted data while significantly reducing the time and computational resources required compared to a full system-wide analysis.

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If the system updates protection policies dynamically based on detected dependencies, then data protection accuracy improves, but the complexity of policy management increases

Engineering Contradiction:
Improveaccuracy of protection policyVSAvoidcomplexity of dynamic policy updates
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system embraces dynamics by enabling protection policies to be automatically updated based on detected dependencies. The data protection manager continuously monitors the system environment, identifies new dependencies as they arise, and dynamically adjusts backup policies to incorporate these relationships. This dynamic approach ensures policies remain accurate and complete without manual intervention, resolving the contradiction by automating the complexity management through intelligent algorithms rather than rigid static configurations.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12608496B2Managing dynamic dependencies of file systems for application aware data protection
Publication Date: 2026.04.21 DELL PROD LP
  • US12608496B2 patent drawing
  • US12608496B2 patent drawing
  • US12608496B2 patent drawing

AI summary

Techniques described herein relate to a method for performing data protection services on a host. The method includes identifying a first protection policy confirmation event associated with a first protection policy corresponding to a first file system of a plurality of file systems of the host obtaining first dependency information associated with the first file system from a data protection agent of the host; making a first determination that the first protection policy is associated with user dependency rules; making a second determination that the user dependency rules specify a protection policy update associated with the first protection policy; updating the first protection policy based on the first dependency information and the user dependency rules to obtain an updated first protection policy; and initiating performance of first data protection services by the data protection agent based on the updated first protection policy.