CN109117312B - Data recovery method and device - Google Patents
Data recovery method and device Download PDFInfo
- Publication number
- CN109117312B CN109117312B CN201810969624.2A CN201810969624A CN109117312B CN 109117312 B CN109117312 B CN 109117312B CN 201810969624 A CN201810969624 A CN 201810969624A CN 109117312 B CN109117312 B CN 109117312B
- Authority
- CN
- China
- Prior art keywords
- user
- data
- log
- writing
- table corresponding
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- 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
- G06F11/1469—Backup restoration techniques
Abstract
The disclosure relates to a data recovery method and apparatus. The method comprises the following steps: traversing and reading all data recorded in the log to obtain user data of each user, wherein the user data of more than two users are recorded in the log; and respectively writing the user data of each user into the data table corresponding to each user. According to the distributed database system and the data reading method, after all data recorded in the log are read, the user data of each user recorded in the log are directly written into the data tables corresponding to each user, so that the number of times of reading and writing operations on a disk is reduced, the pressure on a bottom storage system is reduced, the fault recovery time can be obviously shortened, the fault recovery failure is avoided, and the overall usability of the distributed database system is improved.
Description
Technical Field
The present disclosure relates to the field of data storage technologies, and in particular, to a data recovery method and apparatus.
Background
Distributed databases refer to a logically unified database formed by connecting a plurality of physically distributed data storage units using a high-speed computer network. The basic idea of distributed database is to store data in a distributed manner on a plurality of data storage nodes connected through a network to obtain larger storage capacity and higher concurrent access amount. In recent years, with the high-speed increase of data volume, distributed database technology has also been rapidly developed.
In general, a data storage process of a distributed database system may include: writing data into a Log (Log) while writing the data into a memory, wherein the data in the memory can be written into a disk periodically; when data in the memory of the storage node is lost due to the failure of the distributed database system, data recovery needs to be performed through the Log.
In the related technology, when a distributed database is subjected to fault recovery, a Log is played back first, and sub logs corresponding to users are generated, namely temporary files; and then playing back the Log corresponding to each user, and writing the data recorded in the Log corresponding to each user into the data table corresponding to each user respectively.
Disclosure of Invention
To overcome the problems in the related art, embodiments of the present disclosure provide a data recovery method and apparatus. The technical scheme is as follows:
according to a first aspect of the embodiments of the present disclosure, there is provided a data recovery method, including:
traversing and reading all data recorded in a log to obtain user data of each user, wherein the log records the user data of more than two users;
and respectively writing the user data of each user into the data table corresponding to each user.
In one embodiment, the writing the user data of each user into the data table corresponding to each user respectively includes:
respectively generating a data file corresponding to each user according to the user data of each user;
and respectively loading the data files of the data tables corresponding to the users in the data tables corresponding to the users.
In one embodiment, the method further comprises: when a first storage node is detected to be out of order, acquiring the log corresponding to the first storage node;
correspondingly, the writing the user data of each user into the data table corresponding to each user includes: and respectively writing the user data of each user into a data table corresponding to each user in a second storage node.
In one embodiment, the writing the user data of each user into the data table corresponding to each user respectively includes:
when target data recorded in the log are read, user information corresponding to the target data is obtained;
writing the target data into a data file corresponding to the user information according to the user information;
and loading a data file corresponding to the user information in a data table corresponding to the user information.
According to a second aspect of the embodiments of the present disclosure, there is provided a data recovery apparatus including:
the first acquisition module is used for traversing and reading all data recorded in the log to acquire user data of each user, wherein the user data of more than two users are recorded in the log;
and the writing module is used for writing the user data of each user into the data table corresponding to each user respectively.
In one embodiment, the write module includes:
the generation submodule is used for respectively generating a data file corresponding to each user according to the user data of each user;
and the first loading submodule is used for loading the data file of the data table corresponding to each user in the data table corresponding to each user.
In one embodiment, the apparatus further comprises:
the second acquisition module is used for acquiring the log corresponding to the first storage node when the first storage node is detected to be in fault;
and the writing module writes the user data of each user into a data table corresponding to each user in a second storage node respectively.
In one embodiment, the write module includes:
the acquisition submodule is used for acquiring user information corresponding to the target data when the target data recorded in the log are read;
the writing sub-module is used for writing the target data into a data file corresponding to the user information according to the user information;
and the second loading submodule is used for loading the data file corresponding to the user information in the data table corresponding to the user information.
According to a third aspect of the embodiments of the present disclosure, there is provided a data recovery apparatus including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
traversing and reading all data recorded in a log to obtain user data of each user, wherein the log records the user data of more than two users;
and respectively writing the user data of each user into the data table corresponding to each user.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method embodiments of any one of the above-mentioned first aspects.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: according to the technical scheme, after all data recorded in the log are read, the user data of each user recorded in the log are directly written into the data table corresponding to each user, so that the number of times of reading and writing operations on a magnetic disk is reduced, the pressure on a bottom storage system is reduced, the fault recovery time can be obviously shortened, the fault recovery failure is avoided, and the overall availability of the distributed database system is improved.
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 disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a flow diagram illustrating a method of data recovery in accordance with an exemplary embodiment.
FIG. 2 is a flow diagram illustrating a method of data recovery according to an example embodiment.
FIG. 3 is a flow diagram illustrating a method of data recovery according to an example embodiment.
FIG. 4 is a block diagram illustrating a data recovery apparatus according to an example embodiment.
FIG. 5 is a block diagram illustrating a data recovery apparatus according to an example embodiment.
FIG. 6 is a block diagram illustrating a data recovery apparatus according to an example embodiment.
FIG. 7 is a block diagram illustrating a data recovery apparatus according to an example embodiment.
FIG. 8 is a block diagram illustrating a data recovery apparatus according to an example embodiment.
Fig. 9 is a block diagram illustrating an apparatus according to an example embodiment.
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 implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
In the related art, when a distributed database fails and then recovers the failure, the Log is played back first to generate sub logs corresponding to users, namely temporary files, and then data of the temporary files are written into a data table, specifically, in the related art, the failure recovery process actually needs to read the whole Log from a disk first, write the generated sub logs into the disk respectively, then play back the logs corresponding to the users, read each sub Log from the disk, and write the data recorded in each Log into the data table corresponding to each user in the disk respectively; it can be seen that, in the related art, frequent read/write operations need to be performed on a disk, which causes a large pressure on a bottom storage system, thereby causing slow failure recovery, even failure recovery failure, and reducing the overall availability of the distributed database system.
In order to solve the above problem, an embodiment of the present disclosure provides a data recovery method, where the method includes: traversing and reading all data recorded in the log to obtain user data of each user, wherein the user data of more than two users are recorded in the log; and respectively writing the user data of each user into the data table corresponding to each user. According to the embodiment of the disclosure, after all data recorded in the log are read, the user data of each user recorded in the log are directly written into the data table corresponding to each user, so that the number of read-write operations on a disk is reduced, the pressure on a bottom storage system is reduced, the fault recovery time can be obviously shortened, the fault recovery failure is avoided, and the overall availability of the distributed database system is improved.
Based on the above analysis, embodiments of the disclosed method are described below.
FIG. 1 is a flow chart illustrating a method of data recovery in accordance with an exemplary embodiment; the execution subject of the method can be a server; as shown in fig. 1, the method comprises the following steps 101-102:
in step 101, all data recorded in the log are read in a traversal manner, and user data of each user is obtained, and user data of more than two users are recorded in the log.
For example, when data in the memory of the storage node is lost due to a failure of the distributed database system, all data recorded in the Log is read from the disk in a traversal manner by playing back the Log, and user data of each user is acquired.
In step 102, the user data of each user is written into the data table corresponding to each user.
Illustratively, according to the user data of each user, a data file corresponding to each user is generated respectively; and respectively loading the data files of the data tables corresponding to the users in the data tables corresponding to the users. The format of the generated data file is the same as that of the data file in the directory of the data table in the distributed database.
Optionally, storing the data file corresponding to each user in the directory of the data table corresponding to each user respectively; and when the data table of the user needs to be read, directly loading the data file in the directory of the data table corresponding to the user.
For example, when it is detected that the first storage node fails, data stored in the memory of the first storage node may be lost, and at this time, the log corresponding to the first storage node is obtained, where the log records the data stored in the memory of the first storage node; traversing and reading all data recorded in the log to acquire user data of each user; and respectively writing the user data of each user into a data table corresponding to each user in a magnetic disk of a second storage node, so that the data recovery process is completed.
According to the technical scheme provided by the embodiment of the disclosure, after all data recorded in the log are read, the user data of each user recorded in the log are directly written into the data table corresponding to each user, so that the read-write operation times of a magnetic disk are reduced, the pressure on a bottom storage system is reduced, the fault recovery time can be obviously shortened, the fault recovery failure is avoided, and the overall availability of the distributed database system is improved.
FIG. 2 is a flow chart illustrating a method of data recovery in accordance with an exemplary embodiment. As shown in fig. 2, on the basis of the embodiment shown in fig. 1, the data recovery method according to the present disclosure may include the following steps 201 and 203:
in step 201, all data recorded in the log are read in a traversal manner, and user data of each user is obtained, and user data of more than two users are recorded in the log.
In step 202, a data file corresponding to each user is generated according to the user data of each user.
In step 203, the data file of the data table corresponding to each user is loaded in the data table corresponding to each user.
For example, the data file corresponding to each user is stored in the directory of the data table corresponding to each user, and the data file in the directory of the data table corresponding to the user is directly loaded when the data table of the user needs to be read.
According to the technical scheme provided by the embodiment of the disclosure, after all data recorded in the log are read, the data files in the data tables in the database are generated directly according to the user data of each user and are placed in the directory of the data table corresponding to the user, so that the read-write operation times of the disk in the fault recovery process are greatly reduced, the pressure on a bottom storage system is reduced, the fault recovery time can be obviously shortened, the fault recovery failure is avoided, and the overall availability of the distributed database system is improved.
FIG. 3 is a flow chart illustrating a method of data recovery in accordance with an exemplary embodiment. As shown in fig. 3, on the basis of the embodiment shown in fig. 1, the data recovery method according to the present disclosure may include the following steps 301 and 304:
in step 301, all data recorded in the read log is traversed.
In step 302, when the target data recorded in the log is read, user information corresponding to the target data is acquired.
In step 303, according to the user information, the target data is written into a data file corresponding to the user information.
In step 304, a data file corresponding to the user information is loaded in a data table corresponding to the user information.
According to the technical scheme provided by the embodiment of the disclosure, after all data recorded in the log are read, user data of a user is directly written into a data file of the user, and the data file of the user is loaded in a data table of the user, so that the read-write operation times of a magnetic disk in a fault recovery process are greatly reduced, the pressure on a bottom storage system is reduced, the fault recovery time can be obviously shortened, the fault recovery failure is avoided, and the overall availability of the distributed database system is improved.
The following are embodiments of the disclosed apparatus that may be used to perform embodiments of the disclosed methods.
FIG. 4 is a block diagram illustrating a data recovery apparatus in accordance with an exemplary embodiment; the apparatus may be implemented in various ways, for example with all components of the apparatus being implemented in a server or with components of the apparatus being implemented in a coupled manner on the server side; the apparatus may implement the method related to the present disclosure through software, hardware or a combination of the two, as shown in fig. 4, the data recovery apparatus includes: a first obtaining module 401 and a writing module 402, wherein:
the first obtaining module 401 is configured to traverse all data recorded in the read log, and obtain user data of each user, where the log records user data of more than two users;
the writing module 402 is configured to write the user data of each user into the data table corresponding to each user.
The device provided by the embodiment of the disclosure can be used for executing the technical scheme of the embodiment shown in fig. 1, and the execution mode and the beneficial effect are similar, and are not described again here.
In one possible implementation, as shown in fig. 5, the data recovery apparatus shown in fig. 4 may further include a write module 402 configured to include: generating a sub-module 501 and a first loading sub-module 502, wherein:
the generating submodule 501 is configured to generate a data file corresponding to each user according to the user data of each user;
the first loading submodule 502 is configured to load a data file of a data table corresponding to each user in the data table corresponding to each user.
In a possible implementation manner, the first loading sub-module 502 stores the data file corresponding to each user into the directory of the data table corresponding to each user.
In a possible implementation, as shown in fig. 6, the data recovery apparatus shown in fig. 4 may further include: a second obtaining module 601, configured to obtain, when a failure of a first storage node is detected, the log corresponding to the first storage node;
the writing module 402 writes the user data of each user into a data table corresponding to each user in the second storage node.
In one possible implementation, as shown in fig. 7, the data recovery apparatus shown in fig. 4 may further include a write module 402 configured to include: obtaining a submodule 701, a writing submodule 702 and a second loading submodule 703, wherein:
the obtaining sub-module 701 is configured to, when target data recorded in the log is read, obtain user information corresponding to the target data;
the writing sub-module 702 is configured to write the target data into a data file corresponding to the user information according to the user information;
the second loading submodule 703 is configured to load a data file corresponding to the user information in a data table corresponding to the user information.
Fig. 8 is a block diagram illustrating a data recovery apparatus 800 according to an exemplary embodiment, the data recovery apparatus 800 being adapted for use with a server, the data recovery apparatus 800 including:
a processor 801;
a memory 802 for storing processor-executable instructions;
wherein the processor 801 is configured to:
traversing and reading all data recorded in a log to obtain user data of each user, wherein the log records the user data of more than two users;
and respectively writing the user data of each user into the data table corresponding to each user.
In one embodiment, the processor 801 may be further configured to:
respectively generating a data file corresponding to each user according to the user data of each user;
and respectively loading the data files of the data tables corresponding to the users in the data tables corresponding to the users.
In one embodiment, the processor 801 may be further configured to:
when a first storage node is detected to be out of order, acquiring the log corresponding to the first storage node;
and respectively writing the user data of each user into a data table corresponding to each user in a second storage node.
In one embodiment, the processor 801 may be further configured to:
when target data recorded in the log are read, user information corresponding to the target data is obtained;
writing the target data into a data file corresponding to the user information according to the user information;
and loading a data file corresponding to the user information in a data table corresponding to the user information.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
FIG. 9 is a block diagram illustrating an apparatus in accordance with an example embodiment. For example, the apparatus 900 may be provided as a server. The apparatus 900 comprises a processing component 902 further comprising one or more processors, and memory resources, represented by memory 903, for storing instructions, e.g., applications, executable by the processing component 902. The application programs stored in memory 903 may include one or more modules that each correspond to a set of instructions. Further, the processing component 902 is configured to execute instructions to perform the above-described methods.
The device 900 may also include a power component 906 configured to perform power management of the device 900, a wired or wireless network interface 905 configured to connect the device 900 to a network, and an input/output (I/O) interface 908. The apparatus 900 may operate based on an operating system stored in the memory 903, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
A non-transitory computer readable storage medium, instructions in the storage medium, when executed by a processor of an apparatus 900, enable the apparatus 900 to perform a method comprising:
traversing and reading all data recorded in a log to obtain user data of each user, wherein the log records the user data of more than two users;
and respectively writing the user data of each user into the data table corresponding to each user.
In one embodiment, the writing the user data of each user into the data table corresponding to each user respectively includes:
respectively generating a data file corresponding to each user according to the user data of each user;
and respectively loading the data files of the data tables corresponding to the users in the data tables corresponding to the users.
In one embodiment, the method further comprises: when a first storage node is detected to be out of order, acquiring the log corresponding to the first storage node;
correspondingly, the writing the user data of each user into the data table corresponding to each user includes: and respectively writing the user data of each user into a data table corresponding to each user in a second storage node.
In one embodiment, the writing the user data of each user into the data table corresponding to each user respectively includes:
when target data recorded in the log are read, user information corresponding to the target data is obtained;
writing the target data into a data file corresponding to the user information according to the user information;
and loading a data file corresponding to the user information in a data table corresponding to the user information.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (8)
1. A method for data recovery, comprising:
traversing and reading all data recorded in a log to obtain user data of each user, wherein the log records the user data of more than two users;
writing the user data of each user into a data table corresponding to each user respectively;
the writing the user data of each user into the data table corresponding to each user respectively includes:
respectively generating a data file corresponding to each user according to the user data of each user;
and respectively loading the data files of the data tables corresponding to the users in the data tables corresponding to the users.
2. The method of claim 1, further comprising: when a first storage node is detected to be out of order, acquiring the log corresponding to the first storage node;
correspondingly, the writing the user data of each user into the data table corresponding to each user includes: and respectively writing the user data of each user into a data table corresponding to each user in a second storage node.
3. The method according to claim 1, wherein writing the user data of each user into the data table corresponding to each user respectively comprises:
when target data recorded in the log are read, user information corresponding to the target data is obtained;
writing the target data into a data file corresponding to the user information according to the user information;
and loading a data file corresponding to the user information in a data table corresponding to the user information.
4. A data recovery apparatus, comprising:
the first acquisition module is used for traversing and reading all data recorded in the log to acquire user data of each user, wherein the user data of more than two users are recorded in the log;
the writing module is used for writing the user data of each user into a data table corresponding to each user;
the write module includes:
the generation submodule is used for respectively generating a data file corresponding to each user according to the user data of each user;
and the first loading submodule is used for loading the data file of the data table corresponding to each user in the data table corresponding to each user.
5. The apparatus of claim 4, further comprising:
the second acquisition module is used for acquiring the log corresponding to the first storage node when the first storage node is detected to be in fault;
and the writing module writes the user data of each user into a data table corresponding to each user in a second storage node respectively.
6. The apparatus of claim 4, wherein the write module comprises:
the acquisition submodule is used for acquiring user information corresponding to the target data when the target data recorded in the log are read;
the writing sub-module is used for writing the target data into a data file corresponding to the user information according to the user information;
and the second loading submodule is used for loading the data file corresponding to the user information in the data table corresponding to the user information.
7. A data recovery apparatus, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
traversing and reading all data recorded in a log to obtain user data of each user, wherein the log records the user data of more than two users;
writing the user data of each user into a data table corresponding to each user respectively;
the writing the user data of each user into the data table corresponding to each user respectively includes:
respectively generating a data file corresponding to each user according to the user data of each user;
and respectively loading the data files of the data tables corresponding to the users in the data tables corresponding to the users.
8. A computer-readable storage medium having stored thereon computer instructions, which, when executed by a processor, carry out the steps of the method according to any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810969624.2A CN109117312B (en) | 2018-08-23 | 2018-08-23 | Data recovery method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810969624.2A CN109117312B (en) | 2018-08-23 | 2018-08-23 | Data recovery method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109117312A CN109117312A (en) | 2019-01-01 |
| CN109117312B true CN109117312B (en) | 2022-03-01 |
Family
ID=64860972
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810969624.2A Active CN109117312B (en) | 2018-08-23 | 2018-08-23 | Data recovery method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109117312B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101714169A (en) * | 2009-12-01 | 2010-05-26 | 广州从兴电子开发有限公司 | Method and system for transmitting data on multiple nodes |
| US20150019909A1 (en) * | 2013-07-11 | 2015-01-15 | International Business Machines Corporation | Speculative recovery using storage snapshot in a clustered database |
| CN104301360A (en) * | 2013-07-19 | 2015-01-21 | 阿里巴巴集团控股有限公司 | Method, log server and system for recording log data |
| CN105373448A (en) * | 2015-10-27 | 2016-03-02 | 北京百度网讯科技有限公司 | Method and system for recovering failure data in database |
| CN106254100A (en) * | 2016-07-27 | 2016-12-21 | 腾讯科技（深圳）有限公司 | A kind of data disaster tolerance methods, devices and systems |
| CN106339279A (en) * | 2016-08-24 | 2017-01-18 | 杭州华三通信技术有限公司 | Service restoration method and device |
| CN106547646A (en) * | 2015-09-23 | 2017-03-29 | 阿里巴巴集团控股有限公司 | A kind of data backup and restoration methods, data backup and recovery device |
| CN106599006A (en) * | 2015-10-20 | 2017-04-26 | 阿里巴巴集团控股有限公司 | Data recovery method and device |
| US20170132091A1 (en) * | 2013-09-25 | 2017-05-11 | Amazon Technologies, Inc. | Log-structured distributed storage using a single log sequence number space |
| CN106899648A (en) * | 2016-06-20 | 2017-06-27 | 阿里巴巴集团控股有限公司 | A kind of data processing method and equipment |
-
2018
- 2018-08-23 CN CN201810969624.2A patent/CN109117312B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101714169A (en) * | 2009-12-01 | 2010-05-26 | 广州从兴电子开发有限公司 | Method and system for transmitting data on multiple nodes |
| US20150019909A1 (en) * | 2013-07-11 | 2015-01-15 | International Business Machines Corporation | Speculative recovery using storage snapshot in a clustered database |
| CN104301360A (en) * | 2013-07-19 | 2015-01-21 | 阿里巴巴集团控股有限公司 | Method, log server and system for recording log data |
| US20170132091A1 (en) * | 2013-09-25 | 2017-05-11 | Amazon Technologies, Inc. | Log-structured distributed storage using a single log sequence number space |
| CN106547646A (en) * | 2015-09-23 | 2017-03-29 | 阿里巴巴集团控股有限公司 | A kind of data backup and restoration methods, data backup and recovery device |
| CN106599006A (en) * | 2015-10-20 | 2017-04-26 | 阿里巴巴集团控股有限公司 | Data recovery method and device |
| CN105373448A (en) * | 2015-10-27 | 2016-03-02 | 北京百度网讯科技有限公司 | Method and system for recovering failure data in database |
| CN106899648A (en) * | 2016-06-20 | 2017-06-27 | 阿里巴巴集团控股有限公司 | A kind of data processing method and equipment |
| CN106254100A (en) * | 2016-07-27 | 2016-12-21 | 腾讯科技（深圳）有限公司 | A kind of data disaster tolerance methods, devices and systems |
| CN106339279A (en) * | 2016-08-24 | 2017-01-18 | 杭州华三通信技术有限公司 | Service restoration method and device |
Non-Patent Citations (1)
| Title |
|---|
| "MySQL数据库的备份与恢复探讨";徐安令;《信息与电脑（理论版）》;20140815(第16期);第88-89页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109117312A (en) | 2019-01-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110442560B (en) | Log replay method, device, server and storage medium | |
| WO2017020637A1 (en) | Task allocation method and task allocation apparatus for distributed data calculation | |
| CN107967122B (en) | Data writing method, device and medium for block device | |
| CN106201481A (en) | Assembly management method and apparatus in application development system | |
| CN107391544B (en) | Processing method, device and equipment of column type storage data and computer storage medium | |
| CN109684298A (en) | Database migration method, apparatus, equipment and storage medium | |
| CN115080398A (en) | Automatic interface test system and method | |
| US8300507B2 (en) | Disk position system and method | |
| CN102255866A (en) | Method and device for downloading data | |
| CN111324665A (en) | Log playback method and device | |
| CN115599764A (en) | Method, device and medium for migrating table data | |
| CN114860654A (en) | Method and system for dynamically changing Iceberg table Schema based on Flink data stream | |
| WO2016165461A1 (en) | Automated testing method and apparatus for network management system software of telecommunications network | |
| CN107193736B (en) | Test method, test device, electronic device, and storage medium | |
| CN109829678B (en) | Rollback processing method and device and electronic equipment | |
| CN109117312B (en) | Data recovery method and device | |
| CN110674171A (en) | Script generation method and device and data processing method and device | |
| WO2022166265A1 (en) | Data recovery method and apparatus, device and medium | |
| CN114816247A (en) | Logic data acquisition method and device | |
| CN114153732A (en) | Fault scene testing method and device, electronic equipment and storage medium | |
| CN113111138A (en) | Data processing method, device, computing equipment and medium | |
| CN112948389A (en) | MD 5-based database table data comparison method and equipment | |
| CN110908821A (en) | Method, device, equipment and storage medium for task failure management | |
| CN112596948B (en) | Database cluster data backup method, device, equipment and storage medium | |
| CN110795297B (en) | Electronic equipment testing method and device |
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 |