Rotating Incremental Database Backup Strategy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database backup systems face scalability issues with large databases, requiring significant resources during full backups and leading to peak load limitations, especially for terabyte-sized systems, which can restrict backup times and complicate restore processes.
Innovation Solution
The method involves dividing the database into portions and performing full backups of a fraction of the database alternated with incremental backups of the remaining portions, allowing for efficient resource utilization and asynchronous backup processes across multiple databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a full backup is performed on a large database, then complete data backup is achieved, but peak resource requirements (time, space, computing power, network bandwidth) increase significantly
Solution Approach 1:
The database is divided into multiple segments or portions. Instead of backing up the entire database at once, the system performs incremental backups of individual segments. This segmentation allows backup operations to be distributed over time, reducing peak resource requirements while maintaining complete data backup capability.
Solution Approach 2:
The backup system implements periodic incremental backups of database segments rather than a single full backup. By scheduling backups at regular intervals for different segments, the system smooths out resource consumption patterns and eliminates the need for concentrated peak resources that would be required for a complete full backup.
2Power
If full backups are performed at specific intervals, then resource availability is managed, but backup scheduling flexibility is reduced and restore processes become complex
Solution Approach 1:
By segmenting the database into multiple portions with independent backup schedules, the system allows flexible scheduling of backup operations. Each segment can be backed up at different times based on resource availability, business requirements, or priority levels, without constraining the entire backup process to a single rigid schedule.
Solution Approach 2:
The backup system dynamically adjusts scheduling based on segment priority, resource availability, and change detection. High-priority segments can be backed up more frequently or at more convenient times, while lower-priority segments can be scheduled during off-peak periods, providing operational flexibility that static full backup schedules cannot offer.
3Power
If incremental backups are performed on large databases, then resource consumption is reduced, but the number of backups required for complete restoration increases
Solution Approach 1:
The database is segmented into multiple portions, and incremental backups are performed on these segments rather than on the entire database. This approach reduces the amount of data that needs to be backed up in each incremental operation, lowering resource consumption. Additionally, because segments are smaller and can be restored independently, the overall restoration process can be optimized by restoring only the necessary segments rather than processing through an entire chain of incremental backups.
Data Source
AI summary
A method for backing up a database includes identifying n portions of a database wherein each of the n portions is greater than 0% and less than 100% of the database. The method also includes performing a complete backup of a first 1/n portion of the database and performing an incremental backup on the remaining (n−1)/n portion of the database, and for each subsequent backup, performing a complete backup of a next 1/n portion of the database and performing an incremental backup on the remaining (n−1)/n portion of the database.