Parallel Proxy Backup for RDBMS Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Federated backups in relational database management systems (RDBMS) are inefficient due to sequential data transfer from proxy nodes to a target storage system, leading to suboptimal backup windows and resource wastage.
Innovation Solution
Implementing a parallel proxy module that intelligently splits data backups across multiple nodes based on load balancing, fault tolerance, and resource availability, allowing concurrent data transfer and processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If sequential data transfer from proxy nodes to target storage system is used, then device complexity is reduced, but productivity deteriorates due to suboptimal backup window duration
Solution Approach 1:
The patent divides the backup process into multiple parallel data streams, where each proxy node transfers data concurrently to the target storage system. This segmentation of the monolithic sequential backup into parallel independent streams directly improves productivity by utilizing multiple nodes simultaneously, reducing the overall backup window duration.
Solution Approach 2:
The patent merges multiple data transfer operations from different proxy nodes into a single coordinated backup process. By combining the capabilities of multiple proxy nodes working in parallel, the system achieves improved backup performance while managing complexity through centralized coordination of the merged operations.
2Loss of time
If sequential backup from proxy nodes is performed, then resource utilization is optimized, but loss of time increases due to extended backup window
Solution Approach 1:
The patent ensures continuous useful action by maintaining parallel data transfer operations across multiple proxy nodes throughout the backup process. Instead of sequential execution where nodes wait their turn, all proxy nodes continuously transfer data simultaneously, eliminating idle time and reducing the overall backup window.
Solution Approach 2:
The system performs preliminary organization of backup tasks across multiple proxy nodes before execution, enabling them to start data transfer operations concurrently. This preliminary setup allows the backup process to begin immediately with all nodes active, rather than activating nodes sequentially, thereby reducing time loss.
3Productivity
If multiple proxy nodes are used for federated backup, then resource utilization improves, but productivity deteriorates due to sequential data copying
Solution Approach 1:
The patent segments the backup workload across multiple proxy nodes, with each node handling a portion of the data transfer independently and concurrently. This segmentation enables parallel processing that improves backup throughput while the modular nature of segmented tasks helps manage the complexity of coordinating multiple nodes.
Solution Approach 2:
Each proxy node is designed with universal capabilities to perform data transfer operations independently. This multi-functionality allows any proxy node to handle any portion of the backup workload, enabling flexible parallel processing that improves throughput while simplifying coordination through standardized node interfaces.
Data Source
AI summary
Embodiments describe concurrently backing up data associated with a relational database management system (RDBMS). In an embodiment, a request is received to back up data from multiple nodes to a target storage source. The multiple nodes are configured to provide storage services to data associated with the RDBMS and are communicatively coupled to a backup server configured to manage backup of one or more storage devices. In response to the request, one or more preference nodes are identified from multiple nodes based on a preference configuration. Using a backup algorithm, portions of the backup to be performed are assigned to one or more preference nodes selected from the identified preference nodes. The backup operations are initiated using the selected preference node(s). Each portion is a distinct subset of the data to be backed up and each of the selected preference node(s) is assigned a unique portion.