Database Backup Thread Reassignment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The database backup process is time-consuming, especially for large databases, and existing methods terminate idle buffer manipulator threads, which does not effectively improve backup performance.
Innovation Solution
Reassign idle buffer manipulator threads to the largest tablespace that has not completed the backup process, allowing them to assist in the backup of the largest storage capacity areas, thereby optimizing the backup process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If traditional backup methods are used with termination of idle threads, then system resource management is simplified, but backup time increases significantly for large databases
Solution Approach 1:
The patent recovers idle buffer manipulator threads instead of terminating them. When a tablespace completes backup, its buffer manipulator thread is not discarded but held in an idle state, ready to be reassigned to another tablespace needing backup assistance. This recovery approach maintains productive thread resources while adapting to varying backup workloads across different tablespaces.
Solution Approach 2:
The patent implements dynamic thread assignment where buffer manipulator threads are not statically bound to specific tablespaces but are dynamically reassigned based on real-time backup progress. The system continuously monitors which tablespaces have completed backup and redistributes idle threads to tablespaces that still need backup, creating a flexible and adaptive backup process.
2Productivity
If more threads are allocated to backup process, then backup speed increases, but system complexity increases
Solution Approach 1:
The patent implements a self-service thread management system where the backup process automatically monitors its own progress and manages thread allocation without external intervention. The system self-determines which tablespaces have completed backup and automatically reassignes idle threads to tablespaces that need backup, eliminating the need for complex external thread management mechanisms.
Solution Approach 2:
The patent employs feedback mechanisms where the backup process continuously monitors the completion status of each tablespace and uses this information to dynamically adjust thread allocation. The system receives feedback about which tablespaces have finished backup and automatically responds by redistributing idle threads to remaining work, creating a closed-loop control system that optimizes backup performance.
Data Source
AI summary
The indication of a database backup process starting is received. A plurality of buffer manipulator threads are marked as active. A determination is made whether any of the plurality of buffer manipulator threads marked as active in the database backup process become idle. In response to determining that at least one buffer manipulator thread in the database backup process becomes idle, the at least one idle buffer manipulator thread is reassigned to a first largest tablespace in the database that has not completed the database backup process. The first largest tablespace has a largest storage capacity relative to other tablespaces in the database.