# US 2025/0094384 A1 · Database Aware, Space Efficient, High Performance, Snapshots On Hyper-Scale Distributed Storage

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

- Number: US 2025/0094384 A1
- Document ID: US20250094384A1
- Status: Published application
- Kind: A1
- Application number: 18/885,231
- Filed: 2024-09-13
- Published: 2025-03-20
- Earliest claimed: 2023-09-15
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Nilesh Choudhury; Krishnan Meiyyappan; Semen Ustimenko; Boris Erlikhman; Siddharth Choudhary; Scott Martin
- Web page: https://patentgrep.com/patent/US20250094384A1

## CPC

- G06F 16/128: {Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16)}
- G06F 16/1744: {using compression, e.g. sparse files}
- G06F 16/2246: {Trees, e.g. B+trees}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A database-aware storage server provides instant creation of snapshots without the need to create an intermediate test master database. During the snapshot creation time, the source database stays read-write and completes ongoing reads and writes. The database-aware storage server allows creation of layers of writable snapshots in a hierarchy. All these multiple databases share common data blocks. Any new writes performed by the database post snapshot are stored in blocks of sparse files. This promotes space sharing and reduces the total amount of space used by all these related databases. The allocations for the source and all new snapshot databases share the same common pool of storage. The newly created snapshot databases can access the data store directly without going through an intermediate layer.

## Claims

### Claim 1

A method comprising:
maintaining a set of snapshot tree data structures that represent hierarchical relationships of files of a set of databases comprising a master database;
creating a new snapshot database from a source database within the set of databases, wherein:
the master database comprises one or more data files, and
the new snapshot database comprises one or more sparse files corresponding to the one or more data files;
updating the set of snapshot tree data structures to form an updated set of snapshot tree data structures that includes representation of the one or more sparse files of the new snapshot database;
in response to a request from a client to perform a database operation on a target database within the set of databases, performing a verification of the request based on the updated set of snapshot tree data structures; and
in response to successful verification of the request, performing the database operation on the target database,
wherein the method is performed by one or more computing devices.

### Claim 2 (depends on 1)

The method of claim 1, wherein performing verification of the request comprises determining whether the client has the updated set of snapshot tree data structures.

### Claim 3 (depends on 2)

The method of claim 2, further comprising providing the updated set of snapshot tree data structures to the client in response to failed verification of the request.

### Claim 4 (depends on 2)

The method of claim 2, wherein determining whether the client has the updated snapshot tree data structure comprises determining whether the target database is represented as a leaf node in the updated set of snapshot tree data structures.

### Claim 5 (depends on 1)

The method of claim 1, wherein the source database is writable during creation of the new snapshot database.

### Claim 6 (depends on 1)

The method of claim 1, wherein the source database is the master database.

### Claim 7 (depends on 1)

The method of claim 1, wherein the source database is a snapshot database comprising one or more sparse files corresponding to the one or more data files.

### Claim 8 (depends on 1)

The method of claim 1, wherein updating the set of snapshot tree data structures comprises representing the new snapshot database as a child of the source database in the updated set of snapshot tree data structures.

### Claim 9 (depends on 1)

The method of claim 1, wherein:
creating the new snapshot database comprises creating a clone of the source database and the new snapshot database,
the clone of the source database is a snapshot database comprising a first set of one or more sparse files corresponding to the one or more data files, and
the new snapshot database comprises a second set of one or more sparse files corresponding to the one or more data files, and
updating the set of snapshot tree data structures comprises representing the clone of the source database and the new snapshot database as children of the source database in the updated set of snapshot tree data structures.

### Claim 10 (depends on 1)

The method of claim 1, wherein the database operation comprises a database smart offload operation.

### Claim 11 (depends on 1)

The method of claim 1, wherein:
the target database is the new snapshot database,
the database operation comprises a write to at least one data block of a file of the target database, and
performing the database operation comprises writing the at least one data block to a sparse file of the one or more sparse files.

### Claim 12 (depends on 1)

The method of claim 1, wherein:
the target database is the new snapshot database,
the database operation comprises creating a new file in the target database, and
performing the database operation comprises adding the new file to the one or more sparse files.

### Claim 13 (depends on 1)

The method of claim 1, wherein:
the target database is the new snapshot database,
the database operation comprises a read from a file of the target database, and
performing the database operation comprises reading a set of one or more data blocks from at least one of the one or more sparse files or the one or more data files.

### Claim 14

One or more non-transitory computer-readable media storing instructions which, when executed by one or more processors, causes performance of:
maintaining a set of snapshot tree data structures that represent hierarchical relationships of files of a set of databases comprising a master database;
creating a new snapshot database from a source database within the set of databases, wherein:
the master database comprises one or more data files, and
the new snapshot database comprises one or more sparse files corresponding to the one or more data files;
updating the set of snapshot tree data structures to form an updated set of snapshot tree data structures that includes representation of the one or more sparse files of the new snapshot database;
in response to a request from a client to perform a database operation on a target database within the set of databases, performing a verification of the request based on the updated set of snapshot tree data structures; and
in response to successful verification of the request, performing the database operation on the target database.

### Claim 15 (depends on 14)

The one or more non-transitory computer-readable media of claim 14, wherein performing verification of the request comprises determining whether the client has the updated set of snapshot tree data structures.

### Claim 16 (depends on 15)

The one or more non-transitory computer-readable media of claim 15, further comprising providing the updated set of snapshot tree data structures to the client in response to failed verification of the request.

### Claim 17 (depends on 15)

The one or more non-transitory computer-readable media of claim 15, wherein determining whether the client has the updated set of snapshot tree data structures comprises determining whether the target database is represented as a leaf node in the updated set of snapshot tree data structures.

### Claim 18 (depends on 14)

The one or more non-transitory computer-readable media of claim 14, wherein updating the set of snapshot tree data structures comprises representing the new snapshot database as a child of the source database in the updated set of snapshot tree data structures.

### Claim 19 (depends on 14)

The one or more non-transitory computer-readable media of claim 14, wherein:
creating the new snapshot database comprises creating a clone of the source database and the new snapshot database,
the clone of the source database is a snapshot database comprising a first set of one or more sparse files corresponding to the one or more data files, and
the new snapshot database comprises a second set of one or more sparse files corresponding to the one or more data files, and
updating the set of snapshot tree data structures comprises representing the clone of the source database and the new snapshot database as children of the source database in the updated set of snapshot tree data structures.

### Claim 20 (depends on 14)

The one or more non-transitory computer-readable media of claim 14, wherein the database operation comprises a database smart offload operation.
