CN111177141A - Method, equipment and system for recovering data by utilizing MySQL (MySQL structured query language) parallel copying - Google Patents
Method, equipment and system for recovering data by utilizing MySQL (MySQL structured query language) parallel copying Download PDFInfo
- Publication number
- CN111177141A CN111177141A CN201811331093.0A CN201811331093A CN111177141A CN 111177141 A CN111177141 A CN 111177141A CN 201811331093 A CN201811331093 A CN 201811331093A CN 111177141 A CN111177141 A CN 111177141A
- Authority
- CN
- China
- Prior art keywords
- log
- data
- database
- mysql
- binary
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000011084 recovery Methods 0.000 claims abstract description 48
- 230000010076 replication Effects 0.000 claims abstract description 33
- 238000001914 filtration Methods 0.000 claims abstract description 9
- 238000001514 detection method Methods 0.000 claims description 7
- 238000007781 pre-processing Methods 0.000 claims description 6
- 238000012545 processing Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 6
- 238000007726 management method Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 241000894007 species Species 0.000 description 2
- 241000699670 Mus sp. Species 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007257 malfunction Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000010248 power generation Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 239000007787 solid Substances 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/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 provides a method, equipment and a system for recovering data by utilizing MySQL parallel replication, wherein the method comprises the following steps: receiving a data recovery instruction; acquiring a log point of a binary log with misoperation according to the data recovery instruction; closing the database, restoring the database to the current latest state by using the full-backup file name, storing the binary log of the source database into a corresponding directory according to the configuration information of the relay log in the configuration file, modifying the log name and configuring corresponding parameters; and opening the database, filtering the executed transaction of the full backup log, and calling multithreading to check and playback the recovered data according to the parallelism of the source database. Compared with the existing method for directly recovering the latest backup data, the method has higher data recovery efficiency.
Description
Technical Field
The invention relates to the technical field of data recovery, in particular to a method, equipment and a system for recovering data by utilizing MySQL parallel replication.
Background
A Database (Database) is a warehouse that organizes, stores, and manages data according to a data structure, which is not just storing and managing data, but is turned into various data management ways required by users. There are many types of databases; from the simplest tables storing various data to large database systems capable of mass data storage, the most widely used data is in various aspects.
At present, databases are used in a plurality of services, corresponding management software is often used when the databases are used, and the use of a manager is facilitated. For example, MySQL (open source relational database management system) manages databases using a structured query language. However, in the use process, a misoperation phenomenon of deleting data by mistake and modifying data by mistake often occurs, and as a DBA (data administrator), data recovery (data rollback) needs to be performed on the misoperation, the data rollback is usually realized by using full backup and binlog (database binary log) increment, and when the data size is large, the speed of restoring the binlog by increment is slow, errors are easy to occur, and the data recovery efficiency is low and the recovery time is long.
Disclosure of Invention
In view of the above drawbacks of the prior art, an object of the present invention is to provide a method, device and system for recovering data by MySQL parallel replication, which are used to solve the problems of low data recovery efficiency and long recovery time in the prior art.
To achieve the above and other related objects, in a first aspect of the present application, the present invention provides a method for recovering data by MySQL parallel replication, including:
receiving a data recovery instruction;
acquiring a log point of a binary log with misoperation according to the data recovery instruction;
closing the database, restoring the database to the current latest state by using the full-backup file name, storing the binary log of the source database into a corresponding directory according to the configuration information of the relay log in the configuration file, modifying the log name and configuring corresponding parameters;
and opening the database, filtering the executed transaction of the full backup log, and calling multithreading to check and playback the recovered data according to the parallelism of the source database.
In some embodiments of the first aspect of the present application, the step of obtaining a log point of a binary log in which a malfunction occurs according to the data recovery instruction includes:
and acquiring the approximate time point of the misoperation, searching the current log state of the binary log, comparing the time interval created by the binary log, and determining the log range corresponding to the misoperation in the binary log so as to search the log point of the misoperation in the binary log.
In certain embodiments of the first aspect of the present application, the method further comprises:
when the database is detected to be down and the corresponding relay log is damaged, abandoning the unexecuted relay log, acquiring the binary log from the source database again as the relay log, and executing the transaction again on the basis of the relay log until the execution is completed.
In certain embodiments of the first aspect of the present application, comprising: library-based parallel replication, table-based parallel replication, and row-based parallel replication.
In some embodiments of the first aspect of the present application, the step of starting the database, filtering out transactions executed by the prepare-all log, and calling multithread to view, playback, and recover data according to the parallelism of the source database includes:
and dividing the data to be recovered into corresponding transaction groups according to the types of the data to be recovered and distributing the transaction groups to each working thread according to the number of the working threads in the source database, and copying corresponding transactions in parallel by using the working threads to realize multithread playback recovery of the data.
In a second aspect of the present application, a system for recovering data by MySQL parallel replication is provided, which includes:
the receiving module is used for receiving a data recovery instruction;
the acquisition module is used for acquiring the log points of the binary logs with misoperation according to the data recovery instruction;
the system comprises a preprocessing module, a database management module and a data processing module, wherein the preprocessing module is used for closing the database, restoring the database to the current latest state by using a full-backup file name, storing a binary log of a source database into a corresponding directory according to configuration information of a relay log in a configuration file, modifying the log name and configuring corresponding parameters;
and the data recovery module is used for starting the database, filtering the executed transaction of the full backup log, and calling multithreading to check and playback the recovered data according to the parallelism of the source database.
In certain embodiments of the second aspect of the present application, the obtaining module further comprises:
and acquiring the approximate time point of the misoperation, searching the current log state of the binary log, comparing the time interval created by the binary log, and determining the log range corresponding to the misoperation in the binary log so as to search the log point of the misoperation in the binary log.
In certain embodiments of the second aspect of the present application, the system further comprises:
and the detection module is used for giving up the unexecuted relay logs when the database is detected to be down and the corresponding relay logs are damaged, acquiring the binary logs from the source database again as the relay logs, and executing the transaction again on the basis of the relay logs until the execution is completed.
In certain embodiments of the second aspect of the present application, the data recovery module further comprises:
and dividing the data to be recovered into corresponding transaction groups according to the types of the data to be recovered and distributing the transaction groups to each working thread according to the number of the working threads in the source database, and copying corresponding transactions in parallel by using the working threads to realize multithread playback recovery of the data.
In a third aspect of the present application, there is provided an apparatus comprising:
one or more processors;
a memory; and
one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors to execute the execution instructions, the one or more processors executing the execution instructions to cause the device to perform the method of recovering data using MySQL parallel replication as described.
As described above, the method, device and system for recovering data by MySQL parallel replication of the present invention have the following advantages:
when misoperation occurs in a database, the invention obtains the log point of the binary log with the misoperation, reads the operation record log in the database, restores the database to the current latest state by using the full-backup file name, stores the binary log of the source database into a corresponding directory according to the configuration information of the relay log in the configuration file, modifies the log name and configures corresponding parameters, adopts multithreading to copy corresponding transactions in parallel to realize multithreading playback, analyzes the operation record log to obtain each row of operation, and performs reverse operation on each row of operation to restore data. Compared with the existing method for directly recovering the latest backup data, the method has higher data recovery efficiency.
Drawings
FIG. 1 is a flow chart of a method for recovering data by parallel MySQL replication according to the present invention;
FIG. 2 is a schematic diagram showing a detection process for recovering data by parallel MySQL replication according to the present invention;
FIG. 3 is a block diagram of a data recovery system using MySQL parallel replication according to the present invention;
FIG. 4 is a block diagram showing the complete structure of a system for recovering data by parallel copy of MySQL according to the present invention;
fig. 5 shows a block diagram of a parallel replication recovery device using MySQL according to the present invention.
Element number description:
1 receiving module
2 acquisition module
3 preprocessing module
4 data recovery module
5 detection module
6 processor
7 memory
S1-S4 Steps 1-4
Detailed Description
The following description of the embodiments of the present application is provided for illustrative purposes, and other advantages and capabilities of the present application will become apparent to those skilled in the art from the present disclosure.
In the following description, reference is made to the accompanying drawings that describe several embodiments of the application. The following detailed description is not to be taken in a limiting sense, and the scope of embodiments of the present application is defined only by the claims of the issued patent. Spatially relative terms, such as "upper," "lower," "left," "right," "lower," "below," "lower," "above," "upper," and the like, may be used herein to facilitate describing one element or feature's relationship to another element or feature as illustrated in the figures.
Although the terms first, second, etc. may be used herein to describe various elements in some instances, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, the first preset threshold may be referred to as a second preset threshold, and similarly, the second preset threshold may be referred to as a first preset threshold, without departing from the scope of the various described embodiments. The first preset threshold and the preset threshold are both described as one threshold, but they are not the same preset threshold unless the context clearly indicates otherwise. Similar situations also include a first volume and a second volume.
Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context indicates otherwise, it should be further understood that the terms "comprises" and "comprising" indicate the presence of the stated features, steps, operations, elements, components, items, species, and/or groups, but do not preclude the presence, or addition of one or more other features, steps, operations, elements, components, items, species, and/or groups. A; b; c; a and B; a and C; b and C; A. b and C "are only exceptions to this definition should be done when combinations of elements, functions, steps or operations are inherently mutually exclusive in some manner.
Referring to fig. 1, the present invention provides a flow chart of a method for recovering data by MySQL parallel replication, including:
step S1, receiving a data recovery instruction;
for recovering data based on the MySQL database, firstly, a Binlog must be opened, Format is Row, and secondly, a database and a standby database (source database) must be provided, and the standby database backs up the data of the database. The data recovery command is an external input or an external trigger.
Step S2, acquiring the log points of the binary log with misoperation according to the data recovery instruction;
and obtaining the approximate time point of the misoperation, searching the current log state of the binary log, comparing the time interval created by the binary log, and determining the log range corresponding to the misoperation in the binary log so as to search the log point of the misoperation in the binary log.
Step S3, closing the database, restoring the database to the current latest state by using the full backup file name, storing the binary log of the source database to a corresponding directory according to the configuration information of the relay log in the configuration file, modifying the log name and configuring corresponding parameters;
the method comprises the steps of closing a source database (source server) by adopting a cold backup mode, preventing the source database from writing, enabling data of the database to be the same, copying a binary log into a relay log in the database by utilizing an I/O thread by acquiring a full-standby file, a full-standby file name and a corresponding binary log stored in the source database, reading the middle-to-middle time of a relay day by an SQL thread, and putting an event into the relay log again to update the data, so that the data are consistent with the data in the source database. Opening a binary log, modifying the ID of the database, and setting a binary more-daily value; restarting the source database according to the newly set corresponding parameters and outputting a new state; and the database needs to perform similar configuration on the relay log according to the set parameters in the binary day, such as ID correspondence, until the new state is started after restarting.
And step S4, starting the database, filtering the executed transaction of the full backup log, and calling multithreading to check and playback the recovery data according to the parallelism of the source database.
The data to be recovered is divided into corresponding transaction groups according to the types of the data and distributed to all the working threads according to the number of the working threads in the source database, and the multithreading playback recovery of the data is realized by utilizing the parallel replication of the working threads. The replicated topology may be: there is one source database per database (server), or, there is a unique source database ID per database (server ID), or, there are multiple databases per source database backup, etc.
In this embodiment, when parallel copy is performed on a ROW basis, the log format of the database must be the ROW format, which does not record sql statement context-related information, but only saves which record is modified and which record is modified to what. Therefore, the log content of rowlevel clearly records the details of each row data modification. And the problems that the storage process or function and the trigger of trigger cannot be copied correctly under certain specific conditions do not occur. When misoperation caused by an artificial SQL statement or recovery caused by failure of hot backup conditions such as no master-slave copy and the like occurs, the primary condition of traditional recovery needs mysql to start the binlog log function, meanwhile, all data needing full backup and increment is recovered firstly, then the increment log after the full backup time point is recovered, the SQL file is recovered in sequence, the SQL statement with problems in the SQL file is deleted (passing through time or position points), and finally the SQL statement is recovered to a database.
And when the parallel copy based on the library is performed, the libraries with the same ID are grouped and sent by adopting the same thread, so that the multithread copy is realized to recover data at the fastest speed, and on the basis, the parallel copy based on the table adopts the same principle, which is not described in detail herein.
In the embodiment, the data recovery rate is improved and the recovery performance is improved by realizing the playback of the data to be recovered by parallel copying.
Please refer to fig. 2, which is a schematic diagram of a detection process for recovering data by MySQL parallel replication according to the present invention, the method further includes:
and step SA, when the database is detected to be down and the corresponding relay log is damaged, abandoning the unexecuted relay log, acquiring the binary log from the source database again as the relay log, and executing the transaction again on the basis of the relay log until the execution is completed.
In this embodiment, before the step S4, the step S5 monitors the relay log to prevent the relay log from losing corresponding things, so that the corresponding event can be accurately recovered, and the integrity of data recovery can be ensured later.
Referring to fig. 3, a system for recovering data by MySQL parallel replication is provided, including:
the receiving module 1 is used for receiving a data recovery instruction;
the acquisition module 2 is used for acquiring the log points of the binary logs with misoperation according to the data recovery instruction;
wherein the obtaining module further comprises:
and acquiring the approximate time point of the misoperation, searching the current log state of the binary log, comparing the time interval created by the binary log, and determining the log range corresponding to the misoperation in the binary log so as to search the log point of the misoperation in the binary log.
The preprocessing module 3 is used for closing the database, restoring the database to the current latest state by using the full-backup file name, storing the binary log of the source database into a corresponding directory according to the configuration information of the relay log in the configuration file, modifying the log name and configuring corresponding parameters;
and the data recovery module 4 is used for starting the database, filtering the executed transaction of the full backup log, and calling multithreading to check and playback the recovered data according to the parallelism of the source database.
The data recovery module further comprises:
and dividing the data to be recovered into corresponding transaction groups according to the types of the data to be recovered and distributing the transaction groups to each working thread according to the number of the working threads in the source database, and copying corresponding transactions in parallel by using the working threads to realize multithread playback recovery of the data.
Referring to fig. 4, a block diagram of a complete structure of a system for recovering data by MySQL parallel replication according to the present invention is shown, the system further includes:
the detection module 5 is configured to, when detecting that the standby database is down and a corresponding relay log of the standby database is damaged, abandon the unexecuted relay log; and re-acquiring the binary log from the database as a relay log, and re-executing the transaction by taking the relay log as a criterion until the execution is completed.
In this embodiment, since the apparatus and the method are in a one-to-one correspondence, details of corresponding embodiments, technical effects, and the like are not repeated herein.
Referring to fig. 5, for the present invention, a parallel copy recovery device (electronic device) using MySQL includes:
one or more processors 6;
a memory 7; and
one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors to execute the execution instructions, the one or more processors executing the execution instructions to cause the device to perform the method of recovering data using MySQL parallel replication as described.
In this embodiment, the present application provides a method and system for recovering data by MySQL parallel replication, which is suitable for use in a device (electronic device), such as but not limited to a notebook computer, a tablet computer, a mobile phone, a smart phone, a media player, a Personal Digital Assistant (PDA), a navigator, a smart television, a smart watch, a digital camera, and the like, and a combination of two or more thereof. It should be understood that the electronic device described in the embodiments of the present application is only one example of an application, and that components of the device may have more or fewer components than shown, or a different configuration of components. The various components of the depicted figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits. In the specific embodiment of the present application, the electronic device will be described as a smart phone.
The electronic device also includes a memory controller, peripheral interfaces, RF circuitry, audio circuitry, speakers, microphone, input/output (I/O) subsystems, touch screen, other output or control devices, and external ports. These components communicate over one or more communication buses or signal lines. The electronic device also includes a power system for powering the various components. The power system may include a power management system, one or more power sources (e.g., battery, Alternating Current (AC)), a charging system, power failure detection circuitry, a power converter or inverter, a power status indicator (e.g., Light Emitting Diode (LED)), and any other components associated with power generation, management, and distribution in a portable device.
The electronic device supports various applications, such as one or more of: a mapping application, a rendering application, a word processing application, a website creation application, a disc editing application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
In some embodiments, the processor 6 is also operatively coupled to I/O ports that enable the electronic device to interact with various other electronic devices, and input structures that enable a user to interact with the electronic device. Thus, the input structures may include buttons, keyboards, mice, touch pads, and the like. In addition, the electronic display may include a touch component that facilitates user input by detecting the occurrence and/or location of an object touching its screen (e.g., a surface of the electronic display).
The processor 6 is operatively coupled to memory and/or non-volatile storage. More specifically, the processor may execute instructions stored in the memory and/or the non-volatile storage device to perform operations in the computing device, such as generating image data and/or transmitting image data to an electronic display. As such, the processor may include one or more general purpose microprocessors, one or more application specific processors (ASICs), one or more field programmable logic arrays (FPGAs), or any combination thereof.
The memory 7 may comprise high speed random access memory and may also comprise non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices. In certain embodiments, the memory may also include memory that is remote from the one or more processors, such as network-attached memory accessed via RF circuitry or external ports and a communication network (not shown), which may be the internet, one or more intranets, Local Area Networks (LANs), wide area networks (WLANs), Storage Area Networks (SANs), etc., or a suitable combination thereof. The memory controller may control access to the memory by other components of the device, such as the CPU and peripheral interfaces.
In summary, when an incorrect operation occurs in the database, the present invention obtains the log point of the binary log in which the incorrect operation occurs, reads the operation record log in the database, restores the database to the current latest state by using the full-backup file name, stores the binary log of the source database in the corresponding directory according to the configuration information of the relay log in the configuration file, modifies the log name and configures the corresponding parameters, realizes multithread playback by adopting multithread parallel copy of the corresponding transaction, analyzes the operation record log to obtain each row of operation, and performs a reverse operation on each row of operation to restore data. Compared with the existing method for directly recovering the latest backup data, the method has higher data recovery efficiency. Therefore, the invention effectively overcomes various defects in the prior art and has high industrial utilization value.
The foregoing embodiments are merely illustrative of the principles and utilities of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or change the above-mentioned embodiments without departing from the spirit and scope of the present invention. Accordingly, it is intended that all equivalent modifications or changes which can be made by those skilled in the art without departing from the spirit and technical spirit of the present invention be covered by the claims of the present invention.
Claims (10)
1. A method for recovering data by MySQL parallel replication is characterized by comprising the following steps:
receiving a data recovery instruction;
acquiring a log point of a binary log with misoperation according to the data recovery instruction;
closing the database, restoring the database to the current latest state by using the full-backup file name, storing the binary log of the source database into a corresponding directory according to the configuration information of the relay log in the configuration file, modifying the log name and configuring corresponding parameters;
and opening the database, filtering the executed transaction of the full backup log, and calling multithreading to check and playback the recovered data according to the parallelism of the source database.
2. The method for recovering data by MySQL parallel replication according to claim 1, wherein the step of obtaining a log point of a binary log in which an erroneous operation occurs according to the data recovery instruction comprises:
and acquiring the approximate time point of the misoperation, searching the current log state of the binary log, comparing the time interval created by the binary log, and determining the log range corresponding to the misoperation in the binary log so as to search the log point of the misoperation in the binary log.
3. The method for recovering data by MySQL parallel replication according to claim 1, further comprising:
when the database is detected to be down and the corresponding relay log is damaged, abandoning the unexecuted relay log, acquiring the binary log from the source database again as the relay log, and executing the transaction again on the basis of the relay log until the execution is completed.
4. The method for recovering data by MySQL parallel replication according to claim 1, comprising: library-based parallel replication, table-based parallel replication, and row-based parallel replication.
5. The method for recovering data by utilizing MySQL parallel replication, according to claim 1, wherein the step of starting the database, filtering out the executed transaction of the prepare-all log, and calling multithread view playback to recover data according to the parallelism of the source database comprises the steps of:
and dividing the data to be recovered into corresponding transaction groups according to the types of the data to be recovered and distributing the transaction groups to each working thread according to the number of the working threads in the source database, and copying corresponding transactions in parallel by using the working threads to realize multithread playback recovery of the data.
6. A system for recovering data using MySQL parallel replication, the system comprising:
the receiving module is used for receiving a data recovery instruction;
the acquisition module is used for acquiring the log points of the binary logs with misoperation according to the data recovery instruction;
the system comprises a preprocessing module, a database management module and a data processing module, wherein the preprocessing module is used for closing the database, restoring the database to the current latest state by using a full-backup file name, storing a binary log of a source database into a corresponding directory according to configuration information of a relay log in a configuration file, modifying the log name and configuring corresponding parameters;
and the data recovery module is used for starting the database, filtering the executed transaction of the full backup log, and calling multithreading to check and playback the recovered data according to the parallelism of the source database.
7. The system according to claim 6, wherein the obtaining module further comprises:
and acquiring the approximate time point of the misoperation, searching the current log state of the binary log, comparing the time interval created by the binary log, and determining the log range corresponding to the misoperation in the binary log so as to search the log point of the misoperation in the binary log.
8. The system for recovering data by MySQL parallel replication according to claim 6, further comprising:
and the detection module is used for giving up the unexecuted relay logs when the database is detected to be down and the corresponding relay logs are damaged, acquiring the binary logs from the source database again as the relay logs, and executing the transaction again on the basis of the relay logs until the execution is completed.
9. The system for recovering data using MySQL parallel replication in accordance with claim 6, the data recovery module further comprising:
and dividing the data to be recovered into corresponding transaction groups according to the types of the data to be recovered and distributing the transaction groups to each working thread according to the number of the working threads in the source database, and copying corresponding transactions in parallel by using the working threads to realize multithread playback recovery of the data.
10. An electronic device, characterized in that the device comprises:
one or more processors;
a memory; and
one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors with the execution of the execution instructions by the one or more processors causing the electronic device to perform the method of recovering data using MySQL parallel replication as recited in any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811331093.0A CN111177141A (en) | 2018-11-09 | 2018-11-09 | Method, equipment and system for recovering data by utilizing MySQL (MySQL structured query language) parallel copying |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811331093.0A CN111177141A (en) | 2018-11-09 | 2018-11-09 | Method, equipment and system for recovering data by utilizing MySQL (MySQL structured query language) parallel copying |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111177141A true CN111177141A (en) | 2020-05-19 |
Family
ID=70653483
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811331093.0A Pending CN111177141A (en) | 2018-11-09 | 2018-11-09 | Method, equipment and system for recovering data by utilizing MySQL (MySQL structured query language) parallel copying |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111177141A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113419896A (en) * | 2020-07-24 | 2021-09-21 | 阿里巴巴集团控股有限公司 | Data recovery method and device, electronic equipment and computer readable medium |
| CN114281604A (en) * | 2022-03-02 | 2022-04-05 | 北京金山云网络技术有限公司 | Data recovery method and device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080162590A1 (en) * | 2007-01-03 | 2008-07-03 | Oracle International Corporation | Method and apparatus for data rollback |
| US20120030172A1 (en) * | 2010-07-27 | 2012-02-02 | Oracle International Corporation | Mysql database heterogeneous log based replication |
| CN103838780A (en) * | 2012-11-27 | 2014-06-04 | 阿里巴巴集团控股有限公司 | Data recovery method of database and relevant device |
| CN106547801A (en) * | 2015-09-23 | 2017-03-29 | 北京奇虎科技有限公司 | Database data flash back method and apparatus |
| CN106610876A (en) * | 2015-10-23 | 2017-05-03 | 中兴通讯股份有限公司 | Method and device for recovering data snapshot |
| CN107145403A (en) * | 2017-04-20 | 2017-09-08 | 浙江工业大学 | The relevant database data retrogressive method of web oriented development environment |
-
2018
- 2018-11-09 CN CN201811331093.0A patent/CN111177141A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080162590A1 (en) * | 2007-01-03 | 2008-07-03 | Oracle International Corporation | Method and apparatus for data rollback |
| US20120030172A1 (en) * | 2010-07-27 | 2012-02-02 | Oracle International Corporation | Mysql database heterogeneous log based replication |
| CN103838780A (en) * | 2012-11-27 | 2014-06-04 | 阿里巴巴集团控股有限公司 | Data recovery method of database and relevant device |
| CN106547801A (en) * | 2015-09-23 | 2017-03-29 | 北京奇虎科技有限公司 | Database data flash back method and apparatus |
| CN106610876A (en) * | 2015-10-23 | 2017-05-03 | 中兴通讯股份有限公司 | Method and device for recovering data snapshot |
| CN107145403A (en) * | 2017-04-20 | 2017-09-08 | 浙江工业大学 | The relevant database data retrogressive method of web oriented development environment |
Non-Patent Citations (1)
| Title |
|---|
| 卢栋栋，何清法: "基于多线程的并行实例恢复方法", 《计算机应用》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113419896A (en) * | 2020-07-24 | 2021-09-21 | 阿里巴巴集团控股有限公司 | Data recovery method and device, electronic equipment and computer readable medium |
| CN113419896B (en) * | 2020-07-24 | 2023-12-22 | 阿里巴巴集团控股有限公司 | Data recovery method, device, electronic equipment and computer readable medium |
| CN114281604A (en) * | 2022-03-02 | 2022-04-05 | 北京金山云网络技术有限公司 | Data recovery method and device, electronic equipment and storage medium |
| CN114281604B (en) * | 2022-03-02 | 2022-07-29 | 北京金山云网络技术有限公司 | Data recovery method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10831707B2 (en) | Virtual partitions in virtual databases | |
| US11416344B2 (en) | Partial database restoration | |
| CN110096476B (en) | Data backup method, device and computer readable storage medium | |
| JP6219305B2 (en) | System and method for restoring application data | |
| EP3158469B1 (en) | Scalable eventual consistency system using logical document journaling | |
| US9535932B1 (en) | Backup and restore of databases | |
| US8271445B2 (en) | Storage, organization and searching of data stored on a storage medium | |
| US20130246358A1 (en) | Online verification of a standby database in log shipping physical replication environments | |
| US20130275369A1 (en) | Data record collapse and split functionality | |
| WO2019171296A1 (en) | Resilient, durable, scalable, and consistent distributed timeline data store | |
| WO2016116020A1 (en) | Method, apparatus and apparatus for realizing expired operation of object | |
| CN111176887A (en) | MySQL misoperation rollback method, equipment and system | |
| US20240176770A1 (en) | Consistency checking for distributed analytical database systems | |
| US8386462B2 (en) | Standby index in physical data replication | |
| CN114003657A (en) | Data processing method, system, device and storage medium for distributed database | |
| CN111177141A (en) | Method, equipment and system for recovering data by utilizing MySQL (MySQL structured query language) parallel copying | |
| US10838931B1 (en) | Use of stream-oriented log data structure for full-text search oriented inverted index metadata | |
| US20140337296A1 (en) | Techniques to recover files in a storage network | |
| US11010332B2 (en) | Set-based mutual exclusion using object metadata tags in a storage appliance | |
| US8484171B2 (en) | Duplicate filtering in a data processing environment | |
| Hakozaki et al. | A conceptual design of a generalized database subsystem | |
| US9317546B2 (en) | Storing changes made toward a limit | |
| CN104794022B (en) | Based on believable backup method | |
| CN115878563B (en) | Method for realizing directory-level snapshot of distributed file system and electronic equipment | |
| US10649976B1 (en) | Using a global sequence number for replicating mutating data |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200519 |