Replicant-Based Data Replication for High-Availability Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data replication methods are inefficient in providing high-availability storage across multiple redundant sites, leading to potential data loss and delayed redundancy in critical applications like digital remittance document storage.
Innovation Solution
A system that uses a reference registry and a 'replicant' to efficiently replicate data across multiple storage sites by transmitting a small, efficient file containing necessary information to enable quick registry entry creation and indexing, allowing immediate replication upon receiving content via an API call, with replication logic integrated into the API to manage and retry requests until successful.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional data replication methods are used to store redundant copies at multiple locations, then reliability is improved, but replication speed and efficiency deteriorate
Solution Approach 1:
The patent segments the replication process into two distinct phases: (1) transmitting only the registry replicant (metadata/descriptive entry) to remote sites for immediate local indexing, and (2) subsequent transmission of the actual content data. This segmentation allows the system to achieve immediate replication acknowledgment without waiting for large content transfers, thereby improving replication speed while maintaining reliability through the registry replicant mechanism.
Solution Approach 2:
The patent applies preliminary action by first transmitting and processing the registry replicant (containing descriptive entries about the content) before the actual content data is transmitted. Remote sites can immediately create local registry entries and index the content metadata in advance, enabling fast content retrieval and replication acknowledgment without waiting for the full content transfer to complete.
2Reliability
If extensive computing resources are provisioned for data replication tasks, then reliability is improved, but system complexity and cost increase
Solution Approach 1:
The patent uses copying by transmitting a registry replicant (a simplified copy containing only descriptive entries and metadata about the content) to remote sites instead of copying the entire content data immediately. This lightweight copy enables remote sites to create local registry entries and prepare for content reception without requiring extensive computing resources, thereby reducing system complexity while maintaining replication reliability.
3Productivity
If immediate replication is implemented upon receiving content, then productivity is improved, but data integrity and reliability may deteriorate
Solution Approach 1:
The patent implements feedback by having remote sites send replication status information back to the originating site after receiving and processing the registry replicant. The originating site can track replication status and verify that content has been successfully received and indexed at remote locations, ensuring data integrity while maintaining fast replication throughput through the lightweight registry replicant mechanism.
Data Source
AI summary
Aspects and features of this disclosure provide a high-availability storage platform employing multiple redundant sites. Replication to multiple sites can begin upon receiving content and can be completed quickly, in part through the use of a small and efficient file that can be sent to storage sites. The file enables each storage site to efficiently build appropriate entries in a reference registry for storing and indexing the content. In some examples, a registration request including the content is received and the content is stored in an instance of the centralized storage system at an initial storage site. The aforementioned file is transmitted to additional storage sites to cause the content to be stored in additional instances of the centralized storage system. The file can also be accessed at the additional storage sites to update instances of the reference registry.