Archival System for Third-Party Network Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data backup tools for third-party network services operate on an after-the-fact model, making it ineffective for immediate data access during catastrophic failures, as they rely on the availability of the third-party service for disaster recovery.
Innovation Solution
Implementing an archival system that selectively archives mission critical data from client terminals before it is stored with a third-party network service, using a network computer system that processes communications to extract and store data independently of the third-party service, enabling immediate data access during service unavailability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If data is stored with a third-party network service, then data accessibility and service functionality are improved, but data security and control are worsened
Solution Approach 1:
The patent segments data management into two independent components: third-party network service for primary data storage and accessibility, and local archival system for security and disaster recovery. This segmentation allows the organization to benefit from cloud accessibility while maintaining independent control over backup copies, resolving the contradiction between ease of operation and reliability.
Solution Approach 2:
The archival system acts as an intermediary between the organization and the third-party network service. It intercepts data before it is stored with the vendor, creates independent archival copies, and provides a fallback mechanism. This intermediary approach enables the organization to maintain data security and control while still utilizing third-party services for primary operations.
2Reliability
If conventional backup tools are used, then data backup is achieved, but immediate data access during service failure is lost
Solution Approach 1:
The archival system performs preliminary actions by intercepting and archiving data before it is stored with the third-party vendor. This proactive approach ensures that validated archival copies already exist locally, eliminating the need to wait for vendor backup processes to complete. In the event of service failure, data can be immediately restored from pre-existing archives, resolving the contradiction between backup reliability and recovery time.
3Ease of operation
If reliance on vendor backup processes increases, then service simplicity is improved, but disaster recovery effectiveness is worsened
Solution Approach 1:
The organization implements self-service capability through the archival system, which independently intercepts, validates, and archives data without relying on vendor backup processes. This self-service approach maintains service simplicity for primary operations while ensuring effective disaster recovery through autonomous archival copies that can be restored immediately if the vendor service fails.
Data Source
AI summary
A network computer system to process communications that include at least one of (i) requests sent from a set of client terminals to a third-party network service, or (ii) response communications, sent from the third-party network service to the set of client terminals. The network computer system implements operations to select data sets from the processed communications for archival. The network computer system can store the data sets in association with the determined contextual information in an archival data structure, independent of the third-party network service.