Replication Session Allocation by RPO and Device Headroom

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data synchronization technologies fail to consider performance and load conditions of devices in remote clusters, leading to uneven distribution of replication sessions, which can cause device overload, prolonged downtime, and instability during failovers.

Innovation Solution

Select a target device based on recovery point objective (RPO) and performance headroom of replication sessions, distributing sessions across multiple devices to balance load and ensure even distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If replication sessions are distributed across multiple devices using preset rules, then device resource utilization improves, but load balancing and RPO achievement deteriorate due to ignoring performance headroom and existing session loads

Engineering Contradiction:

Improvedevice resource utilizationVSAvoidRPO achievement

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system continuously monitors performance headroom and existing replication session loads on remote devices, using this feedback to dynamically adjust session distribution decisions. This ensures that new sessions are allocated to devices that can handle them without compromising RPO requirements, resolving the contradiction between resource utilization and reliability.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The session distribution mechanism transitions from static preset rules to dynamic allocation based on real-time device conditions. The system adapts to changing performance headroom and load conditions, optimizing both resource utilization and RPO achievement by making allocation decisions responsive to current system state.

Inventive Principle:

Principle #15Dynamics

2Productivity

If multiple replication sessions are concentrated on single devices, then device resource utilization improves, but device overload and system stability deteriorate during failovers

Engineering Contradiction:

Improvedevice resource utilizationVSAvoidsystem stability

Core Design Contradiction:

ProductivityVSStability of the object's composition

Solution Approach 1:

The system applies different allocation strategies to different devices based on their local conditions such as performance headroom and existing load. Rather than uniform distribution, each device receives sessions appropriate to its capabilities, preventing overload on any single device while maintaining high overall resource utilization.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system changes the allocation parameters dynamically based on device performance metrics. When a device approaches overload thresholds, the system adjusts allocation parameters to redirect sessions to other devices, maintaining system stability while preserving efficient resource utilization during normal operation.

Inventive Principle:

Principle #35Parameter changes

3Speed

If replication sessions are allocated without considering performance headroom, then allocation speed improves, but RPO miss rate increases due to insufficient resources

Engineering Contradiction:

Improveallocation speedVSAvoidRPO achievement

Core Design Contradiction:

SpeedVSReliability

Solution Approach 1:

The system performs preliminary assessment of performance headroom and existing loads before allocating replication sessions. By evaluating device capacity in advance, the system ensures that allocated sessions can be handled without compromising RPO, achieving both fast allocation and high reliability through proactive resource verification.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20260003750A1Method, device, and computer program product for synchronizing data

Publication Date: 2026.01.01 DELL PROD LP

AI summary

Techniques for synchronizing data involve determining, in response to that a replication session in a source cluster is initiated, a recovery point objective (RPO) of the replication session and a plurality of parameters of each device in a plurality of devices in a remote cluster. The plurality of parameters include at least performance headroom and a recovery point objective of a resident replication session. Such techniques further involve selecting a target device from the plurality of devices based on the recovery point objective of the replication session and the plurality of parameters. Such techniques further involve synchronizing data associated with the replication session from the source cluster to the target device in the remote cluster. Accordingly, replication sessions can be evenly distributed across devices, thereby improving resource utilization and data synchronization efficiency, preventing depletion of device utilization, reducing RPO bias, and strengthening the protection for disaster recovery data.