Application System Snapshot Synchronization for Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application systems face inefficiencies in data synchronization, particularly during failover processes, due to the need for full copies which result in high time and bandwidth overheads, leading to delayed failover and inconsistencies in snapshot versions across systems.
Innovation Solution
The method involves determining if the second and third application systems have a common snapshot, allowing for incremental data synchronization only when a common snapshot exists, thereby reducing the need for full copies and enhancing synchronization efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full data copies are performed during failover preparation, then data consistency is ensured, but time consumption and bandwidth overhead increase significantly
Solution Approach 1:
The patent extracts only the necessary data portions that need to be synchronized between application systems. By identifying and transferring only the non-common data blocks rather than performing full data copies, the solution ensures data consistency while significantly reducing the time and bandwidth resources required during failover preparation
Solution Approach 2:
The patent segments the data synchronization process into identifying common snapshots and transferring only the differential portions. This segmentation allows the system to divide the large data transfer task into smaller, more efficient operations, reducing overall failover preparation time while maintaining data consistency
2Reliability
If full data copies are performed during failover preparation, then data consistency is ensured, but bandwidth consumption increases
Solution Approach 1:
The patent extracts and transfers only the essential non-common data blocks between application systems. By using snapshot comparison to identify what data actually needs to be transferred, the solution ensures data consistency is maintained while minimizing bandwidth consumption during failover preparation
3Device complexity
If snapshot version inconsistencies are allowed, then synchronization complexity is reduced, but data reliability decreases
Solution Approach 1:
The patent performs preliminary snapshot comparison and identification of common snapshots before the actual data transfer. By determining which data blocks are non-common in advance, the system prepares the synchronization process efficiently, reducing complexity while ensuring data reliability through targeted transfer of only the necessary data portions
Data Source
AI summary
Techniques manage application systems in an application environment. The application environment includes a first application system, a second application system and a third application system. First snapshot information of a first group of snapshots of the first application system is obtained, the first application system being in active state. Second snapshot information of a second group of snapshots of the second application system is obtained, the second application system being in standby state. It is determined whether the second application system and the third application system have a common snapshot based on the first snapshot information and the second snapshot information. Data is synchronized to the third application system depending on whether the second application system and the third application system have a common snapshot. Overheads required during data synchronization may be reduced as far as possible, and the efficiency of data synchronization may be improved.