Decoupling Snapshot Creation from Metadata Cataloging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data protection techniques, such as Continuous Data Protection (CDP) and Storage Integrated Data Protection (SIDP), require frequent snapshots, leading to performance issues due to the frequent need for network bandwidth and resource allocation during snapshot taking and metadata cataloging.

Innovation Solution

A smart snap controller and intelligent backup storage system that automatically takes snapshots and schedules metadata cataloging independently, decoupling snapshot taking from metadata cataloging to optimize resource usage and reduce network bandwidth requirements, allowing for more efficient data protection with flexible snapshot scheduling and identification of identical snapshots.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If frequent snapshots are taken to improve data protection frequency, then data protection reliability is improved, but network bandwidth consumption and system performance deteriorate

Engineering Contradiction:
Improvedata protection frequencyVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the snapshot process into two independent parts: snapshot creation (data copying) and metadata cataloging (information management). By decoupling these operations, the system can take frequent snapshots without requiring proportional frequent metadata cataloging, thereby reducing network bandwidth consumption while maintaining high data protection frequency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-configuring snapshot policies and metadata cataloging schedules in advance. Metadata cataloging is scheduled to occur at optimized intervals rather than immediately with each snapshot, allowing the system to prepare resource allocation ahead of time and reduce peak bandwidth demands during frequent snapshot operations.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If frequent snapshots are taken to improve data protection frequency, then data protection reliability is improved, but system performance deteriorates due to resource allocation

Engineering Contradiction:
Improvedata protection frequencyVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

By dividing the snapshot workflow into independent snapshot creation and metadata cataloging phases, the system allows snapshot operations to proceed without being blocked by metadata processing. This segmentation prevents resource contention and maintains high system performance even during frequent snapshot operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Metadata cataloging is performed periodically at scheduled intervals rather than with every snapshot. This periodic action reduces the frequency of resource-intensive metadata operations while maintaining adequate data protection coverage, thereby preserving system performance during frequent snapshot cycles.

Inventive Principle:
Principle #19Periodic action

3Measurement precision

If metadata cataloging is performed frequently to maintain accurate data protection records, then measurement precision is improved, but network bandwidth consumption increases

Engineering Contradiction:
Improvemetadata accuracyVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system implements periodic metadata cataloging at strategically determined intervals rather than after every snapshot. This approach maintains sufficiently accurate metadata records for data protection purposes while significantly reducing the frequency of network bandwidth-intensive cataloging operations.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

Metadata cataloging is scheduled and prepared in advance based on snapshot patterns and protection requirements. This preliminary planning allows the system to optimize cataloging timing and frequency, ensuring adequate metadata accuracy while minimizing unnecessary network bandwidth consumption.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If snapshots are taken more frequently to meet CDP and SIDP requirements, then data protection reliability is improved, but the time required for snapshot operations increases

Engineering Contradiction:
Improvedata protection frequencyVSAvoidsnapshot operation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

By separating snapshot creation from metadata cataloging, the system allows snapshots to be created quickly in the background without waiting for metadata processing. This segmentation reduces the perceived snapshot operation time while maintaining the ability to take frequent snapshots for CDP and SIDP compliance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system maintains continuous snapshot creation operations without interruption from metadata cataloging cycles. Snapshot operations proceed continuously at the required frequency for data protection, while metadata cataloging occurs independently in the background, ensuring no loss of snapshot operation time.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS10394658B1High speed snapshots mechanism
Publication Date: 2019.08.27 EMC IP HLDG CO LLC
  • US10394658B1 patent drawing
  • US10394658B1 patent drawing
  • US10394658B1 patent drawing

AI summary

Backup storage is configured to automatically take one or more snapshots of a protected device. After a plurality of snapshots of the protected device have been automatically taken by the backup storage, the backup storage is communicated with in order to catalog metadata associated with the plurality of snapshots.