Selective Data Replication for DRaaS Cost Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Disaster-Recovery-as-a-Service (DRaaS) systems face challenges in optimizing data transfer and storage costs, particularly in terms of network bandwidth and storage footprint, especially when serving numerous clients with large volumes of data, leading to resource bottlenecks at the target site.

Innovation Solution

The implementation of an optimized DRaaS system that uses selective data transfer by analyzing client data and applying an essentialness assessment to determine which data components to replicate, along with policy configuration to minimize costs, employing techniques like deduplication, compression, and optimized network protocols, and providing value-added services such as virus scanning and anomaly detection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all client data is replicated to the target site for disaster recovery, then data protection reliability is improved, but network bandwidth consumption and storage footprint increase significantly

Engineering Contradiction:
Improvedata protection reliabilityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and replicates only the essential and changed data components to the target site, rather than replicating all client data. The essentialness assessment module identifies which data components are critical for disaster recovery, and only those selected components are transferred, thereby reducing network bandwidth consumption while maintaining data protection reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies different replication strategies to different data components based on their essentialness and change status. Critical data components that have changed are replicated with high priority, while non-essential or unchanged components are not replicated, creating a localized quality approach where replication intensity varies by data component importance.

Inventive Principle:
Principle #3Local quality

2Reliability

If all client data is stored at the target site, then data protection reliability is improved, but storage footprint and cost increase

Engineering Contradiction:
Improvedata protection reliabilityVSAvoidstorage footprint
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential data components needed for disaster recovery and stores them at the target site. The essentialness assessment module determines which data components are critical, and only those are selected for storage, thereby reducing storage footprint while maintaining data protection reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by storing only a portion of the client data - specifically, the essential and changed data components - rather than storing all data. This partial replication approach reduces storage footprint at the target site while still providing adequate disaster recovery protection.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If data replication is performed continuously to ensure data protection, then reliability is improved, but network bandwidth consumption increases

Engineering Contradiction:
Improvedata protection reliabilityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements periodic action by monitoring data components for changes and replicating only when changes occur, rather than performing continuous replication. The change detection mechanism triggers replication events periodically based on actual data changes, reducing network bandwidth consumption while maintaining data protection reliability through event-driven updates.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent maintains continuity of useful action by continuously monitoring data components for changes and immediately replicating essential changed components to the target site. This continuous monitoring and selective replication ensures data protection reliability is maintained without the overhead of continuous full-data replication, optimizing network bandwidth usage.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS11561869B2Optimized disaster-recovery-as-a-service system
Publication Date: 2023.01.24 KYNDRYL INC
  • US11561869B2 patent drawing
  • US11561869B2 patent drawing
  • US11561869B2 patent drawing

AI summary

Methods, computer program products, and systems are presented. The methods include, for instance: analyzing a dataset associated with a service provided by the data protection service provider in order to determine a policy for when and how to replicate the respective components of the dataset corresponding to the service from a source site to a target site, such that the target site may perform the service with a minimum cost.