# US 12,007,852 B2 · Systems and methods for backing up clustered and non-clustered data

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

- Number: US 12,007,852 B2
- Document ID: US12007852B2
- Status: Granted
- Kind: B2
- Application number: 17/872,647
- Filed: 2022-07-25
- Published: 2024-01-25
- Granted: 2024-06-11
- Earliest claimed: 2022-07-25
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Sunil Yadav; Shelesh Chopra; Preeti Varma
- Web page: https://patentgrep.com/patent/US12007852B2

## CPC

- G06F 11/1464: {for networked environments}
- G06F 11/1461: {Backup scheduling policy}
- 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

A method for backing up standalone data and clustered data on a node, that includes receiving, by a backup agent, a first backup request, making a first determination that a backup process is not active, and based on the first determination, identifying a first type of data specified in the first backup request, where the first type of data is the standalone data, locating, using a first backup policy, the standalone data in the node, begin generating standalone backup data from the standalone data, receiving, by the backup agent, a second backup request, making a second determination that the backup process is active, and based on the second determination, queuing the second backup request.

## Claims

### Claim 1

A method for backing up standalone data and clustered data on a node, comprising:
receiving, by a backup agent, a first backup request;
making a first determination that a backup process is not active; and
based on the first determination:
identifying a first type of data specified in the first backup request, wherein the first type of data is the standalone data;
locating, using a first backup policy, the standalone data in the node;
begin generating standalone backup data from the standalone data;
receiving, by the backup agent, a second backup request;
making a second determination that the backup process is active; and
based on the second determination:
queuing the second backup request.

### Claim 2 (depends on 1)

The method of claim 1, wherein after queuing the second backup request, the method further comprises:
finish generating the standalone backup data;
making a third determination that the backup process is not active; and
based on the third determination:
identifying a second type of data specified in the second backup request, wherein the second type of data is the clustered data;
locating, using a second backup policy, the clustered data in the node; and
begin generating clustered backup data from the clustered data.

### Claim 3 (depends on 2)

The method of claim 2, wherein after beginning to generate the clustered backup data, the method further comprises:
receiving, by the backup agent, a third backup request;
making a fourth determination that the backup process is active; and
based on the fourth determination:
queuing the third backup request.

### Claim 4 (depends on 3)

The method of claim 3, wherein after queuing the third backup request, the method further comprises:
finish generating the clustered backup data;
making a fifth determination that the backup process is not active; and
based on the fifth determination:
identifying a third type of data specified in the third backup request, wherein the third type of data is disaster recovery data.

### Claim 5 (depends on 4)

The method of claim 4, wherein after identifying the third type of data specified in the third backup request, the method further comprises:
locating, using a third backup policy, the disaster recovery data in the node; and
generating disaster recovery backup data from the disaster recovery data.

### Claim 6 (depends on 1)

The method of claim 1, wherein after queuing the second backup request, the method further comprises:
finish generating the standalone backup data;
making a third determination that the backup process is not active; and
based on the third determination:
identifying a second type of data specified in the second backup request, wherein the second type of data is disaster recovery data;
locating, using a second backup policy, the disaster recovery data in the node; and
generating disaster recovery backup data from the disaster recovery data.

### Claim 7 (depends on 6)

The method of claim 6, wherein after generating the disaster recovery backup data, the method further comprises:
receiving a request to copy the clustered data to a second node.

### Claim 8

A non-transitory computer readable medium comprising instructions which, when executed by a computer processor, enables the computer processor to perform a method for backing up standalone data and clustered data on a node, comprising:
receiving, by a backup agent, a first backup request;
making a first determination that a backup process is not active; and
based on the first determination:
identifying a first type of data specified in the first backup request, wherein the first type of data is the standalone data;
locating, using a first backup policy, the standalone data in the node;
begin generating standalone backup data from the standalone data;
receiving, by the backup agent, a second backup request;
making a second determination that the backup process is active; and
based on the second determination:
queuing the second backup request.

### Claim 9 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein after queuing the second backup request, the method further comprises:
finish generating the standalone backup data;
making a third determination that the backup process is not active; and
based on the third determination:
identifying a second type of data specified in the second backup request, wherein the second type of data is the clustered data;
locating, using a second backup policy, the clustered data in the node; and
begin generating clustered backup data from the clustered data.

### Claim 10 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein after beginning to generate the clustered backup data, the method further comprises:
receiving, by the backup agent, a third backup request;
making a fourth determination that the backup process is active; and
based on the fourth determination:
queuing the third backup request.

### Claim 11 (depends on 10)

The non-transitory computer readable medium of claim 10, wherein after queuing the third backup request, the method further comprises:
finish generating the clustered backup data;
making a fifth determination that the backup process is not active; and
based on the fifth determination:
identifying a third type of data specified in the third backup request, wherein the third type of data is disaster recovery data.

### Claim 12 (depends on 11)

The non-transitory computer readable medium of claim 11, wherein after identifying the third type of data specified in the third backup request, the method further comprises:
locating, using a third backup policy, the disaster recovery data in the node; and
generating disaster recovery backup data from the disaster recovery data.

### Claim 13 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein after queuing the second backup request, the method further comprises:
finish generating the standalone backup data;
making a third determination that the backup process is not active; and
based on the third determination:
identifying a second type of data specified in the second backup request, wherein the second type of data is disaster recovery data;
locating, using a third backup policy, the disaster recovery data in the node; and
generating disaster recovery backup data from the disaster recovery data.

### Claim 14 (depends on 13)

The non-transitory computer readable medium of claim 13, wherein after generating the disaster recovery backup data, the method further comprises:
receiving a request to copy the clustered data to a second node.

### Claim 15

A node, comprising:
memory;
a storage device comprising standalone data and clustered data; and
a processor executing a backup manager, wherein the backup manager is configured to perform a method for backing up the standalone data and the clustered data on the node, comprising:
receiving a first backup request;
making a first determination that a backup process is not active; and
based on the first determination:
identifying a first type of data specified in the first backup request, wherein the first type of data is the standalone data;
locating, using a first backup policy, the standalone data in the node;
begin generating standalone backup data from the standalone data;
receiving a second backup request;
making a second determination that the backup process is active; and
based on the second determination:
queuing the second backup request.

### Claim 16 (depends on 15)

The node of claim 15, wherein after queuing the second backup request, the method further comprises:
finish generating the standalone backup data;
making a third determination that the backup process is not active; and
based on the third determination:
identifying a second type of data specified in the second backup request, wherein the second type of data is the clustered data;
locating, using a second backup policy, the clustered data in the node; and
begin generating clustered backup data from the clustered data.

### Claim 17 (depends on 16)

The node of claim 16, wherein after beginning to generate the clustered backup data, the method further comprises:
receiving a third backup request;
making a fourth determination that the backup process is active; and
based on the fourth determination:
queuing the third backup request.

### Claim 18 (depends on 17)

The node of claim 17, wherein after queuing the third backup request, the method further comprises:
finish generating the clustered backup data;
making a fifth determination that the backup process is not active; and
based on the fifth determination:
identifying a third type of data specified in the third backup request, wherein the third type of data is disaster recovery data.

### Claim 19 (depends on 18)

The node of claim 18, wherein after identifying the third type of data specified in the third backup request, the method further comprises:
locating, using a third backup policy, the disaster recovery data in the node; and
generating disaster recovery backup data from the disaster recovery data.

### Claim 20 (depends on 15)

The node of claim 15, wherein after queuing the second backup request, the method further comprises:
finish generating the standalone backup data;
making a third determination that the backup process is not active; and
based on the third determination:
identifying a second type of data specified in the second backup request, wherein the second type of data is disaster recovery data;
locating, using a third backup policy, the disaster recovery data in the node; and
generating disaster recovery backup data from the disaster recovery data.