WO2024021861A1 - 数据恢复方法及电子设备 - Google Patents

数据恢复方法及电子设备 Download PDF

Info

Publication number
WO2024021861A1
WO2024021861A1 PCT/CN2023/098051 CN2023098051W WO2024021861A1 WO 2024021861 A1 WO2024021861 A1 WO 2024021861A1 CN 2023098051 W CN2023098051 W CN 2023098051W WO 2024021861 A1 WO2024021861 A1 WO 2024021861A1
Authority
WO
WIPO (PCT)
Prior art keywords
backup data
restored
data
backup
incremental
Prior art date
Application number
PCT/CN2023/098051
Other languages
English (en)
French (fr)
Inventor
陈琪
Original Assignee
超聚变数字技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 超聚变数字技术有限公司 filed Critical 超聚变数字技术有限公司
Publication of WO2024021861A1 publication Critical patent/WO2024021861A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G06F11/1453—Management of the data involved in backup or backup restore using de-duplication of the data
    • 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

Definitions

  • the present disclosure relates to the field of data processing technology, and in particular to a data recovery method and electronic equipment.
  • a backup system can currently be set up for the database.
  • the backup system can back up the data in the database through differential incremental backup in each backup time window.
  • the database requires the execution of the command to open reset logs (open resetlogs).
  • open reset logs open reset logs
  • the database will create a new database entity (incarnation). Then, the production equipment obtains the backup data from the backup device and restores it. All data backed up before the point in time are fully restored to achieve database data recovery.
  • Embodiments of the present application provide a data recovery method and electronic device, which can improve the efficiency of data recovery.
  • this application provides a data recovery method, which is executed by production equipment.
  • the method includes: obtaining the identification of the backup data to be restored of the target database; when the backup data to be restored is incremental backup data, obtaining the Restore the backup data; where the restored backup data and the backup data to be restored are backup data based on the same full backup data, the backup time of the restored backup data is earlier than the backup time of the backup data to be restored, and the restored backup data is the backup time The most recent restored backup data from the backup time of the backup data to be restored; in response to querying the first snapshot, restore the backup data to be restored according to the incremental backup data recovery method; where the first snapshot is used to determine that the backup data has been restored
  • the recovery time is the state of the target database; the incremental backup data recovery method is based on the incremental backup data, based on the difference between the backup data to be restored and the restored backup data, to restore the backup data to be restored.
  • this method obtains the identification of the backup data to be restored in the target database, when the backup data to be restored is incremental backup data, the restored backup data based on the same full backup data is obtained, and the first backup data is obtained after querying
  • the backup data to be restored is restored based on the incremental backup data based on the difference between the restored backup data and the backup data to be restored. Since the first snapshot that can restore the target database to the state at the recovery time of the restored backup data is queried in advance, it is avoided that a new database entity is generated after the last data recovery, resulting in the inability to identify the database entity of the target database. And continue to perform data recovery on the basis of the restored backup data, realizing the reuse of the restored backup data, thereby improving the efficiency of data recovery.
  • restoring the backup data to be restored according to an incremental backup data recovery method includes: responding to querying the first snapshot, restoring the target database to the first snapshot according to the first snapshot.
  • One state is the state of the target database after data recovery using the restored backup data; according to the incremental backup data recovery method, the target database in the first state is restored using the backup data to be restored.
  • the backup data to be restored is used to restore the first state
  • the target database includes: obtaining n incremental backup data between the restored backup data and the backup data to be restored; n backup times of data backup between the restored backup data and the backup data to be restored; n is greater than or equal to 1 is an integer; based on n incremental backup data, determine the differential incremental backup data; restore the backup data to be restored of the target database in the first state according to the differential incremental backup data.
  • obtaining the identification of the backup data to be restored of the target database includes: obtaining the identification of the backup data of the target database to be restored from the metadata record information; the metadata record information is included under each backup time. The identification of the backup data recorded when the backup data is backed up.
  • obtaining the identification of the backup data to be restored from the metadata record information can facilitate subsequent determination of the backup data that needs to be restored based on the identification of the backup data to be restored, thereby improving data recovery efficiency.
  • the identifier is used to indicate the backup data type and the serial number corresponding to the backup data type; the backup data type includes full backup data or incremental backup data; the serial number corresponding to the backup data type includes full backup data. Backup serial number or incremental backup serial number.
  • the backup data is identified with the full backup serial number and the incremental backup serial number, which facilitates subsequent determination of the backup data that needs to be restored, thereby improving data recovery efficiency.
  • n incremental backup data between the restored backup data and the backup data to be restored including: an incremental backup sequence number that is greater than the restored backup data, and is less than or equal to the to-be-restored backup data.
  • the incremental backup data corresponding to the incremental backup sequence numbers of the backup data is determined to be n incremental backup data; the incremental backup sequence number is determined based on the identification of the backup data to be restored.
  • the incremental backup sequence number is used to determine the backup data that needs to be restored, thereby improving data recovery efficiency.
  • the method when the backup data to be restored is incremental backup data, before obtaining the restored backup data, the method further includes: determining the backup data type of the backup data to be restored based on the identification of the backup data to be restored, The backup data type includes full backup data or incremental backup data.
  • determining the backup data type of the backup data to be restored through the identification of the backup data to be restored improves the speed of determining the backup data type.
  • the method further includes: when the backup data to be restored is full backup data, restoring the backup data to be restored according to the full backup data method; the full backup data
  • the recovery method is to restore the backup data to be restored based on the full backup data.
  • the first snapshot includes configuration information of the target database at the recovery time of the restored backup data, log information of the target database at the recovery time of the restored backup data, and data of the restored backup data. information.
  • storing the relevant information of the target database in the first snapshot can facilitate the restoration of the target database to the configuration state after the last data recovery, so as to reuse the recovered data.
  • after restoring the backup data to be restored according to the incremental backup data recovery method it also includes: clearing the content in the first snapshot; obtaining the second state of the target database after restoring the backup data to be restored; The second state updates the first snapshot.
  • the first snapshot is updated so that when subsequent data restoration is performed, data restoration can be continued based on the data restored this time.
  • a second snapshot is generated; wherein the second snapshot is used to determine the second state.
  • the first snapshot is added so that when data is restored later, you can choose to continue data restoration based on the data restored this time.
  • the present application provides a data recovery device.
  • the present application can divide the data recovery device into functional modules according to the method provided in the first aspect.
  • each function module can be divided corresponding to each function, or two or more functions can be inherited in one processing module.
  • this application can divide the data recovery device into an identification acquisition module, a data acquisition module, a data recovery module, etc. according to functions.
  • inventions of the present application provide a computing device.
  • the computing device includes a processor and a memory.
  • the memory is used to store computer program instructions.
  • the computer program instructions are loaded and executed by the processor to enable the computing device to implement the above aspect.
  • embodiments of the present application provide a computer-readable storage medium in which at least one computer program instruction is stored, and the computer program instruction is loaded and executed by a processor to implement the above aspects.
  • embodiments of the present application provide a computer program product or computer program.
  • the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium.
  • the processor of the computing device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computing device performs the data recovery method provided in various optional implementations of the above aspects.
  • Figure 1 is a schematic diagram of a data management system according to an exemplary embodiment
  • Figure 2 is a schematic diagram of a differential incremental backup involved in the embodiment shown in Figure 1;
  • Figure 3 is a schematic flowchart of a data recovery method according to an exemplary embodiment
  • Figure 4 is a schematic flowchart of a data recovery method according to an exemplary embodiment
  • Figure 5 is a schematic flowchart of querying whether the first snapshot exists in the embodiment shown in Figure 4;
  • Figure 6 is a schematic flowchart of a database restoration involved in the embodiment shown in Figure 4;
  • Figure 7 is a schematic flow chart of determining differential incremental backup data that needs to be restored in the embodiment shown in Figure 4;
  • Figure 8 is a schematic diagram of a first snapshot update process involved in the embodiment shown in Figure 4.
  • Figure 9 is a schematic diagram of a target database data recovery process involved in the embodiment shown in Figure 4.
  • Figure 10 is a schematic structural diagram of a data recovery device provided by an exemplary embodiment of the present application.
  • Figure 11 is a schematic structural diagram of a computing device provided by an exemplary embodiment of the present application.
  • the "plurality” mentioned in this article means two or more than two.
  • “And/or” describes the relationship between related objects, indicating that there can be three relationships.
  • a and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone.
  • the character “/” generally indicates that the related objects are in an "or” relationship.
  • FIG. 1 is a schematic diagram of a data management system related to an embodiment of the present application.
  • the data management system includes a production system 110 and a backup system 120.
  • the production system 110 includes a database 111, a backup agent component 112, an operating system 113 and a production storage component 114.
  • the backup system 120 includes a backup service component 121 and a backup storage component 122 .
  • the data management system may include backup equipment and production equipment.
  • the production equipment is in the production system 110 and the backup equipment is in the backup system 120 .
  • the production device can be a computing device, and the backup device can also be a computing device.
  • the production device and the backup device can be different computing devices, or they can be the same computing device, and there is no limitation here.
  • the computing device may be a smartphone, tablet, e-book reader, personal laptop, server, etc.
  • the production storage component 114 may be a component with a snapshot generation function
  • the backup agent component 112 may be a plug-in installed on the production device.
  • Backup data may be stored in the backup storage component 122 .
  • the backup service component 121 and the backup agent component 112 can be connected through a communication network.
  • the backup agent component 112 can transmit the backup data to the backup service component 121 through the communication network.
  • the backup service component 121 can send the backup data to the backup storage component 122. for storage.
  • the production system and the backup system can be connected through a communication network.
  • the communication network is a wired network or a wireless network.
  • the above-mentioned wireless network or wired network uses standard communication technologies and/or protocols.
  • the network is usually the Internet, but can be any network, including but not limited to local area network (LAN), metropolitan area network (MAN), wide area network (WAN), mobile, wired or wireless Any combination of networks, private networks, or virtual private networks.
  • data exchanged over the network is represented using technologies and/or formats including hypertext mark-up language (HTML), extensible markup language (XML), etc.
  • HTTP hypertext mark-up language
  • XML extensible markup language
  • customized and/or dedicated data communication technologies may also be used in place of or in addition to the above-described data communication technologies.
  • the computing device can perform data backup through differential incremental backup.
  • differential incremental backup each time the data is backed up, the differential data from the last backup result to the current backup is backed up.
  • Figure 2 is a schematic diagram of a differential incremental backup related to an embodiment of the present application.
  • the computing device can perform full backup during the backup time on the first day, the computing device can perform differential incremental backup during the backup time on the second day, and the computing device can also perform differential incremental backup during the backup time on the third day.
  • the computing device still performs differential incremental backup during the backup time on the fourth day.
  • the data can be fully backed up.
  • the backup time on the first day can be the time when data backup is started
  • the backup time on the second to fourth days can be the time for daily rapid differential incremental backup of data
  • the backup time on the fifth day can be when the data is idle.
  • the full backup data of the first day is the full data of the backup time of the first day.
  • the differential incremental backup data of the second day is the full data backed up at the backup time of the second day and the full data backed up at the backup time of the first day.
  • the differential backup data on the third day is the differential backup data between the full data backed up at the backup time on the third day and the full data backed up at the backup time on the second day.
  • the differential backup data on the fourth day The differential incremental backup data is the differential backup data between the full data backed up at the backup time on the fourth day and the full data backed up at the backup time on the third day.
  • the full backup data on the fifth day is the backup time on the fifth day. All data backed up.
  • data backup during the backup time on the first day can be a full data backup, where the full data includes data a, data b, and data c; data backup during the backup time on the second day can be a differential incremental backup. If data a changes to data d at this time, then the data backup during the backup time on the second day will only back up data a into data d; the data backup during the backup time on the third day will be a differential incremental backup. If the data d becomes data e, then the data backup on the third day of the backup time will only back up data d and become the data e; the data backup on the fourth day of the backup time will be a differential incremental backup.
  • the backup time on the fourth day will be Data backup means only backing up data b into data f; data backup at the backup time on the fifth day can be a full data backup. At this time, the full amount of data includes data e, data f and data c.
  • FIG. 3 shows a schematic flowchart of a data recovery method provided by an exemplary embodiment of the present application.
  • the data recovery method may be executed by a computing device.
  • the computing device may be a production device in the data management system shown in FIG. 1 .
  • the data recovery determination method includes the following steps:
  • Step 301 Obtain the identification of the backup data to be restored of the target database.
  • the production equipment when the data of the target database of the production equipment needs to be restored, the production equipment can obtain the identification of the backup data to be restored of the target database.
  • the backup data to be restored may be the backup data corresponding to the data that needs to be restored in the target database, and the backup data has a corresponding identifier for indicating the data content of the backup data.
  • the production equipment can store the production data in the target database in real time during daily data production.
  • the data in the target database can be backed up at each backup time, and the backup data can be transmitted and stored in the target database.
  • the production equipment can obtain it from the backup device when it needs to perform corresponding data recovery.
  • the target database can be a relational database or an in-memory database.
  • Step 302 When the backup data to be restored is incremental backup data, obtain the restored backup data; where the restored backup data and the backup data to be restored are backup data based on the same full backup data, and the backup time of the restored backup data is earlier.
  • the backup time of the backup data to be restored is the backup time of the backup data to be restored, and the restored backup data is the restored backup data whose backup time is the latest to the backup time of the backup data to be restored.
  • the production equipment determines whether the backup data to be restored is incremental backup data.
  • the backup time can be obtained based on the obtained identification of the backup data to be restored. The most recent backup time of the backup data to be restored, and the restored backup data backed up based on the same full backup data.
  • the restored backup data may be full backup data or incremental backup data.
  • the restored backup data closest to the backup data to be restored can be obtained based on the log content of the target database, and the subsequent step.
  • the latest restored backup data is recorded in the log content of the target database.
  • the backup time can be determined according to the identification of the backup data to be restored.
  • the latest backup data that is earlier than the backup time of the backup data to be restored and is based on the same full backup data is obtained as restored backup data.
  • Step 303 In response to querying the first snapshot, restore the backup data to be restored according to the incremental backup data recovery method; wherein the first snapshot is used to determine the state of the target database at the recovery time of the restored backup data; the incremental backup data
  • the recovery method is a method of restoring the backup data to be restored based on the incremental backup data based on the difference between the backup data to be restored and the restored backup data.
  • the production equipment can start to query whether the first snapshot exists. If the first snapshot is queried, the production equipment can query based on the difference between the backup data to be restored and the restored backup data. Incremental backup data recovery to restore the backup data.
  • the first snapshot may be a storage snapshot generated by the production device after data recovery.
  • the first snapshot may be a storage snapshot generated after the latest data recovery, or may be a storage snapshot generated after each data recovery.
  • the state of the target database at the recovery time of the restored backup data can be used to indicate the restored data contained in the newly generated database entity of the target database after data recovery of the restored backup data.
  • the system change number of the database and the database log number can be used to indicate the restored data contained in the newly generated database entity of the target database after data recovery of the restored backup data.
  • various data management objects set for convenient data management may exist in the database management system, and the data management objects may be database entities.
  • database entities can be data stored in database tables, views, stored procedures, and various data management objects.
  • the production equipment can obtain the identification of the backup data to be restored in the target database, and when the backup data to be restored is incremental backup data, obtain the latest backup data based on the same full backup data.
  • the backup data is restored, and when the first snapshot is queried, the backup data to be restored is restored based on the incremental backup data of the difference between the restored backup data and the backup data to be restored. Since the first snapshot that can restore the target database to the state at the recovery time of the restored backup data is queried in advance, it is avoided that a new database entity is generated after the last data recovery, resulting in the inability to identify the database entity of the target database. And continue to perform data recovery on the basis of the restored backup data, realizing the reuse of the restored backup data, thereby improving the efficiency of data recovery.
  • FIG. 4 shows a schematic flowchart of a data recovery method provided by an exemplary embodiment of the present application.
  • the data recovery method may be executed by a computing device.
  • the computing device may be a production device in the data management system shown in FIG. 1 .
  • This data recovery method includes the following steps:
  • Step 401 Obtain the identification of the backup data to be restored of the target database.
  • the production equipment obtains the identification of the backup data to be restored corresponding to the data that needs to be restored in the target database.
  • the production equipment can obtain the identification of the backup data to be restored of the target database from the metadata record information.
  • the metadata record information includes the identification of the backup data recorded when the backup data is backed up at each backup time.
  • the data produced by the production equipment can be backed up simultaneously.
  • the data backed up at the same time can be recorded in the form of identification, and metadata record information containing the identification of each backup data is generated.
  • the identifier is used to indicate the backup data type and the corresponding serial number of the backup data type; the backup data type includes full backup data or incremental backup data; the corresponding serial number of the backup data type includes full backup Serial number or incremental backup serial number.
  • the backup data type of the backup data at each backup time can be obtained, that is, whether the backup data at each backup time is full backup data or incremental backup data; if the backup data at this backup time is obtained, If the backup data type of the backup data is full backup data, you can also get the serial number of the full backup data at this backup time. If the backup data type of the backup data at this backup time is incremental backup data, you can also get the sequence number. The serial number of the full backup data to which the incremental backup data under the backup time belongs, and the serial number to which the incremental backup data under the full backup data belongs.
  • the full backup sequence number corresponding to the full backup data is recorded at the backup time.
  • the full backup serial number of the last full backup and the incremental backup serial number under the full backup are recorded at the backup time, which can be recorded as "full backup serial number” + " .” + “Incremental backup serial number”.
  • the metadata record information may include the content shown in Table 1 below.
  • Step 402 Determine the backup data type of the backup data to be restored based on the identification of the backup data to be restored.
  • the production equipment can determine the backup data type of the backup data to be restored based on the obtained identification of the backup data to be restored, that is, determine whether the backup data to be restored is full backup data or a certain full backup data.
  • Incremental backup data under data backup
  • the backup data type can include full backup data or incremental backup data.
  • the production equipment can determine the subsequent data recovery method based on the backup data type of the backup data to be restored, it is necessary to determine the backup data type of the backup data to be restored based on the obtained identification of the backup data to be restored.
  • the backup data to be restored needs to be restored based on the backup data after the data backup is performed on the third day's backup time.
  • the backup sequence number is 1.2, which can determine that the backup data type of the backup data to be restored is incremental backup data. If the backup data to be restored needs to be restored through the backup data after data backup at the backup time on the fifth day, the backup data type of the backup data to be restored can be determined based on the backup sequence number 2 at the backup time on the fifth day. It is a full backup of data.
  • Step 403 When the backup data to be restored is full backup data, restore the backup data to be restored according to the full backup data recovery method.
  • the backup data to be restored when the identification of the backup data to be restored is obtained and it is determined that the backup data type of the backup data to be restored is full backup data, the backup data to be restored can be restored according to the full backup data.
  • the full backup data recovery method is a method of restoring the backup data to be restored based on the full backup data.
  • the restored backup data and the backup data to be restored are backup data based on different full backup data, there is no need to reuse based on the first restored backup data, and the data can be restored directly based on the full data.
  • Step 404 When the backup data to be restored is incremental backup data, obtain the restored backup data.
  • the backup data type of the backup data to be restored is incremental backup data by obtaining the identification of the backup data to be restored, it can be determined that the backup data has been restored, and the restored backup data can be obtained.
  • the restored backup data and the backup data to be restored may be backup data based on the same full backup data, and the backup time of the restored backup data is earlier than the backup time of the backup data to be restored.
  • the full backup data contained in the backup data to be restored is determined through the identification of the backup data to be restored, and it is determined that the backup data to be restored contains the same full backup data, and the backup time Whether there is restored backup data in the backup data that is earlier than the backup time of the backup data to be restored. If there is restored backup data that meets the conditions, the restored backup data can be obtained.
  • each restored backup data can be obtained.
  • the backup data to be restored needs to be restored through the backup data after the data backup is performed on the third day's backup time.
  • the backup sequence number 1.2 at the time can determine that the full backup data contained in the backup data to be restored is full backup data 1.
  • the backup sequence number 1.2 at the backup time on the third day can determine the backup that is earlier than the backup data to be restored.
  • the time is the backup time of the next day, and the corresponding backup sequence number is 1.1. If it is determined that data recovery has been performed at the backup time corresponding to the backup sequence number 1.1, obtain the restored backup data at the backup time corresponding to the backup sequence number 1.1. .
  • the full backup contained in the backup data to be restored can be determined based on the backup sequence number 1.3 at the backup time on the fourth day.
  • the data is full backup data 1.
  • the backup sequence number 1.3 at the backup time of the fourth day it can be determined that the backup time earlier than the backup data to be restored is the backup time of the next day.
  • the corresponding backup sequence numbers are 1.1 and 1.2.
  • Step 405 In response to querying the first snapshot, restore the target database to the first state according to the first snapshot.
  • the production equipment queries whether the first snapshot exists. If it is queried that the first snapshot exists, the production equipment can follow the The contents of the first snapshot restore the target database to its first state.
  • the first state may be the state of the target database after data recovery using the restored backup data.
  • the first snapshot can be used to determine the state of the target database at the time of recovery of the restored backup data.
  • the first snapshot may include the configuration information of the target database at the recovery time of the restored backup data, the log information of the target database at the recovery time of the restored backup data, and the data of the restored backup data. information.
  • the configuration information of the target database can include system change number (SCN), domain name system (domain name system, DNS) connection string, database host name and other information;
  • the log information of the target database can include the log number of the database , the log information of the target database is used to record the operation information of the target database;
  • the data information of the restored backup data may include the storage address information of the restored backup data, the end time node information of the restored backup data, etc.
  • the target database After data recovery, the target database needs to create a new database entity (incarnation).
  • the recovered data is in the newly created database entity.
  • the database entity of the new target database is different from the target database before data recovery.
  • database that is to say, the database entities of the newly created target database and the corresponding database log numbers, system change numbers, etc. of the target database before data recovery are different, resulting in the failure to restore the data the next time.
  • Use the restored backup data which results in that every time you use the backup data for data recovery, you can only restore the full amount of data. For example, the most recent full backup data generated before the required data recovery time point is different from the most recent full amount of data.
  • Data recovery is performed on the full amount of data composed of all incremental backup data generated after backing up the data.
  • the target database can be restored to the new target database corresponding to the previously restored backup data when data recovery is needed again.
  • the updated target database enables reuse of restored backup data.
  • the production equipment queries whether the first snapshot exists through the snapshot name of the first snapshot. If the query finds that the first snapshot exists, a confirmation instruction is returned. If the query finds that the first snapshot does not exist, a negative instruction is returned. , when receiving the confirmation instruction, the first snapshot can be called through the interface to perform the first snapshot recovery.
  • the snapshot name of the first snapshot can be Incremental_PRE_SNAP.
  • the backup data to be restored can be restored according to the full data recovery method.
  • the first restored backup data is the restored backup data whose backup time is earlier than the backup time of the backup data to be restored and the most recent backup time of the backup data to be restored.
  • the increase in the backup data to be restored based on the full backup data of the backup data to be restored and the backup data to be restored under the full backup data can be used.
  • the full backup data recovery method is based on the full backup data with the ID of 1, the incremental backup data with the ID of 1.4, and the 1.1 and 1.2 with the IDs of less than 1.4. , 1.3 corresponding incremental backup data recovery methods to restore the backup data.
  • FIG. 5 is a schematic flowchart of querying whether the first snapshot exists according to an embodiment of the present application.
  • the snapshot name of the first snapshot as Incremental_PRE_SNAP as an example, as shown in Figure 5, first log in to the storage system through the storage system interface through the storage user name and the corresponding password (S51) to obtain the permission to query the first snapshot, and then through The storage system uses the interface to query the snapshot information with the snapshot name "Incremental_PRE_SNAP" (S52), and determines whether the snapshot Incremental_PRE_SNAP exists (S53). If it exists, it returns True to respond, and if it does not exist, it returns False to respond.
  • FIG. 6 is a schematic flowchart of restoring a database according to an embodiment of the present application.
  • the snapshot name of the first snapshot as Incremental_PRE_SNAP as an example, as shown in Figure 6, first log in to the storage system through the storage system interface through the storage user name and the corresponding password (S61) to obtain the permission to call the first snapshot, and then through The storage system interface performs snapshot recovery (S62) on the snapshot whose snapshot name is "Incremental_PRE_SNAP".
  • the first snapshot may also be a file system stored by the database configuration, data files and log files.
  • the storage snapshot is generated according to the snapshot function.
  • Step 406 According to the incremental backup data recovery method, restore the backup data to be restored of the target database in the first state.
  • the production equipment can restore the backup data to be restored of the target database in the first state in order according to the incremental backup data recovery method.
  • the incremental backup data recovery method may be a method of restoring the backup data to be restored based on the incremental backup data based on the difference between the backup data to be restored and the restored backup data.
  • n incremental backup data between the restored backup data and the backup data to be restored are obtained; n backup times of data backup between the restored backup data and the backup data to be restored are obtained; n is an integer greater than or equal to 1; then, based on n incremental backup data, determine the differential incremental backup data; restore the backup data to be restored of the target database in the first state according to the differential incremental backup data.
  • the restored backup data and the backup data to be restored are backup data based on the same full backup data, when the restored backup data can be reused, it is only necessary to obtain the difference between the restored backup data and the backup data to be restored.
  • Different n incremental backup data are used to determine the differential incremental backup data, and the data of the target database in the first state is restored based on the restored backup data according to the differential incremental backup data.
  • the restored backup data is the incremental backup data restored at the backup time of the second day
  • the backup data to be restored is the incremental backup data that needs to be restored at the backup time of the fourth day
  • the production equipment can also determine n incremental backup data as differential incremental backup data based on the identifier.
  • the incremental backup data corresponding to the incremental backup sequence number that is greater than the restored backup data and the incremental backup sequence number that is less than or equal to the backup data to be restored can be determined as n incremental backup data.
  • the backup sequence number may be determined based on the identification of the backup data to be restored.
  • the restored backup data is the incremental backup data restored at the backup time of the next day
  • the corresponding identifier is 1.1
  • the backup data to be restored is the fourth day that needs to be restored.
  • the corresponding identifier of the incremental backup data at the backup time is 1.3.
  • the two incremental backup data that determine the difference between the restored backup data and the backup data to be restored are the incremental backup data identified as 1.2 and 1.3.
  • the data of the target database in the first state can be restored according to the incremental backup data identified as 1.2 and 1.3.
  • FIG. 7 is a schematic flowchart of determining differential incremental backup data that needs to be restored according to an embodiment of the present application.
  • the production equipment parses the serial number corresponding to the latest backup data at the current point in time that needs to be restored, parses out the full backup serial number X and the incremental backup serial number Y (S71), and determines whether the backup data to be restored is It is full backup data (S72). If it is determined to be full backup data, the full backup data is directly determined as the backup data that needs to be restored. If it is determined not to be full backup data, the full amount of the last restored backup data can be analyzed. Backup serial number and incremental backup serial number (S73).
  • the serial number of the restored backup data is 1.2
  • the full backup serial number is 1
  • the incremental backup serial number is 2.
  • the serial number of the last restored backup data can be a.b, and then determine whether the full backup sequence number X of the backup data to be restored is equal to the full backup sequence number a of the last restored backup data (S74). If the full backup sequence number The sum of each incremental backup data of number Y (S75), if the full backup sequence number X of the backup data to be restored is equal to the full backup sequence number a of the last restored backup data, continue to determine whether the incremental backup sequence number Y is greater than the incremental backup serial number b (S76).
  • the incremental backup serial number Y is less than or equal to the incremental backup serial number b, it can be determined that the differential incremental backup data to be restored is equal to the full backup data X and the full backup data X. The sum of the incremental backup data that is less than or equal to the incremental backup sequence number Y. If the incremental backup sequence number Y is greater than the incremental backup sequence number b, it can be determined that the differential incremental backup data that needs to be restored is equal to X.(b+1 ) to the sum of the incremental backup data corresponding to X.Y (S77).
  • the production device can clear the contents of the first snapshot and then obtain Restore the second state of the target database after the backup data to be restored, and update the first snapshot according to the second state.
  • the second state may include updated configuration information of the target database after restoring the backup data to be restored, updated log information of the target database after restoring the backup data to be restored, and updated data of the target database after restoring the backup data to be restored. information.
  • the recovered data can be used as newly generated restored backup data, snapshot stored through the first snapshot, and the relevant information of the target database in the first snapshot can be updated for subsequent use.
  • data recovery is continued, data recovery is continued on the basis of the restored data based on the updated first snapshot to improve the efficiency of data recovery.
  • the production equipment can also obtain the second state of the target database after restoring the backup data to be restored, and generate a second snapshot according to the second state; where the second snapshot can be used Determine the second state.
  • the second state may also include the updated configuration information of the target database after restoring the backup data to be restored, the updated log information of the target database after restoring the backup data to be restored, and the updated configuration information of the target database after restoring the backup data to be restored. data information.
  • the second snapshot can restore the database entity of the target database to the second state. When the production device queries the second snapshot, the backup data to be restored can also be restored according to the incremental backup data recovery method.
  • the first snapshot corresponding to each restored backup data is not deleted, and the second snapshot corresponding to the currently restored backup data is added directly by adding a new snapshot, so that the subsequent snapshots including the first snapshot and One of the snapshots in the second snapshot is selected, and based on the restored backup data corresponding to the snapshot, the data is restored according to the differential incremental backup data.
  • FIG. 8 is a schematic diagram of a first snapshot update process related to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a target database data recovery process involved in an embodiment of the present application.
  • the full data includes the full backup data and copies of each incremental backup data under the full backup data (S95).
  • step S93 and step S95 you can First clear the Incremental_PRE_SNAP snapshot, then generate an Incremental_PRE_SNAP snapshot (S96) on the storage according to the target database's configuration information, data disk, and log disk, and then execute the "alter database open resetlogs" command to restart the target database.
  • the current backup data that needs to be restored is the full backup data identified as 1; if the recovery time is on the second day, and the last time The restored backup data is the full backup data identified as 1, and the backup data that currently needs to be restored is the incremental backup data identified as 1.1; if the recovery time is on the third day, and the last restored backup data is For the full backup data marked as 1, the current backup data that needs to be restored is the sum of the incremental backup data marked as 1.1 and the incremental backup data marked as 1.2; if the recovery time is on the third day, and the last time has been The restored backup data is the full amount of data corresponding to the incremental backup data identified as 1.1, then the backup data that currently needs to be restored is the incremental backup data identified as 1.2; if the recovery time is on the fourth day, and the last time has been The restored backup data is the full backup data identified as 1, and the current backup data that needs to be restored is the sum of the incremental backup data
  • the target database can be kept at the time when the last data recovery was completed. status, so that you can continue to use incremental backup data for recovery, reducing the network transmission and processing time of the recovered data, thereby shortening the time required for data recovery of the target database.
  • the production equipment can obtain the identifier of the backup data to be restored in the target database, and when the backup data to be restored is incremental backup data, obtain the restored backup data based on the same full backup data. , and when the first snapshot is queried, the backup data to be restored is restored based on the incremental backup data of the difference between the restored backup data and the backup data to be restored. Since the first snapshot that can restore the target database to the state at the recovery time of the restored backup data is queried in advance, it is avoided that a new database entity is generated after the last data recovery, resulting in the inability to identify the database entity of the target database. And continue to perform data recovery on the basis of the restored backup data, realizing the reuse of the restored backup data, thereby improving the efficiency of data recovery.
  • the data recovery device includes at least one of a hardware structure and a software module corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.
  • Embodiments of the present application can divide the data recovery device into functional units according to the above method examples.
  • each functional unit can be divided corresponding to each function, or two or more functions can be integrated into one processing unit.
  • the above integrated units can be implemented in the form of hardware or software functional units. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.
  • FIG. 10 shows a schematic structural diagram of a data recovery device 1000 provided by an exemplary embodiment of the present application.
  • the data recovery device 1000 is used in computing equipment.
  • the data recovery device 1000 includes:
  • the identification acquisition module 1010 is used to obtain the identification of the backup data to be restored of the target database
  • the data acquisition module 1020 is configured to acquire restored backup data when the backup data to be restored is incremental backup data; wherein the restored backup data and the backup data to be restored are backups based on the same full backup data. Data, the backup time of the restored backup data is earlier than the backup time of the backup data to be restored, and the restored backup data is the most recent restored backup time from the backup time of the backup data to be restored. backup data;
  • the data recovery module 1030 is configured to respond to querying the first snapshot and restore the backup data to be restored in an incremental backup data recovery manner; wherein the first snapshot is used to determine the recovery time of the restored backup data.
  • the state of the target database; the recovery method of the incremental backup data is to restore the incremental backup data based on the difference between the backup data to be restored and the restored backup data. How to restore the backup data.
  • the identification acquisition module 1010 can be used to perform step 301 as shown in Figure 3
  • the data acquisition module 1020 can be used to perform step 302 as shown in Figure 3
  • the data recovery module 1030 can be used to perform step 302 as shown in Figure 3. Step 303 shown in 3.
  • the data recovery module 1030 includes:
  • a state restoration sub-module configured to respond to querying the first snapshot and restore the target database to a first state according to the first snapshot; the first state is to use the restored backup data for data recovery.
  • the recovery submodule is configured to use the backup data to be restored to restore the target database in the first state in an incremental backup data recovery manner.
  • the state restoration sub-module can be used to perform step 405 as shown in Figure 4
  • the recovery sub-module can be used to perform step 406 as shown in Figure 4.
  • the recovery submodule includes:
  • An incremental data acquisition unit is used to acquire n incremental backup data between the restored backup data and the backup data to be restored; n steps are taken between the restored backup data and the backup data to be restored.
  • the backup time of data backup; n is an integer greater than or equal to 1;
  • a difference determination unit configured to determine the difference incremental backup data based on the n incremental backup data
  • a recovery unit configured to back up data according to the differential increment, and use the backup data to be restored to restore the target database in the first state.
  • the identification acquisition module 1010 includes:
  • the identification acquisition submodule is used to obtain the identification of the backup data to be restored of the target database from the metadata record information; the metadata record information includes when the backup data is backed up at each of the backup times. The identification of the backup data recorded.
  • the identifier is used to indicate the backup data type and the sequence number corresponding to the backup data type; the backup data type includes full backup data or incremental backup data; the backup The serial numbers corresponding to each data type include full backup serial numbers or incremental backup serial numbers.
  • the incremental data acquisition unit is used to,
  • the incremental backup data corresponding to the incremental backup sequence number that is greater than the restored backup data and the incremental backup sequence number that is less than or equal to the backup data to be restored is determined as the n increments.
  • Backup data; the incremental backup sequence number is determined based on the identification of the backup data to be restored.
  • the device further includes:
  • a type determination module configured to, when the backup data to be restored is incremental backup data, determine the backup data based on the identifier of the backup data to be restored before obtaining the restored backup data based on the identifier of the backup data to be restored.
  • the backup data type of the backup data to be restored, the backup data type includes full backup data or incremental backup data.
  • the type determination module may be used to perform step 402 as shown in Figure 4.
  • the device further includes:
  • the second recovery module is configured to obtain the identification of the backup data to be restored in the target database, and when the backup data to be restored is the full backup data, restore the backup data to be restored according to the full backup data method;
  • the full backup data recovery method is a method of restoring the backup data to be restored based on the full backup data.
  • the second recovery module can be used to perform step 403 as shown in Figure 4.
  • the first snapshot includes configuration information of the target database at the recovery time of the restored backup data, and configuration information of the target database at the recovery time of the restored backup data. Log information and data information of the restored backup data.
  • the device further includes:
  • a clearing module configured to clear the content in the first snapshot after restoring the backup data to be restored according to the incremental backup data recovery method
  • the first acquisition module is used to acquire the second state of the target database after restoring the backup data to be restored;
  • An update module configured to update the first snapshot according to the second state.
  • the device further includes:
  • the second acquisition module is used to obtain the second state of the target database after restoring the backup data to be restored according to the incremental backup data recovery method
  • some or all of the functions implemented by the identification acquisition module 1010 , the data acquisition module 1020 and the data recovery module 1030 in the data recovery device can be executed by the processor 1110 in FIG. 11 and the memory 1120 in FIG. 11 Program code implementation in.
  • FIG 11 shows a schematic structural diagram of a computing device 1100 provided by an exemplary embodiment of the present application.
  • the computing device 1100 may be an electronic device such as a smartphone, a tablet computer, an e-book, a portable personal computer, a smart wearable device, or the like.
  • the computing device 1100 in this application may include one or more of the following components: a processor 1110 and a memory 1120.
  • Processor 1110 may include one or more processing cores.
  • the processor 1110 uses various interfaces and lines to connect various parts of the entire terminal, and executes the terminal by running or executing instructions, programs, code sets or instruction sets stored in the memory 1120, and calling data stored in the memory 1120.
  • Various functions and processing data may use at least one of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA).
  • DSP digital signal processing
  • FPGA field-programmable gate array
  • PDA programmable logic array
  • the processor 1110 may integrate one or a combination of a central processing unit (Central Processing Unit, CPU), an image processor (graphics processing unit, GPU), a modem, etc.
  • CPU central processing unit
  • GPU graphics processing unit
  • modem etc.
  • the CPU mainly handles the operating system, user interface and application programs, etc.; the modem is used to handle wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 1110 and may be implemented solely through a communication chip.
  • the memory 1120 may include random access memory (RAM) or read-only memory (ROM). Optionally, the memory 1120 includes non-transitory computer-readable storage medium. Memory 1120 may be used to store instructions, programs, codes, sets of codes, or sets of instructions.
  • the memory 1120 may include a program storage area and a data storage area, where the program storage area may store instructions for implementing an operating system and instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.) , instructions for implementing each of the above method embodiments, etc.
  • the operating system can be an Android system (including an in-depth development system based on the Android system), an IOS system developed by Apple (including an in-depth development system based on the IOS system) or other systems.
  • the storage data area can also store data created during use of the terminal (such as phone book, audio and video data, chat record data), etc.
  • the structure of the computing device 1100 shown in the above figures does not constitute a limitation on the computing device 1100.
  • the computing device 1100 may include more or fewer components than shown in the figures. Or combining certain parts, or different parts arrangements.
  • the terminal also includes radio frequency circuits, shooting components, sensors, audio circuits, wireless fidelity (WiFi) components, power supplies, Bluetooth components and other components, which will not be described in detail here.
  • WiFi wireless fidelity
  • Embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium stores at least one computer instruction.
  • the at least one computer instruction is loaded and executed by the processor to implement the data described in each of the above embodiments.
  • Recovery methods For explanations of relevant contents and descriptions of beneficial effects in any of the computer-readable storage media provided above, reference may be made to the corresponding embodiments described above and will not be described again here.
  • An embodiment of the present application also provides a chip.
  • the chip integrates a control circuit and one or more ports for realizing the functions of the above data recovery device.
  • the functions supported by this chip can be referred to above and will not be described again here.
  • the program may be stored in a computer-readable storage medium.
  • the storage medium mentioned above may be a read-only memory, a random access memory, etc.
  • the above-mentioned processing unit or processor can be a central processing unit, a general-purpose processor, an application specific integrated circuit (ASIC), a microprocessor (digital signal processor, DSP), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • FPGA field programmable gate array
  • Embodiments of the present application also provide a computer program product containing instructions. When the instructions are run on a computer, they cause the computer to perform any of the methods in the above embodiments.
  • the computer program product includes one or more computer instructions. When computer program instructions are loaded and executed on a computer, processes or functions according to embodiments of the present application are generated in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g., computer instructions may be transmitted from a website, computer, server or data center via a wired (e.g.
  • Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless means to transmit to another website, computer, server or data center.
  • Computer-readable storage media can be any available media that can be accessed by a computer or include one or more data storage devices such as servers and data centers that can be integrated with the media. Available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, SSD), etc.

Abstract

本申请实施例公开了一种数据恢复方法及电子设备，属于数据处理技术领域。该方法包括：获取目标数据库的待恢复备份数据的标识；在待恢复备份数据是增量备份数据时，获取已恢复备份数据；其中，已恢复备份数据与待恢复备份数据是基于同一全量备份数据的备份数据；响应于查询到第一快照，按照增量备份数据恢复方式恢复待恢复备份数据；其中，第一快照用于确定已恢复备份数据的恢复时间时目标数据库的状态；增量备份数据的恢复方式是基于待恢复备份数据与所述已恢复备份数据之间的差异增量备份数据，恢复待恢复备份数据的方式。实现了对已恢复备份数据进行复用，从而提高了数据恢复的效率。

Description

数据恢复方法及电子设备
本申请要求于2022年07月28日提交国家知识产权局、申请号为202210911760.2、申请名称为“数据恢复方法及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本公开涉及数据处理技术领域，特别涉及一种数据恢复方法及电子设备。
背景技术
随着互联网技术的不断发展，企业越来越依赖于数据处理，因此，对数据库的数据保护越来越重要。
为了减小数据丢失或者损坏对数据处理的影响，目前可以针对数据库设置备份系统，通过备份系统可以在各个备份时间窗口，通过差异增量备份的方式对数据库中的数据进行备份。当需要对数据库中的数据进行恢复时，数据库要求执行打开重置日志(open resetlogs)的指令，数据库会新建一个数据库实体(incarnation)，然后，生产设备从备份设备获取备份数据，对进行恢复的时间点之前备份的全部数据进行全量数据恢复，从而实现数据库数据恢复。
然而，上述方案在对数据进行恢复后会新建一个数据库实体，新建的数据库实体不同于之前的数据库实体，从而导致在之后需要再次进行数据恢复时无法在已恢复数据的基础上继续进行数据恢复，进而导致数据恢复的效率较低。
发明内容
本申请实施例提供了一种数据恢复方法及电子设备，可以提高数据恢复的效率。
第一方面，本申请提供了一种数据恢复方法，该方法由生产设备执行，该方法包括：获取目标数据库的待恢复备份数据的标识；在待恢复备份数据是增量备份数据时，获取已恢复备份数据；其中，已恢复备份数据与待恢复备份数据是基于同一全量备份数据的备份数据，已恢复备份数据的备份时间早于待恢复备份数据的备份时间，且已恢复备份数据是备份时间距离待恢复备份数据的备份时间最近一次的已恢复的备份数据；响应于查询到第一快照，按照增量备份数据恢复方式恢复待恢复备份数据；其中，第一快照用于确定已恢复备份数据的恢复时间时目标数据库的状态；增量备份数据的恢复方式是基于待恢复备份数据与已恢复备份数据之间的差异增量备份数据，恢复待恢复备份数据的方式。
可以理解的是，由于该方法通过获取目标数据库的待恢复备份数据的标识，在待恢复备份数据是增量备份数据时，获取基于同一全量备份数据的已恢复备份数据，并且在查询到第一快照的情况下，根据已恢复备份数据与待恢复备份数据之间的差异增量备份数据恢复待恢复备份数据。由于预先查询到可以使目标数据库恢复到已恢复备份数据的恢复时间时的状态的第一快照，避免了在上一次进行数据恢复后生成新的数据库实体，导致的无法识别目标数据库的数据库实体，并在已恢复备份数据的基础上继续进行数据恢复的问题，实现了对已恢复备份数据进行复用，从而提高了数据恢复的效率。
在一种可能的实现方式中，响应于查询到第一快照，按照增量备份数据恢复方式恢复待恢复备份数据，包括：响应于查询到第一快照，按照第一快照将目标数据库还原成第一状态；第一状态是使用已恢复备份数据进行数据恢复后目标数据库的状态；按照增量备份数据恢复方式，采用待恢复备份数据恢复处于第一状态的目标数据库。
可以理解的是，在查询到第一快照后，将目标数据库进行还原后在还原后的目标数据库的基础上进行数据恢复，可以解决数据恢复后数据库配置更新所导致的无法复用已恢复数据的问题。
在另一种可能的实现方式中，按照增量备份数据恢复方式，采用待恢复备份数据恢复处于第一状态的 目标数据库，包括：获取已恢复备份数据与待恢复备份数据之间n个增量备份数据；已恢复备份数据与待恢复备份数据之间经过n个进行数据备份的备份时间；n是大于等于1的整数；基于n个增量备份数据，确定差异增量备份数据；按照差异增量备份数据，恢复处于第一状态的目标数据库的待恢复备份数据。
可以理解的是，通过已恢复备份数据与待恢复备份数据之间的差异增量备份数据，在已恢复备份数据的基础上继续恢复差异增量备份数据，减少了需要恢复的数据量，从而提高了数据恢复的效率。
在另一种可能的实现方式中，获取目标数据库的待恢复备份数据的标识，包括：从元数据记录信息中获取目标数据库的待恢复备份数据的标识；元数据记录信息包括在各个备份时间下对备份数据进行备份时记录的备份数据的标识。
可以理解的是，从元数据记录信息中获取待恢复备份数据的标识，可以便于后续按照待恢复备份数据的标识确定需要恢复的备份数据，从而提高数据恢复效率。
在另一种可能的实现方式中，标识用于指示备份数据类型以及备份数据类型各自对应的序列号；备份数据类型包括全量备份数据或增量备份数据；备份数据类型各自对应的序列号包括全量备份序列号或增量备份序列号。
可以理解的是，以全量备份序列号以及增量备份序列号对备份数据进行标识，方便后续确定需要恢复的备份数据，从而提高数据恢复效率。
在另一种可能的实现方式中，获取已恢复备份数据与待恢复备份数据之间n个增量备份数据，包括：将大于已恢复备份数据的增量备份序列号，以及，小于等于待恢复备份数据的增量备份序列号各自对应的增量备份数据确定为n个增量备份数据；增量备份序列号是基于待恢复备份数据的标识确定的。
可以理解的是，通过增量备份序列号确定需要恢复的备份数据，从而提高数据恢复效率。
在另一种可能的实现方式中，在待恢复备份数据是增量备份数据时，获取已恢复备份数据之前，还包括：基于待恢复备份数据的标识，确定待恢复备份数据的备份数据类型，所述备份数据类型包括全量备份数据或增量备份数据。
可以理解的是，通过待恢复备份数据的标识确定待恢复备份数据的备份数据类型，提高了备份数据类型的确定速度。
在另一种可能的实现方式中，获取目标数据库的待恢复备份数据的标识之后，还包括：在待恢复备份数据是全量备份数据时，按照全量备份数据方式恢复待恢复备份数据；全量备份数据恢复方式是基于全量备份数据恢复待恢复备份数据的方式。
可以理解的是，扩展了待恢复备份数据仅包括全量备份数据的情况。
在另一种可能的实现方式中，第一快照包括在已恢复备份数据的恢复时间时目标数据库的配置信息、在已恢复备份数据的恢复时间时目标数据库的日志信息以及已恢复备份数据的数据信息。
可以理解的是，第一快照中存储上述目标数据库的相关信息，可以便于将目标数据库还原成上一次进行数据恢复后的配置状态，以便对已恢复数据进行复用。
在另一种可能的实现方式中，按照增量备份数据恢复方式恢复待恢复备份数据之后，还包括：清除第一快照中的内容；获取恢复待恢复备份数据后目标数据库的第二状态；按照第二状态，更新第一快照。
可以理解的是，恢复数据后对第一快照进行更新，以便后续再进行数据恢复时，在本次恢复的数据的基础上继续进行数据恢复。
在另一种可能的实现方式中，按照增量备份数据恢复方式恢复待恢复备份数据之后，还包括：
获取恢复待恢复备份数据后目标数据库的第二状态；
按照第二状态，生成第二快照；其中，第二快照用于确定第二状态。
可以理解的是，恢复数据后对第一快照进行添加，以便后续再进行数据恢复时，可以选择在本次恢复的数据的基础上继续进行数据恢复。
第二方面，本申请提供了一种数据恢复装置，本申请可以根据上述第一方面提供的方法，对该数据恢复装置进行功能模块的划分。例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能继承在一个处理模块中。示例性的，本申请可以按照功能将该数据恢复装置划分为标识获取模块、数据获取模块以及数据恢复模块等。上述划分的各个功能模块执行的可能的技术方案和有益效果的描述均可以参考上述第一方面或其相应的可能的实现方式提供的技术方案，此处不再赘述。
第三方面，本申请实施例提供了一种计算设备，计算设备包括处理器和存储器，该存储器用于存储计算机程序指令，该计算机程序指令由处理器加载并执行以使计算设备实现如上述方面所述的数据恢复方法。
第四方面，本申请实施例提供了一种计算机可读存储介质，该计算机可读存储介质中存储有至少一条计算机程序指令，所述计算机程序指令由处理器加载并执行以实现如上述方面所述的数据恢复方法。
第五方面，本申请实施例提供了一种计算机程序产品或计算机程序，该计算机程序产品或计算机程序包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该计算设备执行上述方面的各种可选实现方式中提供的数据恢复方法。
本申请中第二方面到第五方面及其各种实现方式的具体描述，可以参考第一方面及其各种实现方式中的详细描述；并且，第二方面到第五方面及其各种实现方式的有益效果，可以参考第一方面及其各种实现方式中的有益效果分析，此处不再赘述。
本申请的这些方面或其他方面在以下的描述中会更加简明易懂。
附图说明
图1是根据一示例性实施例示出的一种数据管理系统的示意图；
图2是图1所示实施例中涉及的一种差异增量备份示意图；
图3是根据一示例性实施例示出的一种数据恢复方法的流程示意图；
图4是根据一示例性实施例示出的一种数据恢复方法的流程示意图；
图5是图4所示实施例中涉及的一种查询第一快照是否存在的流程示意图；
图6是图4所示实施例中涉及的一种还原数据库的流程示意图；
图7是图4所示实施例中涉及的一种需要恢复的差异增量备份数据的确定流程示意图；
图8是图4所示实施例中涉及的一种第一快照更新流程示意图；
图9是图4所示实施例中涉及的一种目标数据库数据恢复流程示意图；
图10是本申请一个示例性实施例提供的数据恢复装置的结构示意图；
图11是本申请一个示例性实施例提供的计算设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
在本文中提及的“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请后续实施例提供了一种数据恢复的方案，该数据恢复方案可以应用在企业生产、经营、战略等日常运作时需要数据支撑的场景中，企业为了支持信息技术的不断发展，需要保护企业自身的数据资产，企业的重要信息资产一般可以分散在若干个不同的系统中，可以包括核心数据库、客户数据、交易数据以及各类管理数据，在进行数据日常维护的过程中，可能存在数据存储设备损坏、数据被误操作以及数据被 人为破坏等导致数据同时损坏的风险，因此，需要对数据进行备份，并且基于备份数据进行数据恢复以实现对数据库中的数据的保护。请参考图1，图1是本申请实施例涉及的一种数据管理系统的示意图，该数据管理系统中包括生产系统110以及备份系统120。生产系统110中包括数据库111、备份代理组件112、操作系统113以及生产存储组件114。备份系统120包括备份服务组件121以及备份存储组件122。
其中，数据管理系统中可以包括备份设备以及生产设备，生产设备在生产系统110中，备份设备在备份系统120中。生产设备可以是计算设备，备份设备同样可以是计算设备，生产设备与备份设备可以是不同的计算设备，也可以是同一计算设备，在此不作限制。计算设备可以是智能手机、平板电脑、电子书阅读器、个人便携式计算机、服务器等。
可选的，生产存储组件114可以是具有快照生成功能的组件，备份代理组件112可以是安装在生产设备上的插件。备份存储组件122中可以存储有备份数据。备份服务组件121与备份代理组件112可以通过通信网络相连，备份代理组件112将备份数据可以通过通信网络传输给备份服务组件121，备份服务组件121将备份数据发送给备份存储组件122，对备份数据进行存储。
在一种可能的实现方式中，生产系统与备份系统可以通过通信网络相连。可选的，通信网络是有线网络或无线网络。
可选的，上述的无线网络或有线网络使用标准通信技术和/或协议。网络通常为因特网、但也可以是任何网络，包括但不限于局域网(local area network，LAN)、城域网(metropolitan area network，MAN)、广域网(wide area network，WAN)、移动、有线或者无线网络、专用网络或者虚拟专用网络的任何组合。在一些实施例中，使用包括超文本标记语言(hyper text mark-up language，HTML)、可扩展标记语言(extensible markup language，XML)等的技术和/或格式来代表通过网络交换的数据。此外还可以使用诸如安全套接字层(secure socket layer，SSL)、传输层安全(transport layer security，TLS)、虚拟专用网络(virtual private network，VPN)、网际协议安全(internet protocol security，IPsec)等常规加密技术来加密所有或者一些链路。在另一些实施例中，还可以使用定制和/或专用数据通信技术取代或者补充上述数据通信技术。
示例性的，计算设备可以通过差异增量备份的方式进行数据备份，差异增量备份的方式中每次进行数据备份是将上一次备份结果到本次备份时的差异数据进行备份。
图2是本申请实施例涉及的一种差异增量备份示意图。如图2所示，在第一天的备份时间计算设备可以进行全量备份，在第二天的备份时间计算设备可以进行差异增量备份，在第三天的备份时间计算设备可以同样进行差异增量备份，在第四天的备份时间计算设备仍然进行差异增量备份，在第五天的备份时间时，可以对数据进行全量备份。
其中，第一天的备份时间可以是开始进行数据备份的时间，第二天到第四天的备份时间可以是日常快速对数据进行差异增量备份的时间，第五天的备份时间可以是空闲时刻(如，周末)对数据进行完整的全量备份的时间。
第一天的全量备份数据是第一天的备份时间的全量数据，第二天差异增量备份数据是第二天备份时间处已备份的全量数据与第一天备份时间处已备份的全量数据之间的差异备份数据，第三天的差异增量备份数据是第三天备份时间处已备份的全量数据与第二天备份时间处已备份的全量数据之间的差异备份数据，第四天差异增量备份数据是第四天备份时间处已备份的全量数据与第三天备份时间处已备份的全量数据之间的差异备份数据，第五天的全量备份数据是第五天的备份时间已备份的全量数据。
比如，在第一天的备份时间进行数据备份可以是进行全量数据备份，此时的全量数据包括数据a、数据b以及数据c；第二天的备份时间进行数据备份是进行差异增量备份，若此时的数据a变为数据d，则第二天的备份时间进行数据备份是仅备份数据a变为数据d；第三天的备份时间进行数据备份是进行差异增量备份，若此时的数据d变为数据e，则第三天的备份时间进行数据备份是仅备份数据d变为数据e；第四天的备份时间进行数据备份是进行差异增量备份，若此时的数据b变为数据f，则第四天的备份时间进行 数据备份是仅备份数据b变为数据f；在第五天的备份时间进行数据备份可以是进行全量数据备份，此时的全量数据包括数据e、数据f以及数据c。
图3示出了本申请一个示例性实施例提供的数据恢复方法的流程示意图。其中，该数据恢复方法可以由计算设备执行，比如，该计算设备可以是图1所示的数据管理系统中的生产设备。该数据恢复确定方法包括如下步骤：
步骤301，获取目标数据库的待恢复备份数据的标识。
在本申请实施例中，当生产设备的目标数据库的数据需要进行数据恢复时，生产设备可以获取目标数据库的待恢复备份数据的标识。
其中，待恢复备份数据可以是目标数据库中需要进行数据恢复的数据对应的备份数据，该备份数据对应有标识，用于指示该备份数据的数据内容。
在一种可能的实现方式中，生产设备在日常进行数据生产时，可以实时将生产的数据存储在目标数据库中，目标数据库的数据可以在各个备份时间进行备份处理，将备份数据传输并存储在备份设备中，以供生产设备在需要进行对应的数据恢复时从备份设备中获取。
其中，目标数据库可以是关系型数据库或者内存数据库。
步骤302，在待恢复备份数据是增量备份数据时，获取已恢复备份数据；其中，已恢复备份数据与待恢复备份数据是基于同一全量备份数据的备份数据，已恢复备份数据的备份时间早于待恢复备份数据的备份时间，且已恢复备份数据是备份时间距离待恢复备份数据的备份时间最近一次的已恢复的备份数据。
在本申请实施例中，生产设备确定待恢复备份数据是否为增量备份数据，当确定待恢复数据为增量备份数据时，可以根据获取到的待恢复备份数据的标识，获取备份时间早于待恢复备份数据的备份时间且距离最近的，并且基于同一全量备份数据进行备份的已恢复备份数据。
在一种可能的实现方式中，已恢复备份数据可以是全量备份数据，也可以是增量备份数据。
其中，为了提高通过复用已恢复备份数据，在已恢复备份数据的基础上继续进行数据恢复的效果，可以基于目标数据库的日志内容获取距离待恢复备份数据最近的已恢复备份数据，并进行后续步骤。目标数据库的日志内容中记录有最近一次进行恢复的备份数据。
在一种可能的实现方式中，当待恢复备份数据是增量备份数据时，由于各个备份数据在进行数据备份的过程中可以按照先后顺序进行标识，可以按照待恢复备份数据的标识确定备份时间早于待恢复备份数据的备份时间的，且基于同一全量备份数据的最近一次的备份数据获取为已恢复备份数据。
步骤303，响应于查询到第一快照，按照增量备份数据恢复方式恢复待恢复备份数据；其中，第一快照用于确定已恢复备份数据的恢复时间时目标数据库的状态；增量备份数据的恢复方式是基于待恢复备份数据与已恢复备份数据之间的差异增量备份数据，恢复待恢复备份数据的方式。
在本申请实施例中，生产设备在获取到已恢复备份数据后，可以开始查询是否存在第一快照，若查询到第一快照，则可以根据待恢复备份数据与已恢复备份数据之间的差异增量备份数据恢复待恢复备份数据。
在一种可能的实现方式中，第一快照可以是生产设备在进行数据恢复后生成的存储快照。
其中，第一快照可以是最近一次进行数据恢复后生成的存储快照，也可以是每次进行数据恢复后各自生成的存储快照。
在一种可能的实现方式中，已恢复备份数据的恢复时间时目标数据库的状态可以用于指示目标数据库在对已恢复备份数据进行数据恢复后新生成的数据库实体中包含的恢复后的数据、数据库的系统改变号以及数据库日志号。
其中，数据库管理系统中可以存在各种用于数据管理方便而设定的各种数据管理对象，该数据管理对象可以是数据库实体。
比如，数据库实体可以是数据库表、视图、存储过程、各种数据管理对象中所存储的数据。
综上所述，在本申请实施例中，生产设备可以通过获取目标数据库的待恢复备份数据的标识，在待恢复备份数据是增量备份数据时，获取基于同一全量备份数据的最近一次的已恢复备份数据，并且在查询到第一快照的情况下，根据已恢复备份数据与待恢复备份数据之间的差异增量备份数据恢复待恢复备份数据。由于预先查询到可以使目标数据库恢复到已恢复备份数据的恢复时间时的状态的第一快照，避免了在上一次进行数据恢复后生成新的数据库实体，导致的无法识别目标数据库的数据库实体，并在已恢复备份数据的基础上继续进行数据恢复的问题，实现了对已恢复备份数据进行复用，从而提高了数据恢复的效率。
图4示出了本申请一个示例性实施例提供的数据恢复方法的流程示意图。其中，该数据恢复方法可以由计算设备执行，比如，该计算设备可以是图1所示的数据管理系统中的生产设备。该数据恢复方法包括如下步骤：
步骤401，获取目标数据库的待恢复备份数据的标识。
在本申请实施例中，生产设备获取目标数据库中需要恢复的数据对应的待恢复备份数据的标识。
在一种可能的实现方式中，生产设备可以从元数据记录信息中获取目标数据库的待恢复备份数据的标识。
其中，元数据记录信息包括在各个备份时间下对备份数据进行备份时记录的备份数据的标识。
示例性的，当生产设备生产数据的过程中，可以同步对生产设备生产的数据进行备份，同时进行备份的数据可以以标识的形式进行记录，生成包含各个备份数据的标识的元数据记录信息。
在一种可能的实现方式中，标识用于指示备份数据类型以及备份数据类型各自对应的序列号；备份数据类型包括全量备份数据或增量备份数据；备份数据类型各自对应的序列号包括全量备份序列号或增量备份序列号。
也就是说，通过获取元数据记录信息，可以得到各个备份时间下的备份数据的备份数据类型，即各个备份时间下的备份数据时全量备份数据还是增量备份数据；若得到该备份时间下的备份数据的备份数据类型是全量备份数据，还可以得到该备份时间下的全量备份数据所属的序列号，若得到该备份时间下的备份数据的备份数据类型是增量备份数据，还可以得到该备份时间下的增量备份数据所属的全量备份数据的序列号，以及在该全量备份数据下该增量备份数据所属的序列号。
比如，若在备份时间进行全量备份，则在该备份时间下记录全量备份数据对应的全量备份序列号。若在备份时间进行增量备份，则在该备份时间下记录上一次进行全量备份的全量备份序列号以及在该全量备份下的增量备份序列号，可以记为“全量备份序列号”+“.”+“增量备份序列号”。若按照如图2所示的备份时间进行数据备份，则元数据记录信息可以包括如下表1所示的内容。
表1
步骤402，基于待恢复备份数据的标识，确定待恢复备份数据的备份数据类型。
在本申请实施例中，生产设备可以根据获取到的待恢复备份数据的标识，确定该待恢复备份数据的备份数据类型，即确定该待恢复备份数据是全量备份数据，还是在某一全量备份数据下的增量备份数据，备 份数据类型可以包括全量备份数据或增量备份数据。
由于生产设备可以根据待恢复备份数据的备份数据类型，确定后续恢复数据的方式，所以需要根据获取到的待恢复备份数据的标识，确定待恢复备份数据所属的备份数据类型。
比如，若元数据记录信息中包含的内容如表1所示，待恢复备份数据是需要通过在第三天的备份时间进行数据备份后的备份数据进行数据恢复，根据第三天的备份时间处的备份序列号1.2，可以确定待恢复备份数据的备份数据类型是增量备份数据。若待恢复备份数据是需要通过在第五天的备份时间进行数据备份后的备份数据进行数据恢复，根据第五天的备份时间处的备份序列号2，可以确定待恢复备份数据的备份数据类型是全量备份数据。
步骤403，在待恢复备份数据是全量备份数据时，按照全量备份数据恢复方式恢复待恢复备份数据。
在本申请实施例中，当通过获取待恢复备份数据的标识，确定待恢复备份数据的备份数据类型是全量备份数据，则可以按照全量备份数据恢复待恢复备份数据。
其中，全量备份数据恢复方式是基于全量备份数据恢复待恢复备份数据的方式。
也就是说，当待恢复备份数据对应的备份时间下，刚好通过全量备份的方式进行数据备份，则在此时由于可以获取到全量备份数据，无需在其他已恢复备份数据的基础上继续进行数据恢复，所以可以直接按照全量备份数据恢复待恢复备份数据。
由于已恢复备份数据与待恢复备份数据是基于不同全量备份数据的备份数据，所以无需基于第一已恢复备份数据进行复用，可以直接按照全量数据进行数据恢复。
步骤404，在待恢复备份数据是增量备份数据时，获取已恢复备份数据。
在本申请实施例中，当通过获取待恢复备份数据的标识，确定待恢复备份数据的备份数据类型是增量备份数据，则可以确定已恢复备份数据，并且获取已恢复备份数据。
其中，已恢复备份数据与待恢复备份数据可以是基于同一全量备份数据的备份数据，已恢复备份数据的备份时间早于待恢复备份数据的备份时间。
也就是说，确定待恢复备份数据不属于仅包含全量备份数据的情况时，通过待恢复备份数据的标识确定该待恢复备份数据中包含的全量备份数据，确定包含同一全量备份数据，且备份时间早于待恢复备份数据的备份时间的备份数据中是否存在已恢复备份数据，若存在符合条件的已恢复备份数据，则可以获取该已恢复备份数据。
在一种可能的实现方式中，在确定已恢复备份数据时，可以查询到存在一个或者多个符合条件的已恢复备份数据，可以获取各个已恢复备份数据。
示例性的，若元数据记录信息中包含的内容如表1所示，待恢复备份数据是需要通过在第三天的备份时间进行数据备份后的备份数据进行数据恢复，根据第三天的备份时间处的备份序列号1.2可以确定该待恢复备份数据包含的全量备份数据是全量备份数据1，同时根据第三天的备份时间处的备份序列号1.2可以确定早于该待恢复备份数据的备份时间是第二天的备份时间，对应的备份序列号1.1，若确定在备份序列号1.1对应的备份时间，已进行过数据恢复，则获取备份序列号1.1对应的备份时间处的已恢复备份数据。若待恢复备份数据是需要通过在第四天的备份时间进行数据备份后的备份数据进行数据恢复，根据第四天的备份时间处的备份序列号1.3可以确定该待恢复备份数据包含的全量备份数据是全量备份数据1，同时根据第四天的备份时间处的备份序列号1.3可以确定早于该待恢复备份数据的备份时间是第二天的备份时间，对应的备份序列号是1.1和1.2，若确定在备份序列号1.1对应的备份时间以及备份序列号1.2对应的备份时间，均已进行过数据恢复，则获取备份序列号1.1对应的备份时间处的已恢复备份数据以及备份序列号1.2对应的备份时间处的已恢复备份数据。
步骤405，响应于查询到第一快照，按照第一快照将目标数据库还原成第一状态。
在本申请实施例中，生产设备查询是否存在第一快照，若查询到存在第一快照，则生产设备可以按照 第一快照中的内容将目标数据库还原成第一状态。
其中，第一状态可以是使用已恢复备份数据进行数据恢复后目标数据库的状态。第一快照可以用于确定已恢复备份数据的恢复时间时目标数据库的状态。
在一种可能的实现方式中，第一快照可以包括在已恢复备份数据的恢复时间时目标数据库的配置信息、在已恢复备份数据的恢复时间时目标数据库的日志信息以及已恢复备份数据的数据信息。
其中，目标数据库的配置信息可以包括系统改变号(system change number，SCN)、域名系统(domain name system，DNS)连接字符串、数据库主机名等信息；目标数据库的日志信息可以包括数据库的日志号，目标数据库的日志信息用于记录对目标数据库的操作信息；已恢复备份数据的数据信息可以包括已恢复备份数据的存储地址信息、已恢复备份数据的结束时间节点信息等。
由于在进行数据恢复后，目标数据库需要新建一个数据库实体(incarnation)，恢复后的数据是在该新建的数据库实体中的，该新建的目标数据库的数据库实体与进行数据恢复之前的目标数据库属于不同的数据库，也就是说，新建的目标数据库的数据库实体与进行数据恢复之前的目标数据库各自对应的数据库的日志号、系统改变号等均是不同的，从而导致下一次进行数据恢复时，无法复用已恢复的备份数据，从而导致每次使用备份数据进行数据恢复时都只能按照全量数据恢复，比如，按照所需要进行数据恢复的时间点之前产生的最近一个全量备份数据与从最近一个全量备份数据后产生的所有增量备份数据所组成的全量数据进行数据恢复。通过将之前已恢复备份数据对应的新建的目标数据库更新后的数据库日志号以及SCN等使用第一快照进行存储，可以在再次需要进行数据恢复时，将目标数据库还原成之前已恢复备份数据对应的更新后的目标数据库，从而实现对已恢复备份数据的复用。
在一种可能的实现方式中，生产设备通过第一快照的快照名称查询是否存在第一快照，若查询到存在第一快照，返回确定指令，若查询到不存在第一快照，则返回否定指令，当接收到确定指令时，可以通过接口调用第一快照执行第一快照恢复。
比如，第一快照的快照名称可以是Incremental_PRE_SNAP。
在另一种可能的实现方式中，在第一已恢复备份数据与待恢复备份数据是基于不同全量备份数据的备份数据时，可以按照全量数据恢复方式恢复待恢复备份数据。第一已恢复备份数据是备份时间早于待恢复备份数据的备份时间且距离待恢复备份数据的备份时间最近一次的已经恢复的备份数据。
其中，当第一已恢复备份数据与待恢复备份数据是基于不同的全量备份数据的备份数据时，可以基于待恢复备份数据的全量备份数据、在全量备份数据下的待恢复备份数据处的增量备份数据，以及，在全量备份数据下的待恢复备份数据之前的各个增量备份数据恢复待恢复备份数据。
比如，若待恢复备份数据的备份时间对应的备份标识是1.4，则全量备份数据恢复方式是基于标识为1的全量备份数据、标识为1.4的增量备份数据以及标识为小于1.4的1.1、1.2、1.3各自对应的增量备份数据恢复待恢复备份数据的方式。
示例性的，图5是本申请实施例涉及的一种查询第一快照是否存在的流程示意图。以第一快照的快照名称是Incremental_PRE_SNAP为例，如图5所示，首先通过存储用户名、以及对应密码可以通过存储系统接口登录存储系统(S51)，以获得查询第一快照的权限，然后通过存储系统用接口查询快照名称为“Incremental_PRE_SNAP”的快照信息(S52)，判断快照Incremental_PRE_SNAP是否存在(S53)，若存在则返回True进行响应，若不存在则返回False进行响应。
然后，图6是本申请实施例涉及的一种还原数据库的流程示意图。以第一快照的快照名称是Incremental_PRE_SNAP为例，如图6所示，首先通过存储用户名、以及对应密码可以通过存储系统接口登录存储系统(S61)，以获得调用第一快照的权限，然后通过存储系统接口对快照名称为“Incremental_PRE_SNAP”的快照执行快照恢复(S62)。
在一种可能的实现方式中，第一快照还可以是由数据库的配置、数据文件以及日志文件存储的文件系 统按照快照功能，生成的存储快照。
步骤406，按照增量备份数据恢复方式，恢复处于第一状态的目标数据库的待恢复备份数据。
在本申请实施例中，生产设备可以按照增量备份数据恢复方式，按照顺序恢复处于第一状态的目标数据库的待恢复备份数据。
其中，增量备份数据的恢复方式可以是基于待恢复备份数据与已恢复备份数据之间的差异增量备份数据，恢复待恢复备份数据的方式。
在一种可能的实现方式中，获取已恢复备份数据与待恢复备份数据之间n个增量备份数据；已恢复备份数据与待恢复备份数据之间经过n个进行数据备份的备份时间；n是大于等于1的整数；然后，基于n个增量备份数据，确定差异增量备份数据；按照差异增量备份数据，恢复处于第一状态的目标数据库的待恢复备份数据。
其中，由于已恢复备份数据与待恢复备份数据是基于同一全量备份数据的备份数据，在可以对已恢复备份数据进行复用的情况下，仅需获取已恢复备份数据与待恢复备份数据之间差异的n个增量备份数据，从而确定差异增量备份数据，并且按照差异增量备份数据在已恢复备份数据的基础上恢复处于第一状态下的目标数据库的数据。
示例性的，若确定已恢复备份数据是在第二天的备份时间处恢复的增量备份数据，待恢复备份数据是需要恢复第四天的备份时间处的增量备份数据，则可以确定已恢复备份数据与待恢复备份数据之间差异的2个增量备份数据，按照差异的2个增量备份数据恢复处于第一状态下的目标数据库的数据。
在一种可能的实现方式中，生产设备还可以根据标识确定作为差异增量备份数据的n个增量备份数据。
也就是说，可以将大于已恢复备份数据的增量备份序列号，以及，小于等于待恢复备份数据的增量备份序列号各自对应的增量备份数据确定为n个增量备份数据，增量备份序列号可以是基于待恢复备份数据的标识确定的。
示例性的，如表1所示，若确定已恢复备份数据是在第二天的备份时间处恢复的增量备份数据，对应的标识是1.1，待恢复备份数据是需要恢复的第四天的备份时间处的增量备份数据，对应的标识是1.3，则可以确定已恢复备份数据与待恢复备份数据之间差异的2个增量备份数据是标识为1.2以及标识为1.3的增量备份数据，可以按照标识为1.2以及标识为1.3的增量备份数据恢复处于第一状态下的目标数据库的数据。
示例性的，图7是本申请实施例涉及的一种需要恢复的差异增量备份数据的确定流程示意图。如图7所示，首先生产设备解析当前需要恢复时间点的最近的备份数据对应的序列号，解析出全量备份序列号X以及增量备份序列号Y(S71)，判断该待恢复备份数据是否为全量备份数据(S72)，若判断确定是全量备份数据，则直接将全量备份数据确定为需要进行恢复的备份数据，若判断确定不是全量备份数据，则可以解析上一次恢复的备份数据的全量备份序列号和增量备份序列号(S73)，比如，已恢复备份数据的序列号是1.2，则全量备份序列号为1，增量备份序列号为2。上一次恢复的备份数据的序列号可以是a.b，然后判断待恢复备份数据的全量备份序列号X与上一次已恢复备份数据的全量备份序列号a是否相等(S74)，若待恢复备份数据的全量备份序列号X与上一次已恢复备份数据的全量备份序列号a不相等，则可以确定需要恢复的差异增量备份数据等于全量备份数据X与全量备份数据X下的小于等于增量备份序列号Y的各个增量备份数据之和(S75)，若待恢复备份数据的全量备份序列号X与上一次已恢复备份数据的全量备份序列号a相等，则继续判断增量备份序列号Y是否大于增量备份序列号b(S76)，若增量备份序列号Y小于等于增量备份序列号b，则可以确定需要恢复的差异增量备份数据等于全量备份数据X与全量备份数据X下的小于等于增量备份序列号Y的各个增量备份数据之和，若增量备份序列号Y大于增量备份序列号b，则可以确定需要恢复的差异增量备份数据等于X.(b+1)到X.Y各自对应的增量备份数据之和(S77)。
在一种可能的实现方式中，在进行数据恢复之后，生产设备可以清除第一快照中的内容，然后，获取 恢复待恢复备份数据后目标数据库的第二状态，按照第二状态，更新第一快照。
第二状态中可以包括恢复待恢复备份数据后目标数据库的更新后的配置信息、恢复待恢复备份数据后目标数据库的更新后的日志信息以及恢复待恢复备份数据后的目标数据库的更新后的数据信息。
也就是说，在进行数据恢复后，可以将恢复后的数据作为新生成的已恢复备份数据，通过第一快照进行快照存储，并且对第一快照中的目标数据库的相关信息进行更新，以便后续继续进行数据恢复时，基于更新后的第一快照，在已恢复的数据的基础上继续进行数据恢复，以提高数据恢复的效率。
在另一种可能的实现方式中，在进行数据恢复之后，生产设备还可以获取恢复待恢复备份数据后目标数据库的第二状态，按照第二状态生成第二快照；其中第二快照可以用于确定第二状态。
其中，第二状态同样可以包括恢复待恢复备份数据后目标数据库的更新后的配置信息、恢复待恢复备份数据后目标数据库的更新后的日志信息以及恢复待恢复备份数据后的目标数据库的更新后的数据信息。第二快照可以将目标数据库的数据库实体恢复到第二状态，当生产设备查询到第二快照时，同样可以按照增量备份数据恢复方式恢复待恢复备份数据。
也就是说，之前各个已恢复备份数据各自对应的第一快照不进行删除，直接通过新增快照的方式，增加当前已恢复备份数据对应的第二快照，以实现后续可以从包括第一快照以及第二快照的各个快照中选取一个，以快照各自对应的已恢复备份数据为基础，按照差异增量备份数据进行数据恢复。
比如，图8是本申请实施例涉及的一种第一快照更新流程示意图。如图8所示，首先通过存储用户名、以及对应密码可以通过存储系统接口登录存储系统(S81)，以获得更改、删除或者添加第一快照的权限，然后通过存储系统接口删除快照名称为“Incremental_PRE_SNAP”的第一快照(S82)，通过存储系统接口按照目标数据库的配置信息、数据盘以及日志盘在存储上生成名称为Incremental_PRE_SNAP的第一快照(S83)。
示例性的，图9是本申请实施例涉及的一种目标数据库数据恢复流程示意图。如图9所示，首先，检查Incremental_PRE_SNAP快照是否存在(S91)，然后，若存在Incremental_PRE_SNAP快照，开始检查元数据记录信息，查找是否存在恢复副本元数据，查找需要恢复的增量备份数据的副本(S92)，若存在恢复副本元数据，则可以使用Incremental_PRE_SNAP快照还原目标数据库(S93)，然后使用差异增量备份数据副本恢复目标数据库的数据(S94)；若不存在恢复副本元数据或者通过步骤S91确定不存在Incremental_PRE_SNAP快照，则可以按照全量数据恢复目标数据库的数据，该全量数据包括全量备份数据以及全量备份数据下的各个增量备份数据的副本(S95)，在步骤S93后以及步骤S95后可以先清除Incremental_PRE_SNAP快照，然后按照目标数据库的配置信息、数据盘以及日志盘在存储上生成Incremental_PRE_SNAP快照(S96)，然后执行“alter database open resetlogs”命令，重启目标数据库。
示例性的，按照本申请实施例所示的方案进行数据恢复，在各个恢复时间下进行数据恢复需要恢复的备份数据副本如下表2所示。
表2

其中，若恢复时间是在第一天，且不存在上一次已恢复的数据，则当前需要进行恢复的备份数据是标识为1的全量备份数据；若恢复时间是在第二天，且上一次已恢复的备份数据是标识为1的全量备份数据，则当前需要进行恢复的备份数据是标识为1.1的增量备份数据；若恢复时间是在第三天，且上一次已恢复的备份数据是标识为1的全量备份数据，则当前需要进行恢复的备份数据是标识为1.1的增量备份数据与标识为1.2的增量备份数据之和；若恢复时间是在第三天，且上一次已恢复的备份数据是标识为1.1的增量备份数据处对应的全量数据，则当前需要进行恢复的备份数据是标识为1.2的增量备份数据；若恢复时间是在第四天，且上一次已恢复的备份数据是标识为1的全量备份数据，则当前需要进行恢复的备份数据是标识为1.1的增量备份数据、标识为1.2的增量备份数据与标识为1.3的增量备份数据之和，后续需要进行恢复的备份数据的确定方法可以以此类推。
也就是说，通过结合存储快照，即第一快照的方式来恢复目标数据库到执行“open resetlogs”指令之前的状态，或者目标数据库修改之前的状态，可以使目标数据库保持在上一次数据恢复完成时的状态，从而可以继续使用增量备份数据进行恢复，减少已恢复数据的网络传输和处理时间，从而缩短目标数据库的数据恢复所需时间。
综上所述，在本申请实施例中，生产设备可以通过获取目标数据库的待恢复备份数据的标识，在待恢复备份数据是增量备份数据时，获取基于同一全量备份数据的已恢复备份数据，并且在查询到第一快照的情况下，根据已恢复备份数据与待恢复备份数据之间的差异增量备份数据恢复待恢复备份数据。由于预先查询到可以使目标数据库恢复到已恢复备份数据的恢复时间时的状态的第一快照，避免了在上一次进行数据恢复后生成新的数据库实体，导致的无法识别目标数据库的数据库实体，并在已恢复备份数据的基础上继续进行数据恢复的问题，实现了对已恢复备份数据进行复用，从而提高了数据恢复的效率。
上述主要从方法的角度对本申请实施例的方案进行了介绍。可以理解的是，数据恢复装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和软件模块中的至少一个。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对数据恢复装置进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
示例性的，图10示出了本申请一个示例性实施例提供的数据恢复装置1000的结构示意图。该数据恢复装置1000应用于计算设备中，该数据恢复装置1000包括：
标识获取模块1010，用于获取目标数据库的待恢复备份数据的标识；
数据获取模块1020，用于在所述待恢复备份数据是增量备份数据时，获取已恢复备份数据；其中，所述已恢复备份数据与所述待恢复备份数据是基于同一全量备份数据的备份数据，所述已恢复备份数据的备份时间早于所述待恢复备份数据的备份时间，且所述已恢复备份数据是所述备份时间距离所述待恢复备份数据的备份时间最近一次的已恢复的备份数据；
数据恢复模块1030，用于响应于查询到第一快照，按照增量备份数据恢复方式恢复所述待恢复备份数据；其中，所述第一快照用于确定所述已恢复备份数据的恢复时间时所述目标数据库的状态；所述增量备份数据的恢复方式是基于所述待恢复备份数据与所述已恢复备份数据之间的差异增量备份数据，恢复所述 待恢复备份数据的方式。
例如，结合图3，标识获取模块1010可以用于执行如图3所示的步骤301，数据获取模块1020可以用于执行如图3所示的步骤302，数据恢复模块1030可以用于执行如图3所示的步骤303。
在一种可能的实现方式中，所述数据恢复模块1030，包括：
状态还原子模块，用于响应于查询到所述第一快照，按照所述第一快照将所述目标数据库还原成第一状态；所述第一状态是使用所述已恢复备份数据进行数据恢复后所述目标数据库的状态；
恢复子模块，用于按照增量备份数据恢复方式，采用所述待恢复备份数据恢复处于所述第一状态的所述目标数据库。
例如，结合图4，状态还原子模块可以用于执行如图4所示的步骤405，恢复子模块可以用于执行如图4所示的步骤406。
在一种可能的实现方式中，所述恢复子模块，包括：
增量数据获取单元，用于获取所述已恢复备份数据与所述待恢复备份数据之间n个增量备份数据；所述已恢复备份数据与所述待恢复备份数据之间经过n个进行数据备份的备份时间；所述n是大于等于1的整数；
差异确定单元，用于基于所述n个增量备份数据，确定所述差异增量备份数据；
恢复单元，用于按照所述差异增量备份数据，采用所述待恢复备份数据恢复处于所述第一状态的所述目标数据库。
在一种可能的实现方式中，所述标识获取模块1010，包括：
标识获取子模块，用于从元数据记录信息中获取所述目标数据库的所述待恢复备份数据的标识；所述元数据记录信息包括在各个所述备份时间下对所述备份数据进行备份时记录的所述备份数据的标识。
在一种可能的实现方式中，所述标识用于指示所述备份数据类型以及所述备份数据类型各自对应的序列号；所述备份数据类型包括全量备份数据或增量备份数据；所述备份数据类型各自对应的序列号包括全量备份序列号或增量备份序列号。
在一种可能的实现方式中，所述增量数据获取单元，用于，
将大于所述已恢复备份数据的增量备份序列号，以及，小于等于所述待恢复备份数据的所述增量备份序列号各自对应的所述增量备份数据确定为所述n个增量备份数据；所述增量备份序列号是基于所述待恢复备份数据的标识确定的。
在一种可能的实现方式中，所述装置还包括：
类型确定模块，用于在所述待恢复备份数据是增量备份数据时，根据所述待恢复备份数据的标识，获取已恢复备份数据之前，基于所述待恢复备份数据的标识，确定所述待恢复备份数据的所述备份数据类型，所述备份数据类型包括全量备份数据或增量备份数据。
例如，结合图4，类型确定模块可以用于执行如图4所示的步骤402。
在一种可能的实现方式中，所述装置还包括：
第二恢复模块，用于获取目标数据库的待恢复备份数据的标识之后，在所述待恢复备份数据是所述全量备份数据时，按照所述全量备份数据方式恢复所述待恢复备份数据；所述全量备份数据恢复方式是基于所述全量备份数据恢复所述待恢复备份数据的方式。
例如，结合图4，第二恢复模块可以用于执行如图4所示的步骤403。
在一种可能的实现方式中，所述第一快照包括在所述已恢复备份数据的恢复时间时所述目标数据库的配置信息、在所述已恢复备份数据的恢复时间时所述目标数据库的日志信息以及所述已恢复备份数据的数据信息。
在一种可能的实现方式中，所述装置还包括：
清除模块，用于按照增量备份数据恢复方式恢复所述待恢复备份数据之后，清除所述第一快照中的内容；
第一获取模块，用于获取恢复所述待恢复备份数据后所述目标数据库的第二状态；
更新模块，用于按照所述第二状态，更新所述第一快照。
在一种可能的实现方式中，所述装置还包括：
第二获取模块，用于按照增量备份数据恢复方式恢复所述待恢复备份数据之后，获取恢复所述待恢复备份数据后所述目标数据库的第二状态；
添加模块，用于按照所述第二状态，生成所述第二快照；其中，所述第二快照用于确定所述第二状态。
关于上述可选方式的具体描述可以参见前述的方法实施例，此处不再赘述。此外，上述提供的任一种数据恢复装置的解释以及有益效果的描述均可参考上述对应的方法实施例，不再赘述。
作为示例，结合图11，数据恢复装置中的标识获取模块1010、数据获取模块1020和数据恢复模块1030中的部分或全部实现的功能可以通过图11中的处理器1110执行图11中的存储器1120中的程序代码实现。
图11示出了本申请一个示例性实施例提供的计算设备1100的结构示意图。该计算设备1100可以是智能手机、平板电脑、电子书、便携式个人计算机、智能穿戴设备等电子设备。本申请中的计算设备1100可以包括一个或多个如下部件：处理器1110以及存储器1120。
处理器1110可以包括一个或者多个处理核心。处理器1110利用各种接口和线路连接整个终端内的各个部分，通过运行或执行存储在存储器1120内的指令、程序、代码集或指令集，以及调用存储在存储器1120内的数据，执行终端的各种功能和处理数据。可选地，处理器1110可以采用数字信号处理(digital signal processing，DSP)、现场可编程门阵列(field－programmable gate array，FPGA)、可编程逻辑阵列(programmable logic array，PLA)中的至少一种硬件形式来实现。处理器1110可集成中央处理器(Central Processing Unit，CPU)、图像处理器(graphics processing unit，GPU)和调制解调器等中的一种或几种的组合。其中，CPU主要处理操作系统、用户界面和应用程序等；调制解调器用于处理无线通信。可以理解的是，上述调制解调器也可以不集成到处理器1110中，单独通过一块通信芯片进行实现。
存储器1120可以包括随机存储器(random access memory，RAM)，也可以包括只读存储器(read-only memory，ROM)。可选地，该存储器1120包括非瞬时性计算机可读介质(non-transitory computer-readable storage medium)。存储器1120可用于存储指令、程序、代码、代码集或指令集。存储器1120可包括存储程序区和存储数据区，其中，存储程序区可存储用于实现操作系统的指令、用于实现至少一个功能的指令(比如触控功能、声音播放功能、图像播放功能等)、用于实现上述各个方法实施例的指令等，该操作系统可以是安卓(Android)系统(包括基于Android系统深度开发的系统)、苹果公司开发的IOS系统(包括基于IOS系统深度开发的系统)或其它系统。存储数据区还可以存储终端在使用中所创建的数据(比如电话本、音视频数据、聊天记录数据)等。
除此之外，本领域技术人员可以理解，上述附图所示出的计算设备1100的结构并不构成对计算设备1100的限定，计算设备1100可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。比如，终端中还包括射频电路、拍摄组件、传感器、音频电路、无线保真(wireless fidelity，WiFi)组件、电源、蓝牙组件等部件，在此不再赘述。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有至少一条计算机指令，该至少一条计算机指令由处理器加载并执行以实现如上各个实施例所述的数据恢复方法。关于上述提供的任一种计算机可读存储介质中相关内容的解释及有益效果的描述，均可以参考上述对应的实施例，此处不再赘述。
本申请实施例还提供了一种芯片。该芯片中集成了用于实现上述数据恢复装置的功能的控制电路和一个或者多个端口。可选的，该芯片支持的功能可以参考上文，此处不再赘述。本领域普通技术人员可以理 解实现上述实施例的全部或部分步骤可通过程序来指令相关的硬件完成。所述的程序可以存储于一种计算机可读存储介质中。上述提到的存储介质可以是只读存储器，随机接入存储器等。上述处理单元或处理器可以是中央处理器，通用处理器、特定集成电路(application specific integrated circuit，ASIC)、微处理器(digital signal processor，DSP)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。
本申请实施例还提供了一种包含指令的计算机程序产品，当该指令在计算机上运行时，使得计算机执行上述实施例中的任意一种方法。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如SSD)等。
应注意，本申请实施例提供的上述用于存储计算机指令或者计算机程序的器件，例如但不限于，上述存储器、计算机可读存储介质和通信芯片等，均具有非易失性(non-transitory)。本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读存储介质中或者作为计算机可读存储介质上的一个或多个指令或代码进行传输。计算机可读存储介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述仅为本申请的可选实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (10)

  1. 一种数据恢复方法，其特征在于，所述方法由生产设备执行，所述方法包括：
    获取目标数据库的待恢复备份数据的标识；
    若在所述待恢复备份数据是增量备份数据，获取已恢复备份数据；其中，所述已恢复备份数据的备份时间早于所述待恢复备份数据的备份时间，且所述已恢复备份数据是所述备份时间距离所述待恢复备份数据的备份时间最近一次的已恢复的备份数据；
    若所述已恢复备份数据与所述待恢复备份数据是基于同一全量备份数据的备份数据，响应于查询到第一快照，按照增量备份数据恢复方式恢复所述待恢复备份数据；其中，所述第一快照用于确定所述已恢复备份数据的恢复时间时所述目标数据库的状态；所述增量备份数据的恢复方式是基于所述待恢复备份数据与所述已恢复备份数据之间的差异增量备份数据，恢复所述待恢复备份数据的方式。
  2. 根据权利要求1所述的方法，其特征在于，所述响应于查询到第一快照，按照增量备份数据恢复方式恢复所述待恢复备份数据，包括：
    响应于查询到所述第一快照，按照所述第一快照将所述目标数据库还原成第一状态；所述第一状态是使用所述已恢复备份数据进行数据恢复后所述目标数据库的状态；
    按照增量备份数据恢复方式，采用所述待恢复备份数据恢复处于所述第一状态的所述目标数据库。
  3. 根据权利要求2所述的方法，其特征在于，所述按照增量备份数据恢复方式，采用所述待恢复备份数据恢复处于所述第一状态的所述目标数据库，包括：
    获取所述已恢复备份数据与所述待恢复备份数据之间n个增量备份数据；所述已恢复备份数据与所述待恢复备份数据之间经过n个进行数据备份的备份时间；所述n是大于等于1的整数；
    基于所述n个增量备份数据，确定所述差异增量备份数据；
    按照所述差异增量备份数据，采用所述待恢复备份数据恢复处于所述第一状态的所述目标数据库。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述获取目标数据库的待恢复备份数据的标识，包括：
    从元数据记录信息中获取所述目标数据库的所述待恢复备份数据的标识；所述元数据记录信息包括在各个所述备份时间下对所述备份数据进行备份时记录的所述备份数据的标识。
  5. 根据权利要求4所述的方法，其特征在于，所述标识用于指示备份数据类型以及所述备份数据类型各自对应的序列号；所述备份数据类型包括全量备份数据或增量备份数据；所述备份数据类型各自对应的序列号包括全量备份序列号或增量备份序列号。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，所述获取目标数据库的待恢复备份数据的标识之后，还包括：
    基于所述待恢复备份数据的标识，确定所述待恢复备份数据的所述备份数据类型，所述备份数据类型包括全量备份数据或增量备份数据；
    在所述待恢复备份数据是所述全量备份数据时，按照所述全量备份数据方式恢复所述待恢复备份数据；所述全量备份数据恢复方式是基于所述全量备份数据恢复所述待恢复备份数据的方式。
  7. 根据权利要求1至6任一项所述的方法，其特征在于，所述第一快照包括在所述已恢复备份数据的恢复时间时所述目标数据库的配置信息、在所述已恢复备份数据的恢复时间时所述目标数据库的日志信息以及所述已恢复备份数据的数据信息。
  8. 根据权利要求1至7任一项所述的方法，其特征在于，所述按照增量备份数据恢复方式恢复所述待恢复备份数据之后，还包括：
    清除所述第一快照中的内容；
    获取恢复所述待恢复备份数据后所述目标数据库的第二状态；
    按照所述第二状态，更新所述第一快照。
  9. 根据权利要求1至7任一项所述的方法，其特征在于，所述按照增量备份数据恢复方式恢复所述待恢复备份数据之后，还包括：
    获取恢复所述待恢复备份数据后所述目标数据库的第二状态；
    按照所述第二状态，生成第二快照；其中，所述第二快照用于确定所述第二状态。
  10. 一种计算设备，其特征在于，所述计算设备包括处理器和存储器；所述处理器与所述存储器耦合；所述存储器用于存储计算机指令，所述计算机指令由所述处理器加载并执行以使计算设备实现如权利要求1至9任一所述的数据恢复方法。
PCT/CN2023/098051 2022-07-28 2023-06-02 数据恢复方法及电子设备 WO2024021861A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210911760.2A CN115421968A (zh) 2022-07-28 2022-07-28 数据恢复方法及电子设备
CN202210911760.2 2022-07-28

Publications (1)

Publication Number Publication Date
WO2024021861A1 true WO2024021861A1 (zh) 2024-02-01

Family

ID=84196273

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/098051 WO2024021861A1 (zh) 2022-07-28 2023-06-02 数据恢复方法及电子设备

Country Status (2)

Country Link
CN (1) CN115421968A (zh)
WO (1) WO2024021861A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115421968A (zh) * 2022-07-28 2022-12-02 超聚变数字技术有限公司 数据恢复方法及电子设备
CN115421969A (zh) * 2022-07-30 2022-12-02 超聚变数字技术有限公司 备份数据恢复方法及计算设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111880966A (zh) * 2020-07-09 2020-11-03 腾讯科技（深圳）有限公司 一种数据库数据恢复方法和装置
CN113254267A (zh) * 2021-05-20 2021-08-13 上海安钛飞信息技术有限公司 分布式数据库的数据备份方法和装置
CN113360322A (zh) * 2021-06-25 2021-09-07 上海上讯信息技术股份有限公司 一种基于备份系统恢复数据的方法及设备
CN114036004A (zh) * 2021-11-26 2022-02-11 江苏安超云软件有限公司 数据备份方法、恢复方法及装置
WO2022048495A1 (zh) * 2020-09-01 2022-03-10 阿里云计算有限公司 一种数据备份方法、数据恢复方法、装置及电子设备
CN115421968A (zh) * 2022-07-28 2022-12-02 超聚变数字技术有限公司 数据恢复方法及电子设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111880966A (zh) * 2020-07-09 2020-11-03 腾讯科技（深圳）有限公司 一种数据库数据恢复方法和装置
WO2022048495A1 (zh) * 2020-09-01 2022-03-10 阿里云计算有限公司 一种数据备份方法、数据恢复方法、装置及电子设备
CN113254267A (zh) * 2021-05-20 2021-08-13 上海安钛飞信息技术有限公司 分布式数据库的数据备份方法和装置
CN113360322A (zh) * 2021-06-25 2021-09-07 上海上讯信息技术股份有限公司 一种基于备份系统恢复数据的方法及设备
CN114036004A (zh) * 2021-11-26 2022-02-11 江苏安超云软件有限公司 数据备份方法、恢复方法及装置
CN115421968A (zh) * 2022-07-28 2022-12-02 超聚变数字技术有限公司 数据恢复方法及电子设备

Also Published As

Publication number Publication date
CN115421968A (zh) 2022-12-02

Similar Documents

Publication Publication Date Title
WO2024021861A1 (zh) 数据恢复方法及电子设备
WO2022126974A1 (zh) 基于Kafka的增量数据同步方法、装置、设备及介质
WO2019140828A1 (zh) 电子装置、分布式系统日志查询方法及存储介质
US11093558B2 (en) Providing accountability of blockchain queries
US10146639B1 (en) Recovery of virtual machines from a protection tier
US10762109B2 (en) Asynchronous deletion in non-relational databases
CN111783042A (zh) 数据库的访问控制方法、装置、数据库主系统和电子设备
CN111144926B (zh) 业务请求处理方法、装置、系统、电子设备及可读介质
WO2021017305A1 (zh) 数据的查询方法、装置、电子设备及计算机可读存储介质
WO2021031655A1 (zh) 区块链网络的升级方法及装置、存储介质、电子设备
WO2024027314A1 (zh) 备份数据恢复方法及计算设备
CN116701053B (zh) 生产环境数据库的数据备份恢复方法、装置、设备及介质
US10129328B2 (en) Centralized management of webservice resources in an enterprise
WO2020192663A1 (zh) 一种数据管理方法及相关设备
US11294866B2 (en) Lazy optimistic concurrency control
WO2021012554A1 (zh) 区块链中数据字段的更新方法、装置、介质、电子设备
TWI571754B (zh) 用來進行檔案同步控制之方法與裝置
CN115098297B (zh) 一种云原生存储数据卷的一致性快照生成方法和系统
CN111143461A (zh) 映射关系处理系统、方法和电子设备
US10389743B1 (en) Tracking of software executables that come from untrusted locations
US8650548B2 (en) Method to derive software use and software data object use characteristics by analyzing attributes of related files
EP4348933A1 (en) Managing keys across a series of nodes, based on snapshots of logged client key modifications
KR101935249B1 (ko) 스토어드 프로시져를 이용하여 플로우 기반의 프로세싱을 수행하기 위한 방법, 시스템, 및 장치
CN114328119A (zh) 一种数据库监控方法、系统以及服务器
CN114143308A (zh) 文件上传信息处理方法、装置、计算机设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23845074

Country of ref document: EP

Kind code of ref document: A1