Policy-Based Mtree Replication for Online Backup Appliance Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data protection systems face downtime issues during Mtree replication, requiring offline upgrades of backup appliances, which violate service level agreements due to lengthy downtimes and inefficiencies in managing large data volumes.

Innovation Solution

Implementing a policy-based data migration process using Mtree replication that allows for automated and monitored online migration, enabling the backup application server to control Mtree replication configuration and leverage both Managed File Replication (MFR) and Mtree replication based on customer data movement requirements, thus avoiding offline servicing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Mtree replication is used for data migration during backup appliance upgrades, then data protection capability is maintained, but the data protection application must be taken offline resulting in service downtime

Engineering Contradiction:
Improvedata protection capabilityVSAvoidservice downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system segments the data migration process into distinct phases: initial replication setup, data synchronization, and switchover. The data protection application is divided into multiple instances or components that can operate independently, allowing one instance to be migrated while others continue servicing requests. This segmentation enables continuous operation during migration by distributing the workload across multiple processing units.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-configuring the target backup appliance and establishing replication relationships before the actual migration needs to occur. Data is pre-synchronized and validated in advance, so when the migration is triggered, the system can quickly switch over with minimal downtime. The replication infrastructure is prepared beforehand, eliminating the need for lengthy migration operations during the actual switchover.

Inventive Principle:
Principle #10Preliminary action

2Ease of manufacture

If manual reconfiguration is performed during Mtree replication migration, then migration can be completed, but operational complexity and time required increase significantly

Engineering Contradiction:
Improvemigration completionVSAvoidoperational complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The system implements self-service capabilities through automated configuration management. The data protection application automatically detects the migration state, configures necessary parameters, and updates replication settings without requiring manual intervention. Scripts and automation frameworks handle the reconfiguration tasks, reducing operational complexity from hours of manual work to automated processes that execute with minimal human oversight.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system incorporates feedback mechanisms that continuously monitor the migration progress and system state. Automated feedback loops detect when migration milestones are reached and trigger appropriate configuration changes. The system receives status information from the replication process and automatically adjusts settings, eliminating the need for manual reconfiguration and reducing operational complexity through closed-loop control.

Inventive Principle:
Principle #23Feedback

3Reliability

If large volumes of data are migrated during backup appliance upgrades, then complete data protection coverage is achieved, but migration time and service disruption increase

Engineering Contradiction:
Improvedata protection coverageVSAvoidmigration speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system maintains continuity of useful action by implementing incremental replication that continues data protection operations throughout the migration process. Instead of stopping data protection to perform migration, the system continues to protect data on the source appliance while simultaneously replicating to the target. This parallel operation ensures data protection coverage is maintained at full capacity while migration progresses, eliminating the trade-off between coverage and migration speed.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system employs periodic action through scheduled replication cycles and phased migration approaches. Data is migrated in periodic batches rather than attempting to transfer all data at once, allowing the system to maintain data protection coverage while progressively migrating large volumes. The periodic synchronization cycles ensure data consistency is maintained throughout the migration, achieving complete coverage without requiring the entire migration to complete before protection begins.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS11281637B2System and method for policy based migration using Mtree replication with data protection applications
Publication Date: 2022.03.22 EMC IP HLDG CO LLC
  • US11281637B2 patent drawing
  • US11281637B2 patent drawing
  • US11281637B2 patent drawing

AI summary

Embodiments are described for performing online migration of backup appliances in automated and monitored process from a backup application. The data migration process uses certain Mtree replication methods. It is configured to provide capabilities a backup application server would control, such as Mtree replication configuration from the backup application, a policy driven approach for data center migration, and accommodation of specific customer data recovery needs, and providing a choice to end users for leveraging both Managed File Replication and Mtree replication based on the customer data movement requirements. Such a solution is configured to be generic and applicable to any data protection applications with a policy driven implementation that leverages certain integration points of the system.