US 2019/0377802 A1Published application

Managing per object snapshot coverage in filesystems

AssigneeQumulo, Inc.

InventorsSteven Henry Haber, John Brazel, Neal Thomas Fachan, Robert Edward Gebert, Zacharie Lamont Kirsch, Aaron James Passey, Thomas Scott Urban

Life of this patent

Estimating the term…

patentgrep

Loading patent…

Abstract

Embodiments are directed to managing data in a file system. An object from the file system that has parent objects may be provided. A snapshot in a current epoch may be generated such that the first snapshot may be based on the object and descendants of the object. A coverage set may be provided for the object that references the snapshot and also references each other snapshot that includes the parent objects. Read-only access to a version of the object may be provided based on a correspondence of the version and a snapshot referenced by the coverage set of the object. A coverage engine compares the update to a coverage update epoch (cue) associated with the parent objects. The coverage engine updates coverage sets of the parent objects based on grandparents of the object.

Claims28

Dependent claims

A method for managing data in a file system over a network using one or more processors that execute instructions to perform actions, comprising:

instantiating a file system engine to perform further actions, including:
providing an object from the file system that has one or more parent objects, wherein each object includes one or more entities;
generating a first snapshot in a current epoch, wherein the first snapshot is based on the object and one or more descendants of the object, wherein each epoch refers to a time period in between snapshots or before a next snapshot;
providing a first coverage set, for the object, that references the first snapshot and also references each other snapshot that includes the one or more parent objects;
providing read-only access to a version of the object based on a correspondence of the version and a snapshot referenced by the first coverage set of the object, wherein the snapshot referenced by the first coverage set is employed to increase granularity of the snapshot by covering one or more portions of the file system instead of the entire file system to reduce one or more of a size of the snapshot that is stored, reduce an amount of time to generate the snapshot, or create the snapshot at different rates or times than other snapshots that cover one or more other portions of the file system;
and
instantiating a coverage engine in response to an update to the one or more entities of the object, wherein the coverage engine performs further actions, comprising:
comparing the update to one or more entities of a coverage update epoch associated with the one or more parent objects;
and
updating one or more coverage sets of the one or more parent objects based on one or more grandparents of the object.

7 more elements

A system for managing data in a file system over a network, comprising:

a network computer, comprising:
a memory that stores at least instructions;
and
one or more processors that execute instructions that perform actions, including:
instantiating a file system engine to perform further actions, including:
providing an object from the file system that has one or more parent objects, wherein each object includes one or more entities;
generating a first snapshot in a current epoch, wherein the first snapshot is based on the object and one or more descendants of the object;
providing a first coverage set, for the object, that references the first snapshot and also references each other snapshot that includes the one or more parent objects;
providing read-only access to a version of the object based on a correspondence of the version and a snapshot referenced by the first coverage set of the object, wherein the snapshot referenced by the first coverage set is employed to increase granularity of the snapshot by covering one or more portions of the file system instead of the entire file system to reduce one or more of a size of the snapshot that is stored, reduce an amount of time to generate the snapshot, or create the snapshot at different rates or times than other snapshots that cover one or more other portions of the file system;
and
instantiating a coverage engine in response to an update to the one or more entities of the object, wherein the coverage engine performs further actions, comprising:
comparing the update to one or more entities of a coverage update epoch associated with the one or more parent objects;
and
updating one or more coverage sets of the one or more parent objects based on one or more grandparents of the object;
and
a client computer, comprising:
a memory that stores at least instructions;
and
one or more processors that execute instructions that perform actions, including:
receiving, read-only access version of the object.

17 more elements

A processor readable non-transitory storage media that includes instructions for managing data in a file system over a network, wherein execution of the instructions by one or more processors on one or more network computers performs actions, comprising:

instantiating a file system engine to perform further actions, including:
providing an object from the file system that has one or more parent objects, wherein each object includes one or more entities;
generating a first snapshot in a current epoch, wherein the first snapshot is based on the object and one or more descendants of the object;
providing a first coverage set, for the object, that references the first snapshot and also references each other snapshot that includes the one or more parent objects;
providing read-only access to a version of the object based on a correspondence of the version and a snapshot referenced by the first coverage set of the object, wherein the snapshot referenced by the first coverage set is employed to increase granularity of the snapshot by covering one or more portions of the file system instead of the entire file system to reduce one or more of a size of the snapshot that is stored, reduce an amount of time to generate the snapshot, or create the snapshot at different rates or times than other snapshots that cover one or more other portions of the file system;
and
instantiating a coverage engine in response to an update to the one or more entities of the object, wherein the coverage engine performs further actions, comprising:
comparing the update to one or more entities of a coverage update epoch associated with the one or more parent objects;
and
updating one or more coverage sets of the one or more parent objects based on one or more grandparents of the object.

7 more elements

A network computer for managing data in a file system over a network, comprising:

a memory that stores at least instructions;
and
one or more processors that execute instructions that perform actions, including:
instantiating a file system engine to perform further actions, including:
providing an object from the file system that has one or more parent objects, wherein each object includes one or more entities;
generating a first snapshot in a current epoch, wherein the first snapshot is based on the object and one or more descendants of the object;
providing a first coverage set, for the object, that references the first snapshot and also references each other snapshot that includes the one or more parent objects;
providing read-only access to a version of the object based on a correspondence of the version and a snapshot referenced by the first coverage set of the object, wherein the snapshot referenced by the first coverage set is employed to increase granularity of the snapshot by covering one or more portions of the file system instead of the entire file system to reduce one or more of a size of the snapshot that is stored, reduce an amount of time to generate the snapshot, or create the snapshot at different rates or times than other snapshots that cover one or more other portions of the file system;
and
instantiating a coverage engine in response to an update to the one or more entities of the object, wherein the coverage engine performs further actions, comprising:
comparing the update to one or more entities of a coverage update epoch associated with the one or more parent objects;
and
updating one or more coverage sets of the one or more parent objects based on one or more grandparents of the object.

10 more elements

Dependencies are inferred from the claim text.

Facts

Application: 16/004,182Filed 8 Jun 2018
Published: 12 Dec 2019
Term ends: Not estimatedThe source records don’t support an estimate.

Classification4 codes

G06F 16/128
File system administration, e.g. details of archiving or snapshots: details of file system snapshots on the file-level, e.g. snapshot creation,…
G06F 16/162
File or folder operations, e.g. details of user interfaces specifically adapted to file systems: delete operations
G06F 16/183
Implemented using Network-attached Storage [NAS] architecture: provision of network file services by network file servers, e.g. by using NFS, CIFS
G06F
Computing and data processing

Family

US 11,360,936 B2Related patent
US 2019/0377802 A1This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key