Data backup recovery method and device based on data merging

Abstract

The invention discloses a data backup recovery method and device based on data merging, and the method comprises the steps: obtaining a first data snapshot of initial full backup data; the first data snapshot is mounted to a local database, so that the initial full-amount backup data is backed up in the local database in a full-amount mode; when incremental backup data is obtained, merging the incremental backup data to the first data snapshot to obtain a second data snapshot; uninstalling a mounting point of the local database, and backing up the synthesized total backup data corresponding to the second data snapshot in the local database; and when a data recovery instruction is obtained, recovering data from the local database based on the data recovery instruction to obtain target recovery data. According to the method and the device, relatively high backup efficiency and relatively low recovery complexity can be realized at the same time.

Description

Technical Field

[0001] The present application relates to the field of database technology, and in particular to a data backup and recovery method and device based on data merging. Background Art

[0002] The existing technology generally performs data backup and recovery through full backup, differential incremental backup, etc. The existing full backup refers to a complete copy of all data or applications at a certain point in time, but the backup time is long. The disadvantage of differential incremental backup is that multiple backup files (full backup and multiple differential incremental backups) may be required for recovery, which increases the complexity of recovery, and if there are many differential incremental backups, managing these backup files may become complicated. As a result, the existing data backup and recovery methods cannot take into account both high backup efficiency and low recovery complexity. Summary of the invention

[0003] The embodiments of the present application provide a data backup and recovery method and device based on data merging, which can achieve higher backup efficiency and lower recovery complexity at the same time.

[0004] In a first aspect, the data backup and recovery method based on data merging provided by the present application includes:

[0005] Obtaining a first data snapshot of the initial full backup data;

[0006] Mounting the first data snapshot to a local database so that the initial full backup data is fully backed up in the local database;

[0007] When the incremental backup data is obtained, the incremental backup data is merged into the first data snapshot to obtain a second data snapshot;

[0008] Unmounting the mount point of the local database, so that the synthetic full backup data corresponding to the second data snapshot is backed up in the local database;

[0009] When the data recovery instruction is obtained, the data is recovered from the local database based on the data recovery instruction to obtain target recovery data.

[0010] Optionally, the recovering data from the local database based on the data recovery instruction to obtain target recovery data includes:

[0011] Obtaining a data recovery time point of the data recovery instruction;

[0012] Get the backup time point of each full backup data in the local database;

[0013] Determine whether there is a backup time point that is the same as the data recovery time point among the backup time points;

[0014] If there is no backup time point that is the same as the data recovery time point among the backup time points, the backup time point closest to the data recovery time point after the data recovery time point is determined as the first backup time point, and the backup time point closest to the data recovery time point before the data recovery time point is determined as the second backup time point;

[0015] The first backup time point and the second backup time point are respectively determined as candidate backup time points, and a target evaluation parameter of the candidate backup time point is determined based on a preset weight coefficient of the candidate backup time point and a time difference between the candidate backup time point and the data recovery time point, to obtain a target evaluation parameter of the first backup time point and a target evaluation parameter of the second backup time point, wherein the larger the time difference is, the smaller the target evaluation parameter is, and the preset weight coefficient of the first backup time point is smaller than the preset weight coefficient of the second backup time point;

[0016] If the target evaluation parameter of the first backup time point is greater than the target evaluation parameter of the second backup time point, data is restored from the local database based on the full backup data corresponding to the first backup time point to obtain the target restored data.

[0017] Optionally, the restoring data from the local database based on the full backup data corresponding to the first backup time point to obtain the target restored data includes:

[0018] Acquire a first database operation sequence between the data recovery time point and the first backup time point, wherein the first database operation sequence includes a plurality of database operations;

[0019] Determine a first database inverse operation sequence of the first database operation sequence based on the first database operation sequence, wherein the first database inverse operation sequence includes a plurality of database inverse operations corresponding to a plurality of database operations;

[0020] The full backup data corresponding to the first backup time point is modified based on the first database inverse operation sequence to obtain target recovery data.

[0021] Optionally, the data backup and recovery method based on data merging includes:

[0022] If the target evaluation parameter of the first backup time point is not greater than the target evaluation parameter of the second backup time point, data is restored from the local database based on the full backup data corresponding to the second backup time point to obtain the target restored data.

[0023] Optionally, the restoring data from the local database based on the full backup data corresponding to the second backup time point to obtain the target restored data includes:

[0024] Acquire a second database operation sequence between the second backup time point and the data recovery time point, where the second database operation sequence includes a plurality of database operations;

[0025] The full backup data corresponding to the second backup time point is modified based on the second database operation sequence to obtain target recovery data.

[0026] Optionally, the determining the target evaluation parameter of the candidate backup time point based on a preset weight coefficient of the candidate backup time point and a time difference between the candidate backup time point and the data recovery time point includes:

[0027] Obtaining the number of database operations between the candidate backup time point and the data recovery time point;

[0028] The target evaluation parameter of the candidate backup time point is determined based on a preset weight coefficient of the candidate backup time point, a time difference between the candidate backup time point and the data recovery time point, and a number of database operations between the candidate backup time point and the data recovery time point, wherein the smaller the time difference, the larger the target evaluation parameter, and the smaller the number of database operations, the larger the target evaluation parameter.

[0029] Optionally, before mounting the first data snapshot to a local database so that the initial full backup data is fully backed up in the local database, the method includes:

[0030] Obtaining a database identifier of a database to be backed up input by a user, wherein the database to be backed up is a storage location of the initial full backup data;

[0031] Determining a backup type of the database to be backed up based on the database identifier;

[0032] When the backup type is a permanent full backup type, the first data snapshot is mounted to a local database, so that the initial full backup data is fully backed up in the local database.

[0033] In a second aspect, the data backup and recovery device based on data merging provided by the present application includes:

[0034] An acquisition module, used to acquire a first data snapshot of the initial full backup data;

[0035] A mounting module, used for mounting the first data snapshot to a local database, so that the initial full backup data is fully backed up in the local database;

[0036] a merging module, configured to merge the incremental backup data into the first data snapshot to obtain a second data snapshot when the incremental backup data is acquired;

[0037] an uninstallation module, used for uninstalling the mount point of the local database, so that the synthetic full backup data corresponding to the second data snapshot is backed up in the local database;

[0038] The recovery module is used to recover data from the local database based on the data recovery instruction when a data recovery instruction is obtained to obtain target recovery data.

[0039] Optionally, the recovering data from the local database based on the data recovery instruction to obtain target recovery data includes:

[0040] Obtaining a data recovery time point of the data recovery instruction;

[0041] Get the backup time point of each full backup data in the local database;

[0042] Determine whether there is a backup time point that is the same as the data recovery time point among the backup time points;

[0043] If there is no backup time point that is the same as the data recovery time point among the backup time points, the backup time point closest to the data recovery time point after the data recovery time point is determined as the first backup time point, and the backup time point closest to the data recovery time point before the data recovery time point is determined as the second backup time point;

[0044] The first backup time point and the second backup time point are respectively determined as candidate backup time points, and a target evaluation parameter of the candidate backup time point is determined based on a preset weight coefficient of the candidate backup time point and a time difference between the candidate backup time point and the data recovery time point, to obtain a target evaluation parameter of the first backup time point and a target evaluation parameter of the second backup time point, wherein the larger the time difference is, the smaller the target evaluation parameter is, and the preset weight coefficient of the first backup time point is smaller than the preset weight coefficient of the second backup time point;

[0045] If the target evaluation parameter of the first backup time point is greater than the target evaluation parameter of the second backup time point, data is restored from the local database based on the full backup data corresponding to the first backup time point to obtain the target restored data.

[0046] Optionally, the restoring data from the local database based on the full backup data corresponding to the first backup time point to obtain the target restored data includes:

[0047] Acquire a first database operation sequence between the data recovery time point and the first backup time point, wherein the first database operation sequence includes a plurality of database operations;

[0048] Determine a first database inverse operation sequence of the first database operation sequence based on the first database operation sequence, wherein the first database inverse operation sequence includes a plurality of database inverse operations corresponding to a plurality of database operations;

[0049] The full backup data corresponding to the first backup time point is modified based on the first database inverse operation sequence to obtain target recovery data.

[0050] Optionally, the data backup and recovery method based on data merging includes:

[0051] If the target evaluation parameter of the first backup time point is not greater than the target evaluation parameter of the second backup time point, data is restored from the local database based on the full backup data corresponding to the second backup time point to obtain the target restored data.

[0052] Optionally, the restoring data from the local database based on the full backup data corresponding to the second backup time point to obtain the target restored data includes:

[0053] Acquire a second database operation sequence between the second backup time point and the data recovery time point, where the second database operation sequence includes a plurality of database operations;

[0054] The full backup data corresponding to the second backup time point is modified based on the second database operation sequence to obtain target recovery data.

[0055] Optionally, the determining the target evaluation parameter of the candidate backup time point based on a preset weight coefficient of the candidate backup time point and a time difference between the candidate backup time point and the data recovery time point includes:

[0056] Obtaining the number of database operations between the candidate backup time point and the data recovery time point;

[0057] The target evaluation parameter of the candidate backup time point is determined based on a preset weight coefficient of the candidate backup time point, a time difference between the candidate backup time point and the data recovery time point, and a number of database operations between the candidate backup time point and the data recovery time point, wherein the smaller the time difference, the larger the target evaluation parameter, and the smaller the number of database operations, the larger the target evaluation parameter.

[0058] Optionally, before mounting the first data snapshot to a local database so that the initial full backup data is fully backed up in the local database, the method includes:

[0059] Obtaining a database identifier of a database to be backed up input by a user, wherein the database to be backed up is a storage location of the initial full backup data;

[0060] Determining a backup type of the database to be backed up based on the database identifier;

[0061] When the backup type is a permanent full backup type, the first data snapshot is mounted to a local database, so that the initial full backup data is fully backed up in the local database.

[0062] In a third aspect, the electronic device provided in the present application includes a memory and a processor, the memory stores a computer program, and the processor is used to run the computer program in the memory to implement the steps in the data backup and recovery method based on data merging provided in the present application.

[0063] In a fourth aspect, the computer-readable storage medium provided in the present application stores a plurality of instructions, which are suitable for loading by a processor to implement the steps in the data backup and recovery method based on data merging provided in the present application.

[0064] In a fifth aspect, the computer program product provided in the present application includes a computer program or instructions, which, when executed by a processor, implements the steps in the data backup and recovery method based on data merging provided in the present application.

[0065] In the present application, compared with the related art, a first data snapshot of the initial full backup data is obtained; the first data snapshot is mounted to the local database, so that the initial full backup data is fully backed up in the local database; when the incremental backup data is obtained, the incremental backup data is merged into the first data snapshot to obtain a second data snapshot; the mount point of the local database is unmounted, so that the synthetic full backup data corresponding to the second data snapshot is backed up in the local database; when the data recovery instruction is obtained, the data is restored from the local database based on the data recovery instruction to obtain the target recovery data. The present application obtains a full synthetic full backup data backup by merging the incremental backup data and the first data snapshot of the initial full backup data, so that the full backup data can be quickly obtained, and when recovery is needed, only the corresponding full data needs to be selected to immediately restore to the corresponding time point data, which greatly simplifies the recovery logic and reduces the risk of recovery, thereby being able to achieve both high backup efficiency and low recovery complexity. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0067] Figure 1 It is a scenario diagram of a data backup and recovery system based on data merging provided in an embodiment of the present application;

[0068] Figure 2 It is a flowchart of an embodiment of a data backup and recovery method based on data merging provided in an embodiment of the present application;

[0069] Figure 3 It is a flow chart of determining target evaluation parameters of candidate backup time points based on preset weight coefficients of candidate backup time points and the time difference between the candidate backup time points and the data recovery time points in one embodiment of the data backup and recovery method based on data merging provided by an embodiment of the present application;

[0070] Figure 4 It is a schematic diagram of a login interface when a user creates a backup plan in one embodiment of a data backup and recovery method based on data merging provided in an embodiment of the present application;

[0071] Figure 5 It is a schematic diagram of a database display interface when a user creates a backup plan in one embodiment of a data backup and recovery method based on data merging provided in an embodiment of the present application;

[0072] Figure 6It is a schematic diagram of a plan type selection page when a user creates a backup plan in one embodiment of a data backup and recovery method based on data merging provided in an embodiment of the present application;

[0073] Figure 7 It is a schematic diagram of a created plan display interface when a user creates a backup plan in one embodiment of a data backup and recovery method based on data merging provided in an embodiment of the present application;

[0074] Figure 8 It is a schematic diagram of a backup result display interface when a user creates a backup plan in one embodiment of a data backup and recovery method based on data merging provided in an embodiment of the present application;

[0075] Fig. 9 It is a structural diagram of a data backup and recovery device based on data merging provided in an embodiment of the present application;

[0076] Fig.10 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0077] It should be noted that the principles of the present application are illustrated by implementing them in an appropriate computing environment. The following description is based on the illustrated specific embodiments of the present application and should not be considered as limiting other specific embodiments of the present application that are not described in detail herein.

[0078] In the following description of the present application, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it can be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0079] In the following description of the present application, the terms "first\second\third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.

[0080] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0081] In order to improve the effect of data backup and recovery based on data merging, the embodiments of the present application provide a data backup and recovery method based on data merging, a data backup and recovery device based on data merging, an electronic device, a computer-readable storage medium, and a computer program product. The data backup and recovery method based on data merging can be executed by a data backup and recovery device based on data merging, or by an electronic device integrated with the data backup and recovery device based on data merging.

[0082] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0083] Please refer to Figure 1 , the present application also provides a data backup and recovery system based on data merging, such as Figure 1 As shown, the data backup and recovery system based on data merging includes an electronic device 100, and the data backup and recovery device based on data merging provided by the present application is integrated in the electronic device 100.

[0084] Among them, the electronic device 100 can be any device equipped with a processor and has processing capabilities, such as mobile electronic devices with processors such as smart phones, tablet computers, PDAs, laptops, smart speakers, or fixed electronic devices with processors such as desktop computers, televisions, servers, industrial equipment, etc.

[0085] In addition, if Figure 1 As shown, the data backup and recovery system based on data merging may further include a memory 200 for storing original data, intermediate data and result data.

[0086] In the embodiment of the present application, the memory may be a cloud memory. Cloud storage is a new concept extended and developed from the concept of cloud computing. A distributed cloud storage system (hereinafter referred to as the storage system) refers to a storage system that uses cluster applications, grid technology, and distributed storage file systems to bring together a large number of storage devices of various types (storage devices are also called storage nodes) in the network through application software or application interfaces to work together and provide external data storage and business access functions.

[0087] At present, the storage method of the storage system is: create a logical volume, and when creating a logical volume, allocate physical storage space for each logical volume. The physical storage space may be composed of disks of a storage device or several storage devices. The client stores data on a logical volume, that is, stores the data on the file system. The file system divides the data into many parts, each of which is an object. The object contains not only data but also additional information such as data identification (ID, ID entity). The file system writes each object into the physical storage space of the logical volume, and the file system records the storage location information of each object, so that when the client requests to access the data, the file system can allow the client to access the data according to the storage location information of each object.

[0088] The process of the storage system allocating physical storage space to a logical volume is as follows: based on the estimated capacity of the objects stored in the logical volume (this estimate often has a large margin relative to the actual capacity of the objects to be stored) and the grouping of independent redundant disk arrays (RAID, Redundant Array of Independent Disks), the physical storage space is pre-divided into stripes. A logical volume can be understood as a stripe, thereby allocating physical storage space to the logical volume.

[0089] It should be noted that Figure 1 The scenario diagram of the data backup and recovery system based on data merging shown is merely an example. The data backup and recovery system based on data merging and the scenario described in the embodiment of the present application are intended to more clearly illustrate the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided in the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of the data backup and recovery system based on data merging and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

[0090] It should be noted that the serial numbers of the following embodiments are not intended to limit the preferred order of the embodiments.

[0091] Please refer to Figure 2 , Figure 2 FIG. 1 is a flow chart of an embodiment of a data backup and recovery method based on data merging provided in an embodiment of the present application. Figure 2 As shown, the process of the data backup and recovery method based on data merging provided by this application is as follows:

[0092] 201. Obtain a first data snapshot of the initial full backup data.

[0093] In the embodiment of the present application, the initial full backup data is the data that the user needs to back up. When the user uses the client to connect to the electronic device, the electronic device obtains the initial full backup data in the database to be backed up of the user client.

[0094] The definition of a snapshot is: a completely available copy of a specified data set, which includes an image of the corresponding data at a certain point in time (the point in time when the copy starts). A snapshot can be a copy of the data it represents, or a replica of the data. The main function of a snapshot is to enable online data backup and recovery. When an application failure or file corruption occurs on a storage device, data can be quickly restored to the state of a certain available point in time. Another function of a snapshot is to provide storage users with another data access channel. When the original data is being processed by an online application, users can access the snapshot data and use the snapshot for testing and other tasks. For all storage systems, regardless of high, medium or low-end, snapshots become an indispensable function as long as they are applied to online systems.

[0095] 202. Mount the first data snapshot to the local database, so that the initial full backup data is fully backed up in the local database.

[0096] In an embodiment of the present application, the first data snapshot is mounted to the local database so that the initial full backup data is fully backed up in the local database. Before that, it includes: obtaining the database identifier of the database to be backed up input by the user, the database to be backed up is the storage location of the initial full backup data; determining the backup type of the database to be backed up based on the database identifier; when the backup type is a permanent full backup type, the first data snapshot is mounted to the local database so that the initial full backup data is fully backed up in the local database.

[0097] In an embodiment of the present application, a database identifier is used to identify a database to be backed up that needs to be backed up, for example, the database identifier is test12c. Different database identifiers correspond to different databases to be backed up, and different backup types can be set for different databases to be backed up. The backup type can be a traditional full backup, an incremental backup, and a permanent full backup. Specifically, the incremental backup can be a cumulative incremental backup (Cumulative Incremental Backup) or a differential incremental backup (Differential Incremental Backup).

[0098] Cumulative incremental backup can back up all changed data blocks since the last full backup or cumulative incremental backup. Only a full backup and the latest cumulative incremental backup are needed for recovery, which simplifies the recovery process.

[0099] Differential incremental backups only back up the data blocks that have changed since the last full backup. Compared with cumulative incremental backups, the backup files may be smaller. If the differential incremental backup is lost or damaged, you can still use the full backup and the previous incremental backups to restore.

[0100] Mounting is the process by which the operating system makes computer files and directories on a storage device (such as a hard disk, CD-ROM, or shared resource) available to users through the computer's file system. Generally, when the computer is shut down, each mounted storage will undergo an unmount to ensure that all queued data is written and the integrity of the file system structure on the media is guaranteed.

[0101] In the embodiment of the present application, the first data snapshot is mounted to the local database so that the initial full backup data is fully backed up in the local database. The local database can be a Redis database, a SQLite database, etc., which is set according to the specific situation.

[0102] The backup process starts with a full backup. After the full initial full backup data is snapshotted, it is mounted to the local database through FUSE for data merging. For the first full data, simply mount the first data snapshot of the initial full backup data to the local database. If the local database is started at this time, the relevant data of the local database at this time is consistent with the first initial full backup data.

[0103] 203. When the incremental backup data is obtained, merge the incremental backup data into the first data snapshot to obtain a second data snapshot.

[0104] In the embodiment of the present application, the local database stores data in the form of incremental storage. Delta Push ensures that the protected database only sends the changed incremental backup to the established storage end. There is no need to repeat the full backup. Incremental push is also called "permanent incremental" because the production system will only run incremental backup after completing a one-time full backup. In fact, incremental push is a highly optimized form of source-side deduplication. RMAN block change tracking can efficiently identify the blocks that have changed on the production database without reading the unchanged data, so the network traffic is much lower than other solutions. In this way, low-cost 10Gb Ethernet can be used for backup. There is no need to use expensive dedicated Fibre Channel or Ethernet-based Fibre Channel backup networks. Delta Store controls the assembly of the restored backup blocks. Delta Store verifies the incoming changed data blocks, and then performs compression, indexing and storage operations. These changed blocks are the basis of the virtual full backup of the database. The virtual full backup of the database is a highly space-efficient, pointer-based physical full backup performed during incremental backup. Virtual full backups can improve storage efficiency by more than 10 times, depending on the dataset and change rate of the protected database. The high space efficiency of incremental storage makes it possible to keep a large number of virtual full backups online, significantly shortening disk-based recovery cycles.

[0105] In the embodiment of the present application, the incremental backup data is merged into the first data snapshot through the SQL command 'RMAN RECOVER COPY OF DATABASEWITH TAG' in the local database to obtain the second data snapshot.

[0106] 204. Unmount the mount point of the local database, so that the synthetic full backup data corresponding to the second data snapshot is backed up in the local database.

[0107] After the full backup is completed, the local database starts to receive the additional backup data. In the local database, the SQL command RMANRECOVER COPY OF DATABASE WITH TAG'exclusive TAG' is used to merge the newly added data blocks into the last full snapshot, merge the incremental backup data into the first data snapshot, obtain the second data snapshot, and unmount the mount point of the local database. The snapshot data obtained at this time is the merged synthetic full backup data, which contains the last initial full backup data and this incremental data.

[0108] Furthermore, the synthetic full backup data obtained during the last incremental backup of the local database is obtained according to a preset period, and snapshot data of the synthetic full backup data is generated. The snapshot data of the synthetic full backup data is mounted in the local database. When the incremental backup data is obtained again, the incremental backup data obtained again is merged into the snapshot data of the synthetic full backup data to obtain a new data snapshot, and the mount point of the local database is unmounted, so that the synthetic full backup data corresponding to the new data snapshot is backed up in the local database, thereby obtaining multiple full backup data according to a preset period. The multiple full backup data include the initial full backup data and multiple synthetic full backup data synthesized multiple times. The preset period can be half an hour, one hour, etc., which can be set according to the specific situation.

[0109] When receiving the second incremental data, generate a snapshot of the last synthetic full backup set, mount it to the local database, merge the newly added data blocks of the second incremental data into the last synthetic full backup set snapshot through the SQL command RMAN RECOVER COPY OF DATABASE WITH TAG'exclusive TAG', and unmount the local database mount point. The snapshot data obtained at this time includes the first full backup, the first incremental, and the second incremental data. This process is repeated to ensure that each incremental data can actually be a usable synthetic full data in the backup storage. When recovery is needed, you only need to select the corresponding synthetic full data, and you can immediately mount and restore it to the corresponding point in time. This greatly simplifies the recovery logic and reduces the risk of recovery.

[0110] 205. When the data recovery instruction is obtained, data is recovered from the local database based on the data recovery instruction to obtain target recovery data.

[0111] In the embodiment of the present application, the data recovery instruction includes a data recovery time point. Recovering data from the local database based on the data recovery instruction includes:

[0112] (1) Obtain the data recovery time point of the data recovery instruction.

[0113] In the embodiment of the present application, the data recovery time point can be 10:20, 10:30, etc., which can be set according to the specific situation.

[0114] (2) Obtain the backup time point of each full backup data in the local database.

[0115] In the embodiment of the present application, the multiple full backup data include initial full backup data and multiple synthesized full backup data. The backup time point is the time point of the full backup data backup.

[0116] (3) Determine whether there is a backup time point among the backup time points that is the same as the data recovery time point.

[0117] (4) If there is no backup time point that is the same as the data recovery time point among the backup time points, the backup time point that is closest to the data recovery time point after the data recovery time point is determined as the first backup time point, and the backup time point that is closest to the data recovery time point before the data recovery time point is determined as the second backup time point.

[0118] For example, the synthetic full backup data is obtained when the last incremental backup of the local database is obtained according to the preset period. For example, the preset period is 1 hour. The backup time points of each full backup data in the local database are 10:00, 11:00, and 12:00 respectively. If the data recovery time point is 11:10, the first backup time point is 11:00, and the second backup time point is 12:00.

[0119] (5) The first backup time point and the second backup time point are respectively determined as candidate backup time points, and the target evaluation parameters of the candidate backup time points are determined based on the preset weight coefficients of the candidate backup time points and the time difference between the candidate backup time point and the data recovery time point, so as to obtain the target evaluation parameters of the first backup time point and the target evaluation parameters of the second backup time point, wherein the larger the time difference, the smaller the target evaluation parameters, and the preset weight coefficient of the first backup time point is smaller than the preset weight coefficient of the second backup time point.

[0120] In the embodiment of the present application, the preset weight coefficient of the first backup time point is less than the preset weight coefficient of the second backup time point. The preset weight coefficient of the first backup time point and the preset weight coefficient of the second backup time point can be set according to the specific situation. For example, the preset weight coefficient of the first backup time point is 1, and the preset weight coefficient of the second backup time point is 1.5, which can be set according to the specific situation. Since the first backup time point is after the data recovery time point, a reverse operation is required to recover, so a smaller weight is set.

[0121] (6) If the target evaluation parameter of the first backup time point is greater than the target evaluation parameter of the second backup time point, data is restored from the local database based on the full backup data corresponding to the first backup time point.

[0122] In the embodiment of the present application, data is restored from the local database based on the full backup data corresponding to the first backup time point to obtain target recovery data, including:

[0123] (1) A first database operation sequence between a data recovery time point and a first backup time point is obtained, where the first database operation sequence includes a plurality of database operations.

[0124] In the embodiment of the present application, the type of database operation can be an insert operation, a delete operation, a modify operation, etc., which is set according to the specific situation.

[0125] In an embodiment of the present application, a first database operation sequence between the data recovery time point and the first backup time point is obtained from a log file. Specifically, when the database to be backed up is running, when operations are monitored on the data of the database to be backed up, each database operation performed on the database to be backed up is recorded. For example, the data recovery time point is 11:10, the first backup time point is 11, an insert operation is performed on the database to be backed up at 11:05, and a delete operation is performed on the database to be backed up at 11:09. The first database operation sequence from the data recovery time point to the first backup time point includes an insert operation and a delete operation.

[0126] (2) Determine a first database inverse operation sequence of the first database operation sequence based on the first database operation sequence, where the first database inverse operation sequence includes a plurality of database inverse operations corresponding to the plurality of database operations.

[0127] In the embodiment of the present application, the operation time of the multiple database inverse operations corresponding to the multiple database operations is the same, and the operation contents are opposite.

[0128] In an embodiment of the present application, the inverse operation of the insert operation is a delete operation, and the inverse operation of the delete operation is an insert operation. The multiple database inverse operations of the first database inverse operation sequence are delete operations and insert operations, respectively. For example, the data recovery time point is 11:10, the first backup time point is 11:00, an insert operation is performed on the database to be backed up at 11:05, and a delete operation is performed on the database to be backed up at 11:09. The first database operation sequence from the data recovery time point to the first backup time point includes an insert operation at 11:05 and a delete operation at 11:09. The first database inverse operation sequence includes a delete operation at 11:05 and an insert operation at 11:09.

[0129] (3) Based on the reverse operation sequence of the first database, the full backup data corresponding to the first backup time point is modified to obtain the target recovery data.

[0130] For example, at 11:05, the full backup data corresponding to the first backup time point is inserted, and then at 11:09, the deletion operation is continued to obtain the target recovery data.

[0131] Furthermore, if the target evaluation parameter of the first backup time point is not greater than the target evaluation parameter of the second backup time point, a second database operation sequence between the second backup time point and the data recovery time point is obtained, and the second database operation sequence includes multiple database operations; based on the second database operation sequence, the full backup data corresponding to the second backup time point is modified to obtain the target recovery data.

[0132] In a specific embodiment, the target evaluation parameters of the candidate backup time point are determined based on a preset weight coefficient of the candidate backup time point and the time difference between the candidate backup time point and the data recovery time point, including: weighting the time difference between the candidate backup time point and the data recovery time point based on the preset weight coefficient to obtain the target evaluation parameters of the candidate backup time point.

[0133] like Figure 3 As shown, in a specific embodiment, the target evaluation parameter of the candidate backup time point is determined based on the preset weight coefficient of the candidate backup time point and the time difference between the candidate backup time point and the data recovery time point, including:

[0134] 301. Obtain the number of database operations between the candidate backup time point and the data recovery time point.

[0135] 302. Determine a target evaluation parameter of the candidate backup time point based on a preset weight coefficient of the candidate backup time point, a time difference between the candidate backup time point and the data recovery time point, and a number of database operations between the candidate backup time point and the data recovery time point.

[0136] Among them, the smaller the time difference, the larger the target evaluation parameter, and the smaller the number of database operations, the larger the target evaluation parameter.

[0137] Specifically, the target evaluation parameters of the candidate backup time point are determined based on the preset weight coefficient of the candidate backup time point, the time difference between the candidate backup time point and the data recovery time point, and the number of database operations between the candidate backup time point and the data recovery time point, including:

[0138] (1) Obtain the operation position of the database operation between the candidate backup time point and the data recovery time point.

[0139] In an embodiment of the present application, the data in the local database is stored in a data structure of multiple data tables, the data tables are sequential tables, and the elements of the data structure in the local database are stored continuously. Since the elements of the data structure in the local database are stored continuously, and each element can be directly accessed using a subscript. When inserting or deleting elements in the data table of the local database, it is necessary to move the positions of subsequent elements to maintain the orderliness of the sequential table. For inserting an element with a value of x at subscript position i, it is necessary to move all elements with subscripts i to n-1 one position to the right, and then insert x into the element at position i. For the deletion operation, it is necessary to move all elements with subscripts i+1 to n-1 one position to the left, and then leave the element with subscript n-1 empty.

[0140] (2) Determine the operational complexity of the database operation based on the operation location of the database operation.

[0141] When the operation position of the database operation is different, the movement of the database operation elements under the operation is different and the operation complexity is different.

[0142] Specifically, the operation position of the database operation in the data table to be operated is obtained, the number of elements between the operation position and the element at the end of the data table to be operated is obtained, and the operation complexity of the database operation is determined based on the number of elements between the operation position and the element at the end of the data table to be operated. The more the number of elements between the operation position and the element at the end of the data table to be operated, the higher the operation complexity.

[0143] (3) Determine the total complexity of database operations between the candidate backup time point and the data recovery time point based on the operation complexity of each database operation.

[0144] In a specific embodiment, the operation complexity of each database operation is added together to obtain the total complexity of the database operation.

[0145] In another specific implementation example, the operation type of the database operation is obtained, wherein the operation type is a delete operation, an insert operation, and a modify operation. The complexity weight of the database operation is determined based on the operation type of the database operation, wherein different operation types correspond to different complexity weights; the operation complexity of the database operation is weighted and summed based on the complexity weight of the database operation to obtain the total complexity of the database operation. Different operation types correspond to different complexity weights, which can be set according to specific circumstances. Specifically, database operations of different operation types are performed on the same operation position of the same data table to be operated in advance to obtain the operation completion time, and the complexity weight of the database operation is determined based on the operation completion time of the database operations of different operation types. Among them, the longer the operation completion time, the higher the complexity weight.

[0146] (4) Determine target evaluation parameters of the candidate backup time point based on a preset weight coefficient of the candidate backup time point, the time difference between the candidate backup time point and the data recovery time point, the number of database operations between the candidate backup time point and the data recovery time point, and the total complexity of database operations between the candidate backup time point and the data recovery time point.

[0147] Among them, the smaller the time difference, the larger the target evaluation parameter; the smaller the number of database operations, the larger the target evaluation parameter; the greater the total complexity of database operations, the smaller the number of database operations.

[0148] In the embodiment of the present application, the time difference between the candidate backup time point and the data recovery time point, the number of database operations between the candidate backup time point and the data recovery time point, and the total complexity of database operations between the candidate backup time point and the data recovery time point are normalized to obtain a normalized value of the time difference, a normalized value of the number of database operations, and a normalized value of the total complexity of database operations. The target evaluation parameter Z is determined based on the preset weight coefficient α, the normalized value of the time difference T, the normalized value of the number of database operations M, and the normalized value of the total complexity of database operations O.

[0149] Specifically, the target evaluation parameters satisfy the following formula:

[0150]

[0151] Among them, α is the preset weight coefficient, T is the normalized value of time difference, M is the normalized value of database operation number, O is the normalized value of total complexity of database operation, and Z is the target evaluation parameter.

[0152] Furthermore, the synthetic full backup data obtained during the last incremental backup of the local database is obtained according to a preset period, and snapshot data of the synthetic full backup data is generated. The snapshot data of the synthetic full backup data is mounted in the local database. When the incremental backup data is obtained again, the incremental backup data obtained again is merged into the snapshot data of the synthetic full backup data to obtain a new data snapshot, and the mount point of the local database is unmounted, so that the synthetic full backup data corresponding to the new data snapshot is backed up in the local database, thereby obtaining multiple full backup data according to a preset period. The multiple full backup data include the initial full backup data and multiple synthetic full backup data synthesized multiple times. The preset period can be half an hour, one hour, etc., which can be set according to the specific situation.

[0153] Furthermore, in order to reduce the amount of full backup data in the local database. In a specific embodiment, the local database includes a first local cache database and a second local cache database, wherein the read and write speed of the first local cache database is greater than the read and write speed of the second local cache database, and the data storage upper limit of the first local cache database is less than the data storage upper limit of the second local cache database. For example, the first local cache database is Redis data, and the second local cache database is an Hbase database. When the amount of data in the first local database is greater than a preset value, part of the full backup data cached in the first local cache database is transferred to the second local cache database.

[0154] Correspondingly, restoring data from the local database based on the full backup data corresponding to the first backup time point to obtain target recovery data includes: first searching the first local cache database for the full backup data at the first backup time point, and if the first local cache database does not have the full backup data at the first backup time point, searching the second local cache database for the full backup data at the first backup time point. The first local cache database with a higher read and write speed and the second local cache database with a larger storage capacity cooperate with each other to store data, which can improve the speed of finding data.

[0155] Furthermore, in order to further improve the speed of full backup data, the cache time of each full backup data in the first local cache database is obtained, and the transfer priority of each full backup data is determined based on the cache time of each full backup data, wherein the longer the cache time of the full backup data is, the higher the transfer priority of the full backup data is. When the amount of full backup data cached in the first local cache database is greater than a preset value, the full backup data with the highest transfer priority is transferred from the first local cache database to the second local cache database.

[0156] Furthermore, in order to further improve the speed of searching for target full backup data, the cache time of each full backup data in the first local cache database and the number of times each full backup data is used are obtained, wherein the operation of using the full backup data is sequentially recorded as a number of times used, and the transfer priority of each full backup data is determined based on the cache time and the number of times used of each full backup data, wherein the shorter the cache time of the full backup data, the higher the transfer priority of the full backup data, and the shorter the cache time of the number of times used, the higher the transfer priority of the full backup data. When the amount of full backup data cached in the first local cache database is greater than a preset value, the full backup data with the highest transfer priority is transferred from the first local cache database to the second local cache database.

[0157] Furthermore, the backup time points of each full backup data in the first local cache database are obtained according to a preset period, and each backup time point is determined as a target backup time point, and the backup time point whose time difference with the target backup time point is within a preset time range is determined as a neighborhood time point of the target backup time point, and the number of neighborhood time points of the target backup time point is obtained, and the number of neighborhood time points of each backup time point is obtained. If the target backup time point is the backup time point with the largest number of neighborhood time points, the full backup data corresponding to some neighborhood time points of the target backup time point are transferred from the first local cache database to the second local cache database. The preset time range can be less than 3 hours, etc., which can be set according to the specific situation.

[0158] Furthermore, the full backup data corresponding to the neighboring time point closest to the target backup time point is transferred from the first local cache database to the second local cache database.

[0159] In the embodiment of the present application, obtaining the first data snapshot of the initial full backup data further includes: the user creates a backup plan, and backs up the data according to the preset period according to the backup plan created by the user. The backup plan includes a backup type and a preset period.

[0160] The process for users to create a backup plan is as follows Figure 4-Figure 8 As shown: Figure 4 As shown, Figure 4 The login interface is displayed. The user enters the database ID and account password on the login interface. The interface changes to Figure 5 The database display interface, Figure 5 The database display interface shows the options of each database. By selecting different options, you can enter the plan type selection page of different databases. Figure 6 A database plan type selection page is displayed. The user can select the backup type on the plan type selection page. After the user clicks the OK button, the backup type entered by the user is associated with the database to be backed up corresponding to the database identifier. Figure 7 The created plan display interface, in Figure 7 The created plan display interface displays the created backup plans. When the user selects a created plan on the created plan display interface, the backup starts according to the preset period and enters Figure 8 The backup result display interface is used to display the backup result of the database to be backed up.

[0161] In order to facilitate better implementation of the data backup and recovery method based on data merging provided in the embodiment of the present application, the embodiment of the present application also provides a data backup and recovery device based on data merging based on the above data backup and recovery method based on data merging. The meanings of the terms are the same as those in the above data backup and recovery method based on data merging. For specific implementation details, please refer to the description in the above method embodiment.

[0162] Please refer to Fig. 9 , Fig. 9 A schematic diagram of the structure of a data backup and recovery device based on data merging provided in an embodiment of the present application, the data backup and recovery device based on data merging may include:

[0163] An acquisition module 701 is used to acquire a first data snapshot of the initial full backup data;

[0164] A mounting module 702 is used to mount the first data snapshot to a local database, so that the initial full backup data is fully backed up in the local database;

[0165] A merging module 703 is used to merge the incremental backup data into the first data snapshot to obtain a second data snapshot when the incremental backup data is acquired;

[0166] An unloading module 704 is used to unload the mount point of the local database so that the synthetic full backup data corresponding to the second data snapshot is backed up in the local database;

[0167] The recovery module 705 is used to recover data from the local database based on the data recovery instruction to obtain target recovery data when a data recovery instruction is obtained.

[0168] The specific implementation of each of the above modules can be found in the previous embodiments and will not be described in detail here.

[0169] An embodiment of the present application also provides an electronic device, including a memory and a processor, wherein the processor is used to execute the steps in the data backup and recovery method based on data merging provided in this embodiment by calling a computer program stored in the memory.

[0170] Please refer to Fig.10 , Fig.10 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0171] The electronic device may include components such as a processor 101 with one or more processing cores, a memory 102 with one or more computer-readable storage media, a power supply 103, and an input unit 104. Those skilled in the art will appreciate that the electronic device structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Among them:

[0172] The processor 101 is the control center of the electronic device, which uses various interfaces and lines to connect various parts of the entire electronic device, and executes various functions of the electronic device and processes data by running or executing software programs and / or modules stored in the memory 102, and calling data stored in the memory 102. Optionally, the processor 101 may include one or more processing cores; optionally, the processor 101 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 101.

[0173] The memory 102 can be used to store software programs and modules. The processor 101 executes various functional applications and data processing by running the software programs and modules stored in the memory 102. The memory 102 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 102 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 102 may also include a memory controller to provide the processor 101 with access to the memory 102.

[0174] The electronic device also includes a power supply 103 for supplying power to each component. Optionally, the power supply 103 can be logically connected to the processor 101 through a power management system, so as to manage charging, discharging, and power consumption through the power management system. The power supply 103 can also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0175] The electronic device may further include an input unit 104, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0176] Although not shown, the electronic device may also include a display unit, an image acquisition component, etc., which will not be described in detail here. Specifically in this embodiment, the processor 101 in the electronic device will load the executable code corresponding to one or more computer programs into the memory 102 according to the following instructions, and the processor 101 will execute the steps in the data backup and recovery method based on data merging provided in this application, such as:

[0177] Obtain a first data snapshot of the initial full backup data; mount the first data snapshot to the local database so that the initial full backup data is fully backed up in the local database; when the incremental backup data is obtained, merge the incremental backup data into the first data snapshot to obtain a second data snapshot; unmount the mount point of the local database so that the synthetic full backup data corresponding to the second data snapshot is backed up in the local database; when the data recovery instruction is obtained, restore the data from the local database based on the data recovery instruction to obtain the target recovery data.

[0178] It should be noted that the electronic device provided in the embodiment of the present application and the data backup and recovery method based on data merging in the above embodiment belong to the same concept, and its specific implementation process is detailed in the above related embodiments and will not be repeated here.

[0179] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program stored therein is executed on a processor of an electronic device provided in an embodiment of the present application, the processor of the electronic device executes the steps in the data backup and recovery method based on data merging provided in the present application. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0180] The present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes various optional implementations of the above-mentioned data backup and recovery method based on data merging.

[0181] The above is a detailed introduction to a data backup and recovery method and device based on data merging provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

[0182] It should be noted that when the above embodiments of the present application are applied to specific products or technologies, the relevant data of the user is involved, and the user's permission or consent is required, and the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

Claims

1. A data backup and recovery method based on data merging, characterized in that: include: Obtaining a first data snapshot of the initial full backup data; Mounting the first data snapshot to a local database so that the initial full backup data is fully backed up in the local database; When the incremental backup data is obtained, the incremental backup data is merged into the first data snapshot to obtain a second data snapshot; Unmounting the mount point of the local database, so that the synthetic full backup data corresponding to the second data snapshot is backed up in the local database; When the data recovery instruction is obtained, the data is recovered from the local database based on the data recovery instruction to obtain target recovery data.

2. The data backup and recovery method based on data merging according to claim 1, characterized in that: The recovering data from the local database based on the data recovery instruction to obtain target recovery data includes: Obtaining a data recovery time point of the data recovery instruction; Get the backup time point of each full backup data in the local database; Determine whether there is a backup time point that is the same as the data recovery time point among the backup time points; If there is no backup time point that is the same as the data recovery time point among the backup time points, the backup time point closest to the data recovery time point after the data recovery time point is determined as the first backup time point, and the backup time point closest to the data recovery time point before the data recovery time point is determined as the second backup time point; The first backup time point and the second backup time point are respectively determined as candidate backup time points, and a target evaluation parameter of the candidate backup time point is determined based on a preset weight coefficient of the candidate backup time point and a time difference between the candidate backup time point and the data recovery time point, to obtain a target evaluation parameter of the first backup time point and a target evaluation parameter of the second backup time point, wherein the larger the time difference is, the smaller the target evaluation parameter is, and the preset weight coefficient of the first backup time point is smaller than the preset weight coefficient of the second backup time point; If the target evaluation parameter of the first backup time point is greater than the target evaluation parameter of the second backup time point, data is restored from the local database based on the full backup data corresponding to the first backup time point to obtain the target restored data.

3. The data backup and recovery method based on data merging according to claim 2 is characterized in that: The restoring data from the local database based on the full backup data corresponding to the first backup time point to obtain the target restored data includes: Acquire a first database operation sequence between the data recovery time point and the first backup time point, wherein the first database operation sequence includes a plurality of database operations; Determine a first database inverse operation sequence of the first database operation sequence based on the first database operation sequence, wherein the first database inverse operation sequence includes a plurality of database inverse operations corresponding to a plurality of database operations; The full backup data corresponding to the first backup time point is modified based on the first database inverse operation sequence to obtain target recovery data.

4. The data backup and recovery method based on data merging according to claim 2 is characterized in that: The data backup and recovery method based on data merging includes: If the target evaluation parameter of the first backup time point is not greater than the target evaluation parameter of the second backup time point, data is restored from the local database based on the full backup data corresponding to the second backup time point to obtain the target restored data.

5. The data backup and recovery method based on data merging according to claim 4 is characterized in that: The restoring data from the local database based on the full backup data corresponding to the second backup time point to obtain the target restored data includes: Acquire a second database operation sequence between the second backup time point and the data recovery time point, where the second database operation sequence includes a plurality of database operations; The full backup data corresponding to the second backup time point is modified based on the second database operation sequence to obtain target recovery data.

6. The data backup and recovery method based on data merging according to claim 2, characterized in that: The determining of the target evaluation parameter of the candidate backup time point based on the preset weight coefficient of the candidate backup time point and the time difference between the candidate backup time point and the data recovery time point includes: Obtaining the number of database operations between the candidate backup time point and the data recovery time point; The target evaluation parameter of the candidate backup time point is determined based on a preset weight coefficient of the candidate backup time point, a time difference between the candidate backup time point and the data recovery time point, and a number of database operations between the candidate backup time point and the data recovery time point, wherein the smaller the time difference, the larger the target evaluation parameter, and the smaller the number of database operations, the larger the target evaluation parameter.

7. The data backup and recovery method based on data merging according to claim 1, characterized in that: Before mounting the first data snapshot to the local database so that the initial full backup data is fully backed up in the local database, the method includes: Obtaining a database identifier of a database to be backed up input by a user, wherein the database to be backed up is a storage location of the initial full backup data; Determining a backup type of the database to be backed up based on the database identifier; When the backup type is a permanent full backup type, the first data snapshot is mounted to a local database, so that the initial full backup data is fully backed up in the local database.

8. A data backup and recovery device based on data merging, characterized in that: include: An acquisition module, used to acquire a first data snapshot of the initial full backup data; A mounting module, used for mounting the first data snapshot to a local database, so that the initial full backup data is fully backed up in the local database; a merging module, configured to merge the incremental backup data into the first data snapshot to obtain a second data snapshot when the incremental backup data is acquired; an uninstallation module, used for uninstalling the mount point of the local database, so that the synthetic full backup data corresponding to the second data snapshot is backed up in the local database; The recovery module is used to recover data from the local database based on the data recovery instruction when a data recovery instruction is obtained to obtain target recovery data.

9. An electronic device, characterized in that: It comprises a memory and a processor, wherein the memory stores a computer program, and the processor is used to run the computer program in the memory to execute the steps in the data backup and recovery method based on data merging as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the steps in the data backup and recovery method based on data merging according to any one of claims 1 to 7.

Images