IP Library Granted Patent US 12,158,820
Granted Patent B2
US 12,158,820 · App. 17/746,256 · Granted Dec 3, 2024

Extended recovery of an exported database

Inventors: Snehal Arvind Khandkar (Palo Alto, CA); Yongbing Guo (Saratoga, CA); Udbhav Prasad (Mountain View, CA); Ganesh Karuppur Rajagopalan (Los Gatos, CA); Pandian Raju (Sunnyvale, CA)
Assignee: Rubrik, Inc.
G06F11/1469G06F11/1451G06F2201/80G06F2201/82G06F2201/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,158,820
App. No.
17/746,256
Granted
Dec 3, 2024
Kind
B2
Abstract

Systems and methods for an extended recovery of an exported database are described. The method includes communicating a database from a source host operating in a native database recovery environment, the database being communicated to a backup host operating in a foreign database recovery environment, the native database recovery environment including native snapshot files and native incremental files for storing the database, the foreign database recovery environment including foreign snapshot files and foreign incremental files for storing the database. The method further includes receiving file information and script information, at the source host, the file information including the native snapshot files and the native incremental files, the script to perform operations for causing a recovering of the database in the foreign database recovery environment based on the changes to the database in the foreign database recovery environment after the point-in-time.

Claims (50)

1. A system, comprising:

at least one processor and memory storing instructions that are executable by the at least one processor to perform operations comprising:

communicating data associated with an image of a database from a source host operating in a native database recovery environment to a backup host operating in a foreign database recovery environment; and

receiving file information and script information at the source host from the backup host, wherein the file information comprises snapshot files and incremental files associated with the data associated with the image of database, wherein the script information is based at least in part on template information exported from the source host, and wherein the script information comprises one or more scripts executable by the source host to perform operations comprising:

causing, based at least in part on execution of the one or more scripts received at the source host from the backup host, a recovery of the database to a point-in-time based on the snapshot files and the incremental files,

causing, based at least in part on execution of the one or more scripts received at the source host from the backup host, an identification of changes to the database after the point-in-time, and

causing, based at least in part on execution of the one or more scripts received at the source host from the backup host, and after the recovery of the database to the point-in-time based on the snapshot files and the incremental files, a recovery of the database to a time after the point-in-time based on the changes to the database after the point-in-time.

2. The system of claim 1 , wherein the data associated with the image of the database comprises foreign snapshot files and foreign incremental files.

3. The system of claim 1 , wherein:

the script information comprises a first script that is based on a first template, the first template comprises plug-in value information, and

the plug-in value information comprises the point-in-time and a database name identifying the database.

4. The system of claim 1 , wherein the instructions are executable by the at least one processor to perform further operations comprising:

materializing native snapshot files and native incremental files based on the snapshot files and the incremental files, respectively.

5. The system of claim 1 , wherein the instructions are executable by the at least one processor to perform further operations comprising:

receiving, from the backup host, data associated with the changes to the database after the point-in-time.

6. The system of claim 1 , wherein the system is configured to use a control file to recover the database to the point-in-time, the control file comprising a name for the database.

7. The system of claim 1 , wherein the database is a standalone database and the source host comprises a single node.

8. The system of claim 1 , wherein:

the source host comprises a plurality of nodes configured to store a cluster database, the plurality of nodes comprises a first node and additional nodes, and the system is configured to recover the database on the first node.

9. The system of claim 8 , wherein the instructions are executable by the at least one processor to perform further operations comprising:

opening instances of the database on the additional nodes; and

copying the database from the first node to the additional nodes.

10. A method comprising:

communicating data associated with an image of a database from a source host operating in a native database recovery environment to a backup host operating in a foreign database recovery environment; and

receiving file information and script information at the source host from the backup host, wherein the file information comprises snapshot files and incremental files associated with the data associated with the image of database, wherein the script information is based at least in part on template information exported from the source host, and wherein the script information comprises one or more scripts executable by the source host to perform operations comprising:

causing, based at least in part on execution of the one or more scripts received at the source host from the backup host, a recovery of the database to a point-in-time based on the snapshot files and the incremental files,

causing, based at least in part on execution of the one or more scripts received at the source host from the backup host, an identification of changes to the database after the point-in-time, and

causing, based at least in part on execution of the one or more scripts received at the source host from the backup host, and after the recovery of the database to the point-in-time based on the snapshot files and the incremental files, a recovery of the database to a time after the point-in-time based on the changes to the database after the point-in-time.

11. The method of claim 10 , wherein the data associated with the image of the database comprises foreign snapshot files and foreign incremental files.

12. The method of claim 10 , wherein:

the script information comprises a first script that is based on a first template, the first template comprises plug-in value information, and

the plug-in value information comprises the point-in-time and a database name identifying the database.

13. The method of claim 10 , further comprising:

materializing native snapshot files and native incremental files based on the snapshot files and the incremental files, respectively.

14. The method of claim 10 , further comprising:

receiving, from the backup host, data associated with the changes to the database after the point-in-time.

15. The method of claim 10 , wherein a control file is used to recover the database to the point-in-time, the control file comprising a name for the database.

16. The method of claim 10 , wherein the database is a standalone database and the source host comprises a single node.

17. The method of claim 10 , wherein:

the source host comprises a plurality of nodes configured to store a cluster database, the plurality of nodes comprises a first node and additional nodes, and the database is recovered on the first node.

18. The method of claim 17 , further comprising:

opening instances of the database on the additional nodes; and

copying the database from the first node to the additional nodes.

19. A machine-storage medium storing instructions that are executable by at least one processor to perform operations comprising:

communicating data associated with an image of a database from a source host operating in a native database recovery environment to a backup host operating in a foreign database recovery environment; and

receiving file information and script information at the source host from the backup host, wherein the file information comprises snapshot files and incremental files associated with the data associated with the image of database, wherein the script information is based at least in part on template information exported from the source host, and wherein the script information comprises one or more scripts executable by the source host to perform operations comprising:

causing, based at least in part on execution of the one or more scripts received at the source host from the backup host, a recovery of the database to a point-in-time based on the snapshot files and the incremental files,

causing, based at least in part on execution of the one or more scripts received at the source host from the backup host, an identification of changes to the database after the point-in-time, and

causing, based at least in part on execution of the one or more scripts received at the source host from the backup host, and after the recovery of the database to the point-in-time based on the snapshot files and the incremental files, a recovery of the database to a time after the point-in-time based on the changes to the database after the point-in-time.

20. The machine-storage medium of claim 19 , wherein the data associated with the image of the database comprises foreign snapshot files and foreign incremental files.

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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 29, 2022
From: KHANDKAR, SNEHAL ARVIND; GUO, YONGBING; PRASAD, UDBHAV; RAJAGOPALAN, GANESH KARUPPUR; RAJU, PANDIAN
To: RUBRIK, INC.
Reel/Frame 061901/0979 →
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 →
Continuity (2)
Continuation 16777083 · Jan 30, 2020
Related Publication 20220276937A1 · Sep 1, 2022