Granted Patent B2

US 12,572,559 · App. 18/648,055 · Granted Mar 10, 2026

Inventors: Yashesh Mankad (Sunnyvale, CA); Kamaldeep Khanuja (Dublin, CA); Manish Pratap Singh (Cupertino, CA)

Assignee: Nutanix, Inc.

G06F16/27

Abstract

Claims (48)

1 . A system comprising:

a highly available database server comprising a processor and a memory, the highly available database server including:

a first instance of the database server in a first availability zone of a virtual computing system; and

a second instance of the database server in a second availability zone of the virtual computing system different from the first availability zone;

a highly available administration database including:

a first instance of an administration database in a third availability zone, wherein the first instance of the administration database is configured to store metadata and configuration data for managing at least one customer database; and

a second instance of the administration database in a fourth availability zone different from the third availability zone, wherein the second instance of the administration database is synchronized with the first instance of the administration database to maintain consistency of metadata and configuration data,

wherein the highly available database server and the highly available administration database are configured to manage at least one customer database, wherein the first instance of the database server is located on a first virtual entity in the first availability zone and the first instance of the administration database is located on a second virtual entity in the third availability zone; and

a first proxy in the first availability zone to facilitate communication between a leader database server and the highly available administration database, wherein the leader database server is selected from the first instance of the database server and the second instance of the database server.

2 . The system of claim 1 , wherein the third availability zone is the first availability zone, and wherein the fourth availability zone is the second availability zone.

3 . The system of claim 1 , wherein the third availability zone is one of the first availability zone, the second availability zone, and an additional availability zone.

4 . The system of claim 1 , further comprising:

a second proxy in the second availability zone to facilitate communication between a leader database server and the administration database when the first proxy fails.

5 . The system of claim 1 , wherein the first instance of the database server is a primary database server and the second instance of the database server is a secondary database server, and wherein the second instance of the database server becomes the primary database server upon the first instance of the database server becoming unavailable.

6 . The system of claim 1 , further comprising a consensus keeper configured to record state transitions in the first instance of the administration database and the second instance of the administration database.

7 . The system of claim 2 , wherein the highly available database server and the highly available administration database are configured to redirect database management operations to ensure continuity in response to failure conditions in any availability zone.

8 . The system of claim 1 , wherein resource allocation for the first and second instances of the database server and administration database is dynamically adjusted based on system load or failure conditions.

9 . A method comprising:

creating a highly available database server by:

creating a first instance of the database server in a first availability zone of

a virtual computing system; and

creating a second instance of the database server in a second availability zone of the virtual computing system different from the first availability zone; creating a highly available administration database by:

creating a first instance of an administration database in a third availability zone, wherein the first instance of the administration database is configured to store metadata and configuration data for managing at least one customer database;

creating a second instance of the administration database in a fourth availability zone different from the third availability zone, wherein the second instance of the administration database is synchronized with the first instance of the administration database to maintain consistency of metadata and configuration data,

wherein the highly available database server and the highly available administration database are configured to manage at least one customer database, wherein the first instance of the database server is located on a first virtual entity in the first availability zone and the first instance of the administration database is located on a second virtual entity in the third availability zone; and

creating a first proxy in the first availability zone to facilitate communication between a leader database server and the highly available administration database, wherein the leader database server is selected from the first instance of the database server and the second instance of the database server.

10 . The method of claim 9 , wherein the third availability zone is the first availability zone, and wherein the fourth availability zone is the second availability zone.

11 . The method of claim 9 , wherein the third availability zone is one of the first availability zone, the second availability zone, and an additional availability zone.

12 . The method of claim 9 , further comprising:

creating a second proxy in the second availability zone to facilitate communication between a leader database server and the administration database when the first proxy fails.

13 . The method of claim 9 , wherein the first instance of the database server is a primary database server and the second instance of the database server is a secondary database server, wherein the second instance of the database server becomes the primary database server upon the first instance of the database server becoming unavailable.

14 . The method of claim 9 , further comprising creating a consensus keeper configured to record state transitions in the first instance of the administration database and the second instance of the administration database.

15 . The method of claim 9 , further comprising redirecting database management operations to ensure continuity in response to failure conditions in any availability zone.

16 . The method of claim 9 , wherein resource allocation for the first and second instances of the database server and administration database is dynamically adjusted based on system load or failure conditions.

17 . A non-transitory, computer-readable medium comprising computer-readable instructions stored thereon that when executed by one or more processors cause the one or more processors to:

create a highly available database server by:

creating a first instance of the database server in a first availability zone of a virtual computing system; and

creating a second instance of the database server in a second availability zone of the virtual computing system different from the first availability zone; create a highly available administration database by:

creating a first instance of an administration database in a third availability zone, wherein the first instance of the administration database is configured to store metadata and configuration data for managing at least one customer database;

creating a second instance of the administration database in a fourth availability zone different from the third availability zone, wherein the second instance of the administration database is synchronized with the first instance of the administration database to maintain consistency of metadata and configuration data;

wherein the highly available database server and the highly available administration database are configured to manage at least one customer database, wherein the first instance of the database server is located on a first virtual entity in the first availability zone and the first instance of the administration database is located on a second virtual entity in the third availability zone; and

create a first proxy in the first availability zone to facilitate communication between a leader database server and the highly available administration database, wherein the leader database server is selected from the first instance of the database server and the second instance of the database server.

18 . The non-transitory, computer-readable medium of claim 17 , wherein the third availability zone is the first availability zone, and wherein the fourth availability zone is the second availability zone.

19 . The non-transitory, computer-readable medium of claim 17 , wherein the third availability zone is one of the first availability zone, the second availability zone, and an additional availability zone.

20 . The non-transitory, computer-readable medium of claim 17 , wherein the instructions cause the one or more processors to:

create a second proxy in the second availability zone to facilitate communication between a leader database server and the administration database when the first proxy fails.

21 . The non-transitory, computer-readable medium of claim 17 , wherein the first instance of the database server is a primary database server and the second instance of the database server is a secondary database server, wherein the second instance of the database server becomes the primary database server upon the first instance of the database server becoming unavailable.

22 . The non-transitory, computer-readable medium of claim 17 , wherein the instructions cause the one or more processors to create a consensus keeper configured to record state transitions in the first instance of the administration database and the second instance of the administration database.

Assignments (2)

Continuity (4)

References Cited (250)