Kubernetes Service Cluster Backup via Persistent Volume Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for backing up a service cluster instance in a Kubernetes database are inefficient and do not support rapid backup, leading to incomplete data protection and high availability issues.
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 triggering condition is met, and backing up data to a designated storage area, thereby ensuring comprehensive and efficient backup.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional backup methods are used for service cluster instances, then data backup can be achieved, but the backup efficiency is low and rapid backup cannot be realized
Solution Approach 1:
The patent segments the service cluster instance into multiple container groups, and further divides backup operations into incremental backup phases. Instead of backing up the entire cluster at once, it performs backup at the container group level, allowing parallel processing and significantly improving backup efficiency while reducing total backup time.
Solution Approach 2:
The patent performs preliminary actions by first identifying and marking container groups that need backup, pre-allocating storage resources, and preparing backup metadata before actual data copying begins. This preliminary preparation enables the backup process to proceed more efficiently once initiated.
2Reliability
If entire service cluster instance backup is implemented, then data persistence is ensured, but backup complexity increases
Solution Approach 1:
The patent manages complexity by segmenting the backup system into modular components: container group identification modules, backup decision modules, execution modules, and restoration modules. Each module handles specific tasks independently, making the overall system more manageable and maintainable while ensuring complete cluster backup.
Solution Approach 2:
The patent creates a universal backup framework that can handle different types of container groups, storage backends, and recovery scenarios through a single standardized interface. The backup system is designed to work with various Kubernetes configurations and storage types, reducing the need for multiple specialized backup systems.
3Extent of automation
If manual backup processes are used, then backup can be performed, but automation level is low and rapid recovery cannot be achieved
Solution Approach 1:
The patent implements feedback mechanisms where the backup system continuously monitors the state of container groups, storage resources, and backup progress. Based on this feedback, it automatically adjusts backup strategies, prioritizes critical container groups, and triggers recovery processes when failures are detected, enabling rapid automated response without manual intervention.
Solution Approach 2:
The backup system is designed to be self-service capable, automatically identifying which container groups need backup, selecting appropriate storage locations, executing backup operations, and managing restoration processes without requiring manual configuration or intervention. The system autonomously handles the entire backup and recovery lifecycle.
Data Source
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.