Storage Replication Layer Switching for Multiple Schemes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional storage systems face inefficiencies in data management and reliability due to unnecessary write operations and lack of centralized control over storage processes, leading to reduced reliability and increased wear on storage devices.

Innovation Solution

Implementing a direct-mapped flash storage system where higher-level processes, such as the operating system, manage data allocation and storage operations directly without involving lower-level storage controllers, and utilizing non-volatile RAM for quick data buffering and proactive data recovery mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional storage controllers manage data allocation and storage operations, then storage operations can be automated, but unnecessary write operations occur and reliability decreases

Engineering Contradiction:
Improvestorage system reliabilityVSAvoidstorage operation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the data allocation and storage operation management functions from the traditional storage controller and transfers them to the operating system. This separation allows the OS to make intelligent decisions about data placement while storage controllers focus purely on physical storage operations, eliminating unnecessary write operations and improving reliability without sacrificing automation.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary layer where the operating system acts as a mediator between application processes and storage controllers. This intermediary manages the data allocation decisions and coordinates storage operations across multiple controllers, preventing redundant writes while maintaining automated storage management.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If storage controllers independently manage data allocation, then automated storage operations are achieved, but centralized control is lost and reliability decreases

Engineering Contradiction:
Improvedata integrityVSAvoidstorage operation automation
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The patent merges the data allocation management function with the operating system's existing file system and process management capabilities. This integration allows centralized control for data integrity while leveraging the OS's automated decision-making for storage operations, achieving both reliability and automation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The operating system serves multiple functions: it manages data allocation, coordinates storage operations across distributed controllers, ensures data integrity, and maintains automation. This multi-functional approach consolidates control while preserving automated operations through the OS's comprehensive management capabilities.

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

3Reliability

If multiple storage controllers manage data independently, then storage scalability is improved, but coordination overhead increases and reliability decreases

Engineering Contradiction:
Improvestorage consistencyVSAvoidcontroller coordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments storage management into two distinct responsibilities: the operating system handles data allocation decisions and consistency coordination, while storage controllers handle physical data operations. This segmentation simplifies controller coordination by removing coordination overhead from controllers and placing it in the OS, improving reliability without increasing complexity at the controller level.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The operating system receives feedback from storage controllers about data operations and uses this information to coordinate data allocation decisions. This feedback mechanism allows the OS to maintain storage consistency across multiple controllers while controllers focus on their specialized physical operations, reducing coordination complexity.

Inventive Principle:
Principle #23Feedback

4Duration of action of stationary object

If write operations are performed without centralized management, then storage performance is maintained, but redundant writes occur and device lifespan decreases

Engineering Contradiction:
Improvestorage device lifespanVSAvoidstorage write throughput
Core Design Contradiction:
Duration of action of stationary objectVSProductivity

Solution Approach 1:

The operating system performs preliminary action by pre-managing data allocation decisions before write operations occur. It determines optimal data placement and coordinates write operations to avoid redundancy, extending storage device lifespan by preventing unnecessary writes while maintaining storage performance through proactive planning.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements mechanisms to discard redundant write operations that would waste storage cycles and extend device lifespan. The operating system recovers from potential data loss scenarios by coordinating consistent writes across multiple controllers, ensuring data integrity without sacrificing write throughput through intelligent operation management.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS12464043B2Switching between network layers for replication
Publication Date: 2025.11.04 PURE STORAGE INC
  • US12464043B2 patent drawing
  • US12464043B2 patent drawing
  • US12464043B2 patent drawing

AI summary

Supporting multiple replication schemes across distinct network layers, including: replicating, over a first type of network messaging layer, data between a first storage system and a second storage system; selecting a different messaging layer for data replication; and replicating, over a second type of network messaging layer, data between the first storage system and the second storage system.