Multilayer Manifest Files for Cloud Data Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage systems, such as EMC CloudBoost, face challenges in data retrieval and reconstruction during disaster recovery scenarios, especially when proprietary storage processes are unavailable, making it difficult to recover data from cloud-based storage without deploying the proprietary system.
Innovation Solution
A multilayer manifest process is introduced, where manifest files are generated and integrated with a backup catalog, containing vital information to reconstruct files without relying on proprietary storage processes. These manifest files are successively generated and stored, allowing for secure and efficient recovery of data even without access to the proprietary system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If proprietary storage processes are used to store files in cloud-based storage, then data storage efficiency and deduplication are improved, but data retrieval and reconstruction become difficult when the proprietary system is unavailable
Solution Approach 1:
The patent creates a copy of the essential reconstruction information in the form of manifest files that contain metadata about data chunks. These manifest files are stored separately from the proprietary storage system, enabling data reconstruction through copying chunk data from cloud storage without needing the proprietary reconstruction processes.
Solution Approach 2:
The manifest files act as an intermediary between the stored data chunks and the reconstruction process. They contain vital information (metadata) that mediates the reconstruction process, allowing systems without proprietary software to reconstruct files by using the manifest as a guide to retrieve and assemble data chunks from cloud storage.
2Reliability
If proprietary storage processes are deployed for cloud-based storage, then data protection and deduplication are enhanced, but system complexity and deployment requirements increase during disaster recovery
Solution Approach 1:
The patent extracts the essential reconstruction information from the proprietary storage process and places it into manifest files that are stored separately. This extraction allows the reconstruction capability to be separated from the proprietary system, reducing deployment complexity while maintaining data protection through the manifest metadata that guides chunk assembly.
Solution Approach 2:
The patent segments the data storage system into separate components: data chunks stored in cloud storage, manifest files containing metadata, and reconstruction logic. This segmentation allows the manifest files to be stored and used independently without requiring the full proprietary system, thereby reducing deployment complexity while maintaining reliability.
3Quantity of substance
If data is stored using deduplication and compression processes, then storage capacity utilization is improved, but data reconstruction becomes more complex without proprietary processes
Solution Approach 1:
The patent performs preliminary action by pre-generating manifest files that contain all necessary metadata about compressed and deduplicated data chunks before reconstruction is needed. These manifest files are prepared in advance and stored with the data, eliminating the need for complex proprietary reconstruction processes during disaster recovery while maintaining storage capacity benefits.
Data Source
AI summary
A multilayer manifest enables any file written to an object store using a proprietary storage process, including large virtual machine backup images, to be recovered without being dependent on the proprietary storage process. Upon synchronizing a file written to an object store in cloud-enabled storage, a multilayer manifest process generates a family of manifest files in a self-contained format that represents all the necessary information required to reconstruct the file. The family of manifest files includes an ancestral record used to initiate retrieval of a file, and multiple layers of manifest files associated with the ancestral record. During retrieval, each of the one or more multilayer manifest files is successively reconstructed and used to securely retrieve the next manifest file until no further manifest files remain in the family. Reconstruction of the last multilayer manifest file results in the recovery of the file for which the manifest files were generated.