IP Library Granted Patent US 12,306,722
Granted Patent B2
US 12,306,722 · App. 17/710,714 · Granted May 20, 2025

Blockchain for cloud data management

Inventors: Chendil Kumar Arumugam (Bengaluru, IN); Aditi Maheshwari (Jaipur, IN); Animesh Kumar (Navi Mumbai, IN)
Assignee: Rubrik, Inc.
G06F11/1458H04L9/3242G06F2201/84
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,306,722
App. No.
17/710,714
Granted
May 20, 2025
Kind
B2
Abstract

A method for data management is described. The method may include generating a first snapshot of a first state of a data object, generating, using metadata associated with the first snapshot of the first state, a first hash value, and storing the first hash value to a blockchain. If the data object or device or system supporting the data object fails, then a failover procedure may be used to recover the data object. The method may include receiving an instruction to recover the first state of the data object using the first snapshot, retrieving the first hash value from the blockchain, comparing the first hash value retrieved from the blockchain to a second hash value of the metadata associated with the first snapshot, and determining, based at least in part on a result of the comparing, whether the first snapshot stored in the data management system is unmodified.

Claims (62)

1. A method for data management, comprising:

generating a first snapshot of a first state of a data object managed by a data management system;

storing metadata associated with the first snapshot of the first state in a row of a backup metadata table for the data object;

generating, using the metadata stored in the row of the backup metadata table associated with the first snapshot of the first state, a first hash value;

storing the first hash value to a blockchain;

storing, in the row of the backup metadata table, information indicative of a location of the first hash value as stored to the blockchain;

receiving an instruction to recover the first state of the data object using the first snapshot;

retrieving, using the information indicative of the location, the first hash value from the blockchain based at least in part on the instruction to recover the first state of the data object using the first snapshot;

comparing the first hash value retrieved from the blockchain to a second hash value of the row of the backup metadata table associated with the first snapshot; and

determining, based at least in part on a result of the comparing, whether the first snapshot stored in the data management system is unmodified.

2. The method of claim 1 , further comprising:

storing, to the blockchain, a key associated with the first snapshot, wherein the key is stored to the blockchain in association with the first hash value;

retrieving, based at least in part on the instruction to recover the first state, the key from the blockchain; and

decrypting the first snapshot using the key retrieved from the blockchain.

3. The method of claim 1 , wherein generating the first snapshot comprises:

generating the first snapshot of the data object by a storage appliance of the data management system that manages the data object.

4. The method of claim 1 , wherein the metadata stored in the row of the backup metadata table comprises one or more identifiers associated with the data object, a customer number associated with the data object, a user number associated with the data object, a username associated with the data object, an additional hash value associated with the data object, a timestamp associated with the data object, a time stamp associated with generation of the first hash value, a time stamp associated with generation of the additional hash value, or any combination thereof.

5. The method of claim 1 , wherein the metadata associated with the first snapshot comprises one or more unique identifiers for a plurality of files of the data object.

6. The method of claim 1 , wherein the first hash value is generated based exclusively on one or more inputs that exclude an image captured by the first snapshot, the one or more inputs comprising the metadata associated with the first snapshot.

7. The method of claim 1 , wherein the blockchain is a private blockchain managed by the data management system.

8. The method of claim 1 , wherein:

the first snapshot is of an immutable template file of the data object; and

the first hash value is generated based at least in part on the immutable template file.

9. The method of claim 8 , wherein the data object is a virtual machine, a virtual disc, a hard disc drive, a server, a virtual desktop, or any combination thereof.

10. The method of claim 8 , wherein the immutable template file comprises network certificates, network configurations, server configurations, application configurations, operating system configurations, or any combination thereof.

11. An apparatus for data management, comprising:

a processor;

memory coupled with the processor; and

instructions stored in the memory and executable by the processor to cause the apparatus to:

generate a first snapshot of a first state of a data object managed by a data management system;

store metadata associated with the first snapshot of the first state in a row of a backup metadata table for the data object;

generate, using the metadata stored in the row of the backup metadata table associated with the first snapshot of the first state, a first hash value;

store the first hash value to a blockchain;

store, in the row of the backup metadata table, information indicative of a location of the first hash value as stored to the blockchain;

receive an instruction to recover the first state of the data object using the first snapshot;

retrieve, using the information indicative of the location, the first hash value from the blockchain based at least in part on the instruction to recover the first state of the data object using the first snapshot;

compare the first hash value retrieved from the blockchain to a second hash value of the row of the backup metadata table associated with the first snapshot; and

determine, based at least in part on a result of the comparing, whether the first snapshot stored in the data management system is unmodified.

12. The apparatus of claim 11 , wherein the instructions are further executable by the processor to cause the apparatus to:

store, to the blockchain, a key associated with the first snapshot, wherein the key is stored to the blockchain in association with the first hash value;

retrieve, based at least in part on the instruction to recover the first state, the key from the blockchain; and

decrypt the first snapshot using the key retrieved from the blockchain.

13. The apparatus of claim 11 , wherein, to generate the first snapshot, the instructions are executable by the processor to cause the apparatus to:

generate the first snapshot of the data object by a storage appliance of the data management system that manages the data object.

14. The apparatus of claim 11 , wherein the metadata stored in the row of the backup metadata table comprises one or more identifiers associated with the data object, a customer number associated with the data object, a user number associated with the data object, a username associated with the data object, an additional hash value associated with the data object, a timestamp associated with the data object, a time stamp associated with generation of the first hash value, a time stamp associated with generation of the additional hash value, or any combination thereof.

15. The apparatus of claim 11 , wherein the metadata associated with the first snapshot comprises one or more unique identifiers for a plurality of files of the data object.

16. The apparatus of claim 11 , wherein the first hash value is generated based exclusively on one or more inputs that exclude an image captured by the first snapshot, the one or more inputs comprising the metadata associated with the first snapshot.

17. The apparatus of claim 11 , wherein:

the first snapshot is of an immutable template file of the data object; and

the first hash value is generated based at least in part on the immutable template file.

18. The apparatus of claim 17 , wherein the data object is a virtual machine, a virtual disc, a hard disc drive, a server, a virtual desktop, or any combination thereof.

19. The apparatus of claim 17 , wherein the immutable template file comprises network certificates, network configurations, server configurations, application configurations, operating system configurations, or any combination thereof.

20. A non-transitory computer-readable medium storing code for data management, the code comprising instructions executable by a processor to:

generate a first snapshot of a first state of a data object managed by a data management system;

store metadata associated with the first snapshot of the first state in a row of a backup metadata table for the data object;

generate, using the metadata stored in the row of the backup metadata table associated with the first snapshot of the first state, a first hash value;

store the first hash value to a blockchain;

store, in the row of the backup metadata table, information indicative of a location of the first hash value as stored to the blockchain;

receive an instruction to recover the first state of the data object using the first snapshot;

retrieve, using the information indicative of the location, the first hash value from the blockchain based at least in part on the instruction to recover the first state of the data object using the first snapshot;

compare the first hash value retrieved from the blockchain to a second hash value of the row of the backup metadata table associated with the first snapshot; and

determine, based at least in part on a result of the comparing, whether the first snapshot stored in the data management system is unmodified.

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 Mar 31, 2022
From: ARUMUGAM, CHENDIL KUMAR; MAHESHWARI, ADITI; KUMAR, ANIMESH
To: RUBRIK, INC.
Reel/Frame 059465/0271 →
Continuity (1)
Related Publication 20230315579A1 · Oct 5, 2023
References Cited (8)
US 9152686B2 · Whitehead · 2015 [cited by examiner]
US 9158630B1 · Natanzon · 2015 [cited by applicant]
US 10628268B1 · Baruch et al. · 2020 [cited by applicant]
US 11334443B1 · Aseev · 2022 [cited by examiner]
US 20180322160A1 · Horii · 2018 [cited by examiner]
US 20210117385A1 · Haldar · 2021 [cited by examiner]
US 20210149775A1 · Novotny · 2021 [cited by examiner]
Kalis et al., Validating Data Integrity with Blockchain, 2018 IEEE International Conference on Cloud Computing Technology and Science (CloudCom), Dec. 10-13, 2018, DOI: 10.1109/CloudCom2018.2018.00060, 6 pgs. [cited by applicant]
Cited By (1)
US 12,556,604