IP Library Granted Patent US 12,423,318
Granted Patent B2
US 12,423,318 · App. 18/395,449 · Granted Sep 23, 2025

Automated discovery of databases

Inventors: Kevin Rui Luo (Fremont, CA); Deepti Kochar (San Francisco, CA); Anshul Mohan Gupta (Sunnyvale, CA)
Assignee: Rubrik, Inc.
G06F16/25G06F3/0604G06F3/0647G06F3/067G06F9/3891G06F11/1451G06F11/1458G06F16/24573
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,423,318
App. No.
18/395,449
Granted
Sep 23, 2025
Kind
B2
Abstract

Techniques for database discovery are described. A networked computing system comprises a backup node cluster of a backup service in communication with a host database node cluster of a host, a host database at least initially undiscovered by the backup node cluster, one or more processors coupled with memory storing instructions that, when executed, perform operations comprising at least installing a backup agent on at least one node of the host database node cluster, registering the host at the backup service, based on the host registration, triggering a host database discovery process to discover the undiscovered database automatically, the discovery process including a discovery call, in response to the discovery call, receiving metadata relating to the discovered database, and communicating with the discovered database.

Claims (48)

1. A system, comprising:

a memory storing instructions; and

one or more processors coupled with the memory storing instructions that, when executed, perform operations comprising at least:

registering a host database at a backup service by connecting a backup node cluster to a host database node cluster;

triggering, based on host registration, an automatic host database discovery process to discover one or more undiscovered databases, the automatic host database discovery process using file metadata obtained by the host database node cluster;

discovering one or more databases based at least in part on one or more changes in the file metadata;

monitoring for changes in the one or more discovered databases based at least in part on changes in the file metadata; and

modifying a quantity of the one or more discovered databases based at least in part on the discovery of the one or more databases, wherein the modifying comprises adding or removing the one or more discovered databases from the host database node cluster.

2. The system of claim 1 , wherein modifying the quantity of the one or more discovered databases comprises:

adding or removing the one or more discovered databases from the host database node cluster in accordance with a periodicity, wherein the periodicity is based at least in part on the changes in the file metadata.

3. The system of claim 1 , wherein modifying the quantity of the one or more discovered databases comprises:

adding or removing the one or more discovered databases from the host database node cluster in real time based at least in part on the changes in the file metadata.

4. The system of claim 1 , wherein the operations further comprise:

installing a backup agent on at least one node of the host database node cluster, wherein the backup agent is associated with the backup service or a data management platform.

5. The system of claim 1 , wherein the host database is one of an Oracle, Linux, or AIX database and wherein a backup agent is supported to run on the host database.

6. The system of claim 1 , wherein the host database node cluster includes a Real Application Cluster (RAC).

7. The system of claim 1 , wherein the operations further comprise:

displaying the changes in the file metadata of one or more files in the host database on a user interface.

8. A method, comprising:

registering a host database at a backup service by connecting a backup node cluster to a host database node cluster;

triggering, based on host registration, an automatic host database discovery process to discover one or more undiscovered databases, the automatic host database discovery process using file metadata obtained by the host database node cluster;

discovering one or more databases based at least in part on one or more changes in the file metadata;

monitoring for changes in the one or more discovered databases based at least in part on changes in the file metadata; and

modifying a quantity of the one or more discovered databases based at least in part on the discovery of the one or more databases, wherein the modifying comprises adding or removing the one or more discovered databases from the host database node cluster.

9. The method of claim 8 , wherein modifying the quantity of the one or more discovered databases comprises:

adding or removing the one or more discovered databases from the host database node cluster in accordance with a periodicity, wherein the periodicity is based at least in part on the changes in the file metadata.

10. The method of claim 8 , wherein modifying the quantity of the one or more discovered databases comprises:

adding or removing the one or more discovered databases from the host database node cluster in real time based at least in part on the changes in the file metadata.

11. The method of claim 8 , further comprising:

installing a backup agent on at least one node of the host database node cluster, wherein the backup agent is associated with the backup service or a data management platform.

12. The method of claim 8 , wherein the host database is one of an Oracle, Linux, or AIX database and wherein a backup agent is supported to run on the host database.

13. The method of claim 8 , wherein the host database node cluster includes a Real Application Cluster (RAC).

14. The method of claim 8 , further comprising:

displaying the one or more changes in the file metadata in the host database on a user interface.

15. A non-transitory machine-readable medium including instructions, which when read by a machine, cause the machine to perform operations comprising:

registering a host database at a backup service by connecting a backup node cluster to a host database node cluster;

triggering, based on host registration, an automatic host database discovery process to discover one or more undiscovered databases, the automatic host database discovery process using file metadata obtained by the host database node cluster;

discovering one or more databases based at least in part on one or more changes in the file metadata;

monitoring for changes in the one or more discovered databases based at least in part on changes in the file metadata; and

modifying a quantity of the one or more discovered databases based at least in part on the discovery of the one or more databases, wherein the modifying comprises adding or removing the one or more discovered databases from the host database node cluster.

16. The non-transitory machine-readable medium of claim 15 , wherein modifying the quantity of the one or more discovered databases comprises:

adding or removing the one or more discovered databases from the host database node cluster in accordance with a periodicity, wherein the periodicity is based at least in part on the changes in the file metadata.

17. The non-transitory machine-readable medium of claim 15 , wherein modifying the quantity of the one or more discovered databases comprises:

adding or removing the one or more discovered databases from the host database node cluster in real time based at least in part on the changes in the file metadata.

18. The non-transitory machine-readable medium of claim 15 , wherein the operations further comprise:

installing a backup agent on at least one node of the host database node cluster, wherein the backup agent is associated with the backup service or a data management platform.

19. The non-transitory machine-readable medium of claim 15 , wherein the host database is one of an Oracle, Linux, or AIX database and wherein a backup agent is supported to run on the host database.

20. The non-transitory machine-readable medium of claim 15 , wherein the operations further comprise displaying the one or more changes in the file metadata of one or more files in the host database on a user interface.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 31, 2025
From: LUO, KEVIN RUI; KOCHAR, DEEPTI; GUPTA, ANSHUL MOHAN
To: RUBRIK, INC.
Reel/Frame 070072/0817 →
Continuity (3)
Continuation 18094333 · Jan 6, 2023
Continuation 16728494 · Dec 27, 2019
Related Publication 20240126772A1 · Apr 18, 2024
References Cited (17)
US 10146631B1 · Pradeep · 2018 [cited by examiner]
US 10819557B1 · Epshtein et al. · 2020 [cited by applicant]
US 11157367B1 · Chockalingam et al. · 2021 [cited by applicant]
US 11340996B2 · Luo et al. · 2022 [cited by applicant]
US 11550807B2 · Luo et al. · 2023 [cited by applicant]
US 11561994B2 · Luo et al. · 2023 [cited by applicant]
US 20060101340A1 · Sridhar et al. · 2006 [cited by applicant]
US 20090327630A1 · Akamatsu et al. · 2009 [cited by applicant]
US 20160188898A1 · Karinta et al. · 2016 [cited by applicant]
US 20170206199A1 · Umamageswaran et al. · 2017 [cited by applicant]
US 20170366624A1 · Tsang et al. · 2017 [cited by applicant]
US 20200042395A1 · Chu · 2020 [cited by examiner]
US 20200264957A1 · Bajaj et al. · 2020 [cited by applicant]
US 20210200643A1 · Luo et al. · 2021 [cited by applicant]
US 20210200645A1 · Luo et al. · 2021 [cited by applicant]
US 20210200779A1 · Luo et al. · 2021 [cited by applicant]
Rubrik and Vmware; “Reference Architecture Rubrik and VMware vSphere”, https://www.rubrik.com/content/dam/rubrik/en/resources/white-paper/reference-architecture-Rubrik-and-VMware-vSphere.pdf, total 44 pages, Jul. 2018. [cited by applicant]