Mailstore Server Failover Using Metadata Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current e-mail management systems face challenges in achieving high reliability and fault tolerance due to the need for complete replication of data between main and auxiliary mailstore servers, which can lead to data loss and security issues, especially when the main server fails, as it requires a dedicated network and cannot differentiate between valid and invalid commands or unauthorized changes.
Innovation Solution
A method and system where a first server acts as a mailstore, with a second server capable of replacing it in case of failure, utilizing a communication protocol (ZxLink) and management software modules to verify and transfer metadata and raw data to a third server, which stores and manages the data, allowing for continuous operation without a dedicated network and improving data security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If complete replication of messages is performed in an auxiliary mailstore server, then fault tolerance is improved, but device complexity and network requirements increase
Solution Approach 1:
The patent uses selective copying of only metadata (not complete message replication) to the auxiliary mailstore server. This reduces the data volume that needs to be replicated and stored, thereby simplifying network configuration and reducing device complexity while still maintaining fault tolerance capabilities through metadata availability.
Solution Approach 2:
The patent extracts only the essential metadata from complete message replication. By taking out only the critical identification and routing information needed for fault tolerance, the system avoids the complexity of replicating entire messages while maintaining the ability to restore service continuity.
2Reliability
If a dedicated network is used for supervision management, then reliability is improved, but data security deteriorates due to replication of incorrect commands and unauthorized accesses
Solution Approach 1:
The patent applies local quality by implementing selective data replication based on data type and validity. Instead of replicating all data uniformly, the system applies different replication rules: valid metadata is replicated to ensure continuous operation, while invalid commands and unauthorized accesses are filtered out and not replicated, thereby maintaining data security.
Solution Approach 2:
The patent implements a feedback mechanism through verification modules that check the validity of commands before replication. The system monitors incoming data, verifies its legitimacy, and only replicates validated metadata. This feedback loop prevents incorrect commands and unauthorized accesses from being replicated, maintaining security while ensuring continuous operation.
3Object-affected harmful factors
If verification of metadata validity is implemented, then data security is improved, but processing time increases
Solution Approach 1:
The patent applies preliminary action by implementing verification mechanisms that check metadata validity in advance before replication occurs. By performing verification proactively on incoming metadata, the system identifies and filters invalid data before it enters the replication process, preventing security issues while maintaining efficient processing through early validation.
4Reliability
If auxiliary hardware and supervision software are used for replacement operations, then fault tolerance is improved, but device complexity and data transfer interference increase
Solution Approach 1:
The patent implements self-service by enabling the auxiliary mailstore server to automatically take over operations when the main server fails. The system uses software-based monitoring and automatic failover mechanisms that eliminate the need for complex auxiliary hardware, allowing the auxiliary server to service itself and maintain continuity without additional hardware complexity.
Data Source
AI summary
A method for providing continuous operation on e-mails includes providing a first server located at a first position and acting as mailstore for the user at the user computing device, providing at least one second server located at a second position different from the first position, and providing a third server located at a third position different from the first and second positions. Upon failure of the first server, the method involves preparing the second server to act as mailstore in the place of the first server, the preparing step comprising sending a signal to the second server to find data of the third server by means of pointers, store data in the second server, and convert the data respectively to raw data and metadata and storing the raw data and metadata in the second server.