Configurationless Redundancy for Computing Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Configuring redundant components in computing systems is time-consuming and costly, and existing methods often result in the loss of configuration data when primary components fail, requiring manual reconfiguration of secondary components.
Innovation Solution
A method where a primary component is designated and its configuration automatically copied to secondary components, using a memory accessible by both primary and secondary components, and a communication link, allowing for immediate configuration of secondary components upon failure or replacement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If manual configuration of secondary components is performed, then configuration accuracy is improved, but time consumption and cost increase significantly
Solution Approach 1:
The system performs preliminary configuration actions by automatically copying configuration data from primary to secondary components before failure occurs. This ensures that when a component fails, the secondary component is already configured and ready for immediate activation, eliminating the need for time-consuming manual configuration after failure.
Solution Approach 2:
The patent implements a copying mechanism where configuration data is automatically replicated from primary components to secondary components. This copying process ensures configuration accuracy while eliminating manual intervention, thereby reducing both time consumption and cost associated with manual configuration tasks.
2Reliability
If redundant components are implemented for high availability, then system reliability is improved, but device complexity and cost increase
Solution Approach 1:
The system implements self-service automation where the configuration management process occurs automatically without requiring additional complex management infrastructure. The primary component automatically copies its configuration to secondary components, and the system automatically detects failures and activates backups, reducing the complexity burden that would otherwise be associated with managing redundant components.
Solution Approach 2:
By performing configuration copying in advance before failures occur, the system eliminates the need for complex real-time configuration management during failure scenarios. This preliminary action simplifies the overall system complexity while maintaining high availability through redundant components.
3Device complexity
If configuration data is stored only in primary components, then storage simplicity is improved, but information loss occurs when primary component fails
Solution Approach 1:
The patent implements automatic copying of configuration data from primary to secondary components. This creates redundant copies of the configuration information, ensuring that when a primary component fails, the configuration data is preserved in the secondary component and can be immediately utilized, preventing any information loss.
Solution Approach 2:
The system prepares for potential information loss by creating backup copies of configuration data in advance. This beforehand cushioning ensures that even if the primary component fails completely, the configuration information remains protected and accessible through the secondary component.
Data Source
AI summary
A method for configuring components in a computing system. A selected one of the components is designated as a primary component, the other components thereby automatically adopting a status of secondary component. The designation of the primary component is stored in a first memory that is accessible by at least one of the primary component, at least one secondary component, and the computing system. Upon occurrence of a predetermined computing system event, the first memory is read to determine the designation of the primary component. A configuration file from a second memory is automatically copied to a memory of at least one secondary component, thereby creating a new configuration file in the at least one secondary component.