Dynamic Backup Strategy Selection for Cloud Database Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database backup strategies in cloud environments are inefficient in terms of resource utilization and time, leading to high costs and suboptimal recovery processes, as they often perform full backups daily regardless of the workload, which may not be necessary.
Innovation Solution
A system and process that dynamically determines and selects a backup strategy based on the actual workload of the database, choosing between complete, delta, or no backups, using metrics such as data size, age of last backup, and number of log backups to optimize resource usage and recovery time while maintaining acceptable Recovery Time Objective (RTO) and Recovery Point Objective (RPO) standards.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full backups are performed daily regardless of workload, then data recovery reliability is ensured, but resource consumption (memory, processing, storage) and costs increase
Solution Approach 1:
The backup strategy dynamically adjusts backup frequency and type based on actual database workload conditions. The system monitors workload metrics and automatically selects between full backups, delta backups, or no backups, making the backup approach flexible and adaptive rather than static and rigid.
Solution Approach 2:
The system changes backup parameters (frequency, type, intensity) based on workload conditions. When workload is low, it performs fewer or smaller backups; when workload is high, it adjusts accordingly. This parameter adjustment resolves the contradiction by matching backup intensity to actual data change rates.
2Reliability
If full backups are performed daily, then complete data recovery is possible, but recovery time and administrative overhead increase
Solution Approach 1:
The backup process is segmented into different types: full backups and delta backups. Delta backups capture only changed data since the last full backup, allowing for faster recovery by applying smaller incremental changes rather than restoring complete backup sets.
Solution Approach 2:
Instead of always performing complete full backups, the system performs partial backups (delta backups) that capture only the necessary changed data. This partial action is sufficient for recovery purposes while significantly reducing backup size and recovery time.
3Reliability
If backup frequency is increased, then data loss protection is improved, but storage consumption and processing costs increase
Solution Approach 1:
The system extracts only the changed data portions for backup rather than backing up the entire database repeatedly. Delta backups extract and store only the differences since the last full backup, significantly reducing storage consumption while maintaining adequate data loss protection.
Solution Approach 2:
The system discards redundant backup data and keeps only essential backup sets needed for recovery. By maintaining one full backup and incremental delta backups, it discards unnecessary duplicate data storage while preserving recovery capability.
Data Source
AI summary
A system and method to receive, from a database service executing on a cloud infrastructure, information indicating metrics regarding backups for the database service, the information including at least an indication of an age of a last complete backup for the database service, an indication of a size of changed data since the last complete backup, and an indication of a number of data units changed since the last complete backup; determine a type of backup strategy to instruct the database service to perform based on the received information, the type of backup strategy being one of a complete backup of the database service, a delta backup of the database service, and no backup of the database service; and issue, in response to the determination, an instruction to the database service to execute the determined type of backup.