Container Backup Snapshots for Ephemeral Cluster Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management systems face challenges in efficiently protecting and restoring data in container environments, particularly in ephemeral clusters, which are prone to destruction and require efficient backup strategies to ensure data integrity and availability.

Innovation Solution

A two-phase snapshot approach is implemented, where a first snapshot including metadata and resource data is stored in offsite cloud storage, and a second snapshot of application data is stored in onsite persistent volume, enabling efficient data protection and restoration across clusters.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all data is stored in offsite cloud storage, then data security and disaster recovery are improved, but bandwidth costs and storage expenses increase

Engineering Contradiction:
Improvedata securityVSAvoidbandwidth costs
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments data into two categories: metadata (stored in offsite cloud storage) and application data (stored in onsite persistent volume). This segmentation allows the system to maintain data security for critical metadata while keeping frequently accessed application data locally, thereby reducing bandwidth costs and storage expenses while preserving reliability.

Inventive Principle:
Principle #1Segmentation

2Speed

If all data is stored in onsite storage, then access speed and operational efficiency are improved, but data security and disaster recovery capabilities deteriorate

Engineering Contradiction:
Improveaccess speedVSAvoiddisaster recovery
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

By segmenting data storage locations based on data type, the patent enables fast access to application data stored onsite while maintaining disaster recovery capabilities through offsite cloud storage of metadata. This resolves the contradiction between access speed and disaster recovery.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by storing different types of data in different locations optimized for their specific requirements: metadata in offsite cloud storage for security and application data in onsite persistent volume for speed. This allows each data type to be stored in the most appropriate location.

Inventive Principle:
Principle #3Local quality

3Reliability

If comprehensive data backup is performed, then data integrity is improved, but system complexity and operational overhead increase

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent simplifies the backup system by segmenting it into two distinct phases: metadata backup to offsite cloud storage and application data backup to onsite persistent volume. This segmentation reduces system complexity compared to a single comprehensive backup system while maintaining data integrity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12530264B2Data backup in container management frameworks
Publication Date: 2026.01.20 RUBRIK INC
  • US12530264B2 patent drawing
  • US12530264B2 patent drawing
  • US12530264B2 patent drawing

AI summary

In some examples, a cluster protection system comprises at least one processor and a memory storing instructions which, when executed by the at least one processor, cause the system to perform operations comprising identifying a target cluster or an object in a container management framework, identifying application data and metadata associated with the target cluster or the object, generating a first snapshot of the target cluster or the object, the first snapshot including at least the metadata, storing the first snapshot in offsite cloud storage, generating a second snapshot of the target cluster, the second snapshot including at least the application data, and storing the second snapshot in a persistent volume in onsite storage.