Configuration Tracking Data Redundancy via Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional configuration tracking systems rely on implicit data redundancy, which can lead to data corruption and loss, resulting in binary availability issues and high costs for disaster recovery, as they do not actively manage data redundancy and are dependent on underlying infrastructure.
Innovation Solution
Implementing explicit data redundancy within the configuration tracking system, where the server and agent actively maintain multiple instances and versions of asset data, allowing the system to recover from failures by proactively collaborating and distributing data across the network, independent of external redundancy services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If implicit data redundancy is used through conventional clustering techniques and remote database replication, then data availability is improved, but data consistency and corruption risks worsen due to the binary availability notion and single data instance approach
Solution Approach 1:
The patent segments the monolithic data instance into multiple distributed data instances across different nodes in the configuration tracking system. Each node maintains its own data instance, eliminating the single point of failure and allowing independent operation of multiple instances, thereby resolving the contradiction between availability and consistency.
Solution Approach 2:
The patent introduces a new dimension of data redundancy by implementing explicit data redundancy at the application layer rather than relying solely on infrastructure-level replication. This creates multiple copies of data across different dimensions (nodes, instances, locations), improving both availability and consistency simultaneously.
2Device complexity
If implicit data redundancy is used relying on lower level infrastructure, then implementation complexity is reduced, but control over data redundancy policies and operations is lost
Solution Approach 1:
The configuration tracking system performs self-service for data redundancy management by implementing explicit redundancy mechanisms within the application layer. The system autonomously manages multiple data instances, handles failover, and maintains consistency without requiring external infrastructure services, thereby gaining control while maintaining manageable complexity.
Solution Approach 2:
The patent implements preliminary actions by proactively creating and maintaining multiple data instances before failures occur. The system pre-configures redundant data copies and establishes failover mechanisms in advance, allowing controlled redundancy management rather than reactive infrastructure-dependent approaches.
3Ease of operation
If single data instance approach is used for service operation, then service simplicity is maintained, but degraded service mode during failures is not possible
Solution Approach 1:
The patent implements dynamic service operation by allowing the system to adapt between different operational modes based on availability requirements. Multiple data instances enable the system to dynamically switch between full service mode (using primary instance) and degraded service mode (using backup instances), maintaining operational flexibility and simplicity while improving reliability.
Data Source
AI summary
In one embodiment, a method and apparatus for collaborative data redundancy for configuration management database is disclosed. The method includes requesting, by a server of a configuration tracking system, an agent of the configuration tracking system to retrieve asset data when a copy of the asset data located in the server becomes corrupted, retrieving by the agent the requested asset data from one or more assets, and transferring by the agent the asset data to the server without utilizing data redundancy services performed outside of the configuration tracking system. Other embodiments are also disclosed.