Granted Patent B1

US 11,435,901 · App. 17/484,167 · Granted Sep 6, 2022

Inventors: Michael Anthony Chmiel (Seattle, WA); Duncan Robert Fairbanks (Seattle, WA); Stephen Craig Fleischman (Seattle, WA); Nicholas Graeme Williams (Seattle, WA)

Assignee: Qumulo, Inc.

G06F3/0604G06F3/065G06F3/067G06F3/0614G06F3/0683G06F11/1446G06F11/1448G06F11/1466G06F16/113G06F16/128

Abstract

Claims (85)

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

providing the file system that includes a plurality of storage nodes and a plurality of storage volumes, wherein each of the plurality of storage nodes are based on a compute instance provided by a cloud computing environment (CCE); and

in response to execution of a backup job, performing further actions, including:

disabling the file system and each of the plurality of storage nodes;

identifying one or more storage volumes that are associated with the plurality of disabled storage nodes; and

generating a launch image based on node metadata for a root storage volume; and

in response to generating one or more storage images that archive a copy of information from the one or more identified storage volumes, performing further actions, including:

employing the launch image to re-enable both the file system and the plurality of storage nodes; and

associating one or more network interfaces with the launch image and one or more of the plurality of storage nodes.

2. The method of claim 1 , further comprising:

employing the CCE to provide one or more data stores for the one or storage volumes.

3. The method of claim 1 , further comprising, in response to a confirmation that the file system is consistent, associating a finalized tag with each storage image.

4. The method of claim 1 , wherein disabling the file system and the plurality of storage nodes further comprises:

associating each disabled storage node with a shutdown timestamp; and

confirming that the file system is consistent based on an absence of file system activity occurring subsequent to each shutdown timestamp.

5. The method of claim 1 , wherein generating the one or more storage images, further comprises:

determining a root volume included with the one or more storage volumes;

generating storage node metadata that includes information associated with the storage node that is associated with the root volume; and

associating the storage node metadata with a storage image that corresponds to the root volume.

6. The method of claim 1 , wherein generating the one or more storage images, further comprises:

generating storage volume metadata that includes information associated with each storage volume; and

associating the storage volume metadata for each storage volume with each storage image.

7. The method of claim 1 , further comprising:

providing a backup identifier that corresponds to the backup job;

determining the plurality of storage images based on the backup identifier;

determining storage node metadata from each storage image that corresponds to a root volume;

generating one or more launch images based on the storage node metadata; and

employing the one or more launch images to instantiate the plurality of storage nodes.

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

memory that stores at least instructions; and

one or more processors that execute instructions that perform actions, including:

providing the file system that includes a plurality of storage nodes and a plurality of storage volumes, wherein each of the plurality of storage nodes are based on a compute instance provided by a cloud computing environment (CCE); and

in response to execution of a backup job, performing further actions, including:

disabling the file system and each of the plurality of storage nodes;

identifying one or more storage volumes that are associated with the plurality of disabled storage nodes; and

generating a launch image based on node metadata for a root storage volume; and

in response to generating one or more storage images that archive a copy of information from the one or more identified storage volumes, performing further actions, including:

employing the launch image to re-enable both the file system and the plurality of storage nodes; and

associating one or more network interfaces with the launch image and one or more of the plurality of storage nodes.

9. The network computer of claim 8 , further comprising:

employing the CCE to provide one or more data stores for the one or storage volumes.

10. The network computer of claim 8 , further comprising, in response to a confirmation that the file system is consistent, associating a finalized tag with each storage image.

11. The network computer of claim 8 , wherein disabling the file system and the plurality of storage nodes further comprises:

associating each disabled storage node with a shutdown timestamp; and

confirming that the file system is consistent based on an absence of file system activity occurring subsequent to each shutdown timestamp.

12. The network computer of claim 8 , wherein generating the one or more storage images, further comprises:

determining a root volume included with the one or more storage volumes;

generating storage node metadata that includes information associated with the storage node that is associated with the root volume; and

associating the storage node metadata with a storage image that corresponds to the root volume.

13. The network computer of claim 8 , wherein generating the one or more storage images, further comprises:

generating storage volume metadata that includes information associated with each storage volume; and

associating the storage volume metadata for each storage volume with each storage image.

14. The network computer of claim 8 , further comprising:

providing a backup identifier that corresponds to the backup job;

determining the plurality of storage images based on the backup identifier;

determining storage node metadata from each storage image that corresponds to a root volume;

generating one or more launch images based on the storage node metadata; and

employing the one or more launch images to instantiate the plurality of storage nodes.

15. 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:

providing the file system that includes a plurality of storage nodes and a plurality of storage volumes, wherein each of the plurality of storage nodes are based on a compute instance provided by a cloud computing environment (CCE); and

in response to execution of a backup job, performing further actions, including:

disabling the file system and each of the plurality of storage nodes;

identifying one or more storage volumes that are associated with the plurality of disabled storage nodes; and

generating a launch image based on node metadata for a root storage volume; and

in response to generating one or more storage images that archive a copy of information from the one or more identified storage volumes, performing further actions, including:

employing the launch image to re-enable both the file system and the plurality of storage nodes; and

associating one or more network interfaces with the launch image and one or more of the plurality of storage nodes.

16. The processor readable non-transitory storage media of claim 15 , further comprising:

employing the CCE to provide one or more data stores for the one or storage volumes.

17. The processor readable non-transitory storage media of claim 15 , further comprising:

providing a backup identifier that corresponds to the backup job;

determining the plurality of storage images based on the backup identifier;

determining storage node metadata from each storage image that corresponds to a root volume;

generating one or more launch images based on the storage node metadata; and

employing the one or more launch images to instantiate the plurality of storage nodes.

18. The processor readable non-transitory storage media of claim 15 , wherein disabling the file system and the plurality of storage nodes further comprises:

associating each disabled storage node with a shutdown timestamp; and

confirming that the file system is consistent based on an absence of file system activity occurring subsequent to each shutdown timestamp.

19. The processor readable non-transitory storage media of claim 15 , wherein generating the one or more storage images, further comprises:

determining a root volume included with the one or more storage volumes;

generating storage node metadata that includes information associated with the storage node that is associated with the root volume; and

associating the storage node metadata with a storage image that corresponds to the root volume.

20. The processor readable non-transitory storage media of claim 15 , wherein generating the one or more storage images, further comprises:

generating storage volume metadata that includes information associated with each storage volume; and

associating the storage volume metadata for each storage volume with each storage image.

Assignments (2)

Continuity (1)

Cited By (9)

US 12,222,903 US 12,292,853 US 12,346,290 US 12,443,559 US 12,443,568 US 12,481,625 US 12,585,563 US 12,619,582 US 12,670,081