Local Backup Server Data Block Deduplication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data recovery methods from a managed services provider (MSP) to a client are slow and inefficient, particularly over low bandwidth network connections, as they involve transmitting large data blocks and require significant network resources.
Innovation Solution
The method involves using a local backup server to store and retrieve data blocks, with deduplication techniques to minimize data transmission and a dynamic window scan to optimize disk access and memory usage, allowing for sequential restoration of data blocks while minimizing wait time for unavailable data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data is recovered by transmitting large data blocks over network, then complete data recovery is achieved, but network bandwidth is consumed and recovery speed is slow
Solution Approach 1:
The patent extracts only the necessary data blocks from the backup storage that are needed for recovery, rather than transmitting all data blocks. The system identifies and retrieves only the specific blocks required to reconstruct the target data, significantly reducing network bandwidth consumption while maintaining complete data recovery capability.
Solution Approach 2:
The patent segments the data recovery process into identifying required blocks, retrieving those specific blocks from backup storage, and reconstructing the target data. This segmentation allows the system to optimize each stage independently, particularly by minimizing network transmission to only essential blocks, thereby improving overall recovery speed while reducing bandwidth usage.
2Productivity
If all data blocks are stored locally on client system, then data recovery speed is improved, but storage space requirements increase
Solution Approach 1:
The patent applies local quality by storing data blocks with different characteristics in different locations. Frequently accessed or critical data blocks are stored locally on the client system for rapid retrieval, while less frequently accessed blocks remain in centralized backup storage. This differentiated storage strategy optimizes recovery speed for critical data while minimizing overall local storage requirements.
3Ease of operation
If data blocks are retrieved sequentially from backup storage, then storage access is simplified, but recovery time increases due to waiting for unavailable blocks
Solution Approach 1:
The patent applies preliminary action by pre-identifying all data blocks required for recovery before the actual retrieval process begins. The system analyzes the target data structure and determines the complete set of necessary blocks in advance, then retrieves them systematically from backup storage. This preliminary planning eliminates waiting time during recovery by ensuring all required blocks are identified and fetched without interruption.
Solution Approach 2:
The patent implements dynamics by adapting the data block retrieval strategy based on availability and priority. The system dynamically adjusts the retrieval order and parallelism of block fetching operations, switching between sequential and parallel access patterns depending on storage system state and block availability. This dynamic approach minimizes recovery wait time while maintaining storage access simplicity.
Data Source
AI summary
A method for providing recovery from a remote server to a client includes sending at least one data restore request to the remote server. A data block identifier are received at the client system via a network. A data block associated with the data block identifier is retrieved from a local backup server associated with the client system if the local back up server stores the data block. The data block associated with the data block identifier is received from the remote server if the local backup server does not store the data block. The data block is restored to the client system.