Volume Map Indicators for Cascaded Backup Cleaning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management systems face inefficiencies in cleaning cascaded volumes, particularly when removing backup volumes from a cascade, as they struggle to determine which data needs to be moved to maintain data integrity, leading to unnecessary data transfer and storage issues.

Innovation Solution

The implementation of volume maps that include background copy and write copy indicators allows for the determination of why data is present in each region, enabling efficient data transfer by identifying which data is due to a write or a background copy, thereby reducing the amount of cleaning required when removing a volume from the cascade.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional cleaning methods are used for cascaded volumes, then data integrity can be maintained, but the amount of data transfer and cleaning time increases significantly

Engineering Contradiction:
Improvedata integrityVSAvoidcleaning time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by maintaining volume maps that continuously track the origin of each data region (source volume, background copy status, write copy status) during normal cascade operations. This preliminary tracking eliminates the need for extensive data analysis during the cleaning phase, as the system already knows which regions contain unique data that must be preserved. The volume maps are updated in real-time as data moves through the cascade, enabling efficient cleaning decisions without requiring full data transfers.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If comprehensive data tracking is implemented to reduce cleaning requirements, then cleaning efficiency improves, but system complexity increases

Engineering Contradiction:
Improvecleaning efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments data tracking by maintaining separate volume maps for each cascade level, with each map containing region-specific information about data origin and copy status. Rather than implementing a single complex global tracking system, the patent divides the tracking function into manageable segments corresponding to each volume in the cascade. Each volume map independently tracks its own data regions, allowing the system to achieve comprehensive tracking through multiple simple, modular components rather than one complex centralized system.

Inventive Principle:
Principle #1Segmentation

3Reliability

If all data regions are transferred during cleaning to ensure integrity, then data integrity is maintained, but storage efficiency decreases

Engineering Contradiction:
Improvedata integrityVSAvoidstorage efficiency
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system applies local quality by treating different data regions differently based on their specific characteristics tracked in the volume maps. Rather than uniformly transferring all data regions during cleaning, the system identifies and transfers only those regions that contain unique data not already present in downstream volumes. Regions marked as background copies or write copies are handled differently than original source data, optimizing storage efficiency by eliminating redundant transfers while maintaining data integrity through region-specific cleaning decisions.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9069711B2Source cleaning cascaded volumes using write and background copy indicators
Publication Date: 2015.06.30 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9069711B2 patent drawing
  • US9069711B2 patent drawing
  • US9069711B2 patent drawing

AI summary

Various systems, processes, and products may be used to source clean cascaded volumes. In particular implementations, a system, process, and product for source cleaning cascaded volumes may include the ability to store a primary volume and a plurality of cascaded backup volumes. The system, process, and product may also include the ability to determine whether a write to one of the backup volumes is due to a background copy being made of another volume in the cascade and adjust a background copy indicator in a volume map for the backup volume if the write is due to a background copy and to determine whether a write to one of the backup volumes is due to a write to another volume in the cascade and adjust a write copy indicator in a volume map for the backup volume if the write is due to a write to another cascaded volume.