Cumulative Backup Merging Multiple Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data backup systems require significant storage space and long backup windows, especially in environments with multiple clients, as they generate multiple backups over time, leading to inefficient use of resources and increased costs.

Innovation Solution

Implementing a cumulative backup process where data from multiple nodes is backed up in parallel, merged into a single unified backup, and stored as a cumulative backup, eliminating the need for individual backups and reducing storage requirements and backup time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If individual backups are created for each client, then data protection is ensured, but storage space requirements increase significantly

Engineering Contradiction:
Improvedata protectionVSAvoidstorage space
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent combines multiple individual client backups into a single cumulative backup file. Instead of creating separate backup files for each client (which would consume significant storage space), the system merges all client data into one consolidated backup, dramatically reducing storage requirements while maintaining data protection for all clients.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If multiple backups are maintained indefinitely, then data recovery capability is improved, but storage costs and maintenance burden increase

Engineering Contradiction:
Improvedata recovery capabilityVSAvoidstorage costs
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system maintains a single cumulative backup that grows over time by incorporating data from all clients, rather than maintaining multiple separate backup files indefinitely. This approach preserves data recovery capability while significantly reducing storage costs and maintenance burden associated with managing numerous individual backup files.

Inventive Principle:
Principle #5Merging (Combining)

3Quantity of substance

If combined backup is created only after all individual backups are complete, then storage space is optimized, but backup window time increases

Engineering Contradiction:
Improvestorage space optimizationVSAvoidbackup window time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The system performs preliminary actions by starting to create the cumulative backup file before all individual client backups are complete. The cumulative backup process begins in parallel with individual backup operations, allowing storage space optimization to be achieved without significantly extending the overall backup window time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The cumulative backup process operates continuously and in parallel with individual backup operations. Instead of waiting for all individual backups to complete before starting the combined backup, the system maintains continuous useful action by overlapping the backup processes, thereby optimizing storage space without proportionally increasing backup time.

Inventive Principle:
Principle #20Continuity of useful action

4Quantity of substance

If additional storage space is purchased to accommodate multiple backups, then backup capacity is increased, but cost and maintenance burden increase

Engineering Contradiction:
Improvebackup capacityVSAvoidcost and maintenance
Core Design Contradiction:
Quantity of substanceVSEase of manufacture

Solution Approach 1:

The patent implements a cumulative backup approach that merges all client data into a single backup file, thereby maintaining backup capacity without requiring additional storage space purchases. This eliminates the need for expensive additional hardware and reduces maintenance burden associated with managing and maintaining multiple separate backup systems.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11347591B2Cumulative backups
Publication Date: 2022.05.31 EMC IP HLDG CO LLC
  • US11347591B2 patent drawing
  • US11347591B2 patent drawing
  • US11347591B2 patent drawing

AI summary

In one example, a method includes performing various operations at a backup server. These operations may include receiving, from a node, a request for restoration of a cumulative backup that includes a plurality of partial backups that have been merged together, where the plurality of partial backups includes data from a group of one or more nodes, and the group includes the node. The method further includes checking the cumulative backup to determine whether or not the cumulative backup has been finalized, accessing the cumulative backup when it has been determined that the cumulative backup has been finalized, and restoring the cumulative backup to a target node.