High availability transactional replication

• US 10,642,506 B2
• Filed: 09/08/2017
• Issued: 05/05/2020
• Est. Priority Date: 09/08/2017
• Status: Active Grant

• Current Assignee: Dell Products BV (Dell Technologies Inc.)
• Original Assignee: Dell Products BV (Dell Technologies Inc.)
• Inventors: Bikumala, Sathish Kumar, Rachakonda, Nataraj, Uppuluri, Chandra Sekhar
• Primary Examiner(s): Bonzo, Bryce P
• Assistant Examiner(s): Lin, Katherine
• Application Number:
  US15/699,036
• Publication Number:
  US 20190079682A1
• Time in Patent Office: 970 Days
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1466 to make the backup process non-disruptive
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 2201/80 Database-specific techniques
• CPC Class Codes: G06F 3/0617 in relation to availability

Abstract

Some examples include instructions stored in a memory and executed by one or more processors to configure an availability group that includes a primary database and a secondary database and configure one or more subscriptions associated with the primary database. Individual subscriptions of the one or more subscriptions may identify a network element (e.g., individual subscriber) of one or more network elements that subscribe to receiving a portion of data stored in the primary database. The processors may configure the secondary database to replicate a content of the primary database, configure the secondary database to publish data based on the one or more subscriptions in response to a failover from the primary database to the secondary database, and redirect the one or more subscriptions from the primary database to the availability group.

Claims

1. A computer-implemented method, comprising:

configuring an availability group that includes metadata identifying a primary database and a secondary database of the availability group;

configuring one or more subscriptions associated with the primary database, each subscription of the one or more subscriptions identifying a network element of one or more network elements that subscribes to a portion of data stored in the primary database;

configuring the secondary database to replicate a content of the primary database; and

configuring, based on the one or more subscriptions, the one or more network elements as listeners to the availability group including modifying each subscription of the one or more subscriptions to include information associated with the availability group rather than the primary database, wherein in response to a failover from the primary database to the secondary database, the secondary database publishes data to the listeners of the availability group.

2. The computer-implemented method of claim 1, further comprising:

verifying that, in response to the failover from the primary database to the secondary database, the secondary database publishes the data based on the one or more subscriptions to one or more network elements that were, prior to the failover, receiving the data from the primary database.

3. The computer-implemented method of claim 1, further comprising:

determining a problem with the primary database;

determining that the problem satisfies a failover threshold; and

performing the failover from the primary database to the secondary database.

4. The computer-implemented method of claim 1, wherein, after performing the failover, the secondary database publishes the data, based on the one or more subscriptions, to the one or more network elements that were, prior to the failover, receiving the data from the primary database.

5. The computer-implemented method of claim 1, further comprising:

determining that the failover from the primary database to the secondary database occurred; and

maintaining an atomicity, consistency, isolation, durability of the data being sent to the listeners to the availability group.

6. The computer-implemented method of claim 1, wherein the secondary database is configured as a listener to the primary database.

7. The computer-implemented method of claim 1, wherein:

the data is sent from the availability group to a distributor; and

the distributor forwards the data, based on the one or more subscriptions, to the network elements.

8. One or more non-transitory computer-readable media storing instructions that are executable by one or more processors to perform operations comprising:

configuring, by a distributor, an availability group that includes metadata identifying a primary database and a secondary database of the availability group;

configuring, by the distributor, one or more subscriptions associated with the primary database, each subscription of the one or more subscriptions identifying a network element of one or more network elements that subscribes to a portion of data stored in the primary database;

configuring, by the distributor, the secondary database to replicate a content of the primary database; and

configuring, based on the one or more subscriptions, the one or more network elements as listeners to the availability group including modifying each subscription of the one or more subscriptions to include information associated with the availability group rather than the primary database, wherein in response to a failover from the primary database to the secondary database, the secondary database publishes data to the distributor for forwarding to the listeners of the availability group.

9. The one or more non-transitory computer-readable media of claim 8, further comprising:

determining a problem with the primary database; and

performing the failover from the primary database to the secondary database.

10. The one or more non-transitory computer-readable media of claim 8, wherein, after performing the failover, the secondary database publishes the data to the distributor for forwarding to the one or more network elements based on the one or more subscriptions.

11. The one or more non-transitory computer-readable media of claim 8, wherein the primary database is used to store data associated with staging an electronic commerce (ecommerce) website to receive orders placed by consumers.

12. The one or more non-transitory computer-readable media of claim 8, wherein the primary database is used to store data associated with staging an electronic commerce (ecommerce) website to receive orders placed by enterprise customers.

13. The one or more non-transitory computer-readable media of claim 11, further comprising:

receiving, by the distributor, additional data via a messaging queue; and

distributing, by the distributor, the additional data to the one or more network elements based on the one or more subscriptions.

14. A server comprising:

one or more processors; and

one or more non-transitory computer-readable media storing instructions that are executable by the one or more processors to perform operations comprising;

configuring an availability group that includes metadata identifying a primary database and a secondary database of the availability group;

configuring one or more subscriptions associated with the primary database, each subscription of the one or more subscriptions identifying a network element of one or more network elements that subscribes to a portion of data stored in the primary database;

configuring the secondary database to replicate a content of the primary database; and

configuring, based on the one or more subscriptions, the one or more network elements as listeners to the availability group including modifying each subscription of the one or more subscriptions to include information associated with the availability group rather than the primary database, wherein in response to a failover from the primary database to the secondary database, the secondary database publishes data to the listeners of the availability group.

15. The server of claim 14, the operations further comprising:

detecting a problem associated with the primary database; and

performing the failover from the primary database to the secondary database.

16. The server of claim 14, wherein, after performing the failover, the secondary database publishes the data, based on the one or more subscriptions, to the one or more network elements that were, prior to the failover, receiving the data from the primary database.

17. The server of claim 14, the operations further comprising:

verifying that, in response to the failover from the primary database to the secondary database, the secondary database publishes the data based on the one or more subscriptions to one or more network elements that were, prior to the failover, receiving the data from the primary database.

18. The server of claim 14, the operations further comprising:

determining that the failover from the primary database to the secondary database occurred; and

maintaining an atomicity, consistency, isolation, durability of the data being sent to the listeners to the availability group.

19. The server of claim 14, wherein the secondary database is configured as a listener to the primary database.

20. The server of claim 14, wherein:

the data is sent from the availability group to a distributor; and

the distributor forwards the data, based on the one or more subscriptions, to the network elements.