Staggered Full Snapshot Rollouts for Data Management Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large-scale full snapshot operations in data management systems (DMS) can lead to performance degradation and compliance issues when initiated simultaneously, especially when switching storage engines with incompatible formats.

Innovation Solution

A staggered or phased full snapshot rollout approach is implemented, where full snapshots are acquired in subsets over time, based on unique object identifiers and adjustable percentages, to maintain system performance and compliance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full snapshots are obtained simultaneously for all objects, then complete backup coverage is achieved, but system performance degrades and compliance issues arise

Engineering Contradiction:
Improvebackup coverageVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the set of objects into multiple subsets based on their unique identifiers (e.g., using modulo arithmetic to distribute objects across groups). Full snapshots are then obtained for each subset at different time periods, segmenting the backup process to prevent simultaneous operations from degrading system performance while ensuring all objects are eventually backed up.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements periodic action by scheduling full snapshot operations at different time periods for different subsets of objects. The system obtains full snapshots for a first subset at a first time period, then for a second subset at a second time period, creating a periodic backup rhythm that maintains system performance while achieving complete backup coverage over time.

Inventive Principle:
Principle #19Periodic action

2Reliability

If full snapshots are obtained simultaneously for all objects, then complete backup coverage is achieved, but operational complexity increases

Engineering Contradiction:
Improvebackup coverageVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments objects into subsets based on their unique identifiers, which simplifies the management of large-scale backup operations. By dividing the object set into manageable groups, the system reduces the complexity of coordinating simultaneous backup operations across all objects while maintaining comprehensive backup coverage.

Inventive Principle:
Principle #1Segmentation

3Quantity of substance

If full snapshots are obtained for a large quantity of objects, then comprehensive backup coverage is achieved, but workload peaks occur

Engineering Contradiction:
Improvenumber of snapshotsVSAvoidworkload
Core Design Contradiction:
Quantity of substanceVSPower

Solution Approach 1:

The patent segments the large quantity of objects into smaller subsets, distributing the snapshot acquisition workload across multiple time periods. This segmentation prevents workload peaks by ensuring that only a portion of objects are being backed up at any given time, while still achieving comprehensive backup coverage of all objects.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses periodic action to distribute the snapshot acquisition workload over time. By obtaining full snapshots for different subsets at different time periods, the system prevents simultaneous workload peaks and maintains manageable resource consumption while still capturing comprehensive backup data for all objects.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS12353291B2Obtaining full snapshots for subsets of objects over time
Publication Date: 2025.07.08 RUBRIK INC
  • US12353291B2 patent drawing
  • US12353291B2 patent drawing
  • US12353291B2 patent drawing

AI summary

A data management system (DMS) may use a staggered full snapshot rollout approach to obtain full snapshots of multiple computing objects. The DMS may identify that a quantity of the multiple objects scheduled for full backups by the DMS exceeds a threshold quantity. The DMS may initiate, at a first time, and based on the quantity of objects exceeding the threshold quantity, a first set of full snapshots corresponding to a first subset of objects included in the multiple objects. The DMS may initiate, at a second time subsequent to the first time, a second set of full snapshots corresponding to a second subset of objects included in the multiple objects. The second subset of objects may be different than the first subset of objects. The DMS may continue to obtain full snapshots of respective subsets of the multiple objects until all of the scheduled full snapshots are obtained.