Node ID-Based Data Backup for Cloud Database Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data backup methods for relational database services in public cloud platforms face challenges in efficiently managing data backup across multiple nodes, leading to resource wastage and reliability issues due to duplicate backups and centralized scheduling bottlenecks.
Innovation Solution
A data backup method where each node independently determines whether to back up data based on its identifier matching the backup execution node's identifier, allowing for periodic and incremental backups without centralized scheduling, and includes mechanisms for deduplicating data and managing storage time to prevent redundant backups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If centralized scheduling is used to manage data backup across multiple nodes, then backup coordination is achieved, but resource wastage occurs due to duplicate backups and management bottlenecks increase
Solution Approach 1:
The patent divides the centralized backup management function into independent segments at each node. Each node autonomously determines whether to perform backup by comparing its node ID with the backup execution node ID stored in the storage device, eliminating the need for centralized coordination and preventing duplicate backups.
Solution Approach 2:
Each node performs self-service by independently checking if it should be the backup execution node through ID comparison. This self-determination mechanism allows nodes to autonomously decide whether to back up data without requiring centralized scheduling, reducing management overhead and resource waste.
2Reliability
If periodic backup is performed at preset time intervals, then data reliability is improved, but resource consumption increases due to repeated full backups
Solution Approach 1:
The patent implements periodic backup action by having nodes perform backup operations at preset time intervals. The backup execution node compares its ID with stored backup execution node IDs to determine whether to perform incremental or full backup, optimizing the periodic backup process.
Solution Approach 2:
The patent changes the backup volume parameter dynamically. By comparing node IDs and tracking backup execution history, the system adjusts the backup scope between full backup and incremental backup, reducing the quantity of data backed up during periodic operations while maintaining reliability.
3Reliability
If multiple nodes back up data simultaneously, then backup coverage is improved, but resource consumption and storage overhead increase due to duplicate backups
Solution Approach 1:
The patent extracts the backup execution determination function from the storage device and places it at each node. By storing only the backup execution node ID in the storage device and performing ID comparison at nodes, the system eliminates complex centralized management while preventing duplicate backups.
Solution Approach 2:
Instead of having the storage device manage which nodes perform backup, the patent inverts the approach by having nodes independently determine their backup status through ID comparison. This inversion simplifies the system architecture and eliminates duplicate backups.
Data Source
AI summary
This application provides a data backup method. The method includes: obtaining, by a first node, an identifier of a backup execution node from a storage device; and backing up data of the first node in the storage device responsive to determining that an ID of the first node is the same as the ID of the backup execution node. The embodiments of this application can improve reliability of the data stored by the first node, and prevent a plurality of nodes from redundantly backing up duplicate data in the storage device. The techniques disclosed herein reduce resource consumption.