Disaster recovery processing method and device of data center and computer equipment

Abstract

The application relates to the field of data processing, in particular to a disaster recovery processing method and device of a data center, computer equipment, a computer readable storage medium and a computer program product. In one embodiment, disaster information of a first data center can be acquired, and a disaster accident type is identified. According to the disaster accident type and preset takeover rules, the data takeover authority of a target business scene of the data center can be confirmed. In this way, according to the data takeover authority, other data centers can take over data processing tasks in different business scenes at different levels, so that the continuity of system business is guaranteed, and the security of data is improved.

Description

Technical Field

[0001] This disclosure relates to the field of data processing, and more particularly to a disaster recovery processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product for a data center. Background Technology

[0002] With the development of data processing technologies such as big data computing, data centers that handle data processing tasks are becoming increasingly large. A single computer or server cannot meet the data processing demands, and more and more business systems rely on centrally deployed data centers to maintain operation. In this situation, in the event of an emergency such as a natural disaster or accident, the data center may come to a standstill, causing data processing tasks to stall and business processes to be forced to interrupt.

[0003] To address potential disasters, a common disaster recovery technology involves establishing dual data centers in different locations. If one data center is affected by a disaster or experiences a sudden failure, the other data center can take over the data processing tasks. However, this dual-data center technology can only perform simple data transfers. When faced with more complex business scenarios, it struggles to fully handle the data processing tasks involved, failing to guarantee business continuity and posing a higher risk to data security. Summary of the Invention

[0004] Based on this, and to address the aforementioned technical problems, a disaster recovery processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product for data centers are provided. The technical solution of this disclosure is as follows:

[0005] According to one aspect of the embodiments of this disclosure, a disaster recovery method for a data center is provided, comprising:

[0006] Obtain the disaster / accident type for the first data center;

[0007] According to the preset takeover rules, the data takeover permissions corresponding to the target business scenario of the first data center under the disaster type are confirmed;

[0008] Based on the data takeover permissions, the data processing tasks in the target business scenario are taken over.

[0009] In one embodiment, the data takeover permission includes level one permission, and the step of taking over the data processing tasks in the target business scenario according to the data takeover permission includes:

[0010] When the data takeover permission is at level one, takeover is performed on data processing tasks that are unrelated to data modification in the target business scenario.

[0011] In one embodiment, the data takeover permission includes a second-level permission, and the takeover of the data processing task in the target business scenario according to the data takeover permission includes:

[0012] When the data takeover permission is at level two, takeover is performed on data processing tasks that are not associated with preceding tasks in the target business scenario.

[0013] In one embodiment, prior to obtaining the disaster incident type of the first data center, the method further includes:

[0014] The system periodically accesses the database in the first data center, copies the data from the database, and stores it in a local database.

[0015] In one embodiment, before taking over the data processing task in the target business scenario according to the data takeover permission, the method further includes:

[0016] Query the data in the local database and adjust the data takeover permissions.

[0017] In one embodiment, prior to obtaining the disaster incident type of the first data center, the method further includes:

[0018] Obtain the data communication partner of the first data center, and the first communication line between the first data center and the data communication partner;

[0019] A second communication line is established with the data communication party based on the first communication line.

[0020] According to another aspect of the embodiments of this disclosure, a disaster recovery processing apparatus for a data center is provided, comprising:

[0021] The incident acquisition module is used to acquire the types of disasters and incidents in the first data center;

[0022] The permission confirmation module is used to confirm the data takeover permission of the target business scenario of the first data center under the disaster type according to the preset takeover rules.

[0023] The task takeover module is used to take over the data processing tasks in the target business scenario according to the data takeover permissions.

[0024] According to another aspect of the embodiments of this disclosure, a disaster recovery system for a data center is also provided, comprising at least two data centers, each of the data centers comprising:

[0025] A multi-point access module is used for communication connections with external systems;

[0026] The routing module is used to allocate received data processing tasks according to preset multi-dimensional routing rules;

[0027] A tiered takeover module is used to take over data processing tasks from other data centers; the tiered takeover module includes the disaster recovery processing device as described in the above embodiments.

[0028] The operations and maintenance module is used to monitor the operational status of the data center;

[0029] A database is used to store data related to data processing tasks; the database includes a data synchronization module for replicating data from other data centers.

[0030] According to another aspect of the present disclosure, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the above-described method.

[0031] According to another aspect of the present disclosure, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the above-described method.

[0032] The technical solution provided in this disclosure embodiment can obtain disaster information from a first data center and identify the type of disaster. Based on the type of disaster and preset takeover rules, data takeover authority for the target business scenario of that data center can be confirmed. Thus, based on the data takeover authority, other data centers can perform tiered takeover of data processing tasks in different business scenarios, ensuring the continuity of system services and improving data security.

[0033] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0035] Figure 1 This is a flowchart illustrating a disaster recovery method for a data center in one embodiment.

[0036] Figure 2 This is a flowchart illustrating a disaster recovery method for a data center in another embodiment;

[0037] Figure 3 This is a flowchart illustrating a disaster recovery method for a data center in another embodiment;

[0038] Figure 4 This is a flowchart illustrating a disaster recovery method for a data center in another embodiment;

[0039] Figure 5 This is a flowchart illustrating a disaster recovery method for a data center in another embodiment;

[0040] Figure 6 This is a flowchart illustrating a disaster recovery method for a data center in another embodiment;

[0041] Figure 7 This is a schematic diagram of the structure of a disaster recovery processing device for a data center in one embodiment;

[0042] Figure 8 This is a schematic diagram of the internal structure of a computer device in one embodiment. Detailed Implementation

[0043] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0044] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims. The terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, product, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, product, or apparatus. Without further limitation, the presence of other identical or equivalent elements in a process, method, product, or apparatus that includes said elements is not excluded. For example, the use of terms such as "first," "second," etc., is to denote names and does not indicate any specific order.

[0045] The terms “vertical,” “horizontal,” “left,” “right,” “up,” “down,” “front,” “back,” “circumferential,” “direction of travel,” and similar expressions used herein are based on the orientation or positional relationship shown in the accompanying drawings and are used only for the convenience of describing the invention and simplifying the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention.

[0046] Unless otherwise defined, the technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. The terminology used herein in the specification of this invention is for the purpose of describing particular embodiments only and is not intended to limit the invention. The terms “and / or,” “and / or,” and “at least one of” as used herein include any and all combinations of one or more of the associated listed items. It should be noted that the connections, links, etc., described in this disclosure can be direct connections via interfaces or pins between devices, connections via leads, or wireless connections (communication connections).

[0047] Traditional disaster recovery methods typically involve establishing idle disaster recovery centers in the same city or a different city. These centers are only activated when a normally functioning data center fails due to a disaster. While this approach can resolve data center outages, the time required for data recovery and system failover is excessive, and the long periods of idleness at these centers prevent the effective utilization of hardware resources.

[0048] Therefore, a dual-active architecture has emerged as a solution in related technologies, where two data centers operate simultaneously. Even if one data center fails, services can be transferred to the other, functioning data center. However, in complex business systems such as financial and logistics systems, the logical structures between different business scenarios vary greatly, and there are numerous situations requiring the cooperation of front-end services. Existing dual-active solutions rely on relatively simple methods for data and service transfer, making it difficult to guarantee business continuity in such complex scenarios and posing significant security risks to certain sensitive data.

[0049] To address the aforementioned problems, according to one aspect of an embodiment of this disclosure, such as Figure 1 As shown, a disaster recovery method for data centers is provided, which can be applied to a system containing multiple data centers, such as a first data center, a second data center, a third data center, etc. The disaster recovery method includes:

[0050] Step S210: Obtain the disaster / accident type of the first data center.

[0051] The first data center can be a data center facing a disaster. The type of disaster can be based on a pre-defined category of disaster. For example, disasters such as earthquakes and tsunamis that destroy data center equipment can be classified as mega-disasters, while disasters such as power grid failures that make it difficult for data centers to recover within a certain period of time can be classified as major disasters.

[0052] Specifically, when a disaster occurs in the first data center, disaster information can be obtained first, and the type of disaster can be determined based on the disaster information.

[0053] Step S220: Based on the preset takeover rules, confirm the data takeover permissions corresponding to the target business scenario of the first data center under the disaster / accident type.

[0054] The preset takeover rules can be determined based on the type of disaster and the characteristics of different data processing tasks. The data takeover authority can be the authority of other data centers to take over the business scenarios of the first data center. The business scenario can represent the type of data processing task handled by the data center; for example, in the business system of an online shopping platform, business scenarios can include address modification, shopping cart item removal, and order payment. The target business scenario can be the business scenario of the data processing task that needs to be taken over by the data center in the event of a disaster.

[0055] Specifically, based on the type of disaster and the takeover rules, the data takeover permissions of other data centers for the target business scenarios of the first data center can be determined. For example, if the disaster type of the first data center is a large-scale incident, and the first data center can recover after a period of time, to ensure data security, low-level takeover permissions can be assigned to business scenarios with high importance, such as those involving data modification or confidential data, while high-level takeover permissions can be assigned to business scenarios with lower importance, such as those involving data querying. The low-level takeover permissions may include only being able to modify address information and not being able to modify transaction amounts, while the high-level takeover permissions may include querying all data in the target business scenario. In some other implementations, if the disaster type of the first data center is a very large-scale incident, such as the first data center being unable to recover, to ensure the normal operation of the first data center's business, high-level takeover permissions can be assigned to data processing tasks in all business scenarios.

[0056] It should be noted that if there is more than one other data center, confirming the data takeover rights of other data centers over the target business scenario of the first data center may include assigning the takeover rights of the first data center to any of the other data centers, or it may include assigning the data takeover rights of the first data center for different business scenarios to multiple different data centers. Specifically, assigning the data takeover rights of the first data center for different business scenarios to multiple different data centers can be done based on the data processing methods, trust levels, and other characteristics of the different data centers.

[0057] Step S230: Take over the data processing tasks in the target business scenario according to the data takeover permissions.

[0058] Data processing tasks can include data querying, data modification, etc.

[0059] Specifically, data centers other than the first data center in the system can take over data processing tasks in the target business scenarios within the first data center according to their data takeover permissions. For example, when the system is a business system of an online shopping platform or a financial system for managing user deposits, and the disaster incident type in the first data center is a major incident, the second data center can take over other business scenarios in the first data center except for order payment, and handle all data processing tasks such as data querying and data modification in the other business scenarios in the first data center.

[0060] The technical solution provided in this disclosure embodiment can obtain disaster information from a first data center and identify the type of disaster. Based on the type of disaster and preset takeover rules, data takeover authority for the target business scenario of that data center can be confirmed. Thus, based on the data takeover authority, other data centers can perform tiered takeover of data processing tasks in different business scenarios, ensuring the continuity of system services and improving data security.

[0061] In one embodiment, the data takeover permission includes level one permission, such as... Figure 2 As shown, the step of taking over the data processing tasks in the target business scenario according to the data takeover permission includes:

[0062] Step S2302: When the data takeover permission is at level 1, take over the data processing tasks that are unrelated to data modification in the target business scenario.

[0063] The first-level authority is determined by the type of disaster or accident and the preset takeover rules.

[0064] Specifically, other data centers, based on the aforementioned Level 1 permissions, can take over data processing tasks unrelated to data modification in certain specific business scenarios of the first data center. These data processing tasks unrelated to data modification may include data queries, etc.

[0065] In the above embodiments, after confirming Level 1 permissions for the target business scenario, other data centers can take over data processing tasks such as data queries from the first data center under that target business scenario based on Level 1 permissions. In this way, in the event of a disaster at the first data center, other data centers can take over data processing tasks for certain business scenarios, avoiding business interruptions caused by the failure of the first data center, and ensuring that the data is not modified, thus improving data security.

[0066] In one embodiment, the data takeover permission includes second-level permissions, such as... Figure 3 As shown, the step of taking over the data processing tasks in the target business scenario according to the data takeover permission includes:

[0067] Step S2304: When the data takeover permission is at level two, take over the data processing task that is not associated with the preceding task in the target business scenario.

[0068] Among these, data processing tasks without associated prerequisite tasks can be independent tasks such as modifying user information. If the data processing task is order confirmation, which is associated with the task that previously generated the order, then it does not belong to the category of data processing tasks without associated prerequisite tasks.

[0069] Specifically, other data centers, based on the aforementioned secondary permissions, can take over data processing tasks in certain specific business scenarios of the first data center that are not associated with preceding tasks.

[0070] In the above embodiments, after confirming the level-two permissions for the target business scenario, other data centers can take over the independent data processing tasks of the first data center under that target business scenario based on the level-two permissions. In this way, in the event of a disaster at the first data center, other data centers can take over some data processing tasks in some business scenarios that do not have associated prerequisite tasks, allowing the system to still provide some relatively independent services and improving the system's high availability.

[0071] In one embodiment, such as Figure 4 As shown, before obtaining the disaster incident type for the first data center, the following steps are also included:

[0072] Step S200: Periodically access the database of the first data center, copy the data in the database and store it in the local database.

[0073] Specifically, other data centers can periodically access the database of the first data center through non-intrusive access methods, and copy and store the data in the database into their own databases.

[0074] In the above embodiments, by periodically accessing the database of the first data center, the data processed by the first data center can be effectively backed up and transferred. This way, in the event of a disaster at the first data center, backup data can be retained to prevent the loss of valid data, thus improving the reliability of system data.

[0075] In one embodiment, such as Figure 5 As shown, before taking over the data processing tasks in the target business scenario according to the data takeover permissions, the process also includes:

[0076] Step S222: Query the data in the local database and adjust the data takeover permissions.

[0077] Specifically, before a disaster occurs, other data centers, such as a second data center, can copy data from the first data center and store it in a local database. Based on the data stored in the local database, the established data takeover permissions can be adjusted. For example, if the second data center only has level two permissions for the target business scenario of the first data center and cannot take over data processing tasks with prerequisite tasks, but after querying the local database, it is found that the data of the prerequisite tasks related to the data processing task has been stored in the local database, then the level two permissions can be adjusted to level three permissions, and all data processing tasks under the target business scenario can be taken over based on the level three permissions.

[0078] In the above embodiments, by backing up and transferring data, and querying the local database, the confirmed data takeover permissions can be adjusted. In this way, with the preceding task data already existing in the local database, other data centers can take over all data processing tasks in the target business scenario of the first data center, effectively ensuring the business continuity of the system's data processing.

[0079] In one embodiment, such as Figure 6 As shown, before obtaining the disaster incident type for the first data center, the following steps are also included:

[0080] Step S202: Obtain the data communication party of the first data center and the first communication line between the first data center and the data communication party.

[0081] Among them, the data communication party can be a terminal that sends data to the system and / or receives data sent by the system to other parties.

[0082] Specifically, before obtaining the type of disaster, the second data center can obtain the terminal that transmits data with the first data center in advance through periodic access or other means, and obtain the first communication line between the first data center and the terminal for data transmission.

[0083] Step S204: Establish a second communication line with the data communication party based on the first communication line.

[0084] Specifically, based on the first communication line, the second data center can establish a second communication line with the data communication party to transmit data. In some other embodiments, other data centers, such as a third data center, can also establish other communication lines with the data communication party.

[0085] In the above embodiments, before a disaster occurs, other data centers can obtain the terminal that transmits data with the first data center through periodic access or other means, and establish a corresponding communication line with the terminal based on the first communication line. Thus, after a disaster occurs, other data centers can transmit data with the terminal through the corresponding communication line, ensuring that data corresponding to the terminal can be sent and received normally, avoiding interruption of data processing tasks, and enhancing the continuity of system services.

[0086] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0087] According to another aspect of the embodiments of this disclosure, such as Figure 7 As shown, a disaster recovery processing device for a data center is also provided, comprising:

[0088] The incident acquisition module 310 is used to acquire the types of disaster incidents in the first data center;

[0089] The permission confirmation module 320 is used to confirm the data takeover permission corresponding to the target business scenario of the first data center under the disaster type according to the preset takeover rules.

[0090] The task takeover module 330 is used to take over the data processing tasks in the target business scenario according to the data takeover permissions.

[0091] For specific limitations regarding the aforementioned processing device, please refer to the limitations of the aforementioned processing method above, which will not be repeated here. According to the aforementioned processing method, the processing device can be supplemented with a first module, a second module, etc., to implement the steps in the corresponding method embodiments. Each module in the aforementioned processing device can be implemented entirely or partially through software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor in the computer device in hardware form, or it can be stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0092] According to another aspect of the embodiments of this disclosure, a disaster recovery system for a data center is also provided, comprising at least two data centers, each of the data centers comprising:

[0093] The multi-point access module is used for communication connections with external systems.

[0094] Specifically, multi-point access modules from multiple data centers can be jointly deployed, forming a network access layer through cross-connection and / or U-shaped network structures. This improves network reliability by enabling multi-active operation across multiple data centers at the network access layer. Furthermore, when processing data services, the application layer can select the data center closer to the data communication party, avoiding network latency associated with cross-center transmission and effectively shortening service response time.

[0095] The routing module is used to allocate received data processing tasks according to preset multi-dimensional routing rules.

[0096] Specifically, based on preset multi-dimensional routing rules, the routing module can distribute data processing tasks to different data centers for processing according to elements such as business code and sending organization identifier. In some other embodiments, the routing rules also support different levels of priority configuration depending on the business scenario to which the data processing task belongs.

[0097] A hierarchical takeover module is used to take over data processing tasks from other data centers; the hierarchical takeover module includes the disaster recovery processing device in the above embodiments.

[0098] The operations and maintenance module is used to monitor the operational status of the data center.

[0099] Specifically, the operation and maintenance module includes a monitoring unit for each node in the data center, which can monitor the operating status, real-time performance, memory space, task completion rate, and abnormal task distribution of each node, and generate a system performance analysis report based on the information. The operation and maintenance module also includes a fault diagnosis unit, which can check for single point of failure, cross-data center task timeout, message queue congestion, consistency of key information across multiple data centers, and abnormal response code thresholds, and call the corresponding troubleshooting script to resolve the fault based on the cause of the fault, and can also generate a fault analysis report.

[0100] A database is used to store data related to data processing tasks; the database includes a data synchronization module for replicating data from other data centers.

[0101] Specifically, the data synchronization module can access databases in other data centers through a non-intrusive data access method, and extract, deliver, and copy data from these databases. This enables second-level data synchronization between multiple data centers. If a disaster occurs in one data center, services can be quickly switched to other data centers to avoid interruption, thus improving the system's disaster recovery capabilities.

[0102] In some other embodiments, the system further includes a disaster recovery module. This module pre-stores pre-written scripts that, when executed, can switch or transfer services processed by different data centers, and make corresponding adjustments to related parameters, application startup and shutdown, variable updates, and routing policies. In this way, by completing the data center service switchover through scripting, the system can achieve a second-level RPO (Recovery Point Object) and a minute-level RTO (Recovery Time Object) for system data services.

[0103] According to another aspect of the embodiments of this disclosure, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 8As shown, the computer device includes a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements the aforementioned processing methods. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0104] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0105] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0106] According to another aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0107] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in this application can include at least one relational database and non-relational database. Non-relational databases can include blockchain-based distributed databases, etc., and are not limited thereto. The processors involved in the various embodiments provided in this application may be general-purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited thereto.

[0108] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0109] The embodiments described above are merely illustrative of several implementations of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art, upon considering the specification and practicing the invention disclosed herein, will readily conceive of other embodiments of this disclosure. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0110] It should be understood that this disclosure is not limited to the precise structures already described and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope.

Claims

1. A disaster recovery method for a data center, characterized in that, include: Periodically access the database of the first data center, copy the data in the database and store it in the local database; Obtain the disaster / accident type for the first data center; According to the preset takeover rules, the data takeover permissions corresponding to the target business scenario of the first data center under the disaster type are determined; wherein, the data takeover permissions include level one permissions and level two permissions; Query the data in the local database and adjust the data takeover permissions; When the data takeover permission is at level one, takeover is performed on data processing tasks that are unrelated to data modification in the target business scenario; When the data takeover permission is at level two, takeover is performed on data processing tasks that are not associated with preceding tasks in the target business scenario.

2. The method according to claim 1, characterized in that, Before obtaining the disaster incident type for the first data center, the following is also included: Obtain the data communication partner of the first data center, and the first communication line between the first data center and the data communication partner; A second communication line is established with the data communication party based on the first communication line.

3. A disaster recovery processing device for a data center, characterized in that, include: The incident acquisition module is used to periodically access the database of the first data center, copy the data in the database, and store it in the local database; Obtain the disaster / accident type for the first data center; The permission confirmation module is used to confirm the data takeover permission corresponding to the target business scenario of the first data center under the disaster type according to the preset takeover rules; wherein, the data takeover permission includes first-level permission and second-level permission; The task takeover module is used to query data in the local database and adjust the data takeover permissions; when the data takeover permission is level one, it takes over data processing tasks in the target business scenario that are unrelated to data modification; when the data takeover permission is level two, it takes over data processing tasks in the target business scenario that are not associated with preceding tasks.

4. A disaster recovery system for a data center, characterized in that, It includes at least two data centers, each of which includes: A multi-point access module is used for communication connections with external systems; The routing module is used to allocate received data processing tasks according to preset multi-dimensional routing rules; A hierarchical takeover module is used to take over data processing tasks from other data centers; the hierarchical takeover module includes the disaster recovery processing device as described in claim 3. The operations and maintenance module is used to monitor the operational status of the data center; A database is used to store data related to data processing tasks; the database includes a data synchronization module for replicating data from other data centers.

5. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 2.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 2.

Images