IP Library Granted Patent US 12,045,139
Granted Patent B2
US 12,045,139 · App. 17/521,006 · Granted Jul 23, 2024

Data backup in container management frameworks

Inventors: Guilherme Vale Ferreira Menezes (Los Gatos, CA); Nohhyun Park (San Jose, CA); Abhishek Dharmaprikar (Mountain View, CA); Rajath Subramanyam (Santa Clara, CA); Pin Zhou (San Jose, CA); Gaurav Khandelwal (San Jose, CA); Jiangbin Luo (Cupertino, CA)
Assignee: Rubrik, Inc.
G06F11/1464G06F16/128G06F16/164G06F16/1844
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,045,139
App. No.
17/521,006
Granted
Jul 23, 2024
Kind
B2
Abstract

In some examples, a cluster protection system comprises at least one processor and a memory storing instructions which, when executed by the at least one processor, cause the system to perform operations comprising identifying a target cluster or an object in a container management framework, identifying application data and metadata associated with the target cluster or the object, generating a first snapshot of the target cluster or the object, the first snapshot including at least the metadata, storing the first snapshot in offsite cloud storage, generating a second snapshot of the target cluster, the second snapshot including at least the application data, and storing the second snapshot in a persistent volume in onsite storage.

Claims (40)

1. A method, comprising:

identifying a target cluster comprising one or more containers in a container management framework;

identifying application data and metadata associated with the one or more containers in the target cluster;

generating, at the target cluster, a first snapshot of the target cluster, the first snapshot including at least the metadata associated with the one or more containers;

storing the first snapshot in offsite cloud storage by moving the generated first snapshot from the target cluster to the offsite cloud storage;

generating, at the target cluster, a second snapshot of the target cluster, the second snapshot different from the first snapshot and including at least the application data associated with the one or more containers; and

storing the second snapshot in a persistent volume in onsite storage by moving the generated second snapshot from the target cluster to the persistent volume in the onsite storage.

2. The method of claim 1 , wherein the first snapshot further comprises resource data.

3. The method of claim 2 , wherein a resource to which the resource data relates includes a cluster controller.

4. The method of claim 3 , wherein the cluster controller controls a pod of containers.

5. The method of claim 1 , wherein the first snapshot further comprises a cluster configuration.

6. The method of claim 1 , wherein the first snapshot further comprises a persistent volume claim (PVC).

7. The method of claim 1 , further comprising receiving a restore request for the target cluster and, based on the received restore request, restoring the target cluster using the first snapshot and the second snapshot.

8. A system, comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the system to perform operations, comprising:

identifying a target cluster comprising one or more containers in a container management framework;

identifying application data and metadata associated with the one or more containers in the target cluster;

generating, at the target cluster, a first snapshot of the target cluster, the first snapshot including at least the metadata associated with the one or more containers;

storing the first snapshot in offsite cloud storage by moving the generated first snapshot from the target cluster to the offsite cloud storage;

generating, at the target cluster, a second snapshot of the target cluster, the second snapshot different from the first snapshot and including at least the application data associated with the one or more containers; and

storing the second snapshot in a persistent volume in onsite storage by moving the generated second snapshot from the target cluster to the persistent volume in the onsite storage.

9. The system of claim 8 , wherein the first snapshot further comprises resource data.

10. The system of claim 9 , wherein a resource to which the resource data relates includes a cluster controller.

11. The system of claim 10 , wherein the cluster controller controls a pod of containers.

12. The system of claim 9 , wherein the first snapshot further comprises a cluster configuration.

13. The system of claim 8 , wherein the first snapshot further comprises a persistent volume claim (PVC).

14. The system of claim 8 , wherein the operations further comprise receiving a restore request for the target cluster and, based on the received restore request, restoring the target cluster using the first snapshot and the second snapshot.

15. A non-transitory machine-readable medium comprising instructions that are executable to perform operations, comprising:

identifying a target cluster comprising one or more containers in a container management framework;

identifying application data and metadata associated with the one or more containers in the target cluster;

generating, at the target cluster, a first snapshot of the target cluster, the first snapshot including at least the metadata associated with the one or more containers;

storing the first snapshot in offsite cloud storage by moving the generated first snapshot from the target cluster to the offsite cloud storage;

generating, at the target cluster, a second snapshot of the target cluster, the second snapshot different from the first snapshot and including at least the application data associated with the one or more containers; and

storing the second snapshot in a persistent volume in onsite storage by moving the generated second snapshot from the target cluster to the persistent volume in the onsite storage.

16. The non-transitory machine-readable medium of claim 15 , wherein the first snapshot further comprises resource data.

17. The non-transitory machine-readable medium of claim 16 , wherein a resource to which the resource data relates includes a cluster controller.

18. The non-transitory machine-readable medium of claim 17 , wherein the cluster controller controls a pod of containers.

19. The non-transitory machine-readable medium of claim 16 , wherein the first snapshot further comprises a cluster configuration.

20. The non-transitory machine-readable medium of claim 15 , wherein the first snapshot further comprises a persistent volume claim (PVC).

Assignments (3)
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME NO. 60333/0323 Recorded Jun 13, 2025
From: GOLDMAN SACHS BDC, INC., AS COLLATERAL AGENT
To: RUBRIK, INC.
Reel/Frame 071565/0602 →
GRANT OF SECURITY INTEREST IN PATENT RIGHTS Recorded Jun 10, 2022
From: RUBRIK, INC.
To: GOLDMAN SACHS BDC, INC., AS COLLATERAL AGENT
Reel/Frame 060333/0323 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 15, 2021
From: MENEZES, GUILHERME VALE FERREIRA; PARK, NOHHYUN; DHARMAPRIKAR, ABHISHEK; SUBRAMANYAM, RAJATH; ZHOU, PIN; KHANDELWAL, GAURAV; LUO, JIANGBIN
To: RUBRIK, INC.
Reel/Frame 058112/0180 →
Cited By (1)
US 12,530,264