Network-Based Disaster Recovery for IoT Data Resilience
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional disaster recovery solutions for IoT applications are costly, complex, and inefficient, as they require duplicating data in two databases, leading to data loss during replication and increased storage needs, and are difficult to implement without modifying existing systems.
Innovation Solution
A network-based disaster recovery solution that continuously monitors network traffic, detects missing data packets, and automatically replays them, reducing the need for advanced database replication and minimizing data loss by capturing and archiving network traffic data for self-healing properties without requiring system modifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional database-level data backups are used for disaster recovery, then data can be restored in case of disaster, but storage needs increase and data loss occurs during replication
Solution Approach 1:
The patent extracts the disaster recovery function from the database level to the network package level. Instead of duplicating entire databases, the system captures and stores individual network packages transmitted between devices and the database server, restoring data by replaying these captured packages rather than performing full database replication.
Solution Approach 2:
The system performs preliminary action by continuously capturing and archiving network traffic packages before disasters occur. The package capture process runs in the foreground during normal operation, storing packages in archives with sequential naming conventions, so that when a disaster occurs, pre-captured packages are already available for immediate restoration without needing to perform time-consuming database replication.
2Reliability
If database replication is implemented for disaster recovery, then data redundancy is achieved, but system complexity and implementation difficulty increase
Solution Approach 1:
The patent introduces an intermediary component - the package capture and replay system - that operates at the network level between applications and the database server. This intermediary captures network packages, stores them in archives, and replays them during restoration, providing data redundancy without requiring complex database replication mechanisms or modifications to existing database systems.
Solution Approach 2:
Instead of replicating entire databases with all their complex relationships and constraints, the system creates simple copies of network packages in archival files. Each captured package is stored as a discrete unit with a sequential name, creating a straightforward copy mechanism that avoids the complexity of database replication while still providing sufficient data for restoration.
3Reliability
If continuous monitoring of network traffic is implemented, then missing packages can be detected and replayed, but additional processing resources are required
Solution Approach 1:
The monitoring system serves itself by using the same network packages that are being captured for both their original purpose and for monitoring/restoration purposes. The package capture process naturally records all traffic, and the sequential naming convention automatically detects gaps without requiring additional complex monitoring logic, allowing the system to self-identify missing packages through simple file sequence verification.
Data Source
AI summary
A tool for network-based package monitoring and recovery. The tool scans a database to identify a gap in network traffic data. The tool determines whether at least one gap in the network traffic data is identified in the database, wherein the at least one gap is a gap in communication between a target device and a communication serve. Responsive to a determination that at least one gap in the network traffic data is identified, the tool determines a missing package from a package archive. The tool determines whether there is active network traffic between the target device and the communication server. Responsive to a determination that there is active network traffic between the target device and the communication server, the tool replays the missing package in the active network traffic between the target device and the communication server.