DATABASE REPLICATION SYSTEM

• US 20100114821A1
• Filed: 10/21/2008
• Published: 05/06/2010
• Est. Priority Date: 10/21/2008
• Status: Active Grant

• Current Assignee: TiVo Solutions Inc. (Adeia Inc.)
• Original Assignee: TiVo Inc. (Adeia Inc.)
• Inventors: SCHINE, GABRIEL
• Granted Patent: US 8,612,385 B2
• Time in Patent Office: Days
• US Class Current: 707/623
• CPC Class Codes: G06F 16/275 Synchronous replication

Abstract

A method and apparatus for updating a slave system in a multi-master replication network is provided. The method involves executing a first event on a first master system within the multi-master replication network and executing a second event on a second master system in the multi-master replication network, where the first event and the second event are identical. The method further involves selecting an event from the first event and the second event and executing the selected event on a slave system.

Claims

1. A method for executing an event in a multi-master replication network, comprising:

executing a first event on a first master system in the multi-master replication network;

executing a second event on a second master system in the multi-master replication network, wherein the first event and the second event are identical;

identifying a selected event from a group consisting of the first event and the second event; and

executing the selected event on a slave system.

2. The method of claim 1, wherein the first master system receives a request to execute the first event from a client system, and wherein identifying the selected event comprises:

designating the first master system as an originating system based on the first master system receiving a request from the client system to execute the first event, and

identifying the selected event based on the originating system.

3. The method of claim 1, wherein identifying the selected event comprises:

determining an active master system from a group consisting of the first master system and the second master system; and

identifying an event executed on the active master system as the selected event.

4. The method of claim 1, further comprising:

forwarding the selected event by an intermediate system to the slave system prior to executing the selected event on the slave system.

5. The method of claim 1, wherein identifying the selected event comprises:

identifying a first occurrence of one selected from the group consisting of the first event and the second event; and

identifying the first occurrence as the selected event.

6. The method of claim 1, wherein executing the first event on the first master system comprises modifying a first data repository associated with the first master system, wherein executing the second event on the second master system comprises modifying a second data repository associated with the second master system, and wherein executing the selected event on the slave system comprises modifying a third data repository associated with the slave system.

7. The method of claim 6, wherein the slave system receives the selected event using a MySQL protocol.

8. The method of claim 7, wherein the data repository associated with the slave system comprises a MySQL database, and wherein modifying the data repository associated with the slave system comprises updating the MySQL database based on the information.

14. The apparatus of claim 1, wherein executing the first event by the first master system comprises modifying a first data repository associated with the first master system, wherein executing the second event by the second master system comprises modifying a second data repository associated with the second master system, and wherein executing the selected event by the slave system comprises modifying a third data repository associated with the slave system.

15. The apparatus of claim 14, wherein the slave system obtains the selected event using a MySQL protocol.

16. The apparatus of claim 15, wherein the data repository associated with the slave system comprises a MySQL database, and wherein modifying the data repository associated with the slave system comprises updating the MySQL database based on the information.

9. An apparatus for executing an event in a multi-master replication network comprising:

a first master system is configured to;

execute a first event;

the second master system is configured to;

execute a second event, where the first event and the second event are identical; and

a slave system is configured to;

identify a selected event from a group consisting of the first event and the second event; and

execute the selected event.

10. The apparatus of claim 9, wherein the first master system receives a request to execute the first event from the client system, and wherein the slave system is configured to identify the selected event by:

designating the first master system as an originating system based on the first master system receiving a request from the client system to execute the first event, and

identifying the selected event based on the originating system.

11. The apparatus of claim 9, wherein the slave system is configured to identify the selected event by:

determining an active master system from a group consisting of the first master system and the second master system, wherein the active master system is designated by a user; and

identifying the selected event based on the active master system.

12. The apparatus of claim 9, further comprising:

an intermediate system configured to forward the selected event to the slave system prior to the system executing the selected event.

13. The apparatus of claim 9, wherein the slave system is configured to identify the selected event by:

identifying a first occurrence of one selected from the group consisting of the first event and the second event; and

identifying the first occurrence as the selected event.

17. A computer readable medium comprising software instructions for executing an event in a multi-master replication network, the software instructions comprising functionality for:

executing a first event on a first master system in the multi-master replication network;

executing a second event on a second master system in the multi-master replication network, wherein the first event and the second event are identical;

identifying a selected event from a group consisting of the first event and the second event; and

executing the selected event on a slave system.

18. The computer readable medium of claim 17, wherein the first master system receives a request to execute the first event from a client system, and wherein identifying the selected event comprises:

designating the first master system as an originating system based on the first master system receiving a request from the client system to execute the first event, and

identifying the selected event based on the originating system.

19. The computer readable medium of claim 17, wherein identifying the selected event comprises:

determining an active master system from a group consisting of the first master system and the second master system; and

identifying an event executed on the active master system as the selected event.

20. The computer readable medium of claim 17, wherein the instructions further comprising functionality for:

forwarding the selected event by an intermediate system to the slave system prior to executing the selected event on the slave system.

21. The computer readable medium of claim 17, wherein identifying the selected event comprises:

identifying a first occurrence of one selected from the group consisting of the first event and the second event; and

identifying the first occurrence as the selected event.

22. The computer readable medium of claim 17, wherein executing the first event on the first master system comprises modifying a first data repository associated with the first master system, wherein executing the second event on the second master system comprises modifying a second data repository associated with the second master system, and wherein executing the selected event on the slave system comprises modifying a third data repository associated with the slave system.

23. The computer readable medium of claim 22, wherein the slave system receives the selected event using a MySQL protocol.

24. The computer readable medium of claim 23, wherein the data repository associated with the slave system comprises a MySQL database, and wherein modifying the data repository associated with the slave system comprises updating the MySQL database based on the information.