Backup data processing method and system and electronic equipment

Abstract

The invention discloses a backup data processing method and system and electronic equipment. The method relates to the field of big data, and comprises the steps that synchronous data sent by a disaster recovery gateway is stored in a data storage component of a disaster recovery node, the data storage component is composed of multiple layers of protection structures, and the disaster recovery gateway is used for storing the synchronous data in the disaster recovery node under the condition that the synchronous data sent by a main database is received; forwarding the synchronous data to a standby database, a disaster recovery node and a remote database; and monitoring the first operation states of the main database and the standby database through the disaster recovery node, and sending the disaster recovery data stored in the disaster recovery node to the remote database when the first operation states of the main database and the standby database are abnormal. By means of the method and device, the problem that in the related technology, due to the fact that the timeliness of the data stored in the remote disaster recovery database is low, data missing occurs in the remote disaster recovery database under the condition that the main database and the standby database break down is solved.

Description

Technical Field

[0001] The present application relates to the field of big data, and more specifically, to a method, system, and electronic device for processing backup data. Background Art

[0002] To ensure business continuity and data security, current financial institutions' IT infrastructures generally adopt a two-site, three-center, or multi-site, multi-center deployment architecture. This architecture provides disaster recovery capabilities within a metropolitan area or larger. In-city active-active or active-standby centers can handle site-level failures, while off-site disaster recovery centers ensure cross-regional redundancy.

[0003] However, when the primary data center and backup data center in the same metropolitan area encounter force majeure events (such as natural disasters, large-scale power outages, etc.) at the same time, causing both data centers to be unable to operate normally, relying on an off-site disaster recovery data center becomes the only option.

[0004] Furthermore, because data replication in existing off-site disaster recovery technologies is typically asynchronous, this means that at the moment a primary data center fails, the data held by the off-site disaster recovery center may not be up to date, meaning the RPO (Recovery Point Objective) is not zero. This can lead to the loss of some transaction data during the disaster recovery process, compromising business continuity and data consistency.

[0005] Currently, no effective solution has been proposed to the problem that the timeliness of data stored in the off-site disaster recovery database is low, which leads to data loss in the off-site disaster recovery database when the primary and backup databases fail. Summary of the Invention

[0006] The main purpose of this application is to provide a method, system and electronic device for processing backup data to solve the problem in the related art that the timeliness of data stored in the off-site disaster recovery database is low, resulting in data loss in the off-site disaster recovery database when the primary and backup databases fail.

[0007] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a method for processing backup data is provided. The method includes: storing the synchronous data sent by the disaster recovery gateway in the data storage component of the disaster recovery node, wherein the data storage component is composed of a multi-layer protection structure, and the disaster recovery gateway is used to forward the synchronous data to the backup database, the disaster recovery node and the remote database when receiving the synchronous data sent by the primary database, wherein the remote database asynchronously stores the data in the primary database; monitoring the first operating status of the primary database and the backup database through the disaster recovery node, and sending the disaster recovery data stored in the disaster recovery node to the remote database when the first operating status of the primary database and the backup database are both abnormal.

[0008] Optionally, after storing the synchronization data sent by the disaster recovery gateway in the data storage component of the disaster recovery node, the method also includes: suspending the business operation of the main database; judging whether the disaster recovery node has completed the storage operation of the synchronization data; and sending feedback information to the main database through the disaster recovery node when the disaster recovery node completes the storage operation, wherein the main database continues to perform business operation operations after receiving the feedback information.

[0009] Optionally, after suspending the business operation of the primary database, the method further includes: determining the suspension duration of the business operation of the primary database; judging whether the suspension duration is greater than a preset duration; if the suspension duration is greater than the preset duration, determining that there is an abnormality in the disaster recovery node, and continuing to execute the business operation through the primary database.

[0010] Optionally, the method also includes: obtaining the data volume of each disaster recovery data stored in the disaster recovery node to obtain multiple data volumes; determining the total data volume of the disaster recovery data stored in the disaster recovery node based on the multiple data volumes, and judging whether the total data volume is greater than the data volume threshold; when the total data volume is greater than the data volume threshold, deleting the disaster recovery data in descending order according to the storage time of each disaster recovery data until the total data volume is less than or equal to the data volume threshold.

[0011] Optionally, the method also includes: obtaining the timestamp of each disaster recovery data stored in the disaster recovery node to obtain multiple timestamps; calculating the time difference between each timestamp and the current moment, and judging in turn whether each time difference is greater than a time difference threshold; if there is a target time difference greater than the time difference threshold, deleting the disaster recovery data to which the target time difference belongs.

[0012] Optionally, the method further includes: monitoring the second operating state of the disaster recovery gateway; when the second operating state is abnormal, terminating the business operation of the primary database and switching the disaster recovery gateway until the second operating state of the disaster recovery gateway is normal.

[0013] Optionally, the method also includes: monitoring the second operating state of the disaster recovery gateway; when the second operating state is abnormal, synchronizing the synchronization data to the backup database by the primary database through data synchronization between databases until the second operating state of the disaster recovery gateway changes from abnormal to normal; when the second operating state of the disaster recovery gateway changes from abnormal to normal, the disaster recovery gateway executes the data synchronization operation between the primary database and the backup database.

[0014] To achieve the above-mentioned purpose, according to another aspect of the present application, a backup data processing system is provided. The system includes: a primary database for receiving business data, generating synchronization data based on the business data, and sending the synchronization data to a disaster recovery gateway; a disaster recovery gateway for receiving the synchronization data and forwarding the synchronization data to a backup database, a disaster recovery node, and an off-site database; a disaster recovery node for monitoring the first operating status of the primary database and the backup database, and sending the disaster recovery data stored in the disaster recovery node to the off-site database if the first operating status of both the primary database and the backup database is abnormal; a backup database for synchronously storing data in the primary database; and an off-site database for asynchronously storing data in the primary database.

[0015] In order to achieve the above-mentioned purpose, according to another aspect of the present application, an electronic device is provided, which includes a memory storing an executable program; and a processor for running the program, wherein the above-mentioned method for processing backup data is executed when the program is running.

[0016] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a computer program product is provided, comprising computer instructions, which implement the steps of the above-mentioned method for processing backup data when executed by a processor.

[0017] In an embodiment of the present application, the synchronous data sent by the disaster recovery gateway is stored in the data storage component of the disaster recovery node, wherein the data storage component is composed of a multi-layer protection structure, and the disaster recovery gateway is used to forward the synchronous data to the backup database, the disaster recovery node and the remote database when receiving the synchronous data sent by the primary database, wherein the remote database asynchronously stores the data in the primary database; the first operating status of the primary database and the backup database is monitored by the disaster recovery node, and when the first operating status of the primary database and the backup database are both abnormal, the disaster recovery data stored in the disaster recovery node is sent to the remote database. By utilizing the real-time data backup function of the disaster recovery node, it is achieved that when there is an abnormality in the primary database and the backup database, the latest data can be synchronized to the remote database through the disaster recovery node, thereby ensuring the timeliness and integrity of the data in the remote database, and achieving the purpose of quickly restoring data to the remote database, thereby realizing the technical effect of enhancing data high availability and reducing the risk of data loss. In other words, even if both the primary and backup databases in the same region fail, the presence of the disaster recovery node ensures the integrity and continuity of critical business data, effectively supporting rapid business recovery and avoiding business interruptions caused by data loss. This improves the robustness of the overall architecture and the stability of business processing. This addresses the technical issue in related technologies where the data stored in off-site disaster recovery databases is less up-to-date, leading to data loss in the event of a primary or backup database failure. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings, which constitute part of this application, are intended to provide a further understanding of this application. The exemplary embodiments and descriptions of this application are intended to explain this application and do not constitute an improper limitation on this application. In the accompanying drawings:

[0019] Figure 1 A hardware structure block diagram of a computer terminal for implementing a method for processing backup data is shown;

[0020] Figure 2 is a flowchart of a method for processing backup data provided in Example 1 of the present application;

[0021] Figure 3 is a schematic diagram of a backup data processing system provided in Example 2 of the present application;

[0022] Figure 4 is a schematic diagram of a backup data processing device provided in Example 3 of the present application;

[0023] Figure 5 This is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0024] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in this application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0025] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0026] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0027] It should be noted that the backup data processing method, system and electronic device determined in the present disclosure can be used in the field of big data, and can also be used in any field other than the field of big data. The application field of the backup data processing method, system and electronic device determined in the present disclosure is not limited.

[0028] It should be noted that the collected information, user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) used in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize use or refuse use. If the user chooses to refuse, the expert decision-making process will be entered. For example, an interface is set up between this system and relevant users or institutions. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or institution through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or institution.

[0029] The embodiments or examples of the present disclosure are not exhaustive, but are merely illustrations of some embodiments or examples, and are not intended to be specific limitations on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment or example can be implemented as an independent example, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment or example can also be implemented as an independent example, and the order of the steps in a certain embodiment or example can be arbitrarily exchanged. In addition, the optional methods or optional examples in a certain embodiment or example can be arbitrarily combined; in addition, the various embodiments or examples can be arbitrarily combined. For example, some or all steps of different embodiments or examples can be arbitrarily combined, and a certain embodiment or example can be arbitrarily combined with the optional methods or optional examples of other embodiments or examples.

[0030] For ease of description, some nouns or terms involved in the embodiments of the present application are explained below:

[0031] RPO: Recovery Point Object, refers to the time after a disaster occurs, from when the system goes down and services are unavailable to when the system is restored to support business operations. The difference between these two points is called RPO.

[0032] Example 1

[0033] According to an embodiment of the present application, an embodiment of a method for processing backup data is also provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0034] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 FIG1 shows a hardware structure block diagram of a computer terminal for implementing a method for processing backup data. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more (illustrated as 102a, 102b, ..., 102n in the figure) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It will be understood by those skilled in the art that Figure 1The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0035] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuitry may be a single independent processing module, or may be incorporated in whole or in part into any of the other components of the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuitry serves as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0036] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the backup data processing method in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, realizing the above-mentioned backup data processing method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0037] The transmission device 106 is configured to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by the communications provider of the computer terminal 10. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0038] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0039] Under the above operating environment, this application provides Figure 2The backup data processing method shown in FIG. Figure 2 is a flowchart of a method for processing backup data according to Example 1 of the present application. Figure 2 As shown, the method includes:

[0040] Step S201, stores the synchronous data sent by the disaster recovery gateway in the data storage component of the disaster recovery node, wherein the data storage component is composed of a multi-layer protection structure, and the disaster recovery gateway is used to forward the synchronous data to the backup database, the disaster recovery node and the remote database when receiving the synchronous data sent by the primary database, wherein the remote database asynchronously stores the data in the primary database.

[0041] It should be noted that the disaster recovery gateway is a key device that plays a connecting role in the network. It is responsible for receiving the synchronization data sent by the primary database and forwarding it to the local backup database, disaster recovery node and remote database. Synchronous data refers to the real-time data changes or log information generated by the primary database when performing data update operations. These data need to be synchronized to other backup databases to ensure data consistency. The data storage component, that is, a storage unit in the disaster recovery node, is specifically used to store synchronization data from the disaster recovery gateway. The remote database is located in a different physical location from the primary database (usually a different urban area). Its main function is to receive and store asynchronous data backups of the primary database. Asynchronous storage reduces the impact on the performance of the primary database, and also ensures that when the local data center is unavailable, there is an available data copy for business recovery.

[0042] Specifically, the execution subject of this embodiment can be a disaster recovery node. When the main database performs any data update operation, the generated synchronization data will first be transmitted to the disaster recovery gateway. After receiving these synchronization data, the disaster recovery gateway forwards the data to the local backup database and disaster recovery node to achieve local data redundancy and fault switching capabilities. At the same time, after receiving the synchronization data sent by the disaster recovery gateway, the disaster recovery node needs to store the synchronization data sent by the disaster recovery gateway in the data storage component of the disaster recovery node and back it up through the disaster recovery node. Since the data storage component in the disaster recovery node is composed of a multi-layer protection structure, the disaster recovery node will not be destroyed immediately in the event of a major disaster. At this time, the disaster recovery node can transfer the data stored in the data storage component to the remote database, so that the data in the remote database is consistent with the main database, thereby ensuring the integrity of the business data.

[0043] It should be noted that since the data storage component of the disaster recovery node is composed of a multi-layer protection structure, in order to reduce costs, the main function of the disaster recovery node is to save the difference data between the off-site database and the main database. The disaster recovery node does not need to save a lot of data. Therefore, a small amount of data can be stored in the disaster recovery node, such as the latest 1-2 hours of data logs of the database, to ensure that in the event of a site-level failure in the main database, the disaster recovery node can also fill in the delayed off-site data to the off-site database to ensure that data is not lost.

[0044] For example, city A has a master database for processing large amounts of financial transaction data. According to the process of step S201, whenever the master database completes a transaction and generates corresponding data logs, the disaster recovery gateway will immediately capture these log information. Subsequently, the disaster recovery gateway forwards these data logs to the standby database located in the same city, achieving real-time same-city backup. At the same time, the data logs are also stored in the data storage components of the disaster recovery nodes in the same city to ensure that there are enough data recovery points when local site-level failures occur. Finally, the disaster recovery gateway sends the data logs to the off-site databases in cities B and C via the network. Although these off-site databases receive data in an asynchronous manner, after the data center in city A suffers a major disaster, the off-site databases can provide complete business data together with the data stored in the disaster recovery nodes, thereby providing necessary data recovery capabilities.

[0045] Step S202 : monitoring the first operating status of the primary database and the standby database through the disaster recovery node, and sending the disaster recovery data stored in the disaster recovery node to the remote database when the first operating status of the primary database and the standby database are both abnormal.

[0046] It should be noted that the first operating status refers to the health and operating indicators of the primary and standby databases, including but not limited to data integrity, service availability, system load, hardware fault detection, etc. Disaster recovery data refers to the synchronized data logs stored in the data storage component of the disaster recovery node. These logs contain all data change operations on the primary database in the recent period.

[0047] Specifically, the disaster recovery node also needs to monitor the first operating status of the primary database and the backup database, and when it detects that the first operating status is abnormal, it indicates that an emergency has occurred. At this time, the disaster recovery node will send the stored disaster recovery data (i.e., data logs) to all known off-site databases so that they can use these log information to restore data and re-establish data consistency, thereby quickly resuming business operations.

[0048] It should be noted that the disaster recovery node is independent of the data center, including the computer room, electricity, network, etc. When an infrastructure-level failure occurs in the data center, even if both the primary database and the backup database are abnormal, the disaster recovery node can independently send the saved log data to the remote data center in other cities. The remote data center restores the actual business data based on the log data sent by the disaster recovery node, thereby pulling up the business and providing external services to ensure stable business operation.

[0049] For example, if a power outage in City A's data center causes both the primary and standby databases to cease operation, the disaster recovery node will continuously evaluate the operational status of both databases through its built-in monitoring mechanism. If the primary operational status is confirmed to be abnormal, the disaster recovery node will urgently initiate a recovery process, immediately sending the disaster recovery data stored in its data storage components to the off-site databases in City B and City C. After receiving this disaster recovery data, the off-site databases can use log playback technology to reconstruct the data state before the disaster. This allows them to continue providing services even if the local data center fails completely, avoiding data loss and ensuring business continuity.

[0050] The method for processing backup data provided in the embodiment of the present application adopts a method of storing the synchronous data sent by the disaster recovery gateway in the data storage component of the disaster recovery node, wherein the data storage component is composed of a multi-layer protection structure, and the disaster recovery gateway is used to forward the synchronous data to the backup database, the disaster recovery node and the remote database when receiving the synchronous data sent by the primary database, wherein the remote database asynchronously stores the data in the primary database; the first operating status of the primary database and the backup database is monitored by the disaster recovery node, and when the first operating status of the primary database and the backup database are both abnormal, the disaster recovery data stored in the disaster recovery node is sent to the remote database. By utilizing the real-time data backup function of the disaster recovery node, it is achieved that when there is an abnormality in the primary database and the backup database, the latest data can be synchronized to the remote database through the disaster recovery node, thereby ensuring the timeliness and integrity of the data in the remote database, and achieving the purpose of quickly restoring data to the remote database, thereby realizing the technical effect of enhancing data high availability and reducing the risk of data loss. In other words, even if both the primary and backup databases in the same region fail, the presence of the disaster recovery node ensures the integrity and continuity of critical business data, effectively supporting rapid business recovery and avoiding business interruptions caused by data loss. This improves the robustness of the overall architecture and the stability of business processing. This addresses the technical issue in related technologies where the data stored in off-site disaster recovery databases is less up-to-date, leading to data loss in the event of a primary or backup database failure.

[0051] In order to ensure the consistency of the data stored in the disaster recovery node with the data in the main database, optionally, in the backup data processing method provided in the embodiment of the present application, after storing the synchronization data sent by the disaster recovery gateway in the data storage component of the disaster recovery node, the method also includes: suspending the business operation of the main database; judging whether the disaster recovery node has completed the storage operation of the synchronization data; and sending feedback information to the main database through the disaster recovery node when the disaster recovery node completes the storage operation, wherein the main database continues to perform business operation operations when receiving the feedback information.

[0052] Specifically, while the primary database sends data logs to the disaster recovery gateway, which then distributes them to the disaster recovery nodes and remote databases, the primary database's business operations are suspended to ensure data consistency and integrity. That is, the primary database will no longer accept new business requests until data synchronization is confirmed to be complete. This prevents data inconsistencies caused by new business operations during data synchronization and ensures high consistency between the disaster recovery data and the primary database data.

[0053] At this time, it is necessary to continuously monitor the status of the disaster recovery node, that is, the status of the data storage operation, so as to determine whether the disaster recovery node has successfully stored the synchronized data received from the primary database into its data storage component. When the disaster recovery node confirms that the storage of the latest synchronized data is completed, the disaster recovery node needs to send feedback information to the primary database, indicating that the data storage operation has been completed, so that the feedback information is used to notify the primary database to confirm that the disaster recovery node has successfully stored the synchronized data.

[0054] When the primary database receives feedback from the disaster recovery node and confirms that the latest data log has been safely stored, the primary database will release the business suspension status and resume processing business requests, thereby ensuring business continuity and data security. After confirming the availability of the disaster recovery data, the primary database can resume normal services, thereby ensuring the consistency of data storage in the disaster recovery node.

[0055] For example, assume that in City A's primary data center, the primary database is processing a large amount of financial transaction data. After a data update, the primary database sends the latest data logs to the disaster recovery node near City A and the off-site databases in Cities B and C via the disaster recovery gateway. To ensure data consistency, the primary database pauses accepting new transaction requests and waits for the disaster recovery node to confirm the completion of the data storage operation. After receiving the synchronized data, the disaster recovery node immediately stores the data in its data storage component. After the storage operation is complete, the disaster recovery node sends feedback to the primary database. After receiving the feedback from the disaster recovery node and confirming that the data synchronization is correct, the primary database immediately unpauses its services and resumes processing business requests. At this point, the primary database not only receives new data but also ensures that the data synchronized on the disaster recovery node is consistent with the local data, forming a solid foundation for business continuity and data security.

[0056] This embodiment ensures the consistency of data in the disaster recovery node and the data in the main database by suspending and resuming the business of the main database, thereby ensuring business continuity and data security, and improving the robustness and flexibility of the overall architecture.

[0057] In order to ensure the normal operation of the primary database, optionally, in the backup data processing method provided in the embodiment of the present application, after suspending the business operation of the primary database, the method also includes: determining the suspension duration of the business operation of the primary database; judging whether the suspension duration is greater than the preset duration; if the suspension duration is greater than the preset duration, determining that there is an abnormality in the disaster recovery node, and continuing to execute the business operation through the primary database.

[0058] Specifically, when the primary database suspends business operations, the disaster recovery node may have anomalies, resulting in the inability to send feedback information to the primary database, which in turn causes the primary database to remain in a suspended state. Therefore, it is necessary to record the length of time since the primary database stopped receiving new business requests, that is, the suspension duration, and compare the suspension duration with the preset duration. If the actual suspension time exceeds the preset duration, the anomaly detection mechanism will be triggered to promptly identify anomalies in the data synchronization and confirmation process, avoid long-term business stagnation, and ensure that business continuity is restored as quickly as possible under the premise of data security.

[0059] If the service suspension duration exceeds the preset safety threshold, the DR node may be considered to have experienced an anomaly (e.g., data storage failure, network interruption, etc.). In this case, to prevent the service interruption from impacting users, the primary database will resume receiving and processing service requests, even if DR data synchronization is not yet complete. This ensures business continuity for the primary database and allows for rapid service restoration even in the event of an DR node anomaly, minimizing any adverse impact on users.

[0060] For example, during a data synchronization process, after completing the data changes, the primary database planned to suspend business operations while waiting for the disaster recovery node to confirm that the data has been securely stored. The preset duration is 1 minute, meaning the disaster recovery node should complete data storage and send a confirmation signal within 1 minute. However, if the primary database still does not receive a confirmation signal after waiting for more than 1 minute, it determines that the disaster recovery node may have encountered a problem, such as a network communication failure. At this point, to ensure that business is not affected, the primary database will automatically resume accepting new business requests and continue processing business. Although disaster recovery data synchronization may not be complete, considering that the preset duration has taken into account the balance between business processing and data security, this mechanism can minimize business interruption time while ensuring data security, improving user experience and service quality.

[0061] This embodiment measures the duration of a pause and compares it to a preset duration, enabling timely identification of potential issues with the data storage process on the disaster recovery node. If the pause exceeds the preset duration, the primary database's operations are immediately resumed, avoiding the risk of service stagnation caused by waiting for data synchronization confirmation. Furthermore, this mechanism provides continuous monitoring of the health of the disaster recovery node, facilitating early warning and resolution of issues, reducing the likelihood of service interruptions.

[0062] In order to reduce the amount of data stored in the disaster recovery node and thereby reduce the operating cost of the disaster recovery node, optionally, in the backup data processing method provided in the embodiment of the present application, the method also includes: obtaining the data amount of each disaster recovery data stored in the disaster recovery node to obtain multiple data amounts; determining the total data amount of the disaster recovery data stored in the disaster recovery node based on the multiple data amounts, and judging whether the total data amount is greater than the data amount threshold; when the total data amount is greater than the data amount threshold, deleting the disaster recovery data in descending order according to the storage time of each disaster recovery data until the total data amount is less than or equal to the data amount threshold.

[0063] It's important to note that the volume of disaster recovery data refers to the storage space occupied by each piece of disaster recovery data (i.e., data log) stored on the disaster recovery node. The data volume threshold is the pre-set maximum amount of data that the disaster recovery node's data storage component can safely and efficiently carry. The storage duration is the time interval from the time the disaster recovery data is stored in the disaster recovery node's data storage component to the current moment.

[0064] Specifically, the disaster recovery node will traverse all the disaster recovery data stored in the disaster recovery node's data storage component at a set frequency, collecting the storage space occupied by each piece of data, thereby understanding the data usage in the current disaster recovery node storage component. After determining the storage space occupied by each piece of data, the collected data volume of each disaster recovery data piece is added together to determine the total data volume of all disaster recovery data in the current storage component. The total data volume is then compared with a preset data volume threshold to determine whether it exceeds the limit.

[0065] When the total amount of data in the data storage component of the disaster recovery node exceeds the threshold, the disaster recovery node will sort the disaster recovery data according to its storage time, and give priority to deleting the disaster recovery data with the longest storage time until the total amount of data in the storage component returns to below the threshold. By implementing the first-in-first-out principle, the utilization of storage space is optimized to ensure that the disaster recovery node can continuously receive and store new disaster recovery data, while keeping the data storage capacity in the disaster recovery node at a low level, thereby maintaining the timeliness and high availability of the data in the disaster recovery node.

[0066] This embodiment achieves effective utilization of disaster recovery data storage components and improves data processing efficiency through a refined data capacity management mechanism. First, regular data volume checks ensure that storage components do not reach saturation due to overuse, avoiding data synchronization failures and extended data recovery time. Second, a disaster recovery data cleanup strategy based on storage age ensures that disaster recovery nodes prioritize the most recent and relevant data, improving the accuracy and efficiency of data recovery and reducing recovery risks that may be introduced by outdated data.

[0067] In order to reduce the amount of data stored in the disaster recovery node and thereby reduce the operating cost of the disaster recovery node, optionally, in the backup data processing method provided in the embodiment of the present application, the method also includes: obtaining the timestamp of each disaster recovery data stored in the disaster recovery node to obtain multiple timestamps; calculating the time difference between each timestamp and the current moment, and determining in turn whether each time difference is greater than a time difference threshold; if there is a target time difference greater than the time difference threshold, deleting the disaster recovery data to which the target time difference belongs.

[0068] It should be noted that the timestamp of the disaster recovery data is the precise time point recorded when each piece of disaster recovery data is stored in the disaster recovery node, which is used to track the update and storage history of the data.

[0069] Specifically, the DR node automatically or periodically retrieves all DR data in the DR node's data storage component, extracts the storage timestamp for each piece of data, forms a list of all data storage time points, and calculates the time difference between each piece and the current time, representing the length of time the data has been stored. Each calculated time difference is then compared with a preset time difference threshold to identify and flag DR data that has been stored for too long, exceeding business requirements. This provides a basis for subsequent cleanup, ensuring data timeliness and space utilization within the data storage component.

[0070] If a piece of disaster recovery data is found to have been stored for longer than a preset time difference threshold, the disaster recovery node will automatically mark it as expired and delete it, freeing up the storage space it occupied. By promptly cleaning up expired disaster recovery data, we balance storage space usage with data timeliness, maintain the effective working state of the disaster recovery node's data storage components, and ensure that business data can be quickly and accurately restored when needed.

[0071] For example, suppose a large number of database logs are stored in the data storage component of the disaster recovery node, and each log has a precise storage timestamp. The preset time difference threshold can be 2 hours, that is, any disaster recovery data stored for more than 2 hours will be considered expired data. A database log stored 4 hours ago is found on the disaster recovery node, and the time difference between its timestamp and the current moment is 240 minutes (i.e. 4 hours). Since this time difference is greater than the time difference threshold, this log is marked as expired data and deleted from the data storage component, freeing up the storage space it occupies to accommodate more recent and more timely disaster recovery data.

[0072] This embodiment sets a reasonable time difference threshold and regularly clears data that exceeds this threshold, ensuring high data availability while avoiding waste of storage resources. This not only optimizes the storage performance of the disaster recovery node, but also speeds up data recovery and reduces potential recovery risks caused by data expiration.

[0073] Optionally, in the backup data processing method provided in an embodiment of the present application, the method also includes: monitoring the second operating state of the disaster recovery gateway; when the second operating state is abnormal, terminating the business operation of the primary database and switching the disaster recovery gateway until the second operating state of the disaster recovery gateway is normal.

[0074] It should be noted that the second operating state refers to the healthy operating status of the disaster recovery gateway during data synchronization and transmission, including but not limited to network connectivity, data transmission efficiency, and hardware health. To ensure the stability and accuracy of data synchronization operations, it is necessary to monitor the operating status of the disaster recovery gateway. Periodic health checks can be implemented on the disaster recovery gateway to monitor key indicators in real time, such as network latency, throughput, CPU and memory usage, and error logs, to ensure optimal operation. This allows for timely detection and warning of potential failures or performance degradation in the disaster recovery gateway, providing immediate information support for subsequent troubleshooting and recovery operations.

[0075] If the disaster recovery gateway detects abnormal operating status (such as excessive network latency, increased packet loss, or hardware failure alarms), the primary database's business write function must be immediately suspended to avoid data inconsistencies that may result from data synchronization under abnormal conditions. Simultaneously, the backup disaster recovery gateway can be activated to seamlessly take over data transmission tasks, ensuring the continuity and reliability of the data synchronization process.

[0076] This embodiment significantly enhances the stability and business continuity of the data synchronization architecture by monitoring the operating status of the disaster recovery gateway in real time and combining it with a rapid fault switching and recovery mechanism. On the one hand, it can quickly identify and isolate the faulty disaster recovery gateway, avoiding data transmission delays or data loss caused by gateway failures and ensuring the real-time and accurate data synchronization. On the other hand, by immediately enabling the backup gateway, data synchronization can be restored with almost no notice, ensuring that business is not affected and enhancing the overall system's fault resistance and user experience.

[0077] Optionally, in the backup data processing method provided in the embodiment of the present application, the method also includes: monitoring the second operating state of the disaster recovery gateway; when the second operating state is abnormal, the primary database synchronizes the synchronization data to the backup database through inter-database data synchronization until the second operating state of the disaster recovery gateway changes from abnormal to normal; when the second operating state of the disaster recovery gateway changes from abnormal to normal, the disaster recovery gateway executes the data synchronization operation between the primary database and the backup database.

[0078] Specifically, to ensure the stability and accuracy of data synchronization operations, it's important to monitor the operational status of the disaster recovery gateway. Periodic health checks can be implemented on the disaster recovery gateway to monitor key metrics in real time, such as network latency, throughput, CPU and memory usage, and error logs, to ensure optimal operation. This allows for timely detection and warning of potential failures or performance degradation in the disaster recovery gateway, providing immediate information support for subsequent troubleshooting and recovery operations.

[0079] When the disaster recovery gateway's monitoring results indicate it's in an abnormal state, it automatically adjusts the data synchronization path, establishing a direct connection between the primary and standby databases and executing data synchronization operations to ensure high data availability and consistency. While the primary and standby databases are directly synchronizing data, the faulty disaster recovery gateway can be monitored in real time until it returns to normal operation. Once the disaster recovery gateway returns to normal, it automatically switches back to the original data synchronization mode, with the disaster recovery gateway reassuming the data synchronization task, including reestablishing the connection with the standby database and restoring normal data flow transmission. This restores the data synchronization architecture to its optimal state, maximizing data synchronization efficiency and data processing performance, while also reducing the direct synchronization load on the primary database.

[0080] This embodiment ensures data continuity and integrity, thereby guaranteeing business continuity, by directly synchronizing databases when the disaster recovery gateway experiences an operational anomaly. Once the disaster recovery gateway recovers, it quickly returns to its initial, efficient synchronization state. Overall, this approach effectively reduces the data processing risks associated with disaster recovery gateway failures while balancing data synchronization performance and cost, significantly improving the reliability of data management within financial institutions.

[0081] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0082] Example 2

[0083] The embodiment of the present application further provides a backup data processing system. It should be noted that the backup data processing system of the embodiment of the present application can be used to execute the backup data processing method provided in the above embodiment. The backup data processing system provided in the embodiment of the present application is introduced below.

[0084] Figure 3 Schematic diagram of a data backup processing system according to Example 2 of the present application. Figure 3 As shown, the system includes:

[0085] The main database 31 is used to receive business data, generate synchronization data according to the business data, and send the synchronization data to the disaster recovery gateway 32.

[0086] Specifically, the master database 31 generates real-time data changes or log information when performing data update operations, and synchronizes the above data to the disaster recovery gateway 32 to ensure data consistency, and sends it to multiple databases through the disaster recovery gateway 32.

[0087] The disaster recovery gateway 32 is used to receive synchronization data and forward the synchronization data to the standby database 34, the disaster recovery node 33 and the remote database 35.

[0088] Specifically, when receiving the synchronization data, the disaster recovery gateway 32 needs to send the synchronization data to the standby database 34, the disaster recovery node 33 and the remote database 35, thereby sending the synchronization data to all databases that need to be synchronized.

[0089] The disaster recovery node 33 is used to monitor the first operating status of the primary database 31 and the backup database 34, and when the first operating status of the primary database 31 and the backup database 34 are both abnormal, the disaster recovery data stored in the disaster recovery node 33 is sent to the remote database 35.

[0090] Specifically, the disaster recovery node 33 needs to send data to the remote database 35 when the main database 31 and the backup database 34 are abnormal, so as to obtain complete data in the remote database 35 and ensure that the business can proceed normally through the data in the remote database 35.

[0091] The standby database 34 is used to synchronously store data in the primary database 31 .

[0092] The remote database 35 is used to asynchronously store the data in the main database 31 .

[0093] Example 3

[0094] The embodiment of the present application further provides a backup data processing device. It should be noted that the backup data processing device of the embodiment of the present application can be used to execute the backup data processing method provided in the above embodiment. The backup data processing device provided in the embodiment of the present application is introduced below.

[0095] According to an embodiment of the present application, a device for implementing the above-mentioned method for processing backup data is also provided. Figure 4 Schematic diagram of a backup data processing device according to Example 3 of the present application. Figure 4 As shown, the device includes:

[0096] The storage unit 41 is used to store the synchronous data sent by the disaster recovery gateway in the data storage component of the disaster recovery node, wherein the data storage component is composed of a multi-layer protection structure. The disaster recovery gateway is used to forward the synchronous data to the backup database, the disaster recovery node and the remote database when receiving the synchronous data sent by the primary database, wherein the remote database asynchronously stores the data in the primary database.

[0097] The first sending unit 42 is used to monitor the first operating status of the primary database and the standby database through the disaster recovery node, and when the first operating status of the primary database and the standby database are both abnormal, send the disaster recovery data stored in the disaster recovery node to the remote database.

[0098] The backup data processing device provided in the embodiment of the present application stores the synchronization data sent by the disaster recovery gateway in the data storage component of the disaster recovery node through the storage unit 41, wherein the data storage component is composed of a multi-layer protection structure, and the disaster recovery gateway is used to forward the synchronization data to the backup database, the disaster recovery node and the remote database when receiving the synchronization data sent by the main database, wherein the remote database asynchronously stores the data in the main database; the first sending unit 42 monitors the first operating status of the main database and the backup database through the disaster recovery node, and sends the disaster recovery data stored in the disaster recovery node to the remote database when the first operating status of the main database and the backup database are both abnormal. By utilizing the real-time data backup function of the disaster recovery node, it is achieved that when there is an abnormality in the main database and the backup database, the latest data can be synchronized to the remote database through the disaster recovery node, thereby ensuring the timeliness and integrity of the data in the remote database, and achieving the purpose of quickly restoring data to the remote database, thereby achieving the technical effect of enhancing data high availability and reducing the risk of data loss. In other words, even if both the primary and backup databases in the same region fail, the presence of the disaster recovery node ensures the integrity and continuity of critical business data, effectively supporting rapid business recovery and avoiding business interruptions caused by data loss. This improves the robustness of the overall architecture and the stability of business processing. This addresses the technical issue in related technologies where the data stored in off-site disaster recovery databases is less up-to-date, leading to data loss in the event of a primary or backup database failure.

[0099] Optionally, in the backup data processing device provided in an embodiment of the present application, after the synchronization data sent by the disaster recovery gateway is stored in the data storage component of the disaster recovery node, the device also includes: a pause unit, used to pause the business operation of the main database; a first judgment unit, used to judge whether the disaster recovery node has completed the storage operation of the synchronization data; a second sending unit, used to send feedback information to the main database through the disaster recovery node when the disaster recovery node completes the storage operation, wherein the main database continues to perform business operation operations after receiving the feedback information.

[0100] Optionally, in the backup data processing device provided in the embodiment of the present application, after suspending the business operation of the main database, the device also includes: a first determination unit, used to determine the suspension duration of the business operation of the main database; a second judgment unit, used to judge whether the suspension duration is greater than the preset duration; the second determination unit is used to determine that there is an abnormality in the disaster recovery node when the suspension duration is greater than the preset duration, and continue to execute business operation operations through the main database.

[0101] Optionally, in the backup data processing device provided in the embodiment of the present application, the device also includes: a first acquisition unit, used to obtain the data volume of each disaster recovery data stored in the disaster recovery node to obtain multiple data volumes; a third judgment unit, used to determine the total data volume of the disaster recovery data stored in the disaster recovery node based on the multiple data volumes, and judge whether the total data volume is greater than the data volume threshold; a first deletion unit, used to delete the disaster recovery data in descending order of the storage time of each disaster recovery data when the total data volume is greater than the data volume threshold, until the total data volume is less than or equal to the data volume threshold.

[0102] Optionally, in the backup data processing device provided in the embodiment of the present application, the device also includes: a second acquisition unit, used to obtain the timestamp of each disaster recovery data stored in the disaster recovery node to obtain multiple timestamps; a fourth judgment unit, used to calculate the time difference between each timestamp and the current moment, and judge in turn whether each time difference is greater than the time difference threshold; a second deletion unit, used to delete the disaster recovery data to which the target time difference belongs when there is a target time difference greater than the time difference threshold.

[0103] Optionally, in the backup data processing device provided in the embodiment of the present application, the device also includes: a first monitoring unit, used to monitor the second operating state of the disaster recovery gateway; a switching unit, used to terminate the business operation of the primary database and switch the disaster recovery gateway when the second operating state is abnormal until the second operating state of the disaster recovery gateway is normal.

[0104] Optionally, in the backup data processing device provided in the embodiment of the present application, the device also includes: a second monitoring unit, used to monitor the second operating state of the disaster recovery gateway; a synchronization unit, used to synchronize the synchronization data to the backup database by the primary database through inter-database data synchronization when the second operating state is abnormal, until the second operating state of the disaster recovery gateway changes from abnormal to normal; an execution unit, used to execute the data synchronization operation between the primary database and the backup database by the disaster recovery gateway when the second operating state of the disaster recovery gateway changes from abnormal to normal.

[0105] It should be noted that the above-mentioned storage unit 41 and first sending unit 42 correspond to steps S201 to S202 in Example 1. The examples and application scenarios implemented by the above-mentioned storage unit 41 and first sending unit 42 are the same as those of the corresponding steps, but are not limited to the contents disclosed in the above-mentioned Example 1. It should be noted that the above-mentioned modules or units can be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n). The above-mentioned modules can also be part of the device and can be run in the computer terminal 10 provided in Example 1.

[0106] Example 4

[0107] An embodiment of the present application may provide an electronic device, Figure 5 This is a structural block diagram of an electronic device according to an embodiment of the present application. Figure 5 As shown, the electronic device may include: one or more ( Figure 5 Only one is shown) processor 1002, memory 1004, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0108] Among them, the memory can be used to store software programs and modules, such as program instructions / modules corresponding to the methods and devices in the embodiments of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, implementing the above-mentioned method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network and a combination thereof.

[0109] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: storing the synchronous data sent by the disaster recovery gateway in the data storage component of the disaster recovery node, wherein the data storage component is composed of a multi-layer protection structure, and the disaster recovery gateway is used to forward the synchronous data to the backup database, the disaster recovery node and the remote database when receiving the synchronous data sent by the primary database, wherein the remote database asynchronously stores the data in the primary database; monitoring the first operating status of the primary database and the backup database through the disaster recovery node, and sending the disaster recovery data stored in the disaster recovery node to the remote database when the first operating status of the primary database and the backup database are both abnormal.

[0110] The processor can also call the information and applications stored in the memory through the transmission device to perform the following steps: suspend the business operation of the main database; determine whether the disaster recovery node has completed the storage operation of the synchronized data; when the disaster recovery node completes the storage operation, send feedback information to the main database through the disaster recovery node, wherein the main database continues to perform business operation operations after receiving the feedback information.

[0111] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: determine the suspension duration of the business operation of the main database; determine whether the suspension duration is greater than the preset duration; if the suspension duration is greater than the preset duration, determine that there is an abnormality in the disaster recovery node, and continue to perform business operation operations through the main database.

[0112] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: obtain the data volume of each disaster recovery data stored in the disaster recovery node to obtain multiple data volumes; determine the total data volume of the disaster recovery data stored in the disaster recovery node based on the multiple data volumes, and judge whether the total data volume is greater than the data volume threshold; when the total data volume is greater than the data volume threshold, delete the disaster recovery data in descending order according to the storage time of each disaster recovery data until the total data volume is less than or equal to the data volume threshold.

[0113] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: obtain the timestamp of each disaster recovery data stored in the disaster recovery node to obtain multiple timestamps; calculate the time difference between each timestamp and the current moment, and determine in turn whether each time difference is greater than the time difference threshold; if there is a target time difference greater than the time difference threshold, delete the disaster recovery data to which the target time difference belongs.

[0114] The processor can also call the information and applications stored in the memory through the transmission device to perform the following steps: monitor the second operating state of the disaster recovery gateway; if the second operating state is abnormal, terminate the business operation of the main database and switch the disaster recovery gateway until the second operating state of the disaster recovery gateway is normal.

[0115] The processor can also call the information and applications stored in the memory through the transmission device to perform the following steps: monitor the second operating state of the disaster recovery gateway; when the second operating state is abnormal, the primary database synchronizes the synchronization data to the backup database through inter-database data synchronization until the second operating state of the disaster recovery gateway changes from abnormal to normal; when the second operating state of the disaster recovery gateway changes from abnormal to normal, the disaster recovery gateway performs data synchronization operations between the primary database and the backup database.

[0116] It can be understood by those skilled in the art that Figure 5 The structure shown is for illustration only, and the electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (MID), a PAD, or other terminal devices. Figure 5 It does not limit the structure of the above electronic device. For example, the electronic device may also include Figure 5 More or fewer components (such as network interfaces, display devices, etc.) shown in, or with Figure 5 Different configurations shown.

[0117] A person skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0118] Example 5

[0119] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the backup data processing method provided in the first embodiment.

[0120] Optionally, in this embodiment, the storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0121] An embodiment of the present application further provides a computer program product, which, when executed on a data processing device, is suitable for executing the steps of the method for processing backup data.

[0122] An embodiment of the present application further provides a computer-readable storage medium, which includes a stored executable program, wherein when the executable program runs, the device where the computer-readable storage medium is located is controlled to execute the above-mentioned backup data processing method.

[0123] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0124] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0125] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0126] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of the solution of this embodiment according to actual needs.

[0127] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0128] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0129] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for processing backup data, characterized in that: include: The synchronization data sent by the disaster recovery gateway is stored in the data storage component of the disaster recovery node, wherein the data storage component is composed of a multi-layer protection structure, and the disaster recovery gateway is used to forward the synchronization data sent by the primary database to the standby database, the disaster recovery node and the remote database when receiving the synchronization data, wherein the remote database asynchronously stores the data in the primary database; The first operating status of the primary database and the standby database is monitored by a disaster recovery node, and when the first operating status of the primary database and the standby database are both abnormal, the disaster recovery data stored in the disaster recovery node is sent to the remote database.

2. The method according to claim 1, characterized in that After storing the synchronization data sent by the disaster recovery gateway into the data storage component of the disaster recovery node, the method further includes: Suspending the business operation of the primary database; Determining whether the disaster recovery node has completed the storage operation of the synchronization data; When the disaster recovery node completes the storage operation, feedback information is sent to the primary database through the disaster recovery node, wherein the primary database continues to perform the business operation after receiving the feedback information.

3. The method according to claim 2, characterized in that After suspending the service operation of the primary database, the method further includes: Determining a suspension duration for suspending the business operation by the primary database; Determining whether the pause duration is greater than a preset duration; When the suspension time is longer than the preset time, it is determined that an abnormality exists in the disaster recovery node, and the business operation is continued to be executed through the primary database.

4. The method according to claim 1, wherein The method further comprises: Acquire the data volume of each piece of disaster recovery data stored in the disaster recovery node to obtain multiple data volumes; Determining a total data volume of the disaster recovery data stored in the disaster recovery node according to the multiple data volumes, and judging whether the total data volume is greater than a data volume threshold; When the total data volume is greater than the data volume threshold, the disaster recovery data is deleted in descending order of storage duration of each disaster recovery data until the total data volume is less than or equal to the data volume threshold.

5. The method according to claim 1, characterized in that The method further comprises: Obtaining the timestamp of each piece of disaster recovery data stored in the disaster recovery node to obtain multiple timestamps; Calculate the time difference between each timestamp and the current time, and determine whether each time difference is greater than the time difference threshold in turn; In the case that there is a target time difference greater than the time difference threshold, the disaster recovery data to which the target time difference belongs is deleted.

6. The method according to claim 1, characterized in that The method further comprises: Monitoring a second operating state of the disaster recovery gateway; In the case that the second operating state is abnormal, the business operation of the primary database is terminated, and the disaster recovery gateway is switched until the second operating state of the disaster recovery gateway is normal.

7. The method according to claim 1, characterized in that The method further comprises: Monitoring a second operating state of the disaster recovery gateway; When the second operating state is abnormal, the primary database synchronizes the synchronization data to the standby database through inter-database data synchronization until the second operating state of the disaster recovery gateway changes from abnormal to normal; When the second operation state of the disaster recovery gateway changes from abnormal to normal, the disaster recovery gateway performs a data synchronization operation between the primary database and the standby database.

8. A backup data processing system, characterized in that: include: The main database is used to receive business data, generate synchronization data based on the business data, and send the synchronization data to the disaster recovery gateway; The disaster recovery gateway is used to receive the synchronization data and forward the synchronization data to the standby database, the disaster recovery node and the remote database; a disaster recovery node, configured to monitor the first operating states of the primary database and the standby database, and, when the first operating states of the primary database and the standby database are both abnormal, send the disaster recovery data stored in the disaster recovery node to the remote database; The standby database is used to synchronously store the data in the primary database; The remote database is used to asynchronously store the data in the primary database.

9. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by a processor, the steps of the backup data processing method according to any one of claims 1 to 7 are implemented.

10. An electronic device, characterized in that: include: a memory storing an executable program; A processor is used to run the program, wherein the program executes the backup data processing method according to any one of claims 1 to 7 when running.

Images