# US 2021/0279151 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/0279151 A1
- Document ID: US20210279151A1
- Status: Published application
- Kind: A1
- Application number: 16/812,536
- 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/US20210279151A1

## CPC

- G06F 11/1484: {involving virtual machines}
- G06F 11/2028: {eliminating a faulty processor or activating a spare}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 11/1469: {Backup restoration techniques}
- G06F 11/1471: involving logging of persistent data for recovery
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 16/182: Distributed file systems
- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 3/065: {Replication mechanisms}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 11/1451: {by selection of backup contents}
- G06F 2201/80: Database-specific techniques
- G06F 2201/805: Real-time
- G06F 2201/815: Virtual
- G06F 2201/82: Solving problems relating to consistency
- 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 for iterative node level recovery comprises a node cluster; a database; at least one processor configured by instructions to perform 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 and identifying specific rows of backup data to be restored to the new node; restoring the specific data rows to the new node; identifying new data written by applications, to the existing nodes of the node cluster, during restoration of the new node; iteratively accessing supplementary back up data to identify supplementary data rows to be restored to the new node; and iteratively restoring the supplementary data rows to the new node until the new node is synchronized with the existing nodes in the node cluster.

## Claims

### Claim 1

A networked computing system for iterative node level recovery, the system comprising:
a node cluster;
a database;
at least one processor configured by instructions to perform 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 and identifying specific rows of backup data to be restored to the new node;
restoring the specific data rows to the new node;
identifying new data written by applications, to the existing nodes of the node cluster, during restoration of the new node;
iteratively accessing supplementary back up data to identify supplementary data rows to be restored to the new node; and
iteratively restoring the supplementary data rows to the new node until the new node is synchronized with the existing nodes in the node cluster.

### Claim 2 (depends on 1)

The networked computing system of claim 1, wherein identifying specific rows of backup data to be restored to the new node includes applying a node level filter to identify the specific rows of backup data to be restored to the new node.

### Claim 3 (depends on 2)

The networked computing system of claim 2, wherein the specific rows of backup data include data associated with the failed node and devoid of data associated with the existing nodes of the node cluster.

### Claim 4 (depends on 1)

The networked computing system of claim 1, wherein the supplementary backup data is included in an on-demand supplementary logical backup of the node cluster.

### Claim 5 (depends on 4)

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

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

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

### Claim 7

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 and identifying specific rows of backup data to be restored to the new node;
restoring the specific data rows to the new node;
identifying new data written by applications, to the existing nodes of the node cluster, during restoration of the new node;
iteratively accessing supplementary back up data to identify supplementary data rows to he restored to the new node; and
iteratively restoring the supplementary data rows to the new node until the new node is synchronized with the existing nodes in the node cluster.

### Claim 8 (depends on 7)

The method of claim 7, wherein identifying specific rows of backup data to be restored to the new node includes applying a node level filter to identify the specific rows of backup data to be restored to the new node.

### Claim 9 (depends on 8)

The method of claim 8, wherein the specific rows of backup data include data associated with the failed node and devoid of data associated with the existing nodes of the node cluster.

### Claim 10 (depends on 7)

The method of claim 7, wherein the supplementary backup data is included in an on-demand supplementary logical backup of the node cluster.

### Claim 11 (depends on 10)

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

### Claim 12 (depends on 8, 11)

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

### Claim 13

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 and identifying specific rows of backup data to be restored to the new node;
restoring the specific data rows to the new node;
identifying new data written by applications, to the existing nodes of the node cluster, during restoration of the new node;
iteratively accessing supplementary back up data to identify supplementary rows to be restored to the new node; and
iteratively restoring the supplementary data rows to the new node until the new node is synchronized with the existing nodes in the node cluster.

### Claim 14 (depends on 13)

The medium of claim 13, wherein identifying specific rows of backup data to be restored to the new node includes applying a node level filter to identify the specific rows of backup data to be restored to the new node.

### Claim 15 (depends on 14)

The medium of claim 14, wherein the specific rows of backup data include data associated with the failed node and devoid of data associated with the existing nodes of the node cluster.

### Claim 16 (depends on 13)

The medium of claim 13, wherein the supplementary backup data is included in an on-demand supplementary logical backup of the node cluster.

### Claim 17 (depends on 16)

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

### Claim 18 (depends on 8, 11, 17)

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