# US 2026/0030359 A1 · Systems and methods for managing data storage cluster synchronization

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

- Number: US 2026/0030359 A1
- Document ID: US20260030359A1
- Status: Published application
- Kind: A1
- Application number: 19/294,514
- Filed: 2025-08-08
- Published: 2026-01-29
- Earliest claimed: 2019-05-31
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Mathew GEORGE; Rajsekhar DAS; Vladimir PETTER
- Web page: https://patentgrep.com/patent/US20260030359A1

## CPC

- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 21/575: {Secure boot}
- G06F 3/0622: {in relation to access}
- G06F 3/0631: {by allocating resources to storage systems}
- G06F 3/0637: {Permissions}
- G06F 3/0643: {Management of files}
- G06F 3/0665: {at area level, e.g. provisioning of virtual or logical volumes}
- G06F 9/4405: {Initialisation of multiprocessor systems}
- G06F 9/5016: {the resource being the memory}
- G06F 9/5061: {Partitioning or combining of resources}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 21/6281: {at program execution time, where the protection is within the operating system}
- G06F 21/78: to assure secure storage of data (address-based protection against unauthorised use of memory G06F12/14; record carriers for use with machines and with at least a part designed to carry digital markings G06K19/00)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Some storage systems are configured with VDL (valid data length) type controls that are implemented on a per cluster basis and, in some instances, on a sub-cluster basis, rather than simply a per file basis. In some instances, per-cluster VDL metadata for the storage clusters is stored and referenced at the edge data volume nodes of a distributed network for the storage system rather than, and/or without, storing or synchronizing the per-cluster VDL metadata at a master node that manages the corresponding storage clusters for the different data volume nodes. Sequence controls are also provided and managed by the master node and synchronized with the edge data volume nodes to further control access to data contained in the storage clusters.

## Claims

### Claim 1

A data volume node, comprising:
a data volume comprising a plurality of storage clusters;
at least one processor; and
at least one physical computer-readable storage media having stored computer-executable instructions that are executable by the at least one processor to cause the data volume node to:
receive, from a master metadata volume node, an assignment of one or more storage clusters along with one or more corresponding sequence numbers associated with the one or more storage clusters;
set, by the data volume node, a VDL (valid data length) indicator for a storage cluster of the one or more storage clusters to an initialized state, the storage cluster being associated with a corresponding sequence number by the data volume node;
receive a client write request for the at least one storage cluster, the client write request including a first sequence number;
permit the client write request based on a comparison between the first sequence number and the corresponding sequence number associated with the storage cluster by the data volume node; and
upon permitting the client write request, and upon data being written to the storage cluster, update the VDL indicator for the storage cluster at the data volume node.

### Claim 2 (depends on 1)

The data volume node of claim 1, wherein the computer-executable instructions are executable by the at least one processor to further cause the data volume node to:
obtain a new assignment of the storage cluster from the master metadata volume node, the new assignment including a new sequence number that is associated with the storage cluster by the master metadata volume node, the new assignment causing the data volume node to associate the new sequence number to the storage cluster; and
ensure the VDL indicator for the storage cluster is reset to the initialized state, in response to receiving the updated assignment of the storage cluster.

### Claim 3 (depends on 2)

The data volume node of claim 2, wherein the computer-executable instructions are executable by the at least one processor to further cause the data volume node to:
receive a different client request for access to the storage cluster; and
deny the different client request based on the different client request not being associated with any sequence number that is currently associated with the storage cluster.

### Claim 4 (depends on 3)

The data volume node of claim 3, wherein the corresponding sequence number and the new sequence number are received from the master metadata volume node as encrypted sequence numbers, and wherein the computer-executable instructions are executable by the at least one processor to further cause the data volume node to:
decrypt the encrypted sequence numbers with authentication information received separately from the metadata volume node.

### Claim 5 (depends on 3)

The data volume node of claim 3, wherein the received assignment of the storage cluster also identifies one or more other sequence numbers for one or more corresponding storage clusters contained within the data volume of the data volume node.

### Claim 6 (depends on 5)

The data volume node of claim 5, wherein every sequence number included in the assignment is encrypted with a hash signed by an encryption key for which the data volume node has a corresponding decryption key.

### Claim 7 (depends on 1)

The data volume node of claim 1, wherein the computer-executable instructions are executable by the at least one processor to further cause the data volume node to:
receive a client read request for the storage cluster; and
permit the client read request only when the VDL indicator has been updated so that it is no longer in the initialized state.

### Claim 8 (depends on 1)

The data volume node of claim 1, wherein the VDL indicator is a per-cluster indicator consisting of a single bit.

### Claim 9 (depends on 1)

The data volume node of claim 1, wherein the VDL indicator is a sub-cluster multi-bit watermark indicator that indicates a watermark extent of which the storage cluster has been written to.

### Claim 10

A client computing system, comprising:
at least one processor; and
at least one physical computer-readable storage media having stored computer-executable instructions that are executable by the at least one processor to cause the client computing system to:
provide a file access request to a master metadata volume node for access to a file;
receive, in response to the file access request, an identification of one or more different storage clusters allocated to the file by the master metadata volume node, and which correspond with the file access request, along with one or more sequence numbers that are associated with the one or more different storage clusters, each of the one or more different storage clusters being associated with a corresponding sequence number;
send a data access request to a particular data volume node containing at least a first storage cluster of the one or more different storage clusters along with the corresponding associated sequence number(s); and
either, (1) receive an indication of the data access request being granted by the particular data volume node, or
(2) receive an indication from the particular data volume node that the data access request is denied in response to at least a first of the corresponding sequence number(s) failing to be associated with a corresponding one of the at least the first storage cluster or in response to a VDL (valid data length) indictor.

### Claim 11 (depends on 10)

The client computing system recited in claim 10, wherein the computer-executable instructions are executable by the at least one processor to further cause the client computing system to:
obtain updated sequence number(s) from the master metadata node in response to receiving the indication from the particular data volume node that the file access request is denied; and
provide the updated sequence number(s) to the data volume node with a new file access request and which causes the new file access request to be granted.

### Claim 12 (depends on 10)

The client computing system recited in claim 10, wherein the one or more sequence numbers are received from the master metadata volume node and provided to the data volume node by the client computing system in an encrypted form that the client computing system is unable to decrypt, but which the data volume node is able to decrypt.

### Claim 13 (depends on 10)

The client computing system recited in claim 10, wherein the data access request is a read request.

### Claim 14 (depends on 10)

The client computing system recited in claim 10, wherein the data access request is a write request which causes a write to only a selected portion of the storage cluster.

### Claim 15

A master metadata volume node, comprising:
at least one processor; and
at least one physical computer-readable storage media having stored computer-executable instructions that are executable by the at least one processor to cause the master metadata volume node to:
allocate different storage clusters contained in one or more data volumes of one or more different data volume nodes to a first file by dividing the first file between the different storage clusters;
generate and assign a sequence number to each corresponding storage cluster, each different storage cluster being associated with a different corresponding sequence number, the sequence number for a storage cluster being changed by the master metadata volume node prior to the corresponding storage cluster being reallocated;
provide the assigned sequence numbers for the different storage clusters to the one or more different data volume nodes containing the different storage clusters, respectively;
receive a file access request from a client for the first file; and
provide the client an identification of one or more different storage clusters allocated to the first file, and which correspond with the file access request, along with one or more sequence numbers that are associated with the one or more different storage clusters.

### Claim 16 (depends on 15)

The master metadata volume node recited in claim 15, wherein the computer-executable instructions are executable by the at least one processor to further cause the master metadata volumen node to:
refrain from locally storing, at the master metadata volume node, a VDL (valid data length) indicator for the one or more different storage clusters allocated to the first file, the VDL indicator being stored locally at the one or more different data volume nodes.

### Claim 17 (depends on 15)

The master metadata volume node recited in claim 15, wherein the computer-executable instructions are executable by the at least one processor to further cause the master metadata volume node to:
encrypt the one or more sequence numbers that are associated with the one or more different storage clusters prior to providing the sequence numbers to the client.

### Claim 18 (depends on 17)

The master metadata volume node recited in claim 17, wherein the computer-executable instructions are executable by the at least one processor to further cause the master metadata volume node to:
send authentication information to the one or more data volume nodes for decrypting the encrypted one or more sequence numbers.

### Claim 19 (depends on 15)

The master metadata volume node of claim 15, wherein the computer-executable instructions are executable by the at least one processor to further cause the master metadata volume node to:
reallocate a particular storage cluster contained in a particular data volume at a particular data volume node, which was included in the one of the one or different storage clusters, to a new file;
re-sequence the particular storage cluster by at least generating an updated sequence number for the particular storage cluster and associating the updated sequence number with the particular storage cluster; and
send a new assignment of the particular storage cluster and the updated sequence number associated with the particular storage cluster to the particular data volume node.

### Claim 20 (depends on 19)

The master metadata volume node of claim 19, wherein the new assignment comprises an instruction for the particular data volume to reset a VDL associated with the particular storage cluster at the particular data volume node prior to or without the particular storage cluster being initialized.
