Bandwidth Management in Metro Cluster Data Replication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data protection systems face challenges such as system shutdown during backups, limited recovery points, and lengthy data recovery processes, which hinder continuous data protection and minimize downtime.

Innovation Solution

A method for bandwidth management in a metro-cluster data replication environment, involving synchronous and asynchronous replication between sites, with load balancing to optimize data transfer and ensure continuous data availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If synchronous replication is used to minimize downtime during recovery, then data availability is improved, but bandwidth consumption increases

Engineering Contradiction:
Improvedata availabilityVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system dynamically switches between synchronous and asynchronous replication modes based on operational requirements. Synchronous replication is used when data availability is critical (minimizing downtime), while asynchronous replication is used when bandwidth conservation is prioritized. This dynamic adaptation resolves the contradiction by allowing the system to optimize for different parameters at different times.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The replication process is segmented into two distinct modes: synchronous replication for critical data availability scenarios and asynchronous replication for bandwidth-efficient operations. By dividing the replication strategy into separate segments with different characteristics, the system can selectively apply the appropriate mode based on current needs, thereby resolving the bandwidth versus availability contradiction.

Inventive Principle:
Principle #1Segmentation

2Loss of energy

If load balancing is implemented to distribute I/O across sites, then bandwidth usage is optimized, but system complexity increases

Engineering Contradiction:
Improvebandwidth usageVSAvoidsystem complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

Each site in the metro-cluster is designed to perform multiple functions: it can act as a primary site receiving I/O, a secondary site providing backup capacity, and a replication target. This multi-functionality simplifies the overall system architecture by making all sites interchangeable and equally capable, reducing the complexity that would otherwise arise from specialized roles while still enabling effective load balancing.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Loss of energy

If asynchronous replication is used to balance load, then bandwidth consumption is reduced, but data availability and recovery speed decrease

Engineering Contradiction:
Improvebandwidth consumptionVSAvoiddata availability
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The system dynamically adjusts the replication mode based on real-time conditions. When bandwidth is constrained, asynchronous replication is employed to reduce consumption. When data availability becomes critical, the system can switch to synchronous replication or utilize pre-established synchronous replicas, thus dynamically resolving the contradiction between bandwidth usage and data availability.

Inventive Principle:
Principle #15Dynamics

4Adaptability or versatility

If continuous data protection is implemented with journaling, then recovery to any point in time is enabled, but system complexity and processing overhead increase

Engineering Contradiction:
Improverecovery flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system creates complete copies of data at different points in time through synchronous and asynchronous replication to remote sites. These copies serve as restore points that can be utilized for recovery without requiring complex journaling operations. By using physical replicas instead of relying solely on journal entries, the system achieves recovery flexibility while simplifying the overall architecture.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9594822B1Method and apparatus for bandwidth management in a metro cluster environment
Publication Date: 2017.03.14 EMC IP HLDG CO LLC
  • US9594822B1 patent drawing
  • US9594822B1 patent drawing
  • US9594822B1 patent drawing

AI summary

Example embodiments of the present invention provide a method, an apparatus and a computer-program product for bandwidth management in a metro-cluster data replication environment. The method includes receiving an I/O at a first site and replicating the I/O from the first site to a second site by synchronous replication. Load balancing is then determined between the first site and the second site. Respective portions of the I/O then may be replicated from at least one of the first site and the second site to a third site by asynchronous replication according to the load balancing.