Cloud Data Movement Engine Copy Services Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional cloud data movement engines are incompatible with disaster recovery and high availability solutions due to bypassing integration with copy services, leading to inefficiencies in data storage and retrieval processes.
Innovation Solution
The implementation of a cloud data movement engine that integrates with copy services, allowing for the emulation of host read and write operations, enabling seamless interaction with track services to process store and restore commands, and supporting various copy services capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If the cloud data movement engine uses a device adapter directly for store commands and restore commands, then data transfer speed is improved, but integration with copy services is lost
Solution Approach 1:
The patent introduces track services as an intermediary component between the cloud data movement engine and the device adapter. This mediator enables the system to maintain direct data transfer capabilities while also providing integration with copy services for disaster recovery and high availability solutions. The track services layer handles the coordination between direct cloud storage access and copy service requirements.
2Productivity
If the cloud data movement engine bypasses the cache for data recall, then data access efficiency is improved, but cache consistency and metadata updates become problematic
Solution Approach 1:
The track services act as an intermediary that manages data flow between cloud storage and the cache system. When data is recalled from object storage, track services coordinates the transfer through the cache, ensuring that cache consistency is maintained and metadata is appropriately updated. This resolves the conflict between efficient direct access and cache reliability.
3Adaptability or versatility
If the cloud data movement engine integrates with copy services, then compatibility with disaster recovery solutions is improved, but system complexity increases
Solution Approach 1:
The patent segments the system into distinct functional layers: the cloud data movement engine for direct cloud storage access, the track services for coordination and copy service integration, and the device adapter for physical disk drive management. This segmentation allows each component to have a specific responsibility, reducing overall system complexity while maintaining compatibility with disaster recovery solutions.
Data Source
AI summary
Provided are techniques for cloud based store and restore with copy services. A store command to transfer data from one or more tracks of a volume to cloud storage is received. With track services, data for the one or more tracks in the volume is retrieved by emulating a host read. With a cloud data movement engine, the data for the one or more tracks is converted to data for one or more objects. With the cloud data movement engine, the one or more objects are stored in the cloud storage.