Systems and methods for non-blocking backups

Patent metadata

Field	Value
Publication number	US-11829253-B2
Application number	US-202016895601-A
Country	US
Kind code	B2
Filing date	Jun 8, 2020
Priority date	Sep 25, 2015
Publication date	Nov 28, 2023
Grant date	Nov 28, 2023

Abstract

A database system comprising a database comprising a plurality of data storage nodes, the plurality of data storage nodes including a primary storage node and a plurality of secondary storage nodes. The database system may also include at least one processor configured to: perform at least one write command to a secondary storage node of the plurality of secondary storage nodes; and perform at least one backup command, at least partially in parallel with the at least one write command being performed to the secondary storage node, of at least some data from a snapshot of data stored in the secondary storage node. A method for performing at least one backup command in a database at least partially in parallel with the at least one write command being performed.

First claim

What is claimed is:

1. A database system comprising:
a database comprising a plurality of data storage nodes, the plurality of data storage nodes forming a replica set, the plurality of data storage nodes including, in the replica set, a primary storage node and a plurality of secondary storage nodes; and
at least one processor configured to:
perform at least one write command to a secondary storage node of the plurality of secondary storage nodes; and
perform at least one backup command, at least partially in parallel with the at least one write command being performed to the secondary storage node, of at least some data from a snapshot of data stored in the secondary storage node,
wherein the replica set is configured to store at least one dataset in the database,
wherein the at least one backup command is performed without allocating additional disk capacity beyond that in the replica set,
wherein each backup command of the at least one backup command opens no more than one backup cursor,
wherein storage resources of the backup cursor are released based on whether a heartbeat signal is received within a time interval.

2. The database system of claim 1 , wherein the at least one backup command is performed without allocating additional hardware beyond that in the plurality of data storage nodes.

3. The database system of claim 1 , wherein the at least one processor is configured to validate whether a storage engine supports the at least one backup command.

4. The database system of claim 1 , wherein the database system includes first components that support the at least one backup command and second components that do not support the at least one backup command.

5. The database system of claim 1 , wherein the database follows an eventual consistency model.

6. The database system of claim 1 , wherein the at least one processor is configured to execute a plurality of system components, wherein the system components comprise:
an interface component configured to receive the at least one write command and the at least one backup command;
a snapshot component configured to generate a plurality of snapshots of data stored in the secondary storage node; and
a command processing component configured to apply the at least one write command and perform the at least one backup command.

7. A method for performing at least one backup command in a database comprising a plurality of data storage nodes, the plurality of data storage nodes forming a replica set, the plurality of data storage nodes including, in the replica set, a primary storage node and a plurality of secondary storage nodes, the method comprising:
performing at least one write command to a secondary storage node of the plurality of secondary storage nodes; and
performing at least one backup command, at least partially in parallel with the at least one write command being performed to the secondary storage node, of at least some data from a snapshot of data stored in the secondary storage node,
wherein the replica set is configured to store at least one dataset in the database,
wherein the at least one backup command is performed without allocating additional disk capacity beyond that in the replica set,
wherein each backup command of the at least one backup command opens no more than one backup cursor,
wherein storage resources of the backup cursor are released based on whether a heartbeat signal is received within a time interval.

8. At least one computer-readable storage medium having instructions recorded thereon which, when executed by a computer, cause the computer to perform a method for performing at least one backup command in a database comprising a plurality of data storage nodes, the plurality of data storage nodes forming a replica set, the plurality of data storage nodes including, in the replica set, a primary storage node and a plurality of secondary storage nodes, the method comprising:
performing at least one write command to a secondary storage node of the plurality of secondary storage nodes; and
performing at least one backup command, at least partially in parallel with the at least one write command being performed to the secondary storage node, of at least some data from a snapshot of data stored in the secondary storage node,
wherein the replica set is configured to store at least one dataset in the database,
wherein the at least one backup command is performed without allocating additional disk capacity beyond that in the replica set,
wherein each backup command of the at least one backup command opens no more than one backup cursor,
wherein storage resources of the backup cursor are released based on whether a heartbeat signal is received within a time interval.

9. The at least one computer-readable storage medium of claim 8 , wherein the at least one backup command is performed without allocating additional hardware beyond that in the plurality of data storage nodes.

10. The at least one computer-readable storage medium of claim 8 , wherein the method further comprises validating whether a storage engine supports the at least one backup command.

11. The at least one computer-readable storage medium of claim 8 , wherein the database system includes first components that support the at least one backup command and second components that do not support the at least one backup command.

12. The at least one computer-readable storage medium of claim 8 , wherein the database follows an eventual consistency model.

Assignees

• Cabral Alyson
• Jackson Spencer
• Yao Xiangyu
• Reams Jonathan
• Gottlieb Daniel William
• Horowitz Eliot
• Loverso Susan
• Mongodb Inc

Inventors

• Cabral Alyson
• Jackson Spencer
• Yao Xiangyu
• Reams Jonathan
• Gottlieb Daniel William
• Horowitz Eliot
• Loverso Susan

Classifications

• G06F11/1464 Primary

  for networked environments · CPC title

• G06F9/5016

  the resource being the memory · CPC title

• G06F11/1451 Primary

  by selection of backup contents · CPC title

• G06F11/1461

  Backup scheduling policy · CPC title

• G06F11/1469

  Backup restoration techniques · CPC title