Layered Device Object Stack for Data Replication Consistency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In data storage environments, existing technologies face challenges in maintaining data consistency during replication, leading to potential data corruption and unsuccessful restoration processes.

Innovation Solution

The system and method involve creating a stack of layered device objects, with specific device drivers intercepting and processing Input/Output requests to ensure that data copies remain consistent with production data by strategically inserting multiple device objects within the device stack, allowing for transparent and flexible data replication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data replication is performed using existing technologies, then data copying functionality is achieved, but data consistency between production data and data copy cannot be maintained, leading to potential data corruption

Engineering Contradiction:

Improvedata consistencyVSAvoiddevice object stack structure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The device object is segmented into multiple layered components (first device object, second device object, third device object) that operate independently but cooperatively. Each layer handles specific aspects of IO request processing, allowing complex consistency maintenance functionality to be broken down into manageable, specialized segments that can be inserted into the existing device object stack without replacing the entire structure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The solution implements a nested structure where device objects are embedded within the existing device object stack. The first device object is inserted above the second device object, which is inserted above the third device object, creating a hierarchical nesting pattern. This allows the consistency maintenance mechanism to be integrated within the existing storage system architecture without external additions.

Inventive Principle:

Principle #7Nested doll (Nesting)

2Reliability

If multiple device objects are inserted to maintain data consistency, then data replication reliability is improved, but the complexity of the device structure increases

Engineering Contradiction:

Improvedata consistencyVSAvoidlayered device object stack

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The layered device objects are designed to perform multiple functions within a single structural framework. The same device object stack structure handles both standard IO requests and consistency maintenance operations, eliminating the need for separate dedicated structures. Each device object layer can process various types of requests (read, write, replicate) while maintaining data consistency, providing universal functionality across different operation types.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Reliability

If device objects intercept and process IO requests, then data consistency is maintained, but processing time and system overhead increase

Engineering Contradiction:

Improvedata consistencyVSAvoidIO request processing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by inserting the device object stack structure and establishing the layered architecture in advance, before actual data replication operations begin. This preliminary setup allows the system to automatically handle consistency maintenance during normal operation without requiring real-time complex decision-making, reducing processing time during actual data operations.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The device object stack implements self-service mechanisms where each layer automatically processes and forwards IO requests without requiring external intervention or complex coordination. The layered structure autonomously maintains data consistency through its inherent design, where the first device object receives requests, passes them to the second, which passes to the third, creating a self-managing processing chain that minimizes overhead.

Inventive Principle:

Principle #25Self-service

4Device complexity

If a simple device object structure is used, then system complexity is reduced, but the ability to maintain data consistency during replication is compromised

Engineering Contradiction:

Improvedevice object structureVSAvoiddata consistency

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The solution applies local quality by making the device object stack structure localized to specific consistency maintenance needs rather than applying a complex structure system-wide. The layered device objects are inserted only where data consistency is required, allowing simple structures to be used elsewhere in the system. Each layer of the device object stack provides specialized consistency functionality only where needed, rather than imposing uniform complexity across the entire storage system.

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS7627873B1System and method for handling device objects in a data storage environment for maintaining consistency during data replication

Publication Date: 2009.12.01 EMC IP HLDG CO LLC

AI summary

A system and method related to maintaining consistency of replicated data in a data storage environment. The system handles Input/Output (IO)-Requests in a data storage environment having a server and production data stored on a data storage volume on a data storage system. A copy of the production data is stored on another data storage volume of a second data storage system, wherein IO-Requests to update production data are handled so that the data copy is consistent with the production data after processing the IO-Request.