Dynamic Snapshot Creation Using Data Modification Thresholds

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing snapshot creation methods in data management systems result in unpredictable data loss and inefficient storage utilization, as they are based on fixed time intervals, leading to unnecessary resource usage and space wastage, especially when significant data modifications occur between snapshot cycles.

Innovation Solution

A dynamic snapshot creation method that uses snapshot delta values to determine when to create, replicate, backup, or expire snapshots based on the volume of data modified or number of transactions since the last snapshot, optimizing data loss minimization and storage space utilization by setting threshold values for snapshot actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If snapshots are created at fixed time intervals, then storage capacity is utilized, but significant data modifications between cycles cause unpredictable data loss

Engineering Contradiction:

Improvedata loss predictionVSAvoiddata loss

Core Design Contradiction:

ReliabilityVSLoss of substance

Solution Approach 1:

The patent transforms the static, time-based snapshot creation approach into a dynamic, data-change-based approach. The system continuously monitors data modification volumes and triggers snapshot creation only when changes exceed predefined thresholds, making the snapshot creation process adaptive to actual data state changes rather than following a rigid schedule.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent changes the triggering parameter for snapshot creation from time-based to data-volume-based. By monitoring the volume of modified data blocks and comparing it against thresholds, the system determines when to create snapshots, fundamentally changing the parameter that drives snapshot creation decisions.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If snapshots are created frequently to minimize data loss, then data reliability improves, but storage space is wasted on snapshots with similar data

Engineering Contradiction:

Improvedata protectionVSAvoidstorage space

Core Design Contradiction:

ReliabilityVSVolume of stationary object

Solution Approach 1:

The patent introduces threshold parameters that define minimum significant data change volumes. By setting these thresholds, the system filters out trivial snapshot creations and only generates snapshots when data modifications are substantial enough to warrant storage, thereby optimizing the balance between data protection and storage efficiency.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The patent implements a mechanism to discard unnecessary snapshots by comparing data modification volumes against thresholds. Snapshots that would capture minimal or redundant data changes are prevented from being created, effectively discarding wasted storage operations while maintaining adequate data protection through selective snapshot creation.

Inventive Principle:

Principle #34Discarding and recovering

3Volume of stationary object

If snapshots are created periodically, then storage capacity is utilized, but processing resources are used unnecessarily when no significant changes occur

Engineering Contradiction:

Improvestorage utilizationVSAvoidprocessing resource usage

Core Design Contradiction:

Volume of stationary objectVSUse of energy by moving object

Solution Approach 1:

The patent changes the activation parameter for snapshot creation from time-based periodicity to data-change-based triggering. The system monitors data modification volumes and only initiates snapshot creation processes when changes exceed thresholds, eliminating unnecessary processing resource consumption during periods of minimal data activity.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The system performs self-monitoring of data modification volumes and autonomously decides when snapshot creation is warranted. By having the system track its own data state changes and trigger snapshots only when necessary, it eliminates wasteful processing resources while maintaining adequate storage utilization through intelligent, demand-driven snapshot creation.

Inventive Principle:

Principle #25Self-service

4Volume of stationary object

If snapshots are created based on data modifications, then storage efficiency improves, but determining when to create snapshots becomes more complex

Engineering Contradiction:

Improvestorage efficiencyVSAvoidsnapshot creation logic

Core Design Contradiction:

Volume of stationary objectVSDevice complexity

Solution Approach 1:

The patent introduces threshold values as intermediary parameters that simplify the decision-making process. Instead of complex algorithms to determine snapshot necessity, the system compares data modification volumes against predefined thresholds, using these thresholds as mediators to translate raw data change measurements into clear snapshot creation decisions.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10268695B2Snapshot creation

Publication Date: 2019.04.23 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

In one example an updated snapshot delta value is computed upon occurrence of a new transaction. The new transaction is a data modification operation performed on data blocks of the storage device. Further, the delta value indicates at least one of volume of data modified since creation of a reference snapshot and number of transactions performed since the creation. Subsequently, the updated snapshot delta value is compared with a corresponding threshold value. The threshold value is at least one of a predetermined volume of data modified and a predetermined number of transactions. A snapshot action is subsequently performed based on the comparison.