Database Maintenance Downtime Reduction via Traffic Redirection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database downtime during maintenance, updates, and repairs disrupts the 'always-on' availability of online applications, leading to user frustration and increased costs due to lost transactions and potential errors during rushed recovery processes.
Innovation Solution
Implementing a system that mirrors data from a source database to a target database, limits access to designated tables, redirects traffic during maintenance, captures and replicates updates, and then switches back to the source database, minimizing downtime by maintaining data access and reducing the time required for synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is copied from source database to target database for maintenance, then database availability is improved, but system complexity increases
Solution Approach 1:
The database system is segmented into source database and target database components, allowing independent operation and maintenance. The traffic management is segmented into read traffic (redirected to target) and write traffic (handled by source), enabling parallel maintenance operations without complete system shutdown.
Solution Approach 2:
A traffic manager component is introduced as an intermediary between users and the database system. This mediator redirects read requests to the target database during maintenance while allowing write requests to reach the source database, coordinating traffic flow without requiring system shutdown.
2Loss of time
If traffic is redirected to target database during maintenance, then downtime is reduced, but data synchronization complexity increases
Solution Approach 1:
A pre-synchronization phase is performed before maintenance begins, copying data from source to target database in advance. This preliminary action ensures the target database is ready to handle read traffic immediately when maintenance starts, minimizing the actual downtime period.
Solution Approach 2:
Data synchronization continues throughout the maintenance process rather than stopping. The system maintains continuous data flow between source and target databases, ensuring the target remains an up-to-date backup for read operations while the source undergoes maintenance.
3Reliability
If access is limited to designated tables in target database, then data consistency is improved, but operation flexibility decreases
Solution Approach 1:
Different access permissions are applied to different parts of the database system. The target database allows full read access for general traffic, while designated tables have restricted access for write operations. This local differentiation of access quality maintains data consistency in critical areas while preserving operational flexibility elsewhere.
Solution Approach 2:
Instead of completely blocking write access to the target database, the system allows partial write access to designated tables under controlled conditions. This partial action approach maintains data consistency for critical data while still permitting necessary operational flexibility for specific maintenance scenarios.
Data Source
AI summary
Embodiments enable reduction of database downtime in a live production environment of an on-demand database service during repair and/or maintenance tasks. A source database and a target database are provided. Data is copied from the source database to the target database to create a mirrored set of data. Access is limited to one or more designated tables in the target database. General traffic is redirected from the source database to the target database, wherein the redirection occurs for a duration of a maintenance period. Data modifications that occur in the target database during the maintenance period are captured and then replicated into the source database. Finally, general traffic is redirected from the target database to the source database.