Standby Database Backup Scheduling for Dynamic Role Changes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional backup strategies for databases in high-availability configurations fail to account for dynamic role changes, leading to ineffective backup policies and increased resource utilization due to specifying specific databases, which may become unavailable.
Innovation Solution
Implementing role-based backup policies that ensure databases with specific roles (primary or standby) are consistently backed up, including proactive full backups when role changes are detected, thereby maintaining data protection and reducing resource wastage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional backup strategies specify specific databases for backup, then backup policies can be clearly defined, but the backup may fail when the specified database becomes unavailable due to role changes
Solution Approach 1:
The backup system dynamically determines the standby database based on current role assignments rather than using static database specifications. The system queries the data warehouse to identify which database currently holds the standby role and directs backups to that dynamic target, ensuring backup reliability despite role changes.
Solution Approach 2:
The system implements a feedback mechanism by continuously monitoring database role assignments through queries to the data warehouse. Before executing a backup, the system checks the current role of each database and adjusts the backup target accordingly, ensuring that backups are always directed to the correct standby database.
2Reliability
If backups are performed on the primary database, then data protection is maintained, but resource utilization increases due to redundant backups when role changes occur
Solution Approach 1:
The system dynamically identifies the standby database based on current role assignments rather than always backing up a fixed database. By querying the data warehouse for the current standby role holder and directing backups only to that database, the system avoids redundant backup operations and reduces resource utilization while maintaining data protection.
3Productivity
If incremental backups are performed without detecting role changes, then backup frequency can be increased, but backup integrity is compromised when the designated database changes roles
Solution Approach 1:
The system performs a preliminary check of database roles before executing each backup operation. By querying the data warehouse to confirm the current standby database assignment prior to the backup, the system ensures that incremental backups are directed to the correct database, maintaining backup integrity even at high frequencies.
Solution Approach 2:
The system implements feedback by verifying the current role assignment before each backup execution. This pre-backup verification ensures that incremental backups maintain integrity by always targeting the correct standby database, even when role changes occur between backup cycles.
Data Source
AI summary
In general, embodiments relate to a method for backing up databases, the method includes receiving a backup request, wherein the backup request specifies a role of standby and an asset group identifier for an asset group, identifying, based on the backup request, a database in the asset group, and issuing the backup request for the database.