Kubernetes Cluster Backup Using Persistent Volume Snapshots

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing backup methods for Kubernetes service cluster instances are inefficient and do not support rapid backup, leading to incomplete data backup of service cluster instances.

Innovation Solution

A method and apparatus for service cluster instance backup and recovery that involves setting source persistent volume claims and objects for each container group, creating backup persistent volume claims and objects when a backup condition is met, and backing up data to a designated storage area, thereby ensuring comprehensive backup of the service cluster instance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional backup methods are used for service cluster instances, then the backup process is simple to implement, but the backup efficiency is low and rapid backup cannot be achieved

Engineering Contradiction:
Improvebackup efficiencyVSAvoidbackup system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the service cluster instance into multiple container groups, and further segments the backup process into distinct phases (snapshot creation, data copying, verification). By introducing persistent volume claims and persistent volume objects as intermediate management layers, the system divides the complex backup task into manageable units that can be processed independently and in parallel, thereby improving backup efficiency without overwhelming the system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by pre-configuring persistent volume claims and persistent volume objects before the actual backup process. Storage resources are pre-allocated and bound to container groups in advance, and snapshot mechanisms are prepared beforehand. This preliminary setup enables the backup process to proceed rapidly without ad-hoc resource allocation during the critical backup window, thus improving productivity while maintaining controlled complexity.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the entire service cluster instance is backed up using conventional methods, then data completeness can be achieved, but the backup time is excessive and rapid recovery is not possible

Engineering Contradiction:
Improvedata backup completenessVSAvoidbackup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent employs copying mechanisms through persistent volume objects that create references to storage resources without immediately duplicating all data. Snapshot functionality creates point-in-time copies of the storage state, and data copying is performed selectively based on changes detected since the last backup. This approach ensures data completeness while dramatically reducing the time required compared to traditional full backup methods.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent replaces mechanical data copying with more efficient storage-level mechanisms. Instead of application-level data extraction and transfer, the system uses persistent volume snapshots and storage area network (SAN) copying capabilities. This substitution leverages hardware and storage system optimizations to achieve rapid, complete backups without the overhead of traditional software-based backup processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If backup persistent volume claims and objects are created for each container group, then complete data backup is ensured, but the system complexity increases

Engineering Contradiction:
Improvebackup completenessVSAvoidvolume management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates persistent volume claims and persistent volume objects that serve multiple functions: they manage storage resources, track backup states, enable data recovery, and facilitate container group portability. This multi-functionality reduces the need for separate mechanisms for each concern, thereby improving backup completeness while actually reducing overall system complexity through consolidation of functions into unified objects.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250390394A1Service cluster instance backup and recovery methods and related devices
Publication Date: 2025.12.25 TENCENT TECHNOLOGY (SHENZHEN) CO LTD
  • US20250390394A1 patent drawing
  • US20250390394A1 patent drawing
  • US20250390394A1 patent drawing

AI summary

Service cluster instance backup and recovery methods and related devices are disclosed. For a container group in a service cluster instance to be backed up, a source persistent volume claim and a source persistent volume object corresponding to the container group may be set, and the container group is stored based on the source persistent volume object. When the service cluster instance satisfies a backup triggering condition, for the container group, a backup persistent volume claim and a backup persistent volume object of the container group are created according to the source persistent volume claim and the source persistent volume object corresponding to the container group. To-be-backed-up data of the container group is acquired based on the source persistent volume object. The to-be-backed-up data is backed up to a storage area pointed by the backup persistent volume object according to the backup persistent volume claim of the container group.