CN108038163B - Master and backup control center database synchronization system - Google Patents
Master and backup control center database synchronization system Download PDFInfo
- Publication number
- CN108038163B CN108038163B CN201711276815.2A CN201711276815A CN108038163B CN 108038163 B CN108038163 B CN 108038163B CN 201711276815 A CN201711276815 A CN 201711276815A CN 108038163 B CN108038163 B CN 108038163B
- Authority
- CN
- China
- Prior art keywords
- database server
- data
- server
- standby
- data synchronization
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a synchronous system of a master and standby control center database, which comprises a master control center and a standby control center; the master control center comprises a first master database server and a first slave database server; the standby control center comprises a second main database server and a second standby database server; data synchronization units are respectively deployed on the first main database server, the first standby database server, the second main database server and the second standby database server; the data synchronization unit is used for executing the following processes: judging whether a server where the data synchronization unit is located is an operation server, connecting a local database server when the server where the data synchronization unit is located is the operation server, if the connection is normal, inquiring whether the local database server has changed data, if so, connecting a target database server, and synchronizing the changed data to the target database server; the invention can solve the problem of synchronization of the master control center database and the slave control center database.
Description
Technical Field
The invention relates to the technical field of track control, in particular to a synchronous system of a master and standby control center database.
Background
In an automatic train monitoring ATS system, a main control center and a standby control center exist, wherein the main control center comprises a main database server, a standby database server and a disk array; the standby control center comprises a main database server, a standby database server and a disk array.
In the physical architecture, the database file is stored in the disk array, and when the database application accesses the database, the database file is directly connected with the database server, and the database server completes the operation of accessing the database.
In the ATS system, all databases are applied to read and write one database of the control center at the same time. Thus, the other control center does not receive any data, and thus, there is a need for a solution to the problem of synchronizing data to the other control center.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a master/slave control center database synchronization system, which can solve the problem of master/slave control center database synchronization.
In order to achieve the purpose, the invention provides the following technical scheme:
the invention provides a master-slave control center database synchronization system, which comprises: a main control center and a standby control center; the main control center comprises a first main database server and a first standby database server; the standby control center comprises a second main database server and a second standby database server; data synchronization units are respectively deployed on the first main database server, the first standby database server, the second main database server and the second standby database server;
the data synchronization units in the first main database server, the first standby database server, the second main database server and the second standby database server are all used for executing the following processes:
judging whether the server where the data synchronization unit is located is an operation server, connecting a local database server when the server where the data synchronization unit is located is judged to be the operation server, if the connection is normal, inquiring whether the local database server has changed data, if so, connecting a target database server, and synchronizing the changed data to the target database server;
the local database server is the server where the data synchronization unit is located, and the target database server is the other three database servers except the server where the data synchronization unit is located.
Furthermore, the master control center further comprises a first disk array, and the first disk array is used for the first master database server and the first backup database server to read and write database files;
the standby control center also comprises a second disk array, and the second disk array is used for the second main database server and the second standby database server to read and write database files;
correspondingly, the data synchronization unit deployed on the first master database server judges whether the first master database server has changed data by inquiring whether the working area corresponding to the first master database server on the first disk array has changed data;
the data synchronization unit deployed on the first standby database server judges whether the first standby database server has changed data or not by inquiring whether the working area corresponding to the first standby database server on the first disk array has changed data or not;
the data synchronization unit deployed on the second main database server judges whether the second main database server has changed data by inquiring whether the working area corresponding to the second main database server on the second disk array has changed data;
and the data synchronization unit deployed on the second standby database server judges whether the second standby database server has changed data or not by inquiring whether the working area corresponding to the second standby database server on the second disk array has changed data or not.
Further, the data synchronization unit queries whether the local database server has the changed data or not in a polling mode based on a flashback query result of the Oracle database, wherein a polling time interval is smaller than a flashback query time interval of the Oracle database.
Further, the synchronizing the change data to the target database server by the data synchronizing unit specifically includes:
the data synchronization unit converts the non-binary field of the change data into a Sql statement, executes the Sql statement in the target database server, and synchronizes the change data to the target database server.
Further, when the data synchronization unit fails to execute the Sql statement in the target database server, sending alarm information to an ATS system, rolling back the Sql, and continuing to execute the Sql statement.
Further, before querying the local database server whether the change data exists, the data synchronization unit is further configured to: and judging whether the local database server has unsynchronized data, and if so, synchronizing the unsynchronized data to the target database server.
Further, the data synchronization unit stores the change data to a local database server and marks the change data as unsynchronized data when the connection with the target database server fails.
Further, the data synchronization unit is configured to determine whether a server where the data synchronization unit is located is an operation server according to a message sent by the ATS system.
Further, the data synchronization unit is further configured to, when it is determined that the server where the data synchronization unit is located is not the job server, continue to receive the message sent by the ATS system and continuously determine whether the server where the data synchronization unit is located is the job server according to the received message.
Furthermore, the first master database server, the first backup database server, the second master database server and the second backup database server are respectively provided with a monitoring unit, and the monitoring units are used for monitoring the data synchronization units on the corresponding database servers and restarting the data synchronization units when the data synchronization units are abnormal.
According to the technical scheme, the data synchronization unit is respectively deployed on the four database servers of the main and standby control centers, the data synchronization unit determines which server of which control center is currently the operation server, and synchronizes the change data on the operation server to other non-operation servers, so that the data synchronization of the main and standby control centers is realized.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a master/slave control center database synchronization system according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a data synchronization unit process according to an embodiment of the present invention;
fig. 3 is another schematic diagram of a data synchronization unit processing procedure according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It can be understood that, the data synchronization of the primary and secondary control centers is realized, and the data consistency of the primary and secondary control centers is substantially maintained. When the data inconsistency occurs in the main control center and the standby control center, firstly, which data is the standard is determined, that is, whether the production library is in the main control center or the standby control center is determined. Inconsistent data is then synchronized to the control center where the data is incomplete. According to the thought, the invention provides a master-slave control center database synchronization system, which is used for solving the problem of master-slave control center database synchronization. The following describes the master-slave control center database synchronization system provided by the present invention in detail through a specific embodiment.
An embodiment of the present invention provides a master/slave control center database synchronization system, which is shown in fig. 1and includes: a main control center and a standby control center; the main control center comprises a first main database server and a first standby database server; the standby control center comprises a second main database server and a second standby database server; data synchronization units are respectively deployed on the first main database server, the first standby database server, the second main database server and the second standby database server;
wherein, the data synchronization units in the first master database server, the first slave database server, the second master database server and the second slave database server are all used for executing the process shown in fig. 2:
judging whether the server where the data synchronization unit is located is an operation server, connecting a local database server when the server where the data synchronization unit is located is judged to be the operation server, if the connection is normal, inquiring whether the local database server has changed data, if so, connecting a target database server, and synchronizing the changed data to the target database server;
the local database server is the server where the data synchronization unit is located, and the target database server is the other three database servers except the server where the data synchronization unit is located.
It can be understood that the master control center further includes a first disk array, and the first disk array is used by the first master database server and the first backup database server to read and write database files. Similarly, the standby control center further comprises a second disk array, and the second disk array is used for the second main database server and the second standby database server to read and write database files. Correspondingly, the data synchronization unit deployed on the first master database server judges whether the first master database server has changed data by inquiring whether the working area corresponding to the first master database server on the first disk array has changed data;
the data synchronization unit deployed on the first standby database server judges whether the first standby database server has changed data or not by inquiring whether the working area corresponding to the first standby database server on the first disk array has changed data or not;
the data synchronization unit deployed on the second main database server judges whether the second main database server has changed data by inquiring whether the working area corresponding to the second main database server on the second disk array has changed data;
and the data synchronization unit deployed on the second standby database server judges whether the second standby database server has changed data or not by inquiring whether the working area corresponding to the second standby database server on the second disk array has changed data or not.
It is understood that the data synchronization unit may be a physical hardware unit or a virtual software unit. When the data synchronization unit is a virtual software unit, the virtual software unit can be understood as a computer program (e.g., a synchronization program) capable of implementing the above synchronization function. When the data synchronization unit is a physical hardware unit, it can be understood that a computer program capable of implementing the above synchronization function is run thereon.
As can be seen from the above description, in the primary and secondary control center database synchronization system provided in this embodiment, the data synchronization units are respectively deployed in the four database servers of the primary and secondary control centers, the data synchronization units determine which server of which control center is currently the operation server, and synchronize the change data on the operation server to other non-operation servers, thereby implementing data synchronization of the primary and secondary control centers.
In a preferred embodiment, the data synchronization unit queries whether the local database server has changed data or not in a polling manner based on a flashback query result of the Oracle database, wherein a polling time interval is smaller than a flashback query time interval of the Oracle database.
In a preferred embodiment, the synchronizing the change data to the target database server by the data synchronizing unit specifically includes:
the data synchronization unit converts the non-binary field of the change data into a Sql statement, executes the Sql statement in the target database server, and synchronizes the change data to the target database server.
In a preferred embodiment, when the data synchronization unit fails to execute the Sql statement in the target database server, an alarm message is sent to the ATS system, the Sql is rolled back, and the execution of the Sql statement is continued.
In a preferred embodiment, the data synchronization unit, before querying the local database server whether there is change data, is further configured to: and judging whether the local database server has unsynchronized data, and if so, synchronizing the unsynchronized data to the target database server.
In a preferred embodiment, the data synchronization unit stores the changed data in the local database server and marks the changed data as unsynchronized data when the connection with the target database server fails.
It is understood that, when the connection with the target database server fails, the data synchronization unit may store the changed data to the local database server in a Sql statement manner, and mark the changed data as unsynchronized data. For example, unsynchronized data is saved in a file, such that the file is named save.
In a preferred embodiment, the data synchronization unit is configured to determine whether a server where the data synchronization unit is located is a job server according to a message sent by the ATS system.
In a preferred embodiment, the data synchronization unit is further configured to, when it is determined that the server where the data synchronization unit is located is not the job server, continue to receive the message sent by the ATS system and continuously determine whether the server where the data synchronization unit is located is the job server according to the received message.
In a preferred embodiment, the data synchronization unit sends alarm information to the ATS system if an abnormality occurs during the connection with the local database server.
In a preferred embodiment, the first master database server, the first backup database server, the second master database server, and the second backup database server are further respectively disposed with a monitoring unit, and the monitoring units are configured to monitor the data synchronization units on the corresponding database servers, and restart the data synchronization units when the data synchronization units are abnormal.
The solution provided by the invention is explained in more detail below by means of a more specific embodiment in conjunction with fig. 3. The process of data synchronization by the data synchronization units installed on the four data servers is as follows:
firstly, the data synchronization unit polls the change data of the job server in a polling mode, and when the change of the data is found, the change data is synchronized to the database server of the non-job control center immediately. If the system adopts an Oracle database, the change data of the polling job server can be queried by utilizing the flash of the Oracle database. Since flashback queries only hold data that changes over a period of time, polling times need to be set shorter than database flashback queries.
Then, after the change data is inquired, the non-binary field of the change data is converted into a Sql form, the Sql is executed on the database server of the non-job control center, and the change data is synchronized into the database server of the non-job control center. If the database server of the non-job control center has problems, storing the Sql of the non-binary field of the change data on a disk array of the job control center, wherein the file name is save. Wherein, the [ sequence number ] is the ID number of the data acquired when the changed data in the database server is subjected to the flashback query, and the [ Sql statement ] is the Sql formed by a changed database record. For binary fields, the information of each binary field of each record is respectively saved as a file, and the file name is saved in a user-specified position in the disk array in a mode of 'SqlID _ field name _ YYYYYYMMDD.dat'. The SqlID in the filename is the sequence number of the stored Sql, and YYYMMDD is the date format. The SqlID is the serial number of a non-binary Sql statement corresponding to binary data in the save. This file is not formed when there are no binary fields in a record. When a record has n binary fields, n files are formed.
For example, there are tables TableA and TableB in the database, and the structures of the two tables are shown in tables 1and 2:
table 1 table structure of a database table TableA
| Name of field | Type of field | Whether or not to make a key |
| Train type | integer | Is that |
| Date | datetime | Is that |
| Recording person | varchar(20) | Is that |
Table 2 table structure of a database table TableB
| Name of field | Type of field | Whether or not to make a key |
| Name of configuration file | varchar(30) | Is that |
| Configuration file | blob | |
| Reviser | varchar(20) | Is that |
Assuming that two pieces of data are changed in the table of table 16:36, 10/18/2017, one piece of data is added and the other piece of data is deleted by the change flag in the table, as shown in table 3; the TableB table has a change of data, and the change flag in the table indicates an added data, as shown in table 4. :
table 3 data changed and manner of change in a database table TableA
| Train type | Date | Recording person | Change sign |
| 1 | 20170908 | Zhang three | Increase of |
| 1 | 20170908 | Li four | Deleting |
Table 4 data changed and manner of change in a database table TableA
| Name of configuration file | Configuration file | Reviser | Change sign |
| config | <sdf>sf<dsf> | Wangwu tea | Increase of |
In the above structure, the "profile" field of TableB is a binary field, and the others are all non-binary fields. In the change data in the table, the last column is the column added to the database when the flashback query is performed, and indicates what change, i.e. addition, modification or deletion, is generated by the record. The three records of the two table changes above constitute the following three sql statements, respectively:
① insert to TableA (train type, date, record person) values (1, to _ date ('20170908', 'yyymmdd'), 'Zhang three');
② delete from TableA where train type 1and date to date ('20170908', 'yyymmdd');
③ insert to TableB (profile name, profile, Modifiers) values ('config', $ para, 'Wangpu');
here, $ para represents a binary stream "< sdf > sf < dsf >", and after the statements are composed, the database server of the non-job control center is connected, and the three statements are executed in the database.
If a problem occurs in the database server of the non-job control center, the content in the file save.
① insert to TableA (train type, date, record person) values (1, to _ date ('20170908', 'yyymmdd'), 'Zhang three');
② delete from TableA where train type 1and date to date ('20170908', 'yyymmdd');
③ insert to TableB (profile name, profile, Modifiers) values ('config', $ para, 'Wangpu');
in the file of save, Sql, the sequence number at the front of each line is the sqlID, i.e. the sequence number of the saved Sql. Since only one binary field exists in the table of table b, and there is only one record of change in table b, a file named 3_ profile _20171018.dat is generated at the same time as the save.sql file is generated, and the contents of the file are: "< sdf > sf < dsf >", the contents of this file are the contents of the binary field.
And finally, after the database of the job server is confirmed to be normally connected, searching whether the data which is not synchronized before exists, and if so, synchronizing the data which is not synchronized before. The unsynchronized data is stored locally in a Sql manner, each Sql has a sequence number, when the unsynchronized data is synchronized, the Sql data is executed once, the persistently stored unsynchronized data is deleted after the execution is successful, and the whole execution flow is shown in fig. 3.
Therefore, the problem of synchronization of the main control center database and the standby control center database is solved through the processing mode, and the real-time performance of the synchronization is realized by adjusting the interval time of the polling operation library.
The above examples are only for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A master-slave control center database synchronization system comprises: a main control center and a standby control center; the main control center comprises a first main database server and a first standby database server; the standby control center comprises a second main database server and a second standby database server; the system is characterized in that data synchronization units are respectively deployed on the first main database server, the first standby database server, the second main database server and the second standby database server;
the data synchronization units in the first main database server, the first standby database server, the second main database server and the second standby database server are all used for executing the following processes:
judging whether the server where the data synchronization unit is located is an operation server, connecting a local database server when the server where the data synchronization unit is located is judged to be the operation server, if the connection is normal, inquiring whether the local database server has changed data, if so, connecting a target database server, and synchronizing the changed data to the target database server;
the local database server is a server where the data synchronization unit is located, and the target database server is three other database servers except the server where the data synchronization unit is located;
in the ATS system, all databases are applied to the same time, and only one database of the control center is read and written.
2. The synchronization system of claim 1, wherein the primary control center further comprises a first disk array, the first disk array being used by the first primary database server and the first backup database server to read and write database files;
the standby control center also comprises a second disk array, and the second disk array is used for the second main database server and the second standby database server to read and write database files;
correspondingly, the data synchronization unit deployed on the first master database server judges whether the first master database server has changed data by inquiring whether the working area corresponding to the first master database server on the first disk array has changed data;
the data synchronization unit deployed on the first standby database server judges whether the first standby database server has changed data or not by inquiring whether the working area corresponding to the first standby database server on the first disk array has changed data or not;
the data synchronization unit deployed on the second main database server judges whether the second main database server has changed data by inquiring whether the working area corresponding to the second main database server on the second disk array has changed data;
and the data synchronization unit deployed on the second standby database server judges whether the second standby database server has changed data or not by inquiring whether the working area corresponding to the second standby database server on the second disk array has changed data or not.
3. The synchronization system according to claim 1, wherein the data synchronization unit queries whether the local database server has the changed data or not in a polling manner based on a flashback query result of the Oracle database, wherein a polling time interval is smaller than a flashback query time interval of the Oracle database.
4. The synchronization system according to claim 1, wherein the data synchronization unit synchronizes the change data to the target database server, specifically comprising:
the data synchronization unit converts the non-binary field of the change data into a Sql statement, executes the Sql statement in the target database server, and synchronizes the change data to the target database server.
5. The synchronization system according to claim 4, wherein when the data synchronization unit fails to execute the Sql sentence in the target database server, it sends an alarm message to the ATS system, rolls back the Sql, and continues to execute the Sql sentence.
6. The synchronization system of claim 1, wherein the data synchronization unit, prior to querying the local database server for the presence of the change data, is further configured to: and judging whether the local database server has unsynchronized data, and if so, synchronizing the unsynchronized data to the target database server.
7. The synchronization system according to claim 1, wherein the data synchronization unit stores the change data to the local database server and marks the change data as unsynchronized data when the connection to the target database server fails.
8. The synchronization system according to claim 1, wherein the data synchronization unit is configured to determine whether the server where the data synchronization unit is located is a job server according to a message sent by the ATS system.
9. The synchronization system according to claim 8, wherein the data synchronization unit is further configured to continue receiving the message sent by the ATS system and continuously determining whether the server where the data synchronization unit is located is the job server according to the received message when it is determined that the server where the data synchronization unit is located is not the job server.
10. The synchronization system according to any one of claims 1 to 9, wherein the first master database server, the first backup database server, the second master database server and the second backup database server are respectively provided with a monitoring unit, and the monitoring units are configured to monitor the data synchronization units on the corresponding database servers and restart the data synchronization units when the data synchronization units are abnormal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711276815.2A CN108038163B (en) | 2017-12-06 | 2017-12-06 | Master and backup control center database synchronization system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711276815.2A CN108038163B (en) | 2017-12-06 | 2017-12-06 | Master and backup control center database synchronization system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108038163A CN108038163A (en) | 2018-05-15 |
| CN108038163B true CN108038163B (en) | 2020-07-31 |
Family
ID=62095513
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711276815.2A Active CN108038163B (en) | 2017-12-06 | 2017-12-06 | Master and backup control center database synchronization system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108038163B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108733823A (en) * | 2018-05-22 | 2018-11-02 | 浪潮软件股份有限公司 | A kind of system and method that ORACLE database intranet and extranet data double-ways are synchronized |
| CN110335386B (en) * | 2019-06-25 | 2021-08-03 | 腾讯科技（深圳）有限公司 | Identity authentication method, device, terminal and storage medium |
| CN113656366B (en) * | 2021-08-03 | 2024-05-03 | 北京数码大方科技股份有限公司 | Data processing method and device for electronic warehouse |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102402562A (en) * | 2010-09-14 | 2012-04-04 | 中兴通讯股份有限公司 | Database remote disaster tolerant method and system |
| CN102841895A (en) * | 2011-06-22 | 2012-12-26 | 阿里巴巴集团控股有限公司 | Method and system for processing database state transition |
| CN103744906A (en) * | 2013-12-26 | 2014-04-23 | 乐视网信息技术（北京）股份有限公司 | System, method and device for data synchronization |
| CN105956139A (en) * | 2016-05-12 | 2016-09-21 | 国电南瑞科技股份有限公司 | Method for synchronizing database in two machines |
-
2017
- 2017-12-06 CN CN201711276815.2A patent/CN108038163B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102402562A (en) * | 2010-09-14 | 2012-04-04 | 中兴通讯股份有限公司 | Database remote disaster tolerant method and system |
| CN102841895A (en) * | 2011-06-22 | 2012-12-26 | 阿里巴巴集团控股有限公司 | Method and system for processing database state transition |
| CN103744906A (en) * | 2013-12-26 | 2014-04-23 | 乐视网信息技术（北京）股份有限公司 | System, method and device for data synchronization |
| CN105956139A (en) * | 2016-05-12 | 2016-09-21 | 国电南瑞科技股份有限公司 | Method for synchronizing database in two machines |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108038163A (en) | 2018-05-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11256715B2 (en) | Data backup method and apparatus | |
| EP3111347B1 (en) | Efficient methods and systems for consistent read in record-based multi-version concurrency control | |
| CN109992628B (en) | Data synchronization method, device, server and computer readable storage medium | |
| US9779128B2 (en) | System and method for massively parallel processing database | |
| US7383293B2 (en) | Database backup system using data and user-defined routines replicators for maintaining a copy of database on a secondary server | |
| US8108343B2 (en) | De-duplication and completeness in multi-log based replication | |
| US7490113B2 (en) | Database log capture that publishes transactions to multiple targets to handle unavailable targets by separating the publishing of subscriptions and subsequently recombining the publishing | |
| CN108038163B (en) | Master and backup control center database synchronization system | |
| WO2021077934A1 (en) | Distributed transaction management method and system based on distributed logic timestamp | |
| CN106202365B (en) | Method and system for database update synchronization and database cluster | |
| CN101231652B (en) | Method and system for data storage resynchronization | |
| WO2022134876A1 (en) | Data synchronization method and apparatus, and electronic device and storage medium | |
| US11216346B2 (en) | Coordinated replication of heterogeneous database stores | |
| KR20150137884A (en) | Database Management System providing partial synchronization and method for partial synchronization thereof | |
| CN108153804B (en) | Metadata log updating method for symmetric distributed file system | |
| CN109902127B (en) | Historical state data processing method and device, computer equipment and storage medium | |
| CN110727733A (en) | Main and standby server system and data synchronization method | |
| CN111404737B (en) | Disaster recovery processing method and related device | |
| CN112650629A (en) | Block chain index data recovery method, device, equipment and computer storage medium | |
| CN112800060A (en) | Data processing method and device, computer readable storage medium and electronic equipment | |
| JP2001034518A (en) | Master-slave relation information synchronization system in decentralized database | |
| CN116361078A (en) | Data synchronization method, device, system and medium | |
| CN114116768A (en) | Method for performing read-write separation on database cluster | |
| CN114490570A (en) | Production data synchronization method and device, data synchronization system and server | |
| KR101430239B1 (en) | Method and Apparatus for Synchronizing Data in Active-Active Database Server System |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |