Management Instance Synchronization for Resilient Data Center Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data synchronization methods in data center networks are resource-intensive and inefficient, particularly in managing redundancy and failover scenarios, leading to suboptimal management resilience.
Innovation Solution
Implementing application-level data synchronization between active and backup management system instances, where each application instance selectively transfers and reconstructs data based on what cannot be reconstructed by the backup, optimizing resource usage and ensuring complete data availability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional data synchronization methods are used between active and backup management system instances, then data redundancy is maintained, but resource consumption increases and synchronization efficiency decreases
Solution Approach 1:
The patent extracts and transfers only the specific subset of data that cannot be reconstructed by the backup instance, rather than synchronizing all data. This selective extraction approach reduces resource consumption while maintaining the necessary data redundancy for failover scenarios.
Solution Approach 2:
The system performs partial synchronization by identifying and transferring only the necessary portion of data (the subset that cannot be reconstructed). This partial action approach avoids the excessive resource consumption of full data synchronization while ensuring sufficient redundancy.
2Reliability
If complete data synchronization is performed between active and backup instances, then data availability for failover is ensured, but synchronization time and system overhead increase
Solution Approach 1:
The patent identifies and extracts only the critical subset of data that cannot be reconstructed, transferring only this portion between instances. This extraction principle significantly reduces synchronization time while maintaining data availability for failover by ensuring the essential data is synchronized.
Solution Approach 2:
The system performs preliminary identification of which data can and cannot be reconstructed, allowing the backup instance to pre-prepare for potential failover. This preliminary action reduces the time required during actual failover events by having critical data ready in advance.
3Productivity
If selective data transfer is implemented, then resource efficiency improves, but data completeness for backup reconstruction may be compromised
Solution Approach 1:
The patent implements a feedback mechanism where the backup instance communicates its data reconstruction capabilities to the active instance. Based on this feedback, the active instance determines the precise subset of data that cannot be reconstructed and transfers only that specific portion, ensuring data completeness while maintaining efficiency.
Solution Approach 2:
The system performs exactly the right amount of data transfer by identifying the partial subset that cannot be reconstructed. This avoids both the insufficiency of transferring too little data and the inefficiency of transferring excessive data, achieving optimal synchronization efficiency with complete necessary data.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Various example embodiments for supporting synchronization of management system instances of a management system providing management functions for a network are presented. The synchronization of management system instances of a management system providing management functions for a network may be supported for fabric services system instances of a fabric services system providing management functions for a data center network. The synchronization of fabric services system instances of a fabric services system providing management functions for a data center network may be supported by performing application-level data synchronization between the fabric services system instances of the fabric services system, controlling application-level data synchronization between the fabric services system instances of the fabric services system, reconciling and auditing application-level data synchronization between the fabric services system instances of the fabric services system, or the like, as well as various combinations thereof.