CN113094208A - Method and system for realizing data recovery based on binding interface and Binlog log - Google Patents
Method and system for realizing data recovery based on binding interface and Binlog log Download PDFInfo
- Publication number
- CN113094208A CN113094208A CN202110360975.5A CN202110360975A CN113094208A CN 113094208 A CN113094208 A CN 113094208A CN 202110360975 A CN202110360975 A CN 202110360975A CN 113094208 A CN113094208 A CN 113094208A
- Authority
- CN
- China
- Prior art keywords
- data
- action
- value
- interface
- recovery
- 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
- 238000011084 recovery Methods 0.000 title claims abstract description 67
- 238000000034 method Methods 0.000 title claims abstract description 45
- 230000009471 action Effects 0.000 claims abstract description 115
- 238000012545 processing Methods 0.000 claims abstract description 58
- 230000008859 change Effects 0.000 claims abstract description 51
- 230000001960 triggered effect Effects 0.000 claims abstract description 20
- 238000012790 confirmation Methods 0.000 claims abstract description 13
- 230000000875 corresponding effect Effects 0.000 claims description 40
- 238000012544 monitoring process Methods 0.000 claims description 23
- 230000008569 process Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
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/1448—Management of the data involved in backup or backup restore
-
- 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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- 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/25—Integrating or interfacing systems involving database management systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a method and a system for realizing data recovery based on a binding interface and a Binlog log, comprising the following steps: when a data retrieval request is received, retrieving corresponding value data from a local database according to the data retrieval request; wherein the data retrieval request includes at least: a single value data, or an action pipeline id of the data needing to be recovered, or an interface pipeline id of the data needing to be recovered; the value data is generated by storing a Binlog log triggered by a processing action in the system into a local database according to a key-value format and associating an action pipeline id, an interface pipeline id and the value data corresponding to the processing action. In the method, the detailed information of the data table change is extracted from the retrieved value data, and the detailed information of the data table change comprises the data before the change and the data after the change, so that when a recovery confirmation request is received, the scene can be reproduced by performing data recovery according to the detailed information of the data table change.
Description
Technical Field
The application relates to the technical field of interface testing, in particular to a method and a system for realizing data recovery based on a binding interface and a Binlog log.
Background
If the actual operation behavior of the user is not expected after the actual operation behavior is carried out in the interface test process, the scenario reproduction through data recovery is needed when the troubleshooting process is carried out, but often, because part of table data is changed, it takes a long time to recreate the data scenario at that time, and sometimes, the data scenario cannot be recovered as before, which is not beneficial to efficient troubleshooting and subsequent verification of problems. When a scene needs to be reproduced in the test process at the present stage, generally, the same operation steps need to be repeated repeatedly, the same data scene as much as possible is created, or a specific means such as interface automation or full database intervention is performed by an sql statement, and in any way, specific processing is performed on a specific scene of a case, so that it is difficult to accurately restore the specific scene node to the current scene node.
Disclosure of Invention
In order to overcome the problems that a large amount of human resources are needed for data recovery and data recovery cannot be accurately performed in the related technology at least to a certain extent, the application provides a method and a system for realizing data recovery based on a binding interface and a Binlog log.
The scheme of the application is as follows:
according to a first aspect of the embodiments of the present application, a method for implementing data recovery based on a binding interface and a Binlog log is provided, which includes:
when a data retrieval request is received, retrieving corresponding value data in a local database according to the data retrieval request;
extracting detailed information of data table changes from the retrieved value data;
when receiving a recovery confirmation request, recovering data according to the detailed information of the data table change;
wherein the data retrieval request includes at least: a single value data, or an action pipeline id of the data needing to be recovered, or an interface pipeline id of the data needing to be recovered;
the value data is generated by storing a Binlog log triggered by a processing action in the system into a local database according to a key-value format and associating an action flow id, an interface flow id and the value data corresponding to the processing action.
Preferably, in an implementation manner of the present application, the method further includes:
receiving configuration content set by a user, maintaining action information, an action association interface and an interface association data table;
the configuration content at least comprises: the system comprises an action name, an action unique code, an action binding interface and an interface binding data table.
Preferably, in an implementation manner of the present application, the method further includes:
and monitoring an action log, an interface log and a corresponding Binlog of the system in real time based on preset configuration contents.
Preferably, in an implementation manner of the present application, the method further includes:
after monitoring that a processing action in a system occurs, caching a Binlog log triggered by the processing action in a key-value format; wherein the Binlog log comprises: information on data variations; the key value in the key-value format is an interface flow id corresponding to the processing action, and the value data in the key-value format is detailed information of a change of a data table bound to the interface corresponding to the processing action.
Preferably, in an implementation manner of the present application, the method further includes:
transmitting the key-value data to a local database, and binding a corresponding interface pipeline id for the value data of the key-value data according to the key value of the key-value data;
and monitoring and recording the data relationship between the action flow id and the interface flow id according to preset configuration content, and binding the corresponding action flow id for the value data of the key-value data according to the data relationship between the action flow id and the interface flow id.
Preferably, in an implementation manner of the present application, the method further includes:
and checking according to the triggering time of the processing action, determining that the Binlog log triggered by the processing action is cached, and determining that the Binlog log triggered by the non-relevant action is not cached.
Preferably, in an implementation manner of the present application, when receiving the request for confirming recovery, performing data recovery according to the detailed information of the change of the data table specifically includes:
and when a recovery confirmation request is received, extracting data before change from the detailed information of the data table change, writing an sql script, and setting the data before change as a value to be updated for data recovery.
Preferably, in an implementation manner of the present application, the method further includes:
and after the data recovery is finished, correspondingly modifying the state of each processing action record.
Preferably, in an implementation manner of the present application, when data recovery is performed, recovery is performed only according to the latest recorded processing action, and the historical processing action is not performed.
According to a second aspect of the embodiments of the present application, there is provided a system for implementing data recovery based on a binding interface and a Binlog, including:
the data search module is used for searching corresponding value data in a local database according to a data retrieval request when the data retrieval request is received;
the data recovery module is used for extracting detailed information of data table change from the retrieved value data; when receiving a recovery confirmation request, recovering data according to the detailed information of the data table change;
wherein the data retrieval request includes at least: a single value data, or an action pipeline id of the data needing to be recovered, or an interface pipeline id of the data needing to be recovered;
the value data is generated by storing a Binlog log triggered by a processing action in the system into a local database according to a key-value format and associating an action flow id, an interface flow id and the value data corresponding to the processing action.
The technical scheme provided by the application can comprise the following beneficial effects: when a data retrieval request is received, retrieving corresponding value data from a local database according to the data retrieval request; wherein the data retrieval request includes at least: a single value data, or an action pipeline id of the data needing to be recovered, or an interface pipeline id of the data needing to be recovered; the value data is generated by storing a Binlog log triggered by a processing action in the system into a local database according to a key-value format and associating an action pipeline id, an interface pipeline id and the value data corresponding to the processing action. The Binlog log is used for monitoring database change and records data before and after change of each table in a database table. In the method, the detailed information of the data table change is extracted from the retrieved value data, and the detailed information of the data table change comprises the data before the change and the data after the change, so that when a recovery confirmation request is received, the scene can be reproduced by performing data recovery according to the detailed information of the data table change.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
FIG. 1 is a flow chart illustrating a method for implementing data recovery based on a binding interface and a Binlog log according to an embodiment of the present application;
FIG. 2 is a flow chart illustrating a method for implementing data recovery based on a binding interface and a Binlog log according to another embodiment of the present application;
FIG. 3 is a block diagram illustrating a system for implementing data recovery based on a binding interface and a Binlog log according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an apparatus for implementing data recovery based on a binding interface and a Binlog log according to an embodiment of the present application.
Reference numerals: a data search module-31; a data recovery module-32; a monitoring processing module-33; a configuration module-34; a cache module-35; a storage module-36; a processor-41; a memory-42.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
A method for implementing data recovery based on a binding interface and a Binlog, referring to fig. 1, includes:
s11: when a data retrieval request is received, retrieving corresponding value data from a local database according to the data retrieval request;
s12: extracting detailed information of the change of the data table from the retrieved value data;
s13: when receiving a recovery confirmation request, recovering the data according to the detailed information of the change of the data table;
specifically, when a confirmation recovery request is received, before-change data (before) is extracted from detailed information of changes in the data table, and the sql script is written, and the before-change data is set to a value to be updated to perform data recovery.
Wherein the data retrieval request includes at least: a single value data, or an action pipeline id of the data needing to be recovered, or an interface pipeline id of the data needing to be recovered;
the value data is generated by storing a Binlog log triggered by a processing action in the system into a local database according to a key-value format and associating an action pipeline id, an interface pipeline id and the value data corresponding to the processing action.
The Binlog is used for monitoring database changes, and records data before change (before) and data after change (after) of each table of the database table.
The distributed storage system in the key-value format has the advantages of high query speed, large data storage amount, high support concurrency and suitability for query through the main key. The Key-value database is a database that stores data in Key-value pairs, like maps in Java. The entire database can be understood as a large map, with each key corresponding to a unique value.
When a data retrieval request is received, retrieving corresponding value data from a local database according to the data retrieval request; wherein the data retrieval request includes at least: a single value data, or an action pipeline id of the data needing to be recovered, or an interface pipeline id of the data needing to be recovered; the value data is generated by storing a Binlog log triggered by a processing action in the system into a local database according to a key-value format and associating an action pipeline id, an interface pipeline id and the value data corresponding to the processing action. The Binlog log is used for monitoring database change and records data before and after change of each table in a database table. In the method, the detailed information of the data table change is extracted from the retrieved value data, and the detailed information of the data table change comprises the data before the change and the data after the change, so that when a recovery confirmation request is received, the scene can be reproduced by performing data recovery according to the detailed information of the data table change.
The method for implementing data recovery based on the binding interface and the Binlog in some embodiments, with reference to fig. 2, further includes:
s21: receiving configuration content set by a user, maintaining action information, an action association interface and an interface association data table;
configuring content at least comprises: the system comprises an action name, an action unique code, an action binding interface and an interface binding data table.
The user can log in the system background to set configuration content, maintain action information, action association interface and interface association data table. One action can be associated with a plurality of interfaces, and one interface can be associated with a plurality of data tables, that is, the configured content in the embodiment maintains a tree relationship of one-to-many and then many-to-many.
The method for implementing data recovery based on the binding interface and the Binlog in some embodiments further comprises:
s22: and monitoring an action log, an interface log and a corresponding Binlog of the system in real time based on preset configuration contents.
The monitoring processing module of the system can monitor the action log, the interface log and the corresponding Binlog log of the system in real time based on the preset configuration content.
S23: after monitoring that a processing action in the system occurs, caching a Binlog log triggered by the processing action in a key-value format; wherein the Binlog log comprises: information on data variations; the key value in the key-value format is an interface flow id corresponding to the processing action, and the value data in the key-value format is detailed information of the change of the data table bound by the interface corresponding to the processing action;
the key value in the key-value format is captured by the monitoring processing module, the monitoring processing module monitors that the configured interface records the flow id of the interface after being called, and the flow id of the interface is used as the key value in the key-value format.
Value data in a key-value format is a detailed letter of the change of the data table of the interface binding corresponding to the processing action, and the detailed information of the change of the data table is obtained through a Binlog log.
Preferably, the method further comprises: and checking according to the triggering time of the processing action, and determining that the Binlog log triggered by the processing action is cached, and the Binlog log triggered by the non-related action is not cached.
S24: transmitting the key-value data to a local database, and binding a corresponding interface flow id for the value data of the key-value data according to the key value of the key-value data;
and transmitting the key-value data to a local mysql database through a message middleware, so that the value data and the action flow id can be conveniently associated subsequently.
S25: and monitoring and recording the data relationship between the action flow id and the interface flow id according to the preset configuration content, and binding the corresponding action flow id for the value data of the key-value data according to the data relationship between the action flow id and the interface flow id.
And monitoring and recording the data relationship between the action flow id and the interface flow id according to the relationship between the action and the interface in the preset configuration content.
The action flow id and the interface flow id are not necessarily in one-to-one correspondence, one action flow may trigger a plurality of interface flows, but the relationship of the monitoring data is in one-to-one correspondence, so that the corresponding action flow id may be bound for the value data of the key-value data according to the data relationship between the action flow id and the interface flow id obtained through monitoring.
After the value data binds the action flow id and the interface flow id, steps S11-S13 can be performed.
The method for implementing data recovery based on the binding interface and the Binlog in some embodiments further comprises:
and after the data recovery is finished, correspondingly modifying the state of each processing action record.
Since the action occurring after the data recovery node, which was recorded before, is not already present after the data recovery is completed, the state of each processing action record needs to be modified accordingly.
Furthermore, when data recovery is performed, recovery is performed only according to the latest recorded processing action, and recovery is not performed for the historical processing actions.
For example, data on the first timeline is recovered to obtain data on the second timeline, and when data recovery is performed again, only data on the second timeline can be recovered, but data on the first timeline cannot be recovered.
A system for implementing data recovery based on a binding interface and a Binlog, referring to fig. 3, comprising:
the data searching module 31 is configured to, when receiving a data retrieval request, retrieve corresponding value data from the local database according to the data retrieval request;
a data recovery module 32, configured to extract detailed information of the data table change from the retrieved value data; when receiving a recovery confirmation request, recovering the data according to the detailed information of the change of the data table;
and the monitoring processing module 33 is configured to monitor an action log, an interface log and a corresponding Binlog log of the system in real time based on preset configuration content. And monitoring and recording the data relationship between the action flow id and the interface flow id according to the preset configuration content, and binding the corresponding action flow id for the value data of the key-value data according to the data relationship between the action flow id and the interface flow id.
And the configuration module 34 is used for receiving configuration contents set by a user, maintaining action information, and associating an action interface and an interface associated data table.
And the caching module 35 is used for caching the Binlog log triggered by the processing action in a key-value format after monitoring that the processing action in the system occurs.
And the storage module 36 is configured to transmit the key-value data to the local database, and bind the corresponding interface flow id to the value data of the key-value data according to the key value of the key-value data.
Wherein the data retrieval request includes at least: a single value data, or an action pipeline id of the data needing to be recovered, or an interface pipeline id of the data needing to be recovered;
the value data is generated by storing a Binlog log triggered by a processing action in the system into a local database according to a key-value format and associating an action pipeline id, an interface pipeline id and the value data corresponding to the processing action.
In the system for realizing data recovery based on the binding interface and the Binlog in the embodiment, when a data retrieval request is received, corresponding value data is retrieved in a local database according to the data retrieval request; wherein the data retrieval request includes at least: a single value data, or an action pipeline id of the data needing to be recovered, or an interface pipeline id of the data needing to be recovered; the value data is generated by storing a Binlog log triggered by a processing action in the system into a local database according to a key-value format and associating an action pipeline id, an interface pipeline id and the value data corresponding to the processing action. The Binlog log is used for monitoring database change and records data before and after change of each table in a database table. In the method, the detailed information of the data table change is extracted from the retrieved value data, and the detailed information of the data table change comprises the data before the change and the data after the change, so that when a recovery confirmation request is received, the scene can be reproduced by performing data recovery according to the detailed information of the data table change.
An apparatus for implementing data recovery based on a binding interface and a Binlog, referring to fig. 4, includes:
a processor 41 and a memory 42;
the processor 41 is connected to the memory 42 via a communication bus:
the processor 41 is configured to call and execute a program stored in the memory 42;
the memory 42 is configured to store a program, and the program is at least configured to execute a method for implementing data recovery based on a binding interface and a Binlog log according to any of the above embodiments.
The embodiment of the present invention may further include a storage medium, where the storage medium stores a computer program, and when the computer program is executed by a processor, the computer program implements the steps of the method for implementing data recovery based on the binding interface and the Binlog.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that, in the description of the present application, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present application, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (10)
1. A method for realizing data recovery based on a binding interface and a Binlog log is characterized by comprising the following steps:
when a data retrieval request is received, retrieving corresponding value data in a local database according to the data retrieval request;
extracting detailed information of data table changes from the retrieved value data;
when receiving a recovery confirmation request, recovering data according to the detailed information of the data table change;
wherein the data retrieval request includes at least: a single value data, or an action pipeline id of the data needing to be recovered, or an interface pipeline id of the data needing to be recovered;
the value data is generated by storing a Binlog log triggered by a processing action in the system into a local database according to a key-value format and associating an action flow id, an interface flow id and the value data corresponding to the processing action.
2. The method of claim 1, further comprising:
receiving configuration content set by a user, maintaining action information, an action association interface and an interface association data table;
the configuration content at least comprises: the system comprises an action name, an action unique code, an action binding interface and an interface binding data table.
3. The method of claim 2, further comprising:
and monitoring an action log, an interface log and a corresponding Binlog of the system in real time based on preset configuration contents.
4. The method of claim 3, further comprising:
after monitoring that a processing action in a system occurs, caching a Binlog log triggered by the processing action in a key-value format; wherein the Binlog log comprises: information on data variations; the key value in the key-value format is an interface flow id corresponding to the processing action, and the value data in the key-value format is detailed information of a change of a data table bound to the interface corresponding to the processing action.
5. The method of claim 4, further comprising:
transmitting the key-value data to a local database, and binding a corresponding interface pipeline id for the value data of the key-value data according to the key value of the key-value data;
and monitoring and recording the data relationship between the action flow id and the interface flow id according to preset configuration content, and binding the corresponding action flow id for the value data of the key-value data according to the data relationship between the action flow id and the interface flow id.
6. The method of claim 4, further comprising:
and checking according to the triggering time of the processing action, determining that the Binlog log triggered by the processing action is cached, and determining that the Binlog log triggered by the non-relevant action is not cached.
7. The method according to claim 1, wherein the performing data recovery according to the detailed information of the change of the data table when receiving the request for confirming recovery specifically comprises:
and when a recovery confirmation request is received, extracting data before change from the detailed information of the data table change, writing an sql script, and setting the data before change as a value to be updated for data recovery.
8. The method of claim 1, further comprising:
and after the data recovery is finished, correspondingly modifying the state of each processing action record.
9. The method of claim 8, wherein when data recovery is performed, recovery is performed only based on the most recently recorded processing actions, and historical processing actions do not perform recovery.
10. A system for realizing data recovery based on a binding interface and a Bilog log is characterized by comprising the following steps:
the data search module is used for searching corresponding value data in a local database according to a data retrieval request when the data retrieval request is received;
the data recovery module is used for extracting detailed information of data table change from the retrieved value data; when receiving a recovery confirmation request, recovering data according to the detailed information of the data table change;
wherein the data retrieval request includes at least: a single value data, or an action pipeline id of the data needing to be recovered, or an interface pipeline id of the data needing to be recovered;
the value data is generated by storing a Binlog log triggered by a processing action in the system into a local database according to a key-value format and associating an action flow id, an interface flow id and the value data corresponding to the processing action.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110360975.5A CN113094208B (en) | 2021-04-02 | 2021-04-02 | Method and system for realizing data recovery based on binding interface and Binlog log |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110360975.5A CN113094208B (en) | 2021-04-02 | 2021-04-02 | Method and system for realizing data recovery based on binding interface and Binlog log |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113094208A true CN113094208A (en) | 2021-07-09 |
| CN113094208B CN113094208B (en) | 2024-04-09 |
Family
ID=76673893
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110360975.5A Active CN113094208B (en) | 2021-04-02 | 2021-04-02 | Method and system for realizing data recovery based on binding interface and Binlog log |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113094208B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113254357A (en) * | 2021-07-19 | 2021-08-13 | 国网汇通金财（北京）信息科技有限公司 | Data processing method and device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105933163A (en) * | 2016-06-24 | 2016-09-07 | 微梦创科网络科技（中国）有限公司 | Real-time distributed debugging tracking method and system |
| US9558077B1 (en) * | 2016-06-16 | 2017-01-31 | International Business Machines Corporation | Relational database recovery |
| CN107341212A (en) * | 2017-06-26 | 2017-11-10 | 努比亚技术有限公司 | A kind of buffering updating method and equipment |
| CN112100052A (en) * | 2020-08-07 | 2020-12-18 | 北京奇艺世纪科技有限公司 | Interface test scene playback method and device |
| CN112286941A (en) * | 2020-12-23 | 2021-01-29 | 武汉物易云通网络科技有限公司 | Big data synchronization method and device based on Binlog + HBase + Hive |
| CN112380057A (en) * | 2020-11-12 | 2021-02-19 | 平安科技（深圳）有限公司 | Data recovery method, device, equipment and storage medium |
-
2021
- 2021-04-02 CN CN202110360975.5A patent/CN113094208B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9558077B1 (en) * | 2016-06-16 | 2017-01-31 | International Business Machines Corporation | Relational database recovery |
| CN105933163A (en) * | 2016-06-24 | 2016-09-07 | 微梦创科网络科技（中国）有限公司 | Real-time distributed debugging tracking method and system |
| CN107341212A (en) * | 2017-06-26 | 2017-11-10 | 努比亚技术有限公司 | A kind of buffering updating method and equipment |
| CN112100052A (en) * | 2020-08-07 | 2020-12-18 | 北京奇艺世纪科技有限公司 | Interface test scene playback method and device |
| CN112380057A (en) * | 2020-11-12 | 2021-02-19 | 平安科技（深圳）有限公司 | Data recovery method, device, equipment and storage medium |
| CN112286941A (en) * | 2020-12-23 | 2021-01-29 | 武汉物易云通网络科技有限公司 | Big data synchronization method and device based on Binlog + HBase + Hive |
Non-Patent Citations (1)
| Title |
|---|
| 罗文华;王志铭;: "基于存储形态及特征的HBase数据库灾难恢复机制研究", 信息网络安全, no. 09 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113254357A (en) * | 2021-07-19 | 2021-08-13 | 国网汇通金财（北京）信息科技有限公司 | Data processing method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113094208B (en) | 2024-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8589353B2 (en) | Method for backing up terminal data and system thereof | |
| US8381193B2 (en) | Apparatus, system, and method for visual log analysis | |
| EP3816783B1 (en) | Method and device for data migration | |
| CN101470645B (en) | High-speed cache data recovery method and apparatus | |
| CN114036119A (en) | Data synchronization method based on button and database log | |
| CN109582686B (en) | Method, device, system and application for ensuring consistency of distributed metadata management | |
| CN105824846B (en) | Data migration method and device | |
| WO2018068639A1 (en) | Data recovery method and apparatus, and storage medium | |
| CN109298978B (en) | Recovery method and system for database cluster of specified position | |
| CN111930788B (en) | Processing method, device and equipment of operation request, readable storage medium and system | |
| CN106341485A (en) | Cloud storage method and device | |
| CN114721881B (en) | Database management method, system, electronic device and storage medium | |
| CN111159020B (en) | Method and device applied to synchronous software test | |
| CN113094208B (en) | Method and system for realizing data recovery based on binding interface and Binlog log | |
| CN113467719B (en) | Data writing method and device | |
| CN111078719A (en) | Data recovery method and device, storage medium and processor | |
| CN110895545B (en) | Shared data synchronization method and device | |
| CN108304144B (en) | Data writing-in and reading method and system, and data reading-writing system | |
| CN116501700B (en) | APP formatted file offline storage method, device, equipment and storage medium | |
| CN103714059B (en) | A kind of method and device of more new data | |
| CN110866068B (en) | Advertisement data storage method and device based on HDFS | |
| CN113625952B (en) | Object storage method, device, equipment and storage medium | |
| CN112486831A (en) | Test system, test method, electronic equipment and storage medium | |
| CN113467997B (en) | Data recovery method and device, mobile equipment and storage medium | |
| CN110928945A (en) | Data processing method and device for database and data processing 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 |