# US 2026/0037389 A1 · Opportunistic setting of relationships when cloning files across namespaces in a deduplication filesystem

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0037389 A1
- Document ID: US20260037389A1
- Status: Published application
- Kind: A1
- Application number: 18/789,696
- Filed: 2024-07-31
- Published: 2026-02-05
- Earliest claimed: 2024-07-31
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Nitin Madan; Salil Dangi; Alok Katiyar
- Web page: https://patentgrep.com/patent/US20260037389A1

## CPC

- G06F 11/1466: {to make the backup process non-disruptive}
- G06F 11/1435: {using file system or storage system metadata}
- G06F 11/1448: {Management of the data involved in backup or backup restore}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1453: {using de-duplication of the data}
- G06F 11/1458: {Management of the backup or restore process}
- G06F 11/1464: {for networked environments}
- G06F 11/1469: {Backup restoration techniques}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 16/137: {Hash-based (content-based indexing of textual data G06F16/31)}
- G06F 16/1748: {De-duplication implemented within the file system, e.g. based on file segments (de-duplication techniques in storage systems for the management of data blocks G06F3/0641)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

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.

## Claims

### Claim 1

A computer-implemented method of maintaining parent-child file relationships when cloning an entire first namespace to a second namespace, comprising:
fastcopying a parent file to a child file within the first namespace, wherein the child file has target extended attributes indicating a path relationship to the parent file;
cloning the first namespace to the second namespace including the parent file and child file to generate a cloned parent file and cloned child file in the second namespace;
finding the path relationship between the cloned parent file and cloned child file in the second namespace; and
amending the found path relationship in the target extended attributes of the cloned child file to reference the parent file in the second namespace.

### Claim 2 (depends on 1)

The method of claim 1 wherein the fastcopying comprises making a virtual synthetic (VS) copy of the parent file to generate the child file, and wherein the target extended attributes comprise a synthetic recipe consisting of metadata specifying how to generate the child file.

### Claim 3 (depends on 1)

The method of claim 1 wherein the fastcopying comprises making a fastcopy overwrite (FCOW) copy of the parent file to generate the child file, and wherein the target extended attributes consist of metadata specifying how to generate the child file.

### Claim 4 (depends on 3)

The method of claim 3 wherein the parent file has base extended attributes indicating a path relationship to the child file, the method further comprising amending the path relationship in the parent extended attributes of the cloned parent file to reference the second namespace for the cloned parent file in the second namespace.

### Claim 5 (depends on 1)

The method of claim 1 wherein the cloning comprises a namespace fastcopy operation.

### Claim 6 (depends on 5)

The method of claim 5 further comprising cloning each file in the first namespace to the second namespace and fixing the respective extended attributes for each pair of parent and child copied files as new inodes are created in the second namespace for corresponding cloned parent and child files.

### Claim 7 (depends on 5)

The method of claim 5 wherein the amending maintains an original relative file relationship between the parent and child files in the second namespace to leverage optimizations provided by the copying step with respect to subsequent replication or differencing operations.

### Claim 8 (depends on 7)

The method of claim 7 wherein the replication or differencing operations are performed by backup software in a deduplication backup system comprising a data storage server running a Data Domain File System (DDFS).

### Claim 9 (depends on 8)

The method of claim 8 wherein files of the deduplication backup system are stored in a Merkle tree structure with content data stored in a bottom level of the tree and indexed by fingerprints, and further wherein the copying step copies metadata of the parent file comprising inode information and a reference to the file L6 fingerprint in a first Merkle tree to a second directory for child file.

### Claim 10 (depends on 9)

The method of claim 9 wherein the amending step comprises fixing metadata of at least one of the target extended attributes or base extended attributes.

### Claim 11

A computer-implemented method of maintaining parent-child file relationships when cloning a portion of a first namespace to a second namespace, comprising:
virtual synthetic (VS) copying a parent file to a child file within the first namespace wherein the first namespace contains additional files not copied to the second namespace, wherein the child file has target extended attributes indicating a path relationship to the parent file;
cloning the first namespace to the second namespace including the parent file and child file to generate a cloned parent file and cloned child file in the second namespace;
verifying that each of the parent file and child file are identical to the respective cloned parent file and cloned child file;
finding that the path relationship between the cloned parent file and cloned child file in the second namespace; and
amending the found path relationship in the target extended attributes of the cloned child file to reference the second namespace for the cloned child file in the second namespace.

### Claim 12 (depends on 11)

The method of claim 11 wherein the target extended attributes comprise a synthetic recipe consisting of metadata specifying how to generate the child file.

### Claim 13 (depends on 12)

The method of claim 12 wherein the cloning comprises a namespace fastcopy operation.

### Claim 14 (depends on 12)

The method of claim 12 wherein the amending comprises modifying metadata of the target extended attributes to maintain an original relative file relationship between the parent and child files in the second namespace to leverage optimizations provided by the copying step with respect to subsequent replication or differencing operations.

### Claim 15 (depends on 11)

The method of claim 11 wherein the verifying step comprises comparing hash values of each pair of parent and cloned parent files, and child clone child files to one another.

### Claim 16

A computer-implemented method of maintaining parent-child file relationships when cloning a portion of a first namespace to a second namespace, comprising:
fast copy overwrite (FCOW) copying a parent file to a child file within the first namespace, wherein the child file has target extended attributes indicating a path relationship to the parent file, and the parent file has base extended attributes indicating a path relationship to the child file;
cloning the first namespace to the second namespace including the parent file and child file to generate a cloned parent file and cloned child file in the second namespace;
verifying that each of the parent file and child file are identical to the respective cloned parent file and cloned child file;
finding that the path relationship between the cloned parent file and cloned child file in the second namespace;
first amending the found path relationship in the target extended attributes of the cloned parent file to reference the second namespace for the cloned child file in the second namespace; and
second amending the path relationship in the parent extended attributes of the cloned parent file to reference the parent file in the second namespace.

### Claim 17 (depends on 16)

The method of claim 16 wherein the target extended attributes consist of metadata specifying how to generate the child file.

### Claim 18 (depends on 16)

The method of claim 16 wherein the cloning comprises a namespace fastcopy operation.

### Claim 19 (depends on 18)

The method of claim 18 wherein the amending comprises modifying metadata of the target extended attributes to maintain an original relative file relationship between the parent and child files in the second namespace to leverage optimizations provided by the copying step with respect to subsequent replication or differencing operations.

### Claim 20 (depends on 16)

The method of claim 16 wherein the verifying step comprises comparing hash values of each pair of parent and cloned parent files to one another.
