CN109298976A - Heterogeneous database cluster backup system and method - Google Patents
Heterogeneous database cluster backup system and method Download PDFInfo
- Publication number
- CN109298976A CN109298976A CN201811208785.6A CN201811208785A CN109298976A CN 109298976 A CN109298976 A CN 109298976A CN 201811208785 A CN201811208785 A CN 201811208785A CN 109298976 A CN109298976 A CN 109298976A
- Authority
- CN
- China
- Prior art keywords
- mysql
- cluster
- node
- result
- 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.)
- Granted
Links
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
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 present invention relates to database technical fields, more particularly to a kind of heterogeneous database cluster backup system and side
Method.
Background technique
Database is the core component of modern enterprise, and the core data of enterprises is not only store in database, is also held
The function that core business externally services is carried on a shoulder pole, the core business database of large and medium-sized enterprise generally requires to bear per second thousands of
Operation requests, a few minutes even several seconds delay machines can all cause wholesale economic loss, the high availability of database to enterprise
It is that enterprise has to consider the problems of；On the other hand, data storage must be reliable enough, and system data can be guaranteed in conventional event
It will not lose in barrier, Database Systems have the ability of certain resisting risk, and database needs need for reliable backup to guarantee data security.
The backup deployment way of existing database cluster is often the backup that data are carried out with isomorphism database, for example is used
The MySQL database that MySQL database backs up needs backs up, and a very big problem of this backup mode is,
The bottom layer realization logic of isomorphism database and the mode of realization be it is identical, the Single Point of Faliure as caused by mathematical logic problem will be led
It causes failure to propagate in storage cluster, significantly reduces the availability and efficiency of data-base cluster.
Summary of the invention
It is an object of the invention to: data backup is carried out in order to solve existing data-base cluster using isomorphism database,
Single Point of Faliure caused by mathematical logic problem can be propagated in storage cluster, cause the availability of data-base cluster is lower to ask
Topic, the present invention provide a kind of heterogeneous database cluster backup system and method, increase isomeric data newly in the entrance of MySQL database
Library cluster backup system, and the standby database using heterogeneous database as MySQL node, ensure that data in primary database
With the consistency in backup database, the availability of data-base cluster is improved.
The present invention specifically uses following technical scheme to achieve the goals above:
A kind of heterogeneous database cluster backup system, including operational administrative component and heterogeneous database cluster, the operation
Management assembly is for providing Coordination Treatment ability of the database manipulation from upper application layer to database layer, heterogeneous database cluster
Data backup for MySQL node；The operational administrative component include host node and respectively with host node communication multiple pairs
Node, the host node and vice-node include statement parsing module, message transmitting module and Global Queue's module,
Statement parsing module: for determining the type of MySQL action statement, parsing result is exported；
Message transmitting module: according to the parsing result of statement parsing module, according to the tactful by MySQL action statement of regulation
Operation information be transmitted to MySQL node or heterogeneous database cluster；
Global Queue's module: the MySQL operation of the failure of heterogeneous database cluster operation caused by due to communication is stored
Sentence, and by host node management host node itself and the consistency of Global Queue's mould data in block of all vice-nodes.
Further, it when the vice-node modifies its Global Queue's mould data in block, needs to host node application, application is logical
Later, it is modified by host node to the data in its Global Queue's module.
Further, when current primary node fails, the rule from vice-node according to setting elects new host node, institute
The rule set is stated as existing election algorithm.
Further, the parsing result is DQL, DML, DDL or DCL.
Further, the heterogeneous database cluster includes but is not limited to Vernox cluster, and the Vernox cluster is to melt
Database, including client driven module and Complied executing system are closed,
Client driven module: receiving MySQL action statement, and MySQL action statement is carried out pre-parsed and generated to execute meter
It draws；
Complied executing system: MySQL action statement is carried out after examining the field legitimacy of executive plan, legitimacy to pass through
Optimization executes, and completes the analysis processing and conversion work of MySQL action statement in the database.
A kind of heterogeneous database cluster backup method, includes the following steps:
S1, input action statement: MySQL action statement is passed to operational administrative component by upper application layer, and MySQL operates language
Sentence is located in host node or vice-node；
S2, judge action statement type: statement parsing module parses the type of MySQL action statement, exports parsing result,
The parsing result is DQL, DML, DDL or DCL；
When parsing result is DQL, S4 is executed；When parsing result is non-DQL, S3 is executed；
S3, the transfer of operational administrative component internal sentence: after MySQL action statement is transferred to host node, S4 is executed；
S4, corresponding operation is executed for different parsing results, MySQL node and Vernox cluster, and knot will be executed
Fruit is back to operational administrative component, and implementing result is finally back to upper layer application by operational administrative component.
Further, when parsing result is DQL in the S4, following processing step is specifically included:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node；
Step 2: MySQL node executes sentence: MySQL node executes inquiry operation, and query result is back to operation
Management assembly；
Step 3: returning to implementing result: query result is back to upper application layer by operational administrative component.
Further, when parsing result is the insertion operation of DML in the S4, following processing step is specifically included:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node；
Step 2: MySQL node executes sentence: MySQL node executes insertion operation, and insertion result is back to operation
Management assembly；
Step 3: returning to implementing result: operational administrative component is back to upper application layer for result is inserted into, if insertion result
For failure, then process terminates, if insertion result is successfully, to then follow the steps four；
Step 4: forwarding sentence: self-propagation message and insertion sentence are forwarded to Vernox cluster；
Step 5: Vernox cluster executes sentence: obtaining the value of self-propagation by self-propagation message, then execute parenthesis
Sentence, avoids the self-propagation major key of inserted term from repeating, and returns to insertion result to operational administrative component；
Step 6: guaranteeing the insertion data success of Vernox cluster: if the insertion result in step 5 is successfully process knot
Beam is handled if the insertion result in step 5 is failure according to failure cause, specifically:
It is subsequent from global team if insertion sentence is pushed into Global Queue's module since Communication causes insertion to fail
Insertion operation is executed again in column module, until success；
If carrying out the data simultaneously operating of Vernox cluster because being inserted into failure caused by other reasons, guarantee is inserted into successfully.
Further, when parsing result is the update or delete operation of DML in the S4, following processing step is specifically included
It is rapid:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node and Vernox cluster；
Step 2: MySQL node and Vernox cluster execute sentence: MySQL node and Vernox cluster execute update or
Delete operation, and the implementing result of the two is back to operational administrative component；
Step 3: returning to implementing result: the implementing result of MySQL node is back to upper application layer by operational administrative component
With Vernox cluster；
Step 4: comprehensive implementing result: if MySQL node implementing result is successfully, to then follow the steps five, if MySQL is saved
Point implementing result is failure, then the implementing result of rollback Vernox cluster, it is ensured that the data one of MySQL node and Vernox cluster
Cause property；
Step 5: guarantee Vernox cluster insertion data success: if step 2 Vernox cluster implementing result be successfully,
Process terminates, if step 2 Vernox cluster implementing result is failure, is handled according to failure cause, specifically:
If due to Communication cause update or delete failure, by action statement be pushed into Global Queue's module, it is subsequent from
Update or delete operation are executed in Global Queue's module again, until success；
If carrying out the data simultaneously operating of Vernox cluster because failure is updated or deleted caused by other reasons, guarantee
The data consistency of MySQL node and Vernox cluster.
Further, when parsing result is DDL or DCL in the S4, following processing step is specifically included:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node and Vernox cluster；
Step 2: MySQL node executes sentence: MySQL node executes DDL or DCL operation, and implementing result is back to
Operational administrative component；
Step 3: returning to implementing result: implementing result is back to upper application layer by operational administrative component；
Step 4: Vernox cluster executes sentence: Vernox cluster executes DDL or DCL operation, and process terminates.
Beneficial effects of the present invention are as follows:
1, the operational administrative component that the present invention is innovatively constituted with multinode and the Vernox cluster with MySQL node isomery
Substitution MySQL database carrys out backup node, prevents logic error to propagate in the MySQL main-standby nodes of isomorphism from framework angle
The problem of；Vernox cluster follows MySQL agreement again simultaneously, use invisible to upper layer of for MySQL node doing data backup with it
Family or application layer no longer need to do complicated backup configuration work, and availability is strong.
2, present invention invention uses backup database of the data-base cluster as MySQL node, and backup database itself is
Group meets the high serious forgiveness of backup MySQL node by guaranteeing the serious forgiveness of data-base cluster, and the reliability of standby system is very
By force.
3, the sentence of failure will be executed in backup method of the present invention in heterogeneous database cluster as caused by Communication
Global Queue's module in the management node of operational administrative component is added, is executed in Global Queue's module again when communicating recovery
Sentence can avoid backup cluster instability problem as caused by network cause.
4, in data of the invention insertion process, by first carrying out MySQL sentence, note is returned after MySQL is finished
The self-propagation message of record；Self-propagation message and insertion sentence are transmitted to Vernox cluster by management node again, record increases certainly
Long key assignments is consistent with self-propagation message content, solves the problems, such as that insertion operation record self-propagation key in master/slave data library is inconsistent.
5, backup method of the invention has taken into account data consistency and response speed to the fast response time of upper application layer
Degree.
Detailed description of the invention
Fig. 1 is the overall structure figure of present system.
Fig. 2 is the composition schematic diagram of host node of the present invention and vice-node.
Fig. 3 is the flow chart of the method for the present invention.
Specific embodiment
In order to which those skilled in the art better understand the present invention, with reference to the accompanying drawing with following embodiment to the present invention
It is described in further detail.
Embodiment 1
As depicted in figs. 1 and 2, the present embodiment provides a kind of heterogeneous database cluster backup systems, including operational administrative group
Part and heterogeneous database cluster, the operational administrative component are used to provide database manipulation from upper application layer to database layer
Coordination Treatment ability, data backup of the heterogeneous database cluster for MySQL node can in the case where MySQL node exception
Database manipulation is individually undertaken to upgrade to host node；It can also be held as desired in the case where MySQL node exception does not occur
Carry on a shoulder pole the DQL operation of part；The operational administrative component include host node and respectively with host node communication multiple vice-nodes, it is described
Host node and vice-node include statement parsing module, message transmitting module and Global Queue's module,
Statement parsing module: for determining the type of MySQL action statement, parsing result is exported, the parsing result is
DQL, DML, DDL or DCL；
Message transmitting module: according to the parsing result of statement parsing module, according to the tactful by MySQL action statement of regulation
Operation information be transmitted to MySQL node or heterogeneous database cluster；
Global Queue's module: the MySQL operation of the failure of heterogeneous database cluster operation caused by due to communication is stored
Sentence, and by host node management host node itself and the consistency of Global Queue's mould data in block of all vice-nodes.
When the vice-node modifies its Global Queue's mould data in block, need to pass through after application passes through to host node application
Host node modifies to the data in its Global Queue's module；When current primary node failure, according to setting from vice-node
Rule elect new host node, the rule set is existing election algorithm, such as bully algorithm, ring algorithm etc..
The heterogeneous database cluster includes but is not limited to Vernox cluster, and Vernox cluster being capable of structured data
With the memory database of unstructured data, Vernox and MySQL itself is heterogeneous database, and MySQL is traditional relationship number
According to library, and Vernox is amalgamation database, including client driven module and Complied executing system, client driven module: is received
MySQL action statement carries out pre-parsed to MySQL action statement and generates executive plan；Complied executing system: inspection executes meter
The field legitimacy drawn, legitimacy carries out MySQL action statement optimization after passing through execute, and complete MySQL action statement in number
According to the analysis processing and conversion work in library.
As shown in figure 3, including the following steps: the present embodiment provides a kind of heterogeneous database cluster backup method
S1, input action statement: MySQL action statement is passed to operational administrative component by upper application layer, and MySQL operates language
Sentence is located in host node or vice-node；
S2, judge action statement type: statement parsing module parses the type of MySQL action statement, exports parsing result,
The parsing result is DQL, DML, DDL or DCL；
When parsing result is DQL, S4 is executed；When parsing result is non-DQL, S3 is executed；
S3, the transfer of operational administrative component internal sentence: after MySQL action statement is transferred to host node, S4 is executed；
S4, corresponding operation is executed for different parsing results, MySQL node and Vernox cluster, and knot will be executed
Fruit is back to operational administrative component, and implementing result is finally back to upper layer application by operational administrative component.
When parsing result is DQL in the S4, following processing step is specifically included:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node；
Step 2: MySQL node executes sentence: MySQL node executes inquiry operation, and query result is back to operation
Management assembly；
Step 3: returning to implementing result: query result is back to upper application layer by operational administrative component.
When parsing result is the insertion operation of DML in the S4, following processing step is specifically included:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node；
Step 2: MySQL node executes sentence: MySQL node executes insertion operation, and insertion result is back to operation
Management assembly；
Step 3: returning to implementing result: operational administrative component is back to upper application layer for result is inserted into, if insertion result
For failure, then process terminates, if insertion result is successfully, to then follow the steps four；
Step 4: forwarding sentence: self-propagation message and insertion sentence are forwarded to Vernox cluster；
Step 5: Vernox cluster executes sentence: obtaining the value of self-propagation by self-propagation message, then execute parenthesis
Sentence, avoids the self-propagation major key of inserted term from repeating, and returns to insertion result to operational administrative component；
Step 6: guaranteeing the insertion data success of Vernox cluster: if the insertion result in step 5 is successfully process knot
Beam is handled if the insertion result in step 5 is failure according to failure cause, specifically:
It is subsequent from global team if insertion sentence is pushed into Global Queue's module since Communication causes insertion to fail
Insertion operation is executed again in column module, until success；
If carrying out the data simultaneously operating of Vernox cluster because being inserted into failure caused by other reasons, guarantee is inserted into successfully.
When parsing result is the update or delete operation of DML in the S4, following processing step is specifically included:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node and Vernox cluster；
Step 2: MySQL node and Vernox cluster execute sentence: MySQL node and Vernox cluster execute update or
Delete operation, and the implementing result of the two is back to operational administrative component；
Step 3: returning to implementing result: the implementing result of MySQL node is back to upper application layer by operational administrative component
With Vernox cluster；
Step 4: comprehensive implementing result: if MySQL node implementing result is successfully, to then follow the steps five, if MySQL is saved
Point implementing result is failure, then the implementing result of rollback Vernox cluster, it is ensured that the data one of MySQL node and Vernox cluster
Cause property；
Step 5: guarantee Vernox cluster insertion data success: if step 2 Vernox cluster implementing result be successfully,
Process terminates, if step 2 Vernox cluster implementing result is failure, is handled according to failure cause, specifically:
If due to Communication cause update or delete failure, by action statement be pushed into Global Queue's module, it is subsequent from
Update or delete operation are executed in Global Queue's module again, until success；
If carrying out the data simultaneously operating of Vernox cluster because failure is updated or deleted caused by other reasons, guarantee
The data consistency of MySQL node and Vernox cluster.
When parsing result is DDL or DCL in the S4, following processing step is specifically included:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node and Vernox cluster；
Step 2: MySQL node executes sentence: MySQL node executes DDL or DCL operation, and implementing result is back to
Operational administrative component；
Step 3: returning to implementing result: implementing result is back to upper application layer by operational administrative component；
Step 4: Vernox cluster executes sentence: Vernox cluster executes DDL or DCL operation, and process terminates.
The operational administrative component and replaced with the Vernox cluster of MySQL node isomery that the present invention is innovatively constituted with multinode
Carry out backup node for MySQL database, prevents logic error to propagate in the MySQL main-standby nodes of isomorphism from framework angle
Problem；Vernox cluster follows MySQL agreement again simultaneously, with its, user invisible to upper layer that be that MySQL node does data backup
Or application layer no longer needs to do complicated backup configuration work, availability is strong.
The above, only presently preferred embodiments of the present invention, are not intended to limit the invention, patent protection model of the invention
It encloses and is subject to claims, it is all to change with equivalent structure made by specification and accompanying drawing content of the invention, similarly
It should be included within the scope of the present invention.
Claims (10)
1. a kind of heterogeneous database cluster backup system, it is characterised in that: including operational administrative component and heterogeneous database cluster,
The operational administrative component is for providing Coordination Treatment ability of the database manipulation from upper application layer to database layer, isomery number
The data backup of MySQL node is used for according to library cluster；The operational administrative component includes host node and communicates respectively with host node
Multiple vice-nodes, the host node and vice-node include statement parsing module, message transmitting module and Global Queue's module,
Statement parsing module: for determining the type of MySQL action statement, parsing result is exported；
Message transmitting module: according to the parsing result of statement parsing module, according to the tactful behaviour by MySQL action statement of regulation
MySQL node or heterogeneous database cluster are transmitted to as information；
Global Queue's module: storing the MySQL action statement of the failure of heterogeneous database cluster operation caused by due to communication,
And the consistency of Global Queue's mould data in block of host node itself and all vice-nodes is managed by host node.
2. a kind of heterogeneous database cluster backup system according to claim 1, it is characterised in that: the vice-node modification
When its Global Queue's mould data in block, need to host node application, after application passes through, by host node to its Global Queue's module
Interior data are modified.
3. a kind of heterogeneous database cluster backup system according to claim 1, it is characterised in that: when current primary node loses
When effect, the rule from vice-node according to setting elects new host node.
4. a kind of heterogeneous database cluster backup system according to claim 1, it is characterised in that: the parsing result is
DQL, DML, DDL or DCL.
5. a kind of heterogeneous database cluster backup system according to claim 1, it is characterised in that: the heterogeneous database
Cluster includes but is not limited to Vernox cluster, and the Vernox cluster is amalgamation database, including client driven module and compiling
Execution system,
Client driven module: receiving MySQL action statement, carries out pre-parsed to MySQL action statement and generates executive plan；
Complied executing system: the optimization of MySQL action statement is carried out after examining the field legitimacy of executive plan, legitimacy to pass through
It executes, completes the analysis processing and conversion work of MySQL action statement in the database.
6. a kind of heterogeneous database cluster backup method, which comprises the steps of:
S1, input action statement: MySQL action statement is passed to operational administrative component, MySQL action statement position by upper application layer
In host node or vice-node；
S2, judge action statement type: statement parsing module parses the type of MySQL action statement, exports parsing result, described
Parsing result is DQL, DML, DDL or DCL；
When parsing result is DQL, S4 is executed；When parsing result is non-DQL, S3 is executed；
S3, the transfer of operational administrative component internal sentence: after MySQL action statement is transferred to host node, S4 is executed；
S4, corresponding operation is executed for different parsing results, MySQL node and Vernox cluster, and implementing result is returned
It is back to operational administrative component, implementing result is finally back to upper layer application by operational administrative component.
7. a kind of heterogeneous database cluster backup method according to claim 6, which is characterized in that parsed when in the S4
When being as a result DQL, following processing step is specifically included:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node；
Step 2: MySQL node executes sentence: MySQL node executes inquiry operation, and query result is back to operational administrative
Component；
Step 3: returning to implementing result: query result is back to upper application layer by operational administrative component.
8. a kind of heterogeneous database cluster backup method according to claim 6, which is characterized in that parsed when in the S4
When being as a result the insertion operation of DML, following processing step is specifically included:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node；
Step 2: MySQL node executes sentence: MySQL node executes insertion operation, and insertion result is back to operational administrative
Component；
Step 3: returning to implementing result: operational administrative component is back to upper application layer for result is inserted into, if insertion result is to lose
It loses, then process terminates, if insertion result is successfully, to then follow the steps four；
Step 4: forwarding sentence: self-propagation message and insertion sentence are forwarded to Vernox cluster；
Step 5: Vernox cluster executes sentence: obtaining the value of self-propagation by self-propagation message, then execute insertion sentence, keep away
The self-propagation major key for exempting from inserted term repeats, and returns to insertion result to operational administrative component；
Step 6: guaranteeing the insertion data success of Vernox cluster: if the insertion result in step 5 is that successfully, process terminates,
If the insertion result in step 5 is failure, handled according to failure cause, specifically:
It is subsequent from Global Queue's mould if insertion sentence is pushed into Global Queue's module since Communication causes insertion to fail
Insertion operation is executed in block again, until success；
If carrying out the data simultaneously operating of Vernox cluster because being inserted into failure caused by other reasons, guarantee is inserted into successfully.
9. a kind of heterogeneous database cluster backup method according to claim 6, which is characterized in that parsed when in the S4
When being as a result the update or delete operation of DML, following processing step is specifically included:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node and Vernox cluster；
Step 2: MySQL node and Vernox cluster execute sentence: MySQL node and Vernox cluster execute and update or delete
Operation, and the implementing result of the two is back to operational administrative component；
Step 3: return implementing result: operational administrative component by the implementing result of MySQL node be back to upper application layer and
Vernox cluster；
Step 4: comprehensive implementing result: if MySQL node implementing result is successfully, to then follow the steps five, if MySQL node is held
Row result is failure, then the implementing result of rollback Vernox cluster, it is ensured that MySQL node is consistent with the data of Vernox cluster
Property；
Step 5: guaranteeing the insertion data success of Vernox cluster: if step 2 Vernox cluster implementing result is successfully process
Terminate, if step 2 Vernox cluster implementing result is failure, handled according to failure cause, specifically:
It is subsequent from the overall situation if action statement is pushed into Global Queue's module since Communication causes to update or delete failure
Update or delete operation are executed in Queue module again, until success；
If carrying out the data simultaneously operating of Vernox cluster because failure is updated or deleted caused by other reasons, guarantee MySQL section
The data consistency of point and Vernox cluster.
10. a kind of heterogeneous database cluster backup method according to claim 6, which is characterized in that solved when in the S4
When analysis result is DDL or DCL, following processing step is specifically included:
Step 1: forwarding action statement: MySQL action statement is forwarded in MySQL node and Vernox cluster；
Step 2: MySQL node executes sentence: MySQL node executes DDL or DCL operation, and implementing result is back to operation
Management assembly；
Step 3: returning to implementing result: implementing result is back to upper application layer by operational administrative component；
Step 4: Vernox cluster executes sentence: Vernox cluster executes DDL or DCL operation, and process terminates.
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 true CN109298976A (en) | 2019-02-01 |
| CN109298976B 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) |
Cited By (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 |
| CN112035514A (en) * | 2020-09-02 | 2020-12-04 | 北京金山云网络技术有限公司 | 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 |
| CN113703954A (en) * | 2020-05-21 | 2021-11-26 | 中移(苏州)软件技术有限公司 | Message backup method and device, electronic equipment and computer storage medium |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102662793A (en) * | 2012-03-07 | 2012-09-12 | 江苏引跑网络科技有限公司 | Hot backup and recovery method of distributed database with guarantee of data consistency |
| US20160147614A1 (en) * | 2014-11-25 | 2016-05-26 | Kaushal MITTAL | Synchronized Backup and Recovery of Database Systems |
| 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 |
| CN106407264A (en) * | 2016-08-25 | 2017-02-15 | 成都索贝数码科技股份有限公司 | High-availability and high-consistency database cluster system and command processing method thereof |
| US20170103000A1 (en) * | 2015-10-07 | 2017-04-13 | International Business Machines Corporation | Backup capability for object store used as primary storage |
| CN106708842A (en) * | 2015-11-12 | 2017-05-24 | 阿里巴巴集团控股有限公司 | Data loading method for application system, database and application system |
| CN107301250A (en) * | 2017-07-27 | 2017-10-27 | 南京南瑞集团公司 | A kind of Various database cooperates with backup method |
| CN107391306A (en) * | 2017-07-27 | 2017-11-24 | 国家电网公司 | A kind of isomeric data library backup file access pattern method |
| 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 |
| US20180217900A1 (en) * | 2009-03-31 | 2018-08-02 | Commvault Systems, Inc. | Data mining systems and methods for heterogeneous data sources |
| CN109165262A (en) * | 2018-10-16 | 2019-01-08 | 成都索贝数码科技股份有限公司 | Fragmentation clustering system and fragmentation method of relational large table |
-
2018
- 2018-10-17 CN CN201811208785.6A patent/CN109298976B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180217900A1 (en) * | 2009-03-31 | 2018-08-02 | Commvault Systems, Inc. | Data mining systems and methods for heterogeneous data sources |
| CN102662793A (en) * | 2012-03-07 | 2012-09-12 | 江苏引跑网络科技有限公司 | Hot backup and recovery method of distributed database with guarantee of data consistency |
| US20160147614A1 (en) * | 2014-11-25 | 2016-05-26 | Kaushal MITTAL | Synchronized Backup and Recovery of Database Systems |
| US20170103000A1 (en) * | 2015-10-07 | 2017-04-13 | International Business Machines Corporation | Backup capability for object store used as primary storage |
| CN106708842A (en) * | 2015-11-12 | 2017-05-24 | 阿里巴巴集团控股有限公司 | Data loading method for application system, database and application system |
| 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 |
| 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 |
| CN107301250A (en) * | 2017-07-27 | 2017-10-27 | 南京南瑞集团公司 | A kind of Various database cooperates with backup method |
| CN107391306A (en) * | 2017-07-27 | 2017-11-24 | 国家电网公司 | A kind of isomeric data library backup file access pattern method |
| CN107590256A (en) * | 2017-09-20 | 2018-01-16 | 北京九桥同步软件有限公司 | Heterogeneous database synchronization method and device |
| CN109165262A (en) * | 2018-10-16 | 2019-01-08 | 成都索贝数码科技股份有限公司 | Fragmentation clustering system and fragmentation method of relational large table |
Non-Patent Citations (5)
| Title |
|---|
| DAVID MATOS等: "NoSQL Undo: Recovering NoSQL databases by undoing operations", 《2016 IEEE 15TH INTERNATIONAL SYMPOSIUM ON NETWORK COMPUTING AND APPLICATIONS (NCA)》 * |
| 宓正宇: "基于Goldengate的数据库异地灾备实现", 《电信科学》 * |
| 成都索贝数码科技股份有限公司: "Vernox融合数据库", 《HTTP://WWW.SOBEY.COM/INDEX.PHP?M=CONTENT&C=INDEX&A=LISTS&CATID=52》 * |
| 朗博顿: "《计算机系统可靠性》", 30 September 1988, 国防工业出版社 * |
| 杨明珉等: "MySQL集群到Oracle数据库的数据同步方法", 《计算机系统应用》 * |
Cited By (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 |
| CN112035514A (en) * | 2020-09-02 | 2020-12-04 | 北京金山云网络技术有限公司 | 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109298976B (en) | 2022-04-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109298976A (en) | Heterogeneous database cluster backup system and method | |
| US7779298B2 (en) | Distributed job manager recovery | |
| Bravo et al. | Saturn: A distributed metadata service for causal consistency | |
| CN105760221B (en) | The task of distributed computing framework sends system | |
| Kamburugamuve et al. | Survey of distributed stream processing for large stream sources | |
| CN106445644B (en) | Treating method and apparatus based on the distributed transaction that an improved stage submits | |
| US20120239620A1 (en) | Method and system for synchronization mechanism on multi-server reservation system | |
| US20090043745A1 (en) | Query Execution and Optimization with Autonomic Error Recovery from Network Failures in a Parallel Computer System with Multiple Networks | |
| CN109445802A (en) | The method of privatization Paas platform and its publication application based on container | |
| WO2012000997A1 (en) | An apparatus for processing a batched unit of work | |
| EP3958126A1 (en) | Micro-service component-based database system and related method | |
| CN102317913B (en) | A kind of transaction recovery method and transaction recovery device | |
| US20200401625A1 (en) | Graph processing system | |
| CN112631795A (en) | Method, device, equipment and storage medium for automatically synchronizing service application information | |
| US10346420B2 (en) | Database integration system | |
| CN105703941B (en) | The processing method and processing device of configuration transaction | |
| CN113641739B (en) | Spark-based intelligent data conversion method | |
| Cornejo et al. | Specification and verification of a dynamic reconfiguration protocol for agent-based applications | |
| CN111638939B (en) | Management system and method for Kubernets container platform application life cycle | |
| CN117376092A (en) | Fault root cause positioning method, device, equipment and storage medium | |
| CN111611089A (en) | Asynchronous declaration type micro-service scheduling method | |
| Hara et al. | Database migration: a new architecture for transaction processing in broadband networks | |
| EP3252618B1 (en) | Database integration system | |
| Schewe et al. | Horizontal business process model integration | |
| CN112689831A (en) | Method, apparatus and system for non-disruptive upgrade of distributed coordination engines in a distributed computing environment |
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 |