CN109298976B - Heterogeneous database cluster backup system and method - Google Patents
Heterogeneous database cluster backup system and method Download PDFInfo
- Publication number
- CN109298976B CN109298976B CN201811208785.6A CN201811208785A CN109298976B CN 109298976 B CN109298976 B CN 109298976B CN 201811208785 A CN201811208785 A CN 201811208785A CN 109298976 B CN109298976 B CN 109298976B
- Authority
- CN
- China
- Prior art keywords
- mysql
- statement
- cluster
- node
- vernox
- 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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a heterogeneous database cluster backup system and a method, which relate to the technical field of databases and comprise an operation management component and a heterogeneous database cluster, wherein the operation management component provides coordination processing capacity from an application layer to a database layer for operation, and the heterogeneous database cluster is used for data backup of MySQL nodes; the operation management component comprises a main node and a plurality of auxiliary nodes, wherein the main node and the auxiliary nodes respectively comprise a statement analysis module, a message forwarding module and a global queue module, and the statement analysis module judges the type of the MySQL operation statement; the message forwarding module forwards the operation information of the operation statement to the MySQL node or the heterogeneous database cluster according to the analysis result; the global queue module stores MySQL operation statements of operation failure of the heterogeneous database cluster caused by communication reasons, and the master node manages the consistency of data in the global queue module of each node.
Description
Technical Field
The invention relates to the technical field of databases, in particular to a cluster backup system and method for a heterogeneous database.
Background
The database is a core component of a modern enterprise, the database not only stores core data inside the enterprise, but also bears the function of serving core services, the core service database of a large and medium-sized enterprise often needs to bear thousands of operation requests per second, the downtime of minutes or even seconds causes great economic loss to the enterprise, and the high availability of the database is a problem that the enterprise must consider; on the other hand, data storage must be reliable enough to ensure that system data will not be lost in normal failures, a database system has certain risk resistance capability, and a database needs to be backed up reliably to ensure data safety.
The existing backup deployment mode of the database cluster usually uses a homogeneous database to backup data, for example, the MySQL database to be backed up is used to backup the MySQL database, which has a great problem that the bottom layer implementation logic and implementation mode of the homogeneous database are the same, a single point fault caused by the data logic problem will cause the fault to spread in the storage cluster, and the availability and efficiency of the database cluster are greatly reduced.
Disclosure of Invention
The invention aims to: the invention provides a heterogeneous database cluster backup system and a method, aiming at solving the problem that the usability of a database cluster is low because a single-point fault caused by a data logic problem can be spread in a storage cluster when the existing database cluster adopts an isomorphic database for data backup.
The invention specifically adopts the following technical scheme for realizing the purpose:
a heterogeneous database cluster backup system comprises an operation management component and a heterogeneous database cluster, wherein the operation management component is used for providing coordination processing capacity of database operation from an upper application layer to a database layer, and the heterogeneous database cluster is used for data backup of MySQL nodes; the operation management component comprises a main node and a plurality of auxiliary nodes which are respectively communicated with the main node, wherein the main node and the auxiliary nodes respectively comprise a statement analysis module, a message forwarding module and a global queue module,
a statement analysis module: the system is used for judging the type of the MySQL operation statement and outputting an analysis result;
the message forwarding module: according to the analysis result of the statement analysis module, forwarding the operation information of the MySQL operation statement to the MySQL node or the heterogeneous database cluster according to a specified strategy;
a global queue module: and storing MySQL operation statements of operation failure of the heterogeneous database cluster caused by communication reasons, and managing the consistency of data in the main node and the global queue modules of all the auxiliary nodes by the main node.
Furthermore, when the auxiliary node modifies the data in the global queue module, the auxiliary node needs to apply for the main node, and after the application is passed, the main node modifies the data in the global queue module.
Further, when the current master node fails, a new master node is elected from the slave nodes according to a set rule, wherein the set rule is an existing election algorithm.
Further, the analysis result is DQL, DML, DDL, or DCL.
Further, the heterogeneous database cluster includes but is not limited to a Vernox cluster, the Vernox cluster is a converged database, and comprises a client driving module and a compiling and executing system,
a client driver module: receiving a MySQL operation statement, performing pre-analysis on the MySQL operation statement and generating an execution plan;
compiling the execution system: and checking the field legality of the execution plan, and performing optimized execution of the MySQL operation statement after the legality passes, thereby completing the analysis, processing and conversion work of the MySQL operation statement in the database.
A cluster backup method for heterogeneous databases comprises the following steps:
s1, inputting an operation sentence: the upper application layer transmits the MySQL operation statement to the operation management component, and the MySQL operation statement is located in the main node or the auxiliary node;
s2, judging the type of the operation statement: the statement analysis module analyzes the type of the MySQL operation statement and outputs an analysis result, wherein the analysis result is DQL, DML, DDL or DCL;
when the analysis result is DQL, S4 is performed; when the analysis result is non-DQL, S3 is performed;
s3, operation management component internal statement transfer: after transferring the MySQL operation statement to the main node, executing S4;
and S4, aiming at different analysis results, the MySQL node and the Vernox cluster execute corresponding operations, return the execution results to the operation management component, and finally return the execution results to the upper-layer application by the operation management component.
Further, when the analysis result in S4 is DQL, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to a MySQL node;
step two, the MySQL node executes the statement: the MySQL node executes the query operation and returns the query result to the operation management component;
step three, returning an execution result: and the operation management component returns the query result to the upper application layer.
Further, when the analysis result in S4 is the DML insertion operation, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to a MySQL node;
step two, the MySQL node executes the statement: the MySQL node executes the insertion operation and returns the insertion result to the operation management component;
step three, returning an execution result: the operation management component returns the insertion result to the upper application layer, if the insertion result is failure, the flow is ended, and if the insertion result is success, the fourth step is executed;
step four, forwarding the statement: forwarding the self-growth message and the insertion statement to a Vernox cluster;
step five, the Vernox cluster executes the statement: obtaining a self-growing value through the self-growing message, then executing an insertion statement, avoiding the repetition of the self-growing main key of the insertion item, and returning an insertion result to the operation management component;
step six, ensuring that the Vernox cluster successfully inserts data: if the insertion result in the step five is successful, the process is ended, and if the insertion result in the step five is failed, the processing is performed according to the failure reason, specifically:
if the insertion fails due to the communication problem, pushing the insertion statement into the global queue module, and subsequently executing the insertion operation again from the global queue module until the insertion operation is successful;
and if the insertion fails due to other reasons, performing data synchronization operation of the Vernox cluster to ensure successful insertion.
Further, when the analysis result in S4 is an update or deletion operation of the DML, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to the MySQL node and the Vernox cluster;
step two, the MySQL node and the Vernox cluster execute the statement: the MySQL node and the Vernox cluster execute updating or deleting operation and return the execution results of the MySQL node and the Vernox cluster to the operation management component;
step three, returning an execution result: the operation management component returns the execution result of the MySQL node to the upper application layer and the Vernox cluster;
step four, comprehensively executing results: if the MySQL node execution result is successful, executing the step five, and if the MySQL node execution result is failed, rolling back the execution result of the Vernox cluster to ensure the data consistency of the MySQL node and the Vernox cluster;
step five, ensuring that the Vernox cluster successfully inserts data: if the execution result of the second Vernox cluster is successful, the process is ended, and if the execution result of the second Vernox cluster is failed, the processing is performed according to the failure reason, specifically:
if the updating or deleting fails due to the communication problem, pushing the operation statement into the global queue module, and subsequently executing the updating or deleting operation again from the global queue module until the operation is successful;
and if the updating or deleting fails due to other reasons, performing data synchronization operation of the Vernox cluster, and ensuring the data consistency of the MySQL node and the Vernox cluster.
Further, when the analysis result in S4 is DDL or DCL, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to the MySQL node and the Vernox cluster;
step two, the MySQL node executes the statement: the MySQL node executes DDL or DCL operation and returns an execution result to the operation management component;
step three, returning an execution result: the operation management component returns the execution result to the upper application layer;
step four, the Vernox cluster executes the statement: and the Vernox cluster executes DDL or DCL operation and the process is ended.
The invention has the following beneficial effects:
1. the invention creatively uses an operation management component formed by a plurality of nodes and a Vernox cluster which is heterogeneous to the MySQL node to replace the MySQL database to back up the node, thereby preventing the problem that a logic error is propagated in homogeneous MySQL main and standby nodes from the architecture perspective; meanwhile, the Vernox cluster follows the MySQL protocol, the data backup is carried out on the MySQL nodes by using the Vernox cluster, the data backup is invisible to the upper layer, and a user or an application layer does not need to carry out complex backup configuration work any more, so that the usability is strong.
2. The invention adopts the database cluster as the backup database of the MySQL nodes, the backup database is a cluster, the high fault-tolerant rate of the backup MySQL nodes is met by ensuring the fault-tolerant rate of the database cluster, and the reliability of the backup system is very strong.
3. In the backup method, sentences which are failed to execute due to communication problems in the heterogeneous database cluster are added into the global queue module in the management node of the operation management component, and the sentences in the global queue module are executed when communication is recovered, so that the problem of instability of the backup cluster due to network reasons can be avoided.
4. In the data insertion process, the MySQL statement is executed firstly, and the recorded self-growth message is returned after the MySQL is executed; and then the self-growth message and the insertion statement are forwarded to the Vernox cluster by the management node, the recorded self-growth key value is consistent with the content of the self-growth message, and the problem that the self-growth keys of the main and standby database insertion operation records are inconsistent is solved.
5. The backup method of the invention has high response speed to the upper application layer, and gives consideration to data consistency and response speed.
Drawings
FIG. 1 is an overall block diagram of the system of the present invention.
Fig. 2 is a schematic diagram of the primary node and the secondary node according to the present invention.
Fig. 3 is a flow chart of the method of the present invention.
Detailed Description
For a better understanding of the present invention by those skilled in the art, the present invention will be described in further detail below with reference to the accompanying drawings and the following examples.
Example 1
As shown in fig. 1 and fig. 2, the present embodiment provides a heterogeneous database cluster backup system, including an operation management component and a heterogeneous database cluster, where the operation management component is configured to provide a coordination processing capability of database operations from an upper application layer to a database layer, and the heterogeneous database cluster is configured to backup data of MySQL nodes, and in the case of an abnormal MySQL node, the heterogeneous database cluster can be upgraded to a master node to solely undertake the database operations; partial DQL operation can be undertaken according to requirements under the condition that the MySQL node is not abnormal; the operation management component comprises a main node and a plurality of auxiliary nodes which are respectively communicated with the main node, wherein the main node and the auxiliary nodes respectively comprise a statement analysis module, a message forwarding module and a global queue module,
a statement analysis module: the system is used for judging the type of the MySQL operation statement and outputting an analysis result, wherein the analysis result is DQL, DML, DDL or DCL;
the message forwarding module: according to the analysis result of the statement analysis module, forwarding the operation information of the MySQL operation statement to the MySQL node or the heterogeneous database cluster according to a specified strategy;
a global queue module: and storing MySQL operation statements of operation failure of the heterogeneous database cluster caused by communication reasons, and managing the consistency of data in the main node and the global queue modules of all the auxiliary nodes by the main node.
When the auxiliary node modifies the data in the global queue module, the auxiliary node needs to apply for the main node, and after the application is passed, the main node modifies the data in the global queue module; when the current master node fails, the slave nodes elect a new master node according to a set rule, wherein the set rule is an existing election algorithm, such as a bullly algorithm and a ring algorithm.
The heterogeneous database cluster includes but is not limited to a Vernox cluster, the Vernox cluster can store an in-memory database of structured data and unstructured data, the Vernox itself and MySQL are heterogeneous databases, MySQL is a traditional relational database, and Vernox is a fusion database, and includes a client driving module and a compiling execution system, and the client driving module: receiving a MySQL operation statement, performing pre-analysis on the MySQL operation statement and generating an execution plan; compiling the execution system: and checking the field legality of the execution plan, and performing optimized execution of the MySQL operation statement after the legality passes, thereby completing the analysis, processing and conversion work of the MySQL operation statement in the database.
As shown in fig. 3, the present embodiment provides a backup method for a heterogeneous database cluster, including the following steps:
s1, inputting an operation sentence: the upper application layer transmits the MySQL operation statement to the operation management component, and the MySQL operation statement is located in the main node or the auxiliary node;
s2, judging the type of the operation statement: the statement analysis module analyzes the type of the MySQL operation statement and outputs an analysis result, wherein the analysis result is DQL, DML, DDL or DCL;
when the analysis result is DQL, S4 is performed; when the analysis result is non-DQL, S3 is performed;
s3, operation management component internal statement transfer: after transferring the MySQL operation statement to the main node, executing S4;
and S4, aiming at different analysis results, the MySQL node and the Vernox cluster execute corresponding operations, return the execution results to the operation management component, and finally return the execution results to the upper-layer application by the operation management component.
When the analysis result in S4 is DQL, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to a MySQL node;
step two, the MySQL node executes the statement: the MySQL node executes the query operation and returns the query result to the operation management component;
step three, returning an execution result: and the operation management component returns the query result to the upper application layer.
When the analysis result in S4 is the DML insertion operation, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to a MySQL node;
step two, the MySQL node executes the statement: the MySQL node executes the insertion operation and returns the insertion result to the operation management component;
step three, returning an execution result: the operation management component returns the insertion result to the upper application layer, if the insertion result is failure, the flow is ended, and if the insertion result is success, the fourth step is executed;
step four, forwarding the statement: forwarding the self-growth message and the insertion statement to a Vernox cluster;
step five, the Vernox cluster executes the statement: obtaining a self-growing value through the self-growing message, then executing an insertion statement, avoiding the repetition of the self-growing main key of the insertion item, and returning an insertion result to the operation management component;
step six, ensuring that the Vernox cluster successfully inserts data: if the insertion result in the step five is successful, the process is ended, and if the insertion result in the step five is failed, the processing is performed according to the failure reason, specifically:
if the insertion fails due to the communication problem, pushing the insertion statement into the global queue module, and subsequently executing the insertion operation again from the global queue module until the insertion operation is successful;
and if the insertion fails due to other reasons, performing data synchronization operation of the Vernox cluster to ensure successful insertion.
When the analysis result in S4 is an update or deletion operation of the DML, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to the MySQL node and the Vernox cluster;
step two, the MySQL node and the Vernox cluster execute the statement: the MySQL node and the Vernox cluster execute updating or deleting operation and return the execution results of the MySQL node and the Vernox cluster to the operation management component;
step three, returning an execution result: the operation management component returns the execution result of the MySQL node to the upper application layer and the Vernox cluster;
step four, comprehensively executing results: if the MySQL node execution result is successful, executing the step five, and if the MySQL node execution result is failed, rolling back the execution result of the Vernox cluster to ensure the data consistency of the MySQL node and the Vernox cluster;
step five, ensuring that the Vernox cluster successfully inserts data: if the execution result of the second Vernox cluster is successful, the process is ended, and if the execution result of the second Vernox cluster is failed, the processing is performed according to the failure reason, specifically:
if the updating or deleting fails due to the communication problem, pushing the operation statement into the global queue module, and subsequently executing the updating or deleting operation again from the global queue module until the operation is successful;
and if the updating or deleting fails due to other reasons, performing data synchronization operation of the Vernox cluster, and ensuring the data consistency of the MySQL node and the Vernox cluster.
When the analysis result in S4 is DDL or DCL, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to the MySQL node and the Vernox cluster;
step two, the MySQL node executes the statement: the MySQL node executes DDL or DCL operation and returns an execution result to the operation management component;
step three, returning an execution result: the operation management component returns the execution result to the upper application layer;
step four, the Vernox cluster executes the statement: and the Vernox cluster executes DDL or DCL operation and the process is ended.
The invention creatively uses an operation management component formed by a plurality of nodes and a Vernox cluster which is heterogeneous to the MySQL node to replace the MySQL database to back up the node, thereby preventing the problem that a logic error is propagated in homogeneous MySQL main and standby nodes from the architecture perspective; meanwhile, the Vernox cluster follows the MySQL protocol, the data backup is carried out on the MySQL nodes by using the Vernox cluster, the data backup is invisible to the upper layer, and a user or an application layer does not need to carry out complex backup configuration work any more, so that the usability is strong.
The above description is only a preferred embodiment of the present invention, and not intended to limit the present invention, the scope of the present invention is defined by the appended claims, and all structural changes that can be made by using the contents of the description and the drawings of the present invention are intended to be embraced therein.
Claims (8)
1. A heterogeneous database cluster backup system, characterized by: newly adding a heterogeneous database cluster backup system at the entrance of the MySQL database, and adopting the heterogeneous database as a backup database of MySQL nodes; the operation management component is used for providing coordination processing capability of database operation from an upper application layer to a database layer, and the heterogeneous database cluster is used for data backup of MySQL nodes; the operation management component comprises a main node and a plurality of auxiliary nodes which are respectively communicated with the main node, wherein the main node and the auxiliary nodes respectively comprise a statement analysis module, a message forwarding module and a global queue module,
a statement analysis module: the system is used for judging the type of the MySQL operation statement and outputting an analysis result;
the message forwarding module: according to the analysis result of the statement analysis module, forwarding the operation information of the MySQL operation statement to the MySQL node or the heterogeneous database cluster according to a specified strategy;
a global queue module: storing MySQL operation statements of operation failure of the heterogeneous database cluster caused by communication reasons, and managing the consistency of data in the master node and the global queue modules of all the slave nodes by the master node;
when the auxiliary node modifies the data in the global queue module, the auxiliary node needs to apply for the main node, and after the application is passed, the main node modifies the data in the global queue module.
2. The heterogeneous database cluster backup system of claim 1, wherein: and when the current main node fails, selecting a new main node from the auxiliary nodes according to a set rule.
3. The heterogeneous database cluster backup system of claim 1, wherein: the analysis result is DQL, DML, DDL or DCL.
4. The heterogeneous database cluster backup system of claim 1, wherein: the heterogeneous database cluster comprises but is not limited to a Vernox cluster, the Vernox cluster is a converged database and comprises a client driving module and a compiling and executing system,
a client driver module: receiving a MySQL operation statement, performing pre-analysis on the MySQL operation statement and generating an execution plan;
compiling the execution system: and checking the field legality of the execution plan, and performing optimized execution of the MySQL operation statement after the legality passes, thereby completing the analysis, processing and conversion work of the MySQL operation statement in the database.
5. A heterogeneous database cluster backup method is characterized in that a heterogeneous database cluster backup system is newly added at an entrance of a MySQL database, and the heterogeneous database is used as a standby database of MySQL nodes; the method comprises the following steps:
s1, inputting an operation sentence: the upper application layer transmits the MySQL operation statement to the operation management component, and the MySQL operation statement is located in the main node or the auxiliary node;
s2, judging the type of the operation statement: the statement analysis module analyzes the type of the MySQL operation statement and outputs an analysis result, wherein the analysis result is DQL, DML, DDL or DCL;
when the analysis result is DQL, S4 is performed; when the analysis result is non-DQL, S3 is performed;
s3, operation management component internal statement transfer: after transferring the MySQL operation statement to the main node, executing S4;
s4, aiming at different analysis results, the MySQL node and the Vernox cluster execute corresponding operations, return the execution results to the operation management component, and finally return the execution results to the upper application by the operation management component;
when the analysis result in S4 is the DML insertion operation, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to a MySQL node;
step two, the MySQL node executes the statement: the MySQL node executes the insertion operation and returns the insertion result to the operation management component;
step three, returning an execution result: the operation management component returns the insertion result to the upper application layer, if the insertion result is failure, the flow is ended, and if the insertion result is success, the fourth step is executed;
step four, forwarding the statement: forwarding the self-growth message and the insertion statement to a Vernox cluster;
step five, the Vernox cluster executes the statement: obtaining a self-growing value through the self-growing message, then executing an insertion statement, avoiding the repetition of the self-growing main key of the insertion item, and returning an insertion result to the operation management component;
step six, ensuring that the Vernox cluster successfully inserts data: if the insertion result in the step five is successful, the process is ended, and if the insertion result in the step five is failed, the processing is performed according to the failure reason, specifically:
if the insertion fails due to the communication problem, pushing the insertion statement into the global queue module, and subsequently executing the insertion operation again from the global queue module until the insertion operation is successful;
if the insertion fails due to other reasons, performing data synchronization operation of the Vernox cluster to ensure successful insertion;
when the auxiliary node modifies the data in the global queue module, the auxiliary node needs to apply for the main node, and after the application is passed, the main node modifies the data in the global queue module.
6. The method for backup of a heterogeneous database cluster according to claim 5, wherein when the analysis result in S4 is DQL, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to a MySQL node;
step two, the MySQL node executes the statement: the MySQL node executes the query operation and returns the query result to the operation management component;
step three, returning an execution result: and the operation management component returns the query result to the upper application layer.
7. The method for backing up a cluster of heterogeneous databases according to claim 5, wherein when the analysis result in S4 is an update or delete operation of a DML, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to the MySQL node and the Vernox cluster;
step two, the MySQL node and the Vernox cluster execute the statement: the MySQL node and the Vernox cluster execute updating or deleting operation and return the execution results of the MySQL node and the Vernox cluster to the operation management component;
step three, returning an execution result: the operation management component returns the execution result of the MySQL node to the upper application layer and the Vernox cluster;
step four, comprehensively executing results: if the MySQL node execution result is successful, executing the step five, and if the MySQL node execution result is failed, rolling back the execution result of the Vernox cluster to ensure the data consistency of the MySQL node and the Vernox cluster;
step five, ensuring that the Vernox cluster updating or deleting operation is successful: if the execution result of the second Vernox cluster is successful, the process is ended, and if the execution result of the second Vernox cluster is failed, the processing is performed according to the failure reason, specifically:
if the updating or deleting fails due to the communication problem, pushing the operation statement into the global queue module, and subsequently executing the updating or deleting operation again from the global queue module until the operation is successful;
and if the updating or deleting fails due to other reasons, performing data synchronization operation of the Vernox cluster, and ensuring the data consistency of the MySQL node and the Vernox cluster.
8. The method for backing up a heterogeneous database cluster according to claim 5, wherein when the analysis result in the S4 is DDL or DCL, the method specifically includes the following processing steps:
step one, forwarding an operation statement: forwarding the MySQL operation statement to the MySQL node and the Vernox cluster;
step two, the MySQL node executes the statement: the MySQL node executes DDL or DCL operation and returns an execution result to the operation management component;
step three, returning an execution result: the operation management component returns the execution result to the upper application layer;
step four, the Vernox cluster executes the statement: and the Vernox cluster executes DDL or DCL operation and the process is ended.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811208785.6A CN109298976B (en) | 2018-10-17 | 2018-10-17 | Heterogeneous database cluster backup system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811208785.6A CN109298976B (en) | 2018-10-17 | 2018-10-17 | Heterogeneous database cluster backup system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109298976A CN109298976A (en) | 2019-02-01 |
| CN109298976B true CN109298976B (en) | 2022-04-12 |
Family
ID=65162974
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811208785.6A Active CN109298976B (en) | 2018-10-17 | 2018-10-17 | Heterogeneous database cluster backup system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109298976B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111639113A (en) * | 2019-03-01 | 2020-09-08 | 千寻位置网络有限公司 | System and method for collecting SQL data executed by MySQL database |
| CN113703954A (en) * | 2020-05-21 | 2021-11-26 | 中移(苏州)软件技术有限公司 | Message backup method and device, electronic equipment and computer storage medium |
| CN112035514B (en) * | 2020-09-02 | 2024-09-06 | 北京金山云网络技术有限公司 | Database statement processing method and device, electronic equipment and storage medium |
| CN113064913A (en) * | 2021-03-26 | 2021-07-02 | 北京深思数盾科技股份有限公司 | Interactive statement processing method, electronic device and computer-readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106407264A (en) * | 2016-08-25 | 2017-02-15 | 成都索贝数码科技股份有限公司 | High-availability and high-consistency database cluster system and command processing method thereof |
| CN106708842A (en) * | 2015-11-12 | 2017-05-24 | 阿里巴巴集团控股有限公司 | Data loading method for application system, database and application system |
| CN107402991A (en) * | 2016-09-21 | 2017-11-28 | 广州特道信息科技有限公司 | A kind of method for writing semi-structured data and distributed NewSQL Database Systems |
| CN107590256A (en) * | 2017-09-20 | 2018-01-16 | 北京九桥同步软件有限公司 | Heterogeneous database synchronization method and device |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2010232688C1 (en) * | 2009-03-31 | 2014-04-10 | Commvault Systems, Inc. | Systems and methods for normalizing data of heterogeneous data sources |
| CN102662793A (en) * | 2012-03-07 | 2012-09-12 | 江苏引跑网络科技有限公司 | Hot backup and recovery method of distributed database with guarantee of data consistency |
| US9575849B2 (en) * | 2014-11-25 | 2017-02-21 | Sap Se | Synchronized backup and recovery of database systems |
| US10929246B2 (en) * | 2015-10-07 | 2021-02-23 | International Business Machines Corporation | Backup capability for object store used as primary storage |
| CN106301938A (en) * | 2016-08-25 | 2017-01-04 | 成都索贝数码科技股份有限公司 | A kind of high availability and the data base cluster system of strong consistency and node administration method thereof |
| CN107301250B (en) * | 2017-07-27 | 2020-06-26 | 南京南瑞集团公司 | Multi-source database collaborative backup method |
| CN107391306B (en) * | 2017-07-27 | 2019-12-10 | 国家电网公司 | Heterogeneous database backup file recovery method |
| CN109165262B (en) * | 2018-10-16 | 2022-05-10 | 成都索贝数码科技股份有限公司 | Fragmentation clustering system and fragmentation method of relational large table |
-
2018
- 2018-10-17 CN CN201811208785.6A patent/CN109298976B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106708842A (en) * | 2015-11-12 | 2017-05-24 | 阿里巴巴集团控股有限公司 | Data loading method for application system, database and application system |
| CN106407264A (en) * | 2016-08-25 | 2017-02-15 | 成都索贝数码科技股份有限公司 | High-availability and high-consistency database cluster system and command processing method thereof |
| CN107402991A (en) * | 2016-09-21 | 2017-11-28 | 广州特道信息科技有限公司 | A kind of method for writing semi-structured data and distributed NewSQL Database Systems |
| CN107590256A (en) * | 2017-09-20 | 2018-01-16 | 北京九桥同步软件有限公司 | Heterogeneous database synchronization method and device |
Non-Patent Citations (2)
| Title |
|---|
| MySQL集群到Oracle数据库的数据同步方法;杨明珉等;《计算机系统应用》;20180615;第27卷(第06期);第60-68页 * |
| Vernox融合数据库;成都索贝数码科技股份有限公司;《http://www.sobey.com/index.php?m=content&c=index&a=lists&catid=52》;20180305;第1-5页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109298976A (en) | 2019-02-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109298976B (en) | Heterogeneous database cluster backup system and method | |
| CN101334797B (en) | Distributed file systems and its data block consistency managing method | |
| US7743036B2 (en) | High performance support for XA protocols in a clustered shared database | |
| CN109729129A (en) | Configuration modification method, storage cluster and the computer system of storage cluster | |
| CN109656911A (en) | Distributed variable-frequencypump Database Systems and its data processing method | |
| CN104885054A (en) | System and method for performing a transaction in a massively parallel processing database | |
| CN109189860A (en) | A kind of active and standby increment synchronization method of MySQL based on Kubernetes system | |
| US20060195487A1 (en) | Systems and Methods for Managing the Synchronization of Replicated Version-Managed Databases | |
| CN102317913B (en) | A kind of transaction recovery method and transaction recovery device | |
| CN105630589A (en) | Distributed process scheduling system and process scheduling and execution method | |
| CN101751415B (en) | Metadata service system, metadata synchronized method and writing server updating method | |
| CN113553313B (en) | Data migration method and system, storage medium and electronic equipment | |
| CN103995868A (en) | Distributed system oriented global transaction manager and transaction handling method | |
| CN110569149A (en) | method for triggering automatic emergency switching of Oracle disaster tolerance based on fault detection | |
| US20130346363A1 (en) | Data synchronization method, computer readable recording medium having stored therein data synchronization program, and data synchronization control device | |
| EP4213038A1 (en) | Data processing method and apparatus based on distributed storage, device, and medium | |
| CN103345502A (en) | Transaction processing method and system of distributed type database | |
| CN106503257A (en) | Distributed transaction server method and system based on binlog compensation mechanism | |
| CN105426427A (en) | MPP database cluster replica realization method based on RAID 0 storage | |
| US9612921B2 (en) | Method and system for load balancing a distributed database providing object-level management and recovery | |
| CN102855314A (en) | Real-time database backup system and method based on FPGA (field programmable gate array) | |
| CN105069152A (en) | Data processing method and apparatus | |
| CN109361777A (en) | Synchronous method, synchronization system and the relevant apparatus of distributed type assemblies node state | |
| CN115480714A (en) | Satellite big data distributed storage system based on block chain | |
| CN110427427B (en) | Method for realizing global transaction distributed processing through pin bridging |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220517 Address after: 610041 No. 1, floor 4, building 1, No. 2, Xinyuan south 2nd Road, high tech Zone, Chengdu, Sichuan Patentee after: Chengdu sobei video cloud computing Co.,Ltd. Address before: No.2, south 2nd Road, Xinyuan, high tech Zone, Chengdu, Sichuan 610041 Patentee before: Chengdu Sobey Digital Technology Co.,Ltd. |
|
| TR01 | Transfer of patent right |