Object File System Snapshot Tree for Hybrid Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Hybrid storage systems combining primary storage and cloud computing face compatibility issues, leading to loss of robust functionalities provided by primary storage systems when integrated with cloud computing environments, resulting in cost inefficiencies and scalability limitations.
Innovation Solution
An object file system is implemented to store and manage data within an object store, utilizing a snapshot file system tree structure that allows for independent snapshots, deduplication, and version neutrality, enabling cost-effective storage and scalable access while maintaining data integrity and consistency across snapshots.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If primary storage systems are used to provide robust data storage and management features, then data replication, encryption, and backup functionality are improved, but cost and scalability are worsened
Solution Approach 1:
The system segments storage functionality into two distinct parts: primary storage systems provide robust data management features (replication, encryption, backup), while cloud computing environments provide scalable and cost-effective storage capacity. This segmentation allows each component to excel at its specialized function without the compromises of a hybrid approach.
Solution Approach 2:
A data connector component is introduced as an intermediary between primary storage systems and cloud computing environments. This mediator enables seamless integration and data transfer, allowing the system to leverage both the robust functionality of primary storage and the scalability of cloud storage while maintaining data integrity and consistency across the hybrid architecture.
2Adaptability or versatility
If primary storage systems are integrated with cloud computing environments, then scalability and cost savings are improved, but robust functionalities are worsened
Solution Approach 1:
The data connector component serves as a mediator that bridges primary storage systems and cloud computing environments, enabling the system to access cloud-based scalable storage while preserving the robust data management functionalities of primary storage systems through coordinated operations and data synchronization.
Solution Approach 2:
The system creates a universal storage architecture that combines the strengths of both primary storage systems (robust data management) and cloud computing environments (scalability and cost-effectiveness). The data connector enables the hybrid system to perform multiple functions including data replication, encryption, backup, and scalable storage access simultaneously.
3Adaptability or versatility
If data is stored in cloud computing environments, then scalability and cost savings are improved, but loss of robust functionalities from primary storage systems occurs
Solution Approach 1:
The data connector component acts as an intermediary that extends primary storage system functionalities to cloud-based data. It enables operations such as replication, deduplication, encryption, and backup to be performed on data stored in cloud computing environments, thereby preserving robust data management capabilities while leveraging cloud scalability and cost-effectiveness.
Solution Approach 2:
The system uses copying mechanisms to replicate data between primary storage systems and cloud computing environments. The data connector enables creation and management of data copies, allowing robust functionalities like backup and replication to be implemented in the cloud-based architecture while maintaining data integrity and enabling scalable storage.
Data Source
AI summary
Techniques are provided for on-demand creation and/or utilization of containers and/or serverless threads for hosting data connector components. The data connector components can be used to perform integrity checking, anomaly detection, and file system metadata analysis associated with objects stored within an object store. The data connector components may be configured to execute machine learning functionality to perform operations and tasks. The data connector components can perform full scans or incremental scans. The data connector components may be stateless, and thus may be offlined, upgraded, onlined, and/or have tasks transferred between data connector components. Results of operations performed by the data connector components upon base objects may be stored within sibling objects.


