Heterogeneous Cloud Data Replication via Target Gateway Node
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data replication methods in cloud environments are costly and complex, especially when dealing with heterogeneous primary computing systems, as they require multiple operating systems, volume managers, and file systems, leading to increased licensing, maintenance, and resource management challenges.
Innovation Solution
A low-cost, heterogeneous method for transforming replicated data involves attaching a target gateway node to a storage device at a secondary site, searching for an identifier to determine the starting location for storing replicated data, and receiving data from a source gateway node at a primary site, allowing for efficient storage across multiple primary computing systems with different configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single recovery computing system supports multiple heterogeneous primary systems, then adaptability and versatility improve, but device complexity and cost increase due to requiring multiple operating systems, volume managers, and file systems
Solution Approach 1:
The patent creates a simplified copy of the primary system's data structure in the recovery environment. Instead of replicating full operating systems and applications, it copies only the essential data blocks and metadata structures, allowing the recovery system to reconstruct primary system data without needing identical software environments.
Solution Approach 2:
The patent introduces an intermediary layer (the recovery computing system with simplified software) that mediates between heterogeneous primary systems and the recovery storage. This intermediary handles data transformation and reconstruction, allowing multiple different primary systems to be supported without each requiring its own complex recovery environment.
2Adaptability or versatility
If multiple operating systems and software components are licensed and maintained for heterogeneous primary systems, then adaptability improves, but loss of substance increases due to licensing costs and maintenance overhead
Solution Approach 1:
The patent employs disposable, simplified software components in the recovery system that do not require expensive long-term licenses. The recovery computing system uses basic, cost-effective software that can be discarded or reset after recovery operations, eliminating the need for costly perpetual licenses of multiple operating systems and volume managers.
Solution Approach 2:
Instead of licensing and maintaining expensive copies of multiple operating systems, the patent copies only the necessary data structures and metadata. This selective copying approach avoids the cost of licensing full operating system suites while still enabling support for heterogeneous primary systems.
3Reliability
If data is replicated with full metadata and structure information, then reliability of data recovery improves, but use of energy and network resources increases during replication
Solution Approach 1:
The patent extracts only the essential data blocks and critical metadata from the primary system, leaving behind non-essential data and redundant structure information. This extraction approach maintains sufficient reliability for recovery while significantly reducing the volume of data that must be transmitted and processed during replication.
Solution Approach 2:
The patent applies partial action by replicating only the necessary portions of data and metadata required for recovery, rather than copying entire file systems and all associated metadata. This partial replication strategy achieves adequate reliability for disaster recovery purposes while minimizing network and processing resource consumption.
Data Source
AI summary
Disclosed are methods and the like that provide for transforming replicated data for consumption in the cloud, for example. Such methods can include attaching a target gateway node at a secondary site to a storage device at the secondary site, searching for an identifier stored in the storage device, and storing replicated data in the replication volume. The identifier is associated with an offset stored in the storage device, and the offset identifies a starting location of a replication volume in the storage device. The replicated data is received by the target gateway node from a source gateway node at a primary site. A starting location is received with the replicated data. The target gateway node stores the replicated data at a first location in the storage volume, and the first location is determined based, at least in part, on the starting location and the first storage location.