# US 2021/0279144 A1 · Node level recovery for clustered databases

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

- Number: US 2021/0279144 A1
- Document ID: US20210279144A1
- Status: Published application
- Kind: A1
- Application number: 16/812,522
- Filed: 2020-03-09
- Published: 2021-09-09
- Earliest claimed: 2020-03-09
- Assignees: Rubrik, Inc.
- Applicants: Rubrik, Inc.
- Inventors: Prasenjit Sarkar; Tarun Thakur
- Web page: https://patentgrep.com/patent/US20210279144A1

## CPC

- G06F 11/1464: {for networked environments}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1461: {Backup scheduling policy}
- G06F 11/1469: {Backup restoration techniques}
- G06F 11/1658: {Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit}
- G06F 11/2028: {eliminating a faulty processor or activating a spare}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 11/2097: {maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups)}
- G06F 2201/80: Database-specific techniques
- G06F 2201/815: Virtual
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An example networked computing system comprises a node cluster; a database; at least one processor configured by instructions to perform operations in a method of node level recovery, the method comprising operations including at least: identifying a failed node among existing nodes in the node cluster; identifying and initiating a replacement node as a new node for the node cluster; accessing at the database a logical backup of the node cluster; retrieving logical backup data of the node cluster from the logical backup and applying a node level filter to identify rows of backup data associated with the failed node; and restoring the data rows identified by the node level filter to the new node.

## Claims

### Claim 1

A networked computing system comprising:
a node cluster;
a database;
at least one processor configured by instructions to perform operations in a method of node level recovery, the method comprising operations including at least:
identifying a failed node among existing nodes in the node cluster;
identifying and initiating a replacement node as a new node for the node cluster;
accessing at the database a logical backup of the node cluster;
retrieving logical backup data of the node cluster from the logical backup and
applying a node level filter to identify rows of backup data associated with the failed node; and
restoring the data rows identified by the node level filter to the new node.

### Claim 2 (depends on 1)

The networked computing system of claim 1, wherein the operations further comprise identifying new data written by applications to the existing nodes of the node cluster during restoration of the new node.

### Claim 3 (depends on 2)

The networked computing system of claim 2, wherein the operations further comprise accessing supplementary back up data included in an on-demand supplementary logical backup of the node cluster and applying the node level filter to the supplementary backup data to identify supplementary data rows associated with the new data written by the applications.

### Claim 4 (depends on 3)

The networked computing system of claim 3, wherein the operations further comprise restoring the supplementary data rows identified by the node level filter to the new node.

### Claim 5 (depends on 2, 4)

The networked computing system of claim 4, wherein the operations further comprise repeating at least the operations of claim 2 through claim 4 until no new data, written by applications to the existing nodes during restoration of the new node, is identified.

### Claim 6

A method of node level recovery at a networked computing system including a node cluster, the method comprising:
identifying a failed node among existing nodes in the node cluster;
identifying and initiating a replacement node as a new node for the node cluster;
accessing at the database a logical backup of the node cluster;
retrieving logical backup data of the node cluster from the logical backup and
applying a node level filter to identify rows of backup data associated with the failed node; and
restoring the data rows identified by the node level filter to the new node.

### Claim 7 (depends on 6)

The method of claim 6, wherein the operations further comprise identifying new data written by applications to the existing nodes of the node cluster during restoration of the new node.

### Claim 8 (depends on 7)

The method of claim 7, wherein the operations further comprise accessing supplementary back up data included in an on-demand supplementary logical backup of the node cluster and applying the node level filter to the supplementary backup data to identify supplementary data rows associated with the new data written by the applications.

### Claim 9 (depends on 8)

The method of claim 8, wherein the operations further comprise restoring the supplementary data rows identified by the node level filter to the new node.

### Claim 10 (depends on 7, 9)

The method claim 9, wherein the operations further comprise repeating at least the operations of claim 7 through claim 9 until no new data, written by applications to the existing nodes during restoration of the new node, is identified.

### Claim 11

A non-transitory machine-readable medium including instructions, which when read by a machine, cause the machine to perform operations in a method of node level recovery at a networked computing system including a node cluster, the operations comprising at least:
identifying a failed node among existing nodes in the node cluster;
identifying and initiating a replacement node as a new node for the node cluster;
accessing at the database a logical backup of the node cluster;
retrieving logical backup data of the node cluster from the logical backup and
applying a node level filter to identify rows of backup data associated with the failed node; and
restoring the data rows identified by the node level filter to the new node.

### Claim 12 (depends on 11)

The medium of claim 11, wherein the operations further comprise identifying new data written by applications to the existing nodes of the node cluster during restoration of the new node.

### Claim 13 (depends on 12)

The medium of claim 12, wherein the operations further comprise accessing supplementary back up data included in an on-demand supplementary logical backup of the node cluster and applying the node level filter to the supplementary backup data to identify supplementary data rows associated with the new data written by the applications.

### Claim 14 (depends on 13)

The medium of claim 13, wherein the operations further comprise restoring the supplementary data rows identified by the node level filter to the new node.

### Claim 15 (depends on 12, 14)

The medium of claim 14, wherein the operations further comprise repeating at least the operations of claim 12 through claim 14 until no new data, written by applications to the existing nodes during restoration of the new node, is identified.
