Data processing method and device, equipment and storage medium

By acquiring and restoring cloud backup data at the receiving end, the security and cost issues in cross-LAN data synchronization are resolved, achieving secure, complete, and efficient data synchronization.

CN122072734APending Publication Date: 2026-05-22BEIJING JINGDONG TUOXIAN TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411676170.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-21
Publication Date
2026-05-22

AI Technical Summary

Technical Problem

During data synchronization, there are risks of data leakage and data inconsistency, especially in cross-LAN data synchronization where leased network lines are costly and lack sufficient security.

Method used

By obtaining a list of backup files from the sender at a predetermined frequency at the receiving end, full and incremental backup data are obtained from the sender based on this list, and the data is restored to the target database. This avoids direct data transmission over a dedicated network line and uses an SDK interface for encrypted communication.

Benefits of technology

It ensures security and data integrity during the data synchronization process, reduces reliance on and costs of dedicated network lines, and guarantees timely data recovery and sustainability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122072734A_ABST
    Figure CN122072734A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a data processing method and device, equipment and a storage medium. The method comprises the steps that at a receiving end, a backup file list sent by a sending end is acquired at a first preset frequency, and the backup file list is used for recording full backup data, incremental backup data and corresponding generation time generated by the sending end; based on the backup file list, obtaining full backup data and incremental backup data from the sending end; and recovering the obtained total backup data and incremental backup data to the target database. In this way, the dependence of the synchronous data on the external network opening permission of the database can be decoupled, and the security of the data is ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The exemplary embodiments disclosed herein generally relate to the field of data processing technology, and more specifically, to methods, apparatus, devices, and storage media for data processing. Background Technology

[0002] Data synchronization is the process of copying data from one system or platform to another. Various risks often exist during data synchronization, such as data leakage and data inconsistency. Therefore, how to avoid these risks during data synchronization is a crucial and pressing issue. Summary of the Invention

[0003] In a first aspect of this disclosure, a method for data processing is provided. The method includes: at a receiving end, acquiring a list of backup files sent by a sending end at a first predetermined frequency, the list of backup files recording full backup data, incremental backup data, and corresponding generation times generated by the sending end; based on the list of backup files, acquiring full backup data and incremental backup data from the sending end; and restoring the acquired full backup data and incremental backup data to a target database.

[0004] In a second aspect of this disclosure, an apparatus for data processing is provided. The apparatus includes: a first acquisition module configured to acquire a list of backup files sent by a sender at a first predetermined frequency, the backup file list recording full backup data, incremental backup data, and corresponding generation times generated by the sender; a second acquisition module configured to acquire full backup data and incremental backup data from the sender based on the backup file list; and a recovery module configured to restore the acquired full backup data and incremental backup data to a target database.

[0005] In a third aspect of this disclosure, an electronic device is provided. The electronic device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method of the first aspect of this disclosure when executed by the at least one processing unit.

[0006] In a fourth aspect of this disclosure, a computer-readable storage medium is provided. This computer-readable storage medium stores a computer program that can be executed by a processor to perform the method according to a first aspect of this disclosure.

[0007] In a fifth aspect of this disclosure, a computer program product is provided. The computer program product includes computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the method according to a first aspect of this disclosure.

[0008] It should be understood that the content described in this summary section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0009] The above and other features, advantages, and aspects of various implementations of this disclosure will become more apparent in the following detailed description, taken in conjunction with the accompanying drawings. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0010] Figure 1 A schematic diagram of an example environment in which embodiments of the present disclosure can be implemented is shown;

[0011] Figure 2 A flowchart of a data processing procedure according to some embodiments of the present disclosure is shown;

[0012] Figure 3 A schematic diagram illustrating a data processing procedure in a medical setting according to some embodiments of the present disclosure is shown;

[0013] Figure 4 A block diagram of an apparatus for data processing according to some embodiments of the present disclosure is shown; and

[0014] Figure 5 A block diagram of an electronic device in which one or more embodiments of the present disclosure may be implemented is shown. Detailed Implementation

[0015] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0016] It should be noted that the acquisition, storage, and application of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0017] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below.

[0018] As briefly mentioned above, various risks exist during data synchronization. For example, when using a master-slave synchronization method, considering network security and latency, the data synchronization process needs to be within the same local area network (LAN). If data needs to be synchronized from a cloud platform or cloud server to a local database, since the cloud platform or cloud server and the local database are not on the same LAN, a dedicated network line is required for synchronization, but dedicated network lines are expensive. Another example is using third-party synchronization software. In this case, the target database (such as the local database in the example above) needs to be connected to the third-party synchronization software, and access permissions to the target database need to be granted. Without a dedicated network line, the security risks are high.

[0019] To at least partially address the aforementioned problems and other potential issues in traditional solutions, this disclosure provides a data processing solution. According to various embodiments of this disclosure, at the receiving end, a list of backup files sent by the sending end is acquired at a first predetermined frequency. This backup file list records the full backup data, incremental backup data, and corresponding generation times generated by the sending end. Based on the backup file list, the full backup data and incremental backup data are acquired from the sending end. The acquired full backup data and incremental backup data are then restored to the target database. In this way, the dependency of synchronized data on the database's external network access can be decoupled, ensuring data security.

[0020] The following description will focus on exemplary embodiments of the present disclosure with reference to the accompanying drawings.

[0021] Figure 1 A schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented is shown. For example... Figure 1 As shown, environment 100 includes two servers, for example, a first server 110 and a second server 120. In embodiments of this disclosure, the second server 120 is configured to generate full backup data 140 and incremental backup data 150 for data stored within the second server 120 at a predetermined frequency. The first server 110 is configured to obtain the full backup data 140 and incremental backup data 150 from the second server 120 and synchronize the data to database 130.

[0022] In the following text, the data processing scheme will be described using the example of the first server 110 as a local server, the second server 120 as a cloud server, and the database as a local database. Therefore, it can be understood that the first server 110 can also be called the local server 110, the second server 120 can also be called the cloud server 120, and the database 130 can also be called the local database 130.

[0023] In some embodiments, the server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. The server may include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in a cloud environment, and so on.

[0024] In some embodiments, database 130 can be any type of database. For example, a relational database management system (RDBMS), a non-relational database (Not Only SQL, NoSQL), an object-oriented database management system (OODBMS), a distributed database system (DDS), and so on.

[0025] In some embodiments, a communication connection may be established between the first server 110 and the second server 120, and a communication connection may be established between the first server 110 and the database 130. The communication connection may be established via wired or wireless means. The communication connection may include, but is not limited to, Bluetooth connections, mobile network connections, Universal Serial Bus (USB) connections, Wireless Fidelity (WiFi) connections, etc., and the embodiments of this disclosure are not limited in this respect.

[0026] It should be understood that the structure and function of environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of this disclosure.

[0027] Figure 2 A flowchart of a data processing procedure 200 according to some embodiments of the present disclosure is shown. Procedure 200 can be implemented at a local server 110. The following is in conjunction with... Figure 1 A detailed description of process 200 is provided.

[0028] In box 210, local server 110 obtains a list of backup files sent by cloud server 120 at a first frequency. In this document, local server 110 is sometimes referred to as the "receiver" and cloud server 120 is sometimes referred to as the "sender".

[0029] In some embodiments, cloud server 120 is configured with one or more Software Development Kit (SDK) interfaces. When the backup file list is authorized, local server 110 can obtain the backup file list from cloud server 120 through the SDK interface. This avoids obtaining relevant data from cloud server 120 via a dedicated network line, thereby reducing data synchronization costs. Alternatively or additionally, local server 110 can obtain the backup file list through a subscription.

[0030] Furthermore, the process by which the local server 110 obtains the backup file list can be encrypted. Specifically, the encryption process or method can be implemented using a script (e.g., a script implemented in Python). Based on the script, a third-party library (e.g., the Requests package) can be introduced to send HTTP requests to the SDK interface of the cloud server 120, thereby obtaining the backup file list. During the HTTP request process, the data involved can be encrypted using an application key (AppKey) and an application secret (AppSecret). Alternatively or additionally, the local server 110 can request the backup file list from the cloud server 120 once every 30 seconds.

[0031] In embodiments of this disclosure, the backup file list is used to record the full backup data 140, incremental backup data 150 generated by the cloud server 120, and their corresponding generation times. In this document, full backup data may sometimes be referred to as a "full backup file," and incremental backup data may sometimes be referred to as an "incremental backup file." In some embodiments, the backup file list may be a table.

[0032] In some embodiments, the backup file list may be a list that includes full backup data 140, the generation time of full backup data 140, incremental backup data 150, and the generation time of incremental backup data 150. Alternatively, it may be two lists, one of which contains only full backup data 140 and the generation time of full backup data 140, and the other of which contains only incremental backup data 150 and the generation time of incremental backup data 150.

[0033] In some embodiments, after obtaining the backup file list, the local server 110 can store the backup file list in a specified location. For example, if the backup file list includes a list containing full backup data 140 and its generation time, and a list containing incremental backup data 150 and its generation time, the local server 110 can store the list containing full backup data 140 and its generation time in a first specified location, and store the list containing incremental backup data 150 and its generation time in a second specified location.

[0034] As an example, the first storage location can be the storage location corresponding to the directory / data / download / dump on the file hard drive of local server 110, and the second storage location can be the storage location corresponding to the directory / data / download / binlog on the file hard drive of local server 110.

[0035] In this article, the list containing full backup data 140 and the generation time of full backup data 140 is sometimes referred to as the "full backup file list", and the list containing incremental backup data 150 and the generation time of incremental backup data 150 is sometimes referred to as the "incremental backup file list".

[0036] In box 220, local server 110 obtains full backup data 140 and incremental backup data 150 from cloud server 120 based on the backup file list.

[0037] In some embodiments, the process by which the local server 110 obtains full backup data 140 and incremental backup data 150 from the cloud server 120 can also be encrypted. The encryption method can be the same as the encryption method used to obtain the backup file list, which will not be described in detail here.

[0038] In some embodiments, cloud server 120 is configured to provide full backup data at a second predetermined frequency and incremental backup data at a third predetermined frequency. For example, cloud server 120 may provide full backup data daily on a daily basis, and incremental backup data every 5 minutes. It should be understood that when local server 110 retrieves the backup file list once every 30 seconds, the number of data entries in the full backup data in the backup file list retrieved within the same day remains unchanged, and the number of data entries in the incremental backup data in the backup file list retrieved within the same 5-minute interval also remains unchanged.

[0039] When local server 110 retrieves full backup data 140 and incremental backup data 150 from cloud server 120, it can refer to the backup file list. For example, when local server 110 retrieves the backup file list from cloud server 120 for the first time, the list includes 100 full backup data entries and 5 incremental backup data entries. Local server 110 can then retrieve the corresponding data from cloud server 120 based on the 100 full backup data entries and 5 incremental backup data entries in the backup file list. When local server 110 retrieves the backup file list from cloud server 120 for the second time, the list now includes 100 full backup data entries and 7 incremental backup data entries. These 7 incremental backup data entries include the 5 incremental backup data entries from the first retrieved backup file list. In this case, local server 110 only needs to retrieve the additional 2 incremental backup data entries from cloud server 120.

[0040] Of course, there are other situations. For example, if the first backup file list obtained by local server 110 contains 100 full backup data entries and 5 incremental backup data entries, and the second backup file list obtained contains 150 full backup data entries and 7 incremental backup data entries, local server 110 can obtain the additional 50 full backup data entries and 2 incremental backup data entries from cloud server 120 based on the backup file list.

[0041] In some embodiments, the local server 110 may store the acquired full backup data 140 and incremental backup data 150 to designated locations respectively. For example, the full backup data 140 may be stored at the location where the full backup file list is stored, and the incremental backup data 150 may be stored at the location where the incremental backup file list is stored. Of course, it may also be stored at other designated locations, and the embodiments of this disclosure are not limited thereto.

[0042] In some embodiments, during the acquisition of full backup data 140 and incremental backup data 150 from cloud server 120, local server 110 may generate a log to record the acquired full backup data 140, incremental backup data 150, and the corresponding acquisition time. During data synchronization, by comparing the log with the acquired backup file list, it is possible to avoid missing any one or more data entries in the full backup data 140 and / or incremental backup data 150, thereby ensuring data integrity.

[0043] In box 230, the local server 110 restores the acquired full backup data 140 and incremental backup data 150 to the local database 130.

[0044] Specifically, local server 110 can use a third-party decompression tool (e.g., mysql_backup_extract) to decompress the full backup data 140, and use a backup tool (e.g., xtrabackup) to restore the decompressed data to local database 130. Alternatively or additionally, local server 110 can specify the location to restore the full backup data 140. Similarly, local server 110 can use the same method to restore incremental backup data 150 to local database 130.

[0045] In some embodiments, during the restoration of incremental backup data 150 to local database 130, a log may also be generated to record the restored incremental backup data 150 and the corresponding restoration time. For example, monitoring this log can determine whether the incremental backup data 150 has been successfully restored. Alternatively or additionally, this log can be monitored using appropriate tools (e.g., mysqlbinlog).

[0046] In some embodiments, if the incremental backup data 150 fails to be restored, the local server 110 may issue an alarm message in response to determining that the number of times the incremental backup data 150 has been re-acquired has reached a predetermined number and the incremental backup data 150 has still not been acquired. Alternatively or additionally, the number of times may be 3.

[0047] If the local server 110 responds to the fact that the number of times it has reacquired incremental backup data 150 has not reached the predetermined number and incremental backup data 150 has been acquired, it will continue to restore the acquired incremental backup data 150. Of course, the premise for issuing an alarm message is not only that the incremental backup data 150 restoration fails, but also that the incremental backup data 150 download fails and / or the backup file list download fails.

[0048] In some embodiments, if incremental backup data 150 fails to be restored and the duration of the failure exceeds a predetermined duration, the most recent full backup data 140 can be determined based on the backup file list and restored to the local database 130.

[0049] Based on the above process, the local server 110 continuously obtains a list of backup files from the cloud server 120, and downloads full backup data 140 and incremental backup data 150 from the cloud server 120 based on the list of backup files. The downloaded full backup data 140 and incremental backup data 150 are continuously restored to the local database 130 until the data synchronization process is completed.

[0050] To more clearly explain the data processing solutions provided in some embodiments of this disclosure, examples from the medical field are described below. It is understood, of course, that the embodiments of this disclosure are not limited to this application scenario.

[0051] Figure 3 A schematic diagram of a data processing procedure 300 in a medical setting according to some embodiments of the present disclosure is shown. The following continues in conjunction with... Figure 1 Let me introduce it.

[0052] like Figure 3 As shown, on the cloud side, in box 310, cloud server 120 backs up data in the cloud database. The backup files include full backup files (dump files) and incremental backup files (binlog files). In some embodiments, cloud server 120 can be configured to perform a full backup of the data in the cloud database once a day and an incremental backup every 5 minutes. In some embodiments, cloud server 120 is configured to have multiple SDK interfaces, which, when authorized, can support obtaining backup files through the SDK interfaces.

[0053] On the hospital server room side, in box 320, local server 110 pulls dump and binlog files from cloud server 120. In some embodiments, a plugin or script can be installed on local server 110 to subscribe to a list of backup files from cloud server 120, and to download dump and binlog files from cloud server 120 based on the list of backup files. In some embodiments, the plugin or script can use the Requests package to subscribe to the list of backup files from cloud server 120 and download the corresponding backup files.

[0054] Furthermore, the subscription and retrieval processes are encrypted. In some embodiments, the subscription address, application key, and application privacy key can be configured on the cloud server 120.

[0055] In box 330, local server 110 stores the corresponding backup files. In some embodiments, local server 110 may store the subscribed backup file list and the corresponding downloaded backup files to a specified location (e.g., / data / download / dump and / data / download / binlog), and record the downloaded backup files through a log to form a download list. In some embodiments, local server 110 may store the download list to a specified location (e.g., / data / download / down.log), thereby ensuring data integrity and preventing data loss or omission.

[0056] In box 340, local server 110 restores the dump file in its entirety to database 130. In some embodiments, local server 110 may use a third-party decompression tool (e.g., mysql_backup_extract) to decompress the dump file and use a backup tool (e.g., xtrabackup) to restore the decompressed data to database 130.

[0057] In box 350, local server 110 continuously and incrementally restores the binlog file to database 130. In some embodiments, database 130 may be a MySQL database. Local server 110 may be a Linux server.

[0058] In some embodiments, the local server 110 can query the most recent binlog node obtained from the database 130, locate the file corresponding to the start position of the binlog based on the backup file list and the most recent binlog node, and use mysqlbinlog to restore the binlog file nodes.

[0059] Therefore, by repeating the above process, the data in the cloud server 120 can be synchronized to the database 130 in the hospital's computer room.

[0060] In box 360, if the local server 110 detects a binlog failure event, it can enable automatic retries a predetermined number of times (e.g., 3 times). In the embodiments of this disclosure, retries refer to the re-recovery of the binlog file. When the binlog file is successfully and continuously recovered after the predetermined number of retries, it can be integrated with the hospital's alarm system to send telephone and SMS alerts so that maintenance personnel can intervene in a timely manner.

[0061] In box 370, the local server 110 monitors binlog recovery events. If the recovery process continues to fail and issues a warning notification, and the recovery time of the binlog file is interrupted for a long time, the most recent dump file can be found and a full recovery can be performed again, thus ensuring that a full recovery can be retried in case of abnormality.

[0062] In summary, the data processing solution proposed in this disclosure can decouple the synchronization of data from the database's external network access, thus ensuring data security; it uses an SDK interface to encrypt and obtain backup files, reducing reliance on dedicated network lines, thereby significantly reducing costs while ensuring data security; and it provides timely and effective data recovery with strong sustainability.

[0063] Figure 4A block diagram of an apparatus 400 for data processing according to some embodiments of the present disclosure is shown. The apparatus 400 may be implemented in a first server 110. Various modules / components in the apparatus 400 may be implemented by hardware, software, firmware, or any combination thereof.

[0064] The device 400 includes a first acquisition module 410, configured to acquire a list of backup files sent by a sender at a first predetermined frequency. The backup file list records full backup data, incremental backup data, and corresponding generation times generated by the sender. The device 400 also includes a second acquisition module 420, configured to acquire full backup data and incremental backup data from the sender based on the backup file list. The device 400 further includes a recovery module 430, configured to restore the acquired full backup data and incremental backup data to a target database.

[0065] In some embodiments, the recovery module 430 is further configured to, in the event that incremental backup data recovery fails and the duration of the recovery failure exceeds a predetermined duration, determine the most recent full backup data based on the backup file list; and restore the most recent full backup data to the target database.

[0066] In some embodiments, the device 400 further includes an alarm module configured to reacquire incremental backup data in the event of failure to recover incremental backup data; and to issue an alarm message in response to determining that the number of times incremental backup data has been reacquired has reached a predetermined number and incremental backup data has still not been acquired.

[0067] In some embodiments, the backup file list includes a full backup file list and an incremental backup file list, and the device 400 further includes a storage module configured to store the full backup data and the full backup file list to a first designated location at the receiving end; and to store the incremental backup data and the incremental backup file list to a second designated location at the receiving end.

[0068] In some embodiments, the apparatus 400 further includes a first generation module configured to generate a first log during the restoration of incremental backup data to a target database. The first log is used to record the restored incremental backup data and the corresponding restoration time.

[0069] In some embodiments, the apparatus 400 further includes a second generation module configured to generate a second log during the acquisition of full backup data and incremental backup data from the sending end. The second log is used to record the acquired full backup data, incremental backup data, and the corresponding acquisition time.

[0070] In some embodiments, the process of obtaining full backup data, incremental backup data, and a list of backup files is encrypted.

[0071] In some embodiments, the sender is configured to provide full backup data at a second predetermined frequency and incremental backup data at a third predetermined frequency.

[0072] The units included in device 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units may be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. In addition to or as an alternative to machine-executable instructions, some or all of the units in device 400 may be implemented at least partially by one or more hardware logic components. By way of example and not limitation, exemplary types of hardware logic components that may be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-chips (SoCs), complex programmable logic devices (CPLDs), and so on.

[0073] Figure 5 A block diagram of an electronic device 500 in which one or more embodiments of the present disclosure may be implemented is shown. It should be understood that... Figure 5 The electronic device 500 shown is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. Figure 5 The electronic device 500 shown can be used to achieve Figure 1 Remote device 120 and / or terminal device 110.

[0074] like Figure 5 As shown, electronic device 500 is in the form of a general-purpose electronic device. Components of electronic device 500 may include, but are not limited to, one or more processors or processing units 510, memory 520, storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. Processing unit 510 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 520. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 500.

[0075] Electronic device 500 typically includes multiple computer storage media. Such media can be any available media accessible to electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 520 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 530 can be a removable or non-removable medium and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data (e.g., training data for training) and can be accessed within electronic device 500.

[0076] Electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not explicitly stated... Figure 5 As shown, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks can be provided. In these cases, each drive can be connected to a bus (not shown) via one or more data media interfaces. Memory 520 may include computer program product 525 having one or more program modules configured to perform various methods or actions of various embodiments of this disclosure.

[0077] Communication unit 540 enables communication with other electronic devices via a communication medium. Additionally, the functionality of components of electronic device 500 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, electronic device 500 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0078] Input device 550 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 560 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 500 can also communicate with one or more external devices (not shown) via communication unit 540 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 500, or with any device that enables electronic device 500 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interface (not shown).

[0079] According to an exemplary implementation of this disclosure, a computer-readable storage medium is provided that stores one or more computer instructions, wherein the one or more computer instructions are executed by a processor to implement the methods described above. According to an exemplary implementation of this disclosure, a computer program product is also provided, which is tangibly stored on a non-transient computer-readable medium and includes computer-executable instructions that are executed by a processor to implement the methods described above.

[0080] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products implemented according to this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0081] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0082] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0083] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0084] Various implementations of this disclosure have been described above. The foregoing description is exemplary and not exhaustive, nor is it limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the implementations disclosed herein.

Claims

1. A method for data processing, comprising: At the receiving end, a list of backup files sent by the sending end is acquired at a first predetermined frequency. The list of backup files is used to record the full backup data, incremental backup data and corresponding generation time generated by the sending end. Based on the list of backup files, the full backup data and the incremental backup data are obtained from the sending end; as well as The acquired full backup data and incremental backup data are restored to the target database.

2. The method according to claim 1, further comprising: If the incremental backup data recovery fails and the duration of the failure exceeds a predetermined duration, the most recent full backup data is determined based on the backup file list. as well as Restore the most recent full backup data to the target database.

3. The method according to claim 1, further comprising: If the incremental backup data recovery fails, the incremental backup data will be reacquired. as well as An alarm is issued in response to the determination that the incremental backup data has been retrieved a predetermined number of times and the incremental backup data has still not been retrieved.

4. The method according to claim 1, wherein the backup file list includes a full backup file list and an incremental backup file list, and the method further includes: The full backup data and the full backup file list are stored in the first designated location on the receiving end; as well as The incremental backup data and the list of incremental backup files are stored in a second designated location on the receiving end.

5. The method according to claim 1, further comprising: During the restoration of the incremental backup data to the target database, a first log is generated, which records the restored incremental backup data and the corresponding restoration time.

6. The method according to claim 1, further comprising: During the process of acquiring the full backup data and the incremental backup data from the sending end, a second log is generated. The second log is used to record the acquired full backup data, the incremental backup data, and the corresponding acquisition time.

7. The method of claim 1, wherein the process of obtaining the full backup data, the incremental backup data, and the backup file list is encrypted.

8. The method of claim 1, wherein the sending end is configured to provide the full backup data at a second predetermined frequency and the incremental backup data at a third predetermined frequency.

9. An apparatus for data processing, comprising: The first acquisition module is configured to acquire a list of backup files sent by the sending end at a first predetermined frequency. The list of backup files is used to record the full backup data, incremental backup data and corresponding generation time generated by the sending end. The second acquisition module is configured to acquire the full backup data and the incremental backup data from the sending end based on the backup file list. as well as The recovery module is configured to restore the acquired full backup data and incremental backup data to the target database.

10. An electronic device, comprising: At least one processing unit; as well as At least one memory, coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, which, when executed by the at least one processing unit, cause the electronic device to perform the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program stored thereon, the computer program being executable by a processor to implement the method according to any one of claims 1 to 8.

12. A computer program product comprising computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the method according to any one of claims 1 to 8.