Backup Manager for Interdependent Application Writers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data backup systems struggle to effectively back up applications with dependencies, leading to inconsistencies and system failures during recovery, as they often skip open files and fail to manage dependencies between applications and databases.

Innovation Solution

The system employs writers and writer components to organize data into backup groupings, allowing for selective backup and recovery of individual writers and components, ensuring that dependent data is included to maintain a consistent state, using metadata and shadow copies to manage backup operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional backup systems are used to back up open files, then backup speed is improved, but data consistency deteriorates because open files are skipped or cannot be effectively backed up

Engineering Contradiction:
Improvebackup speedVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by taking a snapshot of the file system state before backup begins, and using transaction logs to track and recover open files during the backup process, ensuring data consistency without sacrificing backup speed

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary backup manager that coordinates between the application processes holding open files and the backup system, using transaction logs and snapshot data to mediate the backup of open files while maintaining data consistency

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If applications are backed up as logical units to preserve system state, then reliability is improved, but device complexity increases due to the need to manage dependencies between applications and databases

Engineering Contradiction:
Improvesystem state preservationVSAvoiddependency management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the backup process into distinct components: snapshot creation, transaction log capture, dependency identification, and coordinated recovery. This segmentation allows each component to handle specific aspects of logical unit backup, reducing overall system complexity while maintaining reliability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements feedback mechanisms where the backup manager continuously monitors application state, transaction logs, and dependency relationships, using this feedback to dynamically adjust the backup process and ensure complete, consistent backups of logical units with their dependencies

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS7418619B1Backup and restore operations of interdependent system components
Publication Date: 2008.08.26 EMC IP HLDG CO LLC
  • US7418619B1 patent drawing
  • US7418619B1 patent drawing
  • US7418619B1 patent drawing

AI summary

Systems and methods for backing up or restoring interdependent applications. During a backup or recovery process, the writers and writer components included in the backup groupings of a client are displayed. Some of the writers and writer components can be individually selected for backup or recovery. Some of the writer components may have a dependency on a writer component in another writer. The dependency is automatically selected, although a user can disable the automatic selection of the dependency or deselect the dependency. The dependency is then backed up or recovered along with the selected writers and selected writer components.