# US 2026/0086902 A1 · File server clone refresh of file systems and volumes

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

- Number: US 2026/0086902 A1
- Document ID: US20260086902A1
- Status: Published application
- Kind: A1
- Application number: 18/894,310
- Filed: 2024-09-24
- Published: 2026-03-26
- Earliest claimed: 2024-09-24
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Maneesh Singhal; Rvsmp Kumar; Suhas Bk; Adithi Gurunath
- Web page: https://patentgrep.com/patent/US20260086902A1

## CPC

- G06F 11/1461: {Backup scheduling policy}
- G06F 11/1662: {the resynchronized component or unit being a persistent storage device (re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008)}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1464: {for networked environments}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 2201/80: Database-specific techniques
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

File server clone refresh of file systems and volumes (e.g., using a computerized tool), is enabled. For example, a system can comprise at least one processor, and at least one memory that stores executable instructions that, when executed by the at least one processor, facilitate performance of operations. The operations can comprise, in response to a determination that a first file server is to be cloned to a second file server, determining changed files between the first file server and the second file server, and determining configuration changes, applicable to the first file server, relative to a prior cloning of the first file server, in response to determining the changed files, applying changes corresponding to the changed files to the second file server, and in response to determining the configuration changes, applying the configuration changes to the second file server.

## Claims

### Claim 1

A system, comprising:
at least one processor; and
at least one memory that stores executable instructions that, when executed by the at least one processor, facilitate performance of operations, comprising:
in response to a determination that a first file server is to be cloned to a second file server, determining changed files between the first file server and the second file server, and determining configuration changes, applicable to the first file server, relative to a prior cloning of the first file server, wherein the configuration changes comprise lightweight directory access protocol (LDAP) configuration changes;
in response to determining the changed files, applying changes corresponding to the changed files to the second file server; and
in response to determining the configuration changes, applying the configuration changes to the second file server.

### Claim 2 (depends on 1)

The system of claim 1, wherein the determination that the first file server is to be cloned to the second file server comprises a determination that the first file server is to be identically cloned to the second file server, and wherein the applying of the configuration changes to the second file server comprises replacing a second configuration of the second file server with a first configuration of the first file server.

### Claim 3 (depends on 1)

The system of claim 1, wherein the determination that the first file server is to be cloned to the second file server comprises a determination that the first file server is to be non-identically cloned to the second file server, and wherein the applying of the configuration changes to the second file server comprises merging a second configuration of the second file server with a first configuration of the first file server.

### Claim 4 (depends on 1)

The system of claim 1, wherein the configuration changes further comprise server message block configuration changes, network file system configuration changes, or share or export mapping configuration changes.

### Claim 5 (depends on 1)

The system of claim 1, wherein the second file server comprises a cloned version of the first file server.

### Claim 6 (depends on 1)

The system of claim 1, wherein the operations further comprise:
generating a snapshot of the second file server, wherein the second file server is restored from the snapshot in response to a determination that the applying of the changes corresponding to the changed files to the second file server or the applying of the configuration changes to the second file server resulted in an error.

### Claim 7 (depends on 6)

The system of claim 6, wherein the error comprises a complete failure of the second file server.

### Claim 8 (depends on 1)

The system of claim 1, wherein the configuration changes comprise client access configuration changes.

### Claim 9 (depends on 1)

The system of claim 1, wherein the second file server comprises multiple copies from the first file server.

### Claim 10 (depends on 1)

The system of claim 1, wherein the second file server comprises an immutable golden copy of the first file server.

### Claim 11

A non-transitory machine-readable medium, comprising executable instructions that, when executed by at least one processor, facilitate performance of operations, comprising:
in response to a determination that a first network attached storage server is to be copied to a second network attached storage server, determining changed files between the first network attached storage server and the second network attached storage server, and determining configuration changes, applicable to the first network attached storage server, relative to a prior copying of the first network attached storage server, wherein the configuration changes comprise lightweight directory access protocol (LDAP) configuration changes;
in response to determining the changed files, applying changes corresponding to the changed files to the second network attached storage server; and
in response to determining the configuration changes, applying the configuration changes to the second network attached storage server.

### Claim 12 (depends on 11)

The non-transitory machine-readable medium of claim 11, wherein the determination that the first network attached storage server is to be copied to the second network attached storage server comprises a determination that the first network attached storage server is to be identically copied to the second network attached storage server, and wherein the applying of the configuration changes to the second network attached storage server comprises replacing a second configuration of the second network attached storage server with a first configuration of the first network attached storage server.

### Claim 13 (depends on 11)

The non-transitory machine-readable medium of claim 11, wherein the determination that the first network attached storage server is to be copied to the second network attached storage server comprises a determination that the first network attached storage server is to be non-identically copied to the second network attached storage server, and wherein the applying of the configuration changes to the second network attached storage server comprises merging a second configuration of the second network attached storage server with a first configuration of the first network attached storage server.

### Claim 14 (depends on 11)

The non-transitory machine-readable medium of claim 11, wherein the configuration changes further comprise at least one of lightweight server message block configuration changes, network file system configuration changes, or share or export mapping configuration changes.

### Claim 15 (depends on 11)

The non-transitory machine-readable medium of claim 11, wherein the second network attached storage server comprises an exact copy of the first network attached storage server.

### Claim 16

A method, comprising:
in response to a determination that a first file server is to be cloned to a second file server, determining, by a system comprising a processor, changed files between the first file server and the second file server, and determining, by the system, configuration changes, applicable to the first file server, relative to a prior cloning of the first file server, wherein the configuration changes comprise lightweight directory access protocol (LDAP) configuration changes;
in response to determining the changed files, applying, by the system, changes corresponding to the changed files to the second file server; and
in response to determining the configuration changes, applying, by the system, the configuration changes to the second file server.

### Claim 17 (depends on 16)

The method of claim 16, further comprising:
generating, by the system, a snapshot of the second file server, wherein the second file server is restored from the snapshot in response to a determination that the applying of the changes corresponding to the changed files to the second file server or the applying of the configuration changes to the second file server resulted in an error.

### Claim 18 (depends on 17)

The method of claim 17, wherein the error comprises a partial failure of the second file server.

### Claim 19 (depends on 16)

The method of claim 16, wherein the configuration changes comprise client access configuration changes.

### Claim 20 (depends on 16)

The method of claim 16, wherein the second file server comprises at least two copies of the first file server.
