NAS Server Cloning via LUN Duplication and Metadata Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current NAS server management solutions are cumbersome and error-prone, especially for large systems with hundreds of NAS servers, as they require individual file systems to be snapped and exported, leading to inefficiencies and increased complexity.

Innovation Solution

The method involves NAS server cloning, where a clone NAS server is created by cloning the set of LUNs and configuring new network addresses and file system identifiers, allowing the clone to operate independently and evolve independently, with no duplication of non-modified file system pieces, thus enabling fast and efficient cloning operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If individual file systems are snapped and exported for each NAS server, then data backup and disaster recovery can be achieved, but the management complexity and time required increase significantly for large systems with hundreds of NAS servers

Engineering Contradiction:
Improvedisaster recovery capabilityVSAvoidtime to snap and export file systems
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent merges the management of multiple individual file systems into a single NAS server-level cloning operation. Instead of snapping and exporting each file system separately, the system clones the entire NAS server including all its file systems as one unit, dramatically reducing the time and complexity for disaster recovery operations in large-scale environments

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements a copying mechanism that creates a complete clone of a source NAS server including all file systems, configurations, and data. This clone can be rapidly deployed for disaster recovery testing or as a standby system, eliminating the need to manually snap and export each file system individually

Inventive Principle:
Principle #26Copying

2Reliability

If individual file systems are snapped and exported for each NAS server, then data backup can be achieved, but the operational complexity and error probability increase for large systems

Engineering Contradiction:
Improvedata backup integrityVSAvoidmanagement complexity of file systems
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines the backup operation at the NAS server level rather than the individual file system level. The cloning process automatically handles all file systems within a NAS server as a unified operation, reducing management complexity and minimizing human error in large-scale backup operations

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The NAS server cloning mechanism automatically manages the backup process including identifying all file systems, creating appropriate clones, and handling metadata updates. This self-service approach eliminates the need for manual intervention in complex multi-file-system backup scenarios, reducing operational complexity

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If complete duplication of file systems is performed for cloning, then independent operation of clone NAS server is achieved, but data storage space is wasted due to duplication of non-modified pieces

Engineering Contradiction:
Improveindependent operation capabilityVSAvoiddata storage space
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent implements a nested structure where clone file systems share underlying storage blocks with source file systems when data is identical. The clone NAS server maintains independence through metadata and mapping structures that reference shared storage resources, allowing space-efficient cloning while preserving independent operation capability

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The system applies local quality by allowing different levels of duplication: highly redundant for modified data blocks, and shared for unchanged data blocks. This enables the clone to operate independently while minimizing storage waste by duplicating only the necessary portions of file systems

Inventive Principle:
Principle #3Local quality

4Ease of operation

If manual tracking of individual file systems is required, then precise control over each file system is achieved, but the burden becomes overwhelming and error-prone for large systems

Engineering Contradiction:
Improvecontrol over file systemsVSAvoidtime to manage file systems
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The NAS server cloning mechanism automatically discovers, tracks, and manages all file systems within a NAS server without requiring manual intervention. The system self-services the entire cloning process including identifying file system boundaries, creating appropriate clones, and updating metadata, dramatically reducing the time and effort required for NAS server replication

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10498821B1Managing NAS server cloning in network attached storage (NAS) cluster
Publication Date: 2019.12.03 EMC IP HLDG CO LLC
  • US10498821B1 patent drawing
  • US10498821B1 patent drawing
  • US10498821B1 patent drawing

AI summary

A technique for managing data storage provides multiple physical computing machines and block storage arranged in a NAS (network attached storage) cluster. The physical computing machines run NAS servers, with each NAS server including an FSDB (file system database) that identifies a set of file systems that belong to the NAS server. LUNs (Logical UNits) in the block storage provide backing store for the set of file systems of each NAS server. The NAS cluster performs a NAS server cloning operation in which an existing source NAS server is cloned in its entirety to create a separate clone NAS server, the operation automatically cloning all the separate file systems of the source NAS server and related metadata without a need for user involvement on a per-filesystem basis.