Cross-Namespace File Cloning With Parent-Child Relationship Repair

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Maintaining file relationships between files becomes challenging when cloning across different namespaces in deduplication filesystems, leading to inefficiencies in replication and potential violations of service level agreements (SLAs).

Innovation Solution

Implementing a method to opportunistically set or repair file relationships by using implicit and explicit methods to update extended attributes, ensuring parent-child relationships are maintained across namespaces during cloning operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If file cloning is performed across different namespaces using fastcopy, then cloning speed and efficiency are improved, but file relationships between parent and child files are lost or broken

Engineering Contradiction:
Improvecloning speedVSAvoidfile relationship integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by setting extended attributes on the source file before cloning, and then automatically applying these attributes to the cloned file. This preliminary setup ensures that file relationship information is preserved during the fastcopy operation, resolving the contradiction between cloning speed and relationship integrity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Extended attributes serve as an intermediary mechanism that carries file relationship information across the namespace boundary. The system uses these attributes to encode parent-child file relationships, allowing the fastcopy operation to maintain relationship integrity without sacrificing cloning performance.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If traditional copying methods are used to maintain file relationships, then relationship integrity is preserved, but replication time and resource consumption increase

Engineering Contradiction:
Improvefile relationship integrityVSAvoidreplication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Instead of copying actual file data, the system copies only the extended attributes containing relationship information. This attribute-based copying approach maintains file relationship integrity while avoiding the time and resource costs of traditional data copying, thus resolving the contradiction between reliability and time loss.

Inventive Principle:
Principle #26Copying

3Reliability

If extended attributes are manually updated after cloning, then file relationships can be maintained, but operational complexity and potential for errors increase

Engineering Contradiction:
Improvefile relationship integrityVSAvoidoperational simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements self-service by automatically updating extended attributes on cloned files based on the source file's attributes. This automation eliminates manual intervention, reducing operational complexity and potential for errors while maintaining file relationship integrity, thus resolving the contradiction between reliability and ease of operation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12619504B2Opportunistic setting of relationships when cloning files across namespaces in a deduplication filesystem
Publication Date: 2026.05.05 DELL PROD LP
  • US12619504B2 patent drawing
  • US12619504B2 patent drawing
  • US12619504B2 patent drawing

AI summary

Enhancing data replication performance optimization by maintaining parent-child file relationships when cloning an entire or portion of a first namespace to a second namespace for backups cloned across namespaces in a deduplication filesystem. The file copies may be made by either virtual synthetic (VS) copies that keep a one-way relationship between parent-child files or fast copy overwrite (FCOW) copies that keep a two-way parent-child relationship. Extended attributes are used as metadata for the files to indicate a path or recipe to generate the child file. The extended attributes for the cloned parent and child files are fixed to reference the second namespace so that a relative relationship between the parent and child files is maintained after cloning to the second namespace.