IP Library › Granted Patent US 12,699,633
Granted Patent B2
US 12,699,633 · App. 18/957,564 · Granted Aug 4, 2026

Utilizing a tablespace to export to a native database recovery environment

Inventors: Snehal Arvind Khandkar (Palo Alto, CA); Yongbing Guo (Saratoga, CA); Udbhav Prasad (Mountain View, CA)
Assignee: Rubrik, Inc.
G06F11/1469G06F16/2282G06F16/27G06F2201/80G06F2201/82G06Q10/0838
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,699,633
App. No.
18/957,564
Filed
Nov 22, 2024
Granted
Aug 4, 2026
Kind
B2
Examiner
WOO, ISAAC M
Art Unit
2163
USPC
707/675
Abstract

Systems and methods to utilize a tablespace to export to a native database recovery environment are described. The system receives file information and script information at a source host that operates in a native database recovery environment. The file information and the script information are received from a backup host that utilizes foreign snapshot files and foreign incremental files for storing the file information. The file information includes native snapshot files and native incremental files. The script information includes one or more scripts that execute, at the source host, to perform operations comprising: mounting the directories; opening an auxiliary database; restoring a tablespace in the auxiliary database; recovering the tablespace in the auxiliary database based on the native incremental files; exporting the tablespace metadata information from the auxiliary database; recovering the tablespace in the database based on the tablespace metadata information; and unmounting the directories.

Claims (58)

1 . An apparatus, comprising:

at least one processor;

memory coupled to the at least one processor; and

instructions stored in the memory, wherein the instructions are executable by the at least one processor to:

receive, at a foreign database recovery environment, export information that indicates an identifier of a tablespace and a point-in-time to which the tablespace is to be recovered, wherein the tablespace is stored at a native database in a native database recovery environment;

execute a job at a backup host operating in the foreign database recovery environment based on the export information, wherein the instructions to execute the job are executable by the at least one processor to:

generate script information based on the export information, the script information comprising scripts for recovering the tablespace at the point-in-time in the native database recovery environment; and

retrieve file information that comprises snapshot files and incremental files associated with the native database in which the tablespace is stored; and

export the file information and the script information from the backup host to a source host operating in the native database recovery environment.

2 . The apparatus of claim 1 , wherein, to retrieve the file information, the instructions are executable by the at least one processor to cause the apparatus to:

retrieve the snapshot files and the incremental files from one or more databases in the foreign database recovery environment based on using the identifier of the tablespace to query the one or more databases.

3 . The apparatus of claim 1 , wherein the instructions are further executable by the at least one processor to cause the apparatus to:

receive, after exporting the file information and the script information to the source host, one or more images of the native database from the source host; and

generate updated snapshot files and incremental files for the native database based on the one or more images received from the source host.

4 . The apparatus of claim 1 , the instructions are further executable by the at least one processor to cause the apparatus to:

establish a connection between the source host and the backup host via one or more directories, wherein the file information and the script information are exported to the source host using the established connection.

5 . The apparatus of claim 1 , wherein:

the snapshot files comprise images of files and directories stored in the native database; and

the incremental files indicate changes made to the native database between a first point-in-time and a second point-in-time.

6 . The apparatus of claim 1 , wherein:

the source host comprises a first set of one or more virtual machines operating in the native database recovery environment; and

the backup host comprises a second set of one or more virtual machines operating in the foreign database recovery environment.

7 . The apparatus of claim 1 , wherein the foreign database recovery environment is configured to provide backup and recovery services for the native database recovery environment.

8 . The apparatus of claim 1 , wherein the foreign database recovery environment is different from the native database recovery environment.

9 . A computer-implemented method, comprising:

receiving, at a foreign database recovery environment, export information that indicates an identifier of a tablespace and a point-in-time to which the tablespace is to be recovered, wherein the tablespace is stored at a native database in a native database recovery environment;

executing a job at a backup host operating in the foreign database recovery environment based on the export information, wherein executing the job further comprises:

generating script information based on the export information, the script information comprising scripts for recovering the tablespace at the point-in-time in the native database recovery environment; and

retrieving file information that comprises snapshot files and incremental files associated with the native database in which the tablespace is stored; and

exporting the file information and the script information from the backup host to a source host operating in the native database recovery environment.

10 . The computer-implemented method of claim 9 , wherein retrieving the file information comprises:

retrieving the snapshot files and the incremental files from one or more databases in the foreign database recovery environment based on using the identifier of the tablespace to query the one or more databases.

11 . The computer-implemented method of claim 9 , further comprising:

receiving, after exporting the file information and the script information to the source host, one or more images of the native database from the source host; and

generating updated snapshot files and incremental files for the native database based on the one or more images received from the source host.

12 . The computer-implemented method of claim 9 , further comprising:

establishing a connection between the source host and the backup host via one or more directories, wherein the file information and the script information are exported to the source host using the established connection.

13 . The computer-implemented method of claim 9 , wherein:

the snapshot files comprise images of files and directories stored in the native database; and

the incremental files indicate changes made to the native database between a first point-in-time and a second point-in-time.

14 . The computer-implemented method of claim 9 , wherein:

the source host comprises a first set of one or more virtual machines operating in the native database recovery environment; and

the backup host comprises a second set of one or more virtual machines operating in the foreign database recovery environment.

15 . The computer-implemented method of claim 9 , wherein the foreign database recovery environment is configured to provide backup and recovery services for the native database recovery environment.

16 . The computer-implemented method of claim 9 , wherein the foreign database recovery environment is different from the native database recovery environment.

17 . A non-transitory computer-readable medium storing code, the code comprising instructions executable by at least one processor to:

receive, at a foreign database recovery environment, export information that indicates an identifier of a tablespace and a point-in-time to which the tablespace is to be recovered, wherein the tablespace is stored at a native database in a native database recovery environment;

execute a job at a backup host operating in the foreign database recovery environment based on the export information, wherein the instructions to execute the job are executable by the at least one processor to:

generate script information based on the export information, the script information comprising scripts for recovering the tablespace at the point-in-time in the native database recovery environment; and

retrieve file information that comprises snapshot files and incremental files associated with the native database in which the tablespace is stored; and

export the file information and the script information from the backup host to a source host operating in the native database recovery environment.

18 . The non-transitory computer-readable medium of claim 17 , wherein, to retrieve the file information, the instructions are executable by the at least one processor to:

retrieve the snapshot files and the incremental files from one or more databases in the foreign database recovery environment based on using the identifier of the tablespace to query the one or more databases.

19 . The non-transitory computer-readable medium of claim 17 , wherein the instructions are further executable by the at least one processor to:

receive, after exporting the file information and the script information to the source host, one or more images of the native database from the source host; and

generate updated snapshot files and incremental files for the native database based on the one or more images received from the source host.

20 . The non-transitory computer-readable medium of claim 17 , wherein the instructions are further executable by the at least one processor to:

establish a connection between the source host and the backup host via one or more directories, wherein the file information and the script information are exported to the source host using the established connection.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 21, 2025
From: KHANDKAR, SNEHAL ARVIND; GUO, YONGBING; PRASAD, UDBHAV
To: RUBRIK, INC.
Reel/Frame 070582/0204 →
Continuity (3)
Division 17820288 · Aug 17, 2022
Continuation 16777001 · Jan 30, 2020
Related Publication 20250086070A1 · Mar 13, 2025
References Cited (62)
US 5857208A · Ofek · 1999 [cited by applicant]
US 6061769A · Kapulka et al. · 2000 [cited by applicant]
US 6785786B1 · Gold et al. · 2004 [cited by applicant]
US 6847983B2 · Somalwar et al. · 2005 [cited by applicant]
US 7099900B1 · Bromley et al. · 2006 [cited by applicant]
US 7406473B1 · Brassow et al. · 2008 [cited by applicant]
US 7873601B1 · Kushwah · 2011 [cited by applicant]
US 7937547B2 · Liu et al. · 2011 [cited by applicant]
US 8364648B1 · Sim-Tang · 2013 [cited by applicant]
US 9444811B2 · Nara et al. · 2016 [cited by applicant]
US 10474539B1 · Yadav et al. · 2019 [cited by applicant]
US 10649952B1 · Chakankar et al. · 2020 [cited by applicant]
US 10664356B1 · Ugur-Ozekinci · 2020 [cited by examiner]
US 10795777B1 · Goyal · 2020 [cited by applicant]
US 10936545B1 · Chockalingam et al. · 2021 [cited by applicant]
US 11194761B2 · Khandkar et al. · 2021 [cited by applicant]
US 11232002B2 · Upadhyay et al. · 2022 [cited by applicant]
US 20020120785A1 · Somalwar et al. · 2002 [cited by applicant]
US 20030200480A1 · Beattie · 2003 [cited by applicant]
US 20050278394A1 · Oks et al. · 2005 [cited by applicant]
US 20060235905A1 · Kapur · 2006 [cited by applicant]
US 20070185922A1 · Kapoor et al. · 2007 [cited by applicant]
US 20070294274A1 · Kano · 2007 [cited by applicant]
US 20090089313A1 · Cooper et al. · 2009 [cited by applicant]
US 20110218968A1 · Liu et al. · 2011 [cited by applicant]
US 20120323854A1 · Schreter · 2012 [cited by applicant]
US 20130117554A1 · Ylonen · 2013 [cited by applicant]
US 20130232245A1 · Antosz et al. · 2013 [cited by applicant]
US 20140095452A1 · Lee et al. · 2014 [cited by applicant]
US 20140325267A1 · Liu et al. · 2014 [cited by applicant]
US 20150019494A1 · Griffith et al. · 2015 [cited by applicant]
US 20160085543A1 · Islam et al. · 2016 [cited by applicant]
US 20160117228A1 · Farlee et al. · 2016 [cited by applicant]
US 20160132400A1 · Pawar et al. · 2016 [cited by applicant]
US 20160147613A1 · Schefe et al. · 2016 [cited by applicant]
US 20160154707A1 · Kumarasamy et al. · 2016 [cited by applicant]
US 20170075765A1 · Chen · 2017 [cited by applicant]
US 20170185431A1 · Lv et al. · 2017 [cited by applicant]
US 20180060181A1 · Rajamani et al. · 2018 [cited by applicant]
US 20180096068A1 · Venkataramanappa et al. · 2018 [cited by applicant]
US 20180246650A1 · Nara et al. · 2018 [cited by applicant]
US 20190065322A1 · Chakankar et al. · 2019 [cited by applicant]
US 20190155699A1 · Luo et al. · 2019 [cited by applicant]
US 20190288915A1 · Denyer et al. · 2019 [cited by applicant]
US 20200042395A1 · Chu et al. · 2020 [cited by applicant]
US 20200233840A1 · Chakankar et al. · 2020 [cited by applicant]
US 20210182159A1 · Srinivasan et al. · 2021 [cited by applicant]
US 20210240579A1 · Khandkar et al. · 2021 [cited by applicant]
US 20210240580A1 · Khandkar et al. · 2021 [cited by applicant]
US 20210240581A1 · Khandkar et al. · 2021 [cited by applicant]
US 20210240582A1 · Khandkar et al. · 2021 [cited by applicant]
US 20210240660A1 · Khandkar et al. · 2021 [cited by applicant]
US 20210240661A1 · Khandkar et al. · 2021 [cited by applicant]
US 20220188194A1 · Liu et al. · 2022 [cited by applicant]
WO 9912098A1 · 1999 [cited by applicant]
WO 2005111867A2 · 2005 [cited by applicant]
WO 2011002777A2 · 2011 [cited by applicant]
WO 2012092325A1 · 2012 [cited by applicant]
WO 2014052851A1 · 2014 [cited by applicant]
Cohesity, Explaining Cohesity's Space-Efficient Target and Source-Side Dedupe Integration for Oracle RMAN, Jan. 4, 2018, URL: https://www.cohesity.com/blogs/explaining-cohesitys-space-efficient-target-source-side-dedupe… [cited by applicant]
Cohesity, Oracle Database Protection and Recovery with RMAN, Dec. 27, 2017, URL: https://www.cohesity.com/blogs/title-streamlining-oracle-database-protection-recovery-cohesity-oracle-rman/, 5 pages. [cited by applicant]
Son et al., “SSD-Assisted Backup and recovery for Database Systems”, IEEE 33rd International Conference on Data Engineering (ICDE), Apr. 2017, pp. 285-296. [cited by applicant]