Disaster recovery system, disaster recovery processing method, device, storage medium, and program product

Abstract

Embodiments of the present disclosure provide a disaster recovery system, a disaster recovery processing method, a device, a storage medium, and a program product. The disaster recovery system comprises a first computing system and a second computing system; a first server and a first service resource are deployed in the first computing system; a second server and a second service resource are deployed in the second computing system; data backup is performed between the first service resource and the second service resource by means of data synchronization; the first server is configured to access the first service resource by means of a first connection established with the first service resource, and in the case of a failure of the first service resource, access the second service resource by means of a second connection established with the second service resource; and the second server is configured to access the first service resource by means of a first connection established with the first service resource, and in the case of a failure of the first service resource, access the second service resource by means of a second connection established with the second service resource. The technical solution provided in the embodiments of the present disclosure improves the resource utilization rate.

Description

Disaster recovery system, disaster recovery processing method, device, storage medium and program product

[0002] Cross-reference to related applications

[0004] The present disclosure claims priority to the Chinese patent publication No. 202411253325.0, entitled "Disaster recovery system, disaster recovery processing method, device, storage medium and program product", filed on September 6, 2024, the disclosure of which is incorporated herein by reference in its entirety.

[0006] TECHNICAL FIELD

[0008] Embodiments of the present disclosure relate to the technical field of computer, and particularly relate to a disaster recovery system, a disaster recovery processing method, a device, a storage medium and a program product.

[0010] BACKGROUND

[0012] In order to ensure that the computing system does not lose data and can still provide services externally in the event of a failure caused by natural disasters, human accidents or other emergencies, the current common way to solve the problem of failure is to use the main and backup disaster recovery method, that is, to configure a main computing system and a backup computing system, the main computing system is responsible for daily service provision, and the backup computing system is in standby state. When the main computing system fails, the backup computing system can take over the task of the main computing system and provide services externally. However, this disaster recovery method cannot efficiently utilize resources, resulting in resource waste and low resource utilization rate.

[0014] SUMMARY

[0016] Embodiments of the present disclosure provide a disaster recovery system, a disaster recovery processing method, a device, a storage medium and a program product to solve the problem of low resource utilization rate in the prior art.

[0018] In a first aspect, a disaster recovery system is provided in embodiments of the present disclosure, comprising a first computing system and a second computing system; a first service end and a first service resource are deployed in the first computing system; a second service end and a second service resource are deployed in the second computing system; the first service resource and the second service resource are backed up through data synchronization between them;

[0020] The first service end is configured to access the first service resource based on an access request through a first connection established with the first service resource; and in the event of a failure of the first service resource, access the second service resource based on the access request through a second connection established with the second service resource;

[0022] The second service end is configured to access the first service resource based on the access request through a first connection established with the first service resource, and access the second service resource based on the access request through a second connection established with the second service resource in the case of failure of the first service resource.

[0024] The first service end is configured to publish a first message in the first message queue based on a message publishing request through a first connection established with the first message queue, set a first label for the first message, and consume the first message provided with the first label from the first message queue based on a message consumption request; in the case of failure of the second message queue, configure the second label to consume a second message provided with the second label from the first message queue based on a message consumption request.

[0026] The second service end is configured to publish a second message in the second message queue based on a message publishing request through a second connection established with the second message queue, set the second label for the second message, and consume the second message provided with the second label from the second message queue based on a message consumption request; in the case of failure of the first message queue, configure the first label to consume the first message provided with the first label from the second message queue based on a message consumption request.

[0028] In a third aspect, a disaster recovery processing method is provided in the embodiments of the present disclosure, and is applied to a disaster recovery system. The disaster recovery system includes a first computing system and a second computing system. The first computing system is deployed with a first service end and a first service resource. The second computing system is deployed with a second service end and a second service resource. The first service resource and the second service resource are backed up through data synchronization. The method includes the following steps.

[0030] The first connection established with the first service resource is disconnected, and the second service resource is accessed based on the access request through a second connection established with the second service resource in the case of failure of the first service resource.

[0032] In a fourth aspect, the present disclosure provides a disaster recovery processing method, applied to a disaster recovery system, the disaster recovery system comprising a first computing system and a second computing system; the first computing system comprising a first service end and a first service resource; the second computing system comprising a second service end and a second service resource; the first service resource and the second service resource performing data backup through data synchronization; the method comprising:

[0034] receiving an access request of at least one client;

[0036] distributing the access request to the first service end and the second service end;

[0038] in the case of failure of the first computing system, sending the access request to the second service end; in the case of failure of the second computing system, sending the access request to the first service end.

[0040] In a fifth aspect, the present disclosure provides a computing device, comprising a processing component and a storage component; the storage component storing one or more computer instructions; the one or more computer instructions being configured to be invoked and executed by the processing component to implement the disaster recovery processing method of the third aspect or the disaster recovery processing method of the fourth aspect.

[0042] In a sixth aspect, the present disclosure provides a computer storage medium storing a computer program, the computer program being configured to be executed by a computer to implement the disaster recovery processing method of the third aspect or the disaster recovery processing method of the fourth aspect.

[0044] In a seventh aspect, the present disclosure provides a computer program product, comprising computer program / instructions, the computer program / instructions being configured to be executed by a computer to implement the disaster recovery processing method of the third aspect or the disaster recovery processing method of the fourth aspect.

[0046] The embodiment of the present disclosure provides a disaster recovery system, comprising a first computing system and a second computing system; a first service end and a first service resource are arranged in the first computing system; a second service end and a second service resource are arranged in the second computing system; the first service resource and the second service resource are backed up through data synchronization; the first service end is configured to access the first service resource based on an access request through a first connection established with the first service resource; in the case of failure of the first service resource, the second service resource is accessed based on the access request through a second connection established with the second service resource; the second service end is configured to access the first service resource based on an access request through a first connection established with the first service resource; in the case of failure of the first service resource, the second service resource is accessed based on the access request through a second connection established with the second service resource. In the embodiment, the first service end and the second service end can access the service resource based on the access request, the pressure of a single service end can be reduced, and the performance of the system can be improved. Since the first computing system and the second computing system can simultaneously provide services to the outside, compared with the main computing system providing services to the outside, the disaster recovery computing system is idle on a daily basis and is only enabled in the case of failure, so that the resource utilization rate is improved. In addition, the first service end and the second service end access the first service resource through the first connection, in the case of failure of the first service resource, the first service end and the second service end access the second service resource through the second connection, so that the two service ends access the same service resource, the data synchronization of the two service resources caused by simultaneous access of the two service resources is avoided, and the consistency of the data can be ensured.

[0048] These aspects or other aspects of the present disclosure will be made clearer in the following description of embodiments.

[0050] BRIEF DESCRIPTION OF DRAWINGS

[0052] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the following will briefly introduce the drawings needed to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present disclosure, and for those skilled in the art, other drawings can also be obtained from these drawings without creative labor.

[0054] Fig. 1 shows a structural schematic diagram of one embodiment of a disaster recovery system provided by the present disclosure;

[0056] Fig. 2 shows a structural schematic diagram of another embodiment of a disaster recovery system provided by the present disclosure;

[0058] Fig. 3 shows a structural schematic diagram of another embodiment of a disaster recovery system provided by the present disclosure;

[0060] FIG. 4 shows a structural schematic diagram of still another embodiment of a disaster recovery system provided by the present disclosure;

[0062] FIG. 5 shows a structural schematic diagram of still another embodiment of a disaster recovery system provided by the present disclosure;

[0064] FIG. 6 shows a structural schematic diagram of still another embodiment of a disaster recovery system provided by the present disclosure;

[0066] FIG. 7 shows a flow chart of an embodiment of a disaster recovery processing method provided by the present disclosure;

[0068] FIG. 8 shows a flow chart of still another embodiment of a disaster recovery processing method provided by the present disclosure;

[0070] FIG. 9 shows a structural schematic diagram of an embodiment of a computing device provided by the present disclosure. DETAILED DESCRIPTION

[0072] In order to enable persons skilled in the art to better understand the present disclosure scheme, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present disclosure.

[0074] It should be noted that the "first", "second", etc. in the present disclosure are used to distinguish different components, messages, devices, modules, etc., and do not represent the order or limit the types of "first" and "second".

[0076] The technical solutions of the embodiments of the present disclosure can be applied in a disaster recovery scenario.

[0078] As described in the background, the resource utilization rate of the active-standby disaster recovery mode is low. In order to improve the resource utilization rate, the inventors think that two computing systems can be configured to participate in providing services to the outside at the same time, and then the inventors propose the technical scheme of the present disclosure after a series of researches. The technical scheme of the present disclosure provides a disaster recovery system, which comprises a first computing system and a second computing system; the first computing system is deployed with a first service end and a first service resource; the second computing system is deployed with a second service end and a second service resource; the first service resource and the second service resource are backed up through data synchronization; the first service end is configured to access the first service resource based on an access request through a first connection established with the first service resource; in the case of failure of the first service resource, the first service end is configured to access the second service resource based on a distributed access request through a second connection established with the second service resource; the second service end is configured to access the first service resource based on an access request through a first connection established with the first service resource; in the case of failure of the first service resource, the second service end is configured to access the second service resource based on an access request through a second connection established with the second service resource. In the embodiment, the first service end and the second service end can both access the service resource based on the received access request, which can reduce the pressure on a single service end and improve the performance of the system. Since the first computing system and the second computing system can provide services to the outside at the same time, compared with the case where the main computing system provides services to the outside, the disaster recovery computing system is idle on a daily basis and is only enabled in the case of failure, thereby improving the resource utilization rate. In addition, the first service end and the second service end both access the first service resource through the first connection, and in the case of failure of the first service resource, the first service end and the second service end both access the second service resource through the second connection, which ensures that the two service ends access the same service resource and avoids the case where the two service resources are accessed at the same time, which causes the two service resources to perform data synchronization and results in data coverage, thereby ensuring the consistency of the data.

[0080] In an actual application, the technical scheme of the embodiment of the present disclosure can be applied in a cloud computing scenario. Cloud computing is one of the fastest growing trends in computer technology, which involves providing hosting services over a network. A cloud computing environment provides computing and storage resources as services to end users. The end users can make requests to the provided services for processing. The processing capacity of the services is usually limited by the configured resources.

[0082] Cloud computing is a service delivery model that aims to enable on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with the service provider.

[0084] In a cloud computing scenario, the first computing system can be a primary cloud room, the second computing system can be a disaster recovery cloud room, the first service end can be a primary cloud service application deployed in the primary cloud room, and the second service end can be a backup cloud service application deployed in the disaster recovery cloud room. The first service resource and the second service resource can be cloud product instances provided by the cloud computing environment, which can include computing instances, storage instances, database instances, network instances, security instances, and the like. The computing instance can be a virtual machine instance, and the user can run an operating system and a service program by creating a virtual machine instance. The storage instance can include an object storage service for storing unstructured data such as pictures and texts, or a block storage service for providing block-level storage. The database instance can be a relational database (MySQL, PostgreSQL, etc.) or a non-relational database (MongoDB, Cassandra, etc.). The network instance can be a virtual private cloud (VPC) or a load balancer. The security instance can include a firewall or a defense system. In one implementation, the first service end and the second service end can be service programs running in the computing instance, and the first service resource and the second service resource can be storage instances or database instances, etc., for the service programs to access accordingly. In one or more embodiments below, the technical solutions of the present disclosure will be introduced by taking the cloud computing environment as an example. Of course, the embodiments of the present disclosure are not limited to the cloud computing environment, but can be implemented in combination with any other type of computing environment known or developed in the future.

[0086] The technical solutions in the embodiments of the present disclosure will be described clearly and completely below in combination with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, but not all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present disclosure.

[0088] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present disclosure are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation portal for user to choose authorization or refusal.

[0090] It should be noted that the technical solutions of the embodiments of the present disclosure are applicable to a network virtual environment, and the described user generally refers to a "virtual user". A real user can register a user account in a server through a registration method to obtain a user identity in a network environment.

[0092] The implementation details of the technical solutions of the embodiments of the present disclosure are described below in detail.

[0094] FIG. 1 is a structural schematic diagram of an embodiment of a disaster recovery system provided by the present disclosure. The disaster recovery system can include a first computing system 101 and a second computing system 102. The first computing system 101 is deployed with a first server 103 and a first service resource 104. The second computing system 102 is deployed with a second server 105 and a second service resource 106. The first service resource 104 and the second service resource 106 perform data backup through data synchronization.

[0096] The first server 103 can be configured to access the first service resource 104 based on an access request through a first connection established with the first service resource 104. In the case of a failure of the first service resource 104, the second server 105 is configured to access the second service resource 106 based on an access request through a second connection established with the second service resource 106.

[0098] The second server 105 can be configured to access the first service resource 104 based on an access request through a first connection established with the first service resource 104. In the case of a failure of the first service resource 104, the second server 105 is configured to access the second service resource 106 based on an access request through a second connection established with the second service resource 106.

[0100] The access request can come from at least one client 107. The client 107 can be a browser, an APP (Application), a web application such as an H5 (HyperText Markup Language, 5th edition) application, a light application (also known as a small program, a lightweight application), a cloud application, or the like. The client 107 can be deployed in an electronic device, and needs to rely on the device or some app in the device to run, and the like. The electronic device can have a display screen and support information browsing, and the like, and can be a personal mobile terminal such as a mobile phone, a tablet computer, a personal computer, a desktop computer, a smart speaker, a smart watch, and the like. Various other types of applications can also be configured in the electronic device, such as human-computer dialogue applications, model training applications, text processing applications, web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, and the like. The electronic device can be used by a user, and has functions such as computing, networking, and communication required by the user, and can be a mobile phone, a tablet computer, a personal computer, a wearable device, and the like. The electronic device can generally include at least one processing component and at least one storage component. The electronic device can also include a network card chip, a 10 bus, an audio and video component, and the like, which are not limited by the present disclosure. Optionally, according to the implementation form of the electronic device, some peripheral devices such as a keyboard, a mouse, an input pen, and a printer can also be included, which are not limited by the present disclosure.

[0102] The computing system can be a machine room, also known as a data center, and can be a space specially provided for running computers and other network devices, and is set up to host server, storage device, network device, and the like IT (Internet Technology) hardware facilities. The computing system can include many physical machines to run a server or service resource, and the like. In a cloud computing scenario, the computing system can be a basis for providing computing, storage, and network resources, and generally has characteristics such as large scale, high availability, and automated operation and maintenance, and provides computing resources, storage services, network services, and the like.

[0104] The first computing system 101 and the second computing system 102 can be a master and a backup system, for example, the first computing system can be a master computing system, and the second computing system 102 can be a backup computing system of the first computing system 101.

[0106] The first computing system 101 and the second computing system 102 can be physically connected through an optical fiber or the like to transmit data.

[0108] The first service end 103 can run in the first computing system 101, and in a cloud computing scenario, the first service end 103 can be a service program running in a physical machine of the first computing system 101 or a virtual machine deployed in the physical machine. The second service end 105 can be a backup service end of the first service end 103, and run in the second computing system 102, and can be a service program running in a physical machine of the second computing system 102 or a virtual machine deployed in the physical machine.

[0110] The at least one client 107 can be deployed in a user-side system, and a traffic distribution system can be deployed in the user-side system to distribute access requests sent by the at least one client 107 to the disaster recovery system. Optionally, the traffic distribution system can distribute the access requests of the at least one client 107 to the first service end 103 and the second service end 105 according to a forwarding rule, for example, according to the respective traffic proportions of the first service end 103 and the second service end 105, and the like. The traffic distribution system can be implemented as a load balancer in actual application. Of course, the access requests received by the first service end 103 and the second service end 105 can also be distributed in a distributed manner, which will be described in detail in the embodiments below.

[0112] The second service resource 106 can be a backup service resource of the first service resource 104, and the first service resource 104 and the second service resource 106 perform data backup through a data synchronization manner.

[0114] In this embodiment, the first service end 103 and the second service end 105 can access the service resource based on the access request, which can reduce the pressure on a single service end and improve the performance of the system. Since the first computing system 101 and the second computing system 102 can simultaneously provide services to the outside, compared with a main computing system providing services to the outside, a main-backup disaster recovery mode in which a disaster recovery computing system is idle on a daily basis and is only enabled in case of failure, improves the resource utilization rate. In addition, the first service end 103 and the second service end 105 both access the first service resource 104 through the first connection, and in case of failure of the first service resource 104, the first service end 103 and the second service end 105 both access the second service resource 106 through the second connection, which ensures that the two service ends access the same service resource, avoids data synchronization between two service resources caused by simultaneous access to two service resources, and causes data coverage, and can ensure the consistency of data.

[0116] In some embodiments, the disaster recovery system can further comprise a control system. The control system can be configured to receive an access request from the at least one client 107, and distribute the access request to the first server 103 and the second server 105.

[0118] In other words, the access request from the at least one client 107 can be sent to the control system, and the control system can distribute the access request to the first server 103 and the second server 105.

[0120] In some embodiments, the control system can be deployed in the first computing system or the second computing system. In addition, the control system can be independent of the first computing system and the second computing system.

[0122] In some embodiments, as shown in FIG. 2, the system architecture is different from that shown in FIG. 1. The control system can comprise a first control system. The first control system can comprise at least one first control end 108. The at least one first control end 108 can be deployed in the first computing system 101 and the second computing system 102. For example, the at least one first control end can comprise at least one first control end deployed in the first computing system 101 and the second computing system 102. In practical applications, the target first control end among the at least one first control end 108 can distribute the access request from the at least one client 107 to the first server 103 and the second server 105.

[0124] In addition, the at least one first control end 108 can be configured to reselect any first control end as a target control end in the case of failure of the target first control end.

[0126] The at least one control end 108 can form a cluster, for example, a Raft (a distributed consensus algorithm) cluster. In the Raft cluster, the target first control end acts as a leader node (Leader), and the remaining first control ends act as follower nodes (Follower). In the case of failure of the leader node, the follower nodes become candidate nodes (Candidate) to reselect the leader node, etc. In addition, the target first control end and the remaining first control ends can report their health status through heartbeat messages.

[0128] The first control end 108 can be implemented as a DNS (Domain Name System) for example. The DNS can resolve the domain name used in the access request to the access address of the corresponding first service end 103 or second service end 105 according to the mapping relationship (referred to as A record) between the domain name and the access address such as IP (Internet Protocol) address stored by the DNS, and then the access request can be routed to the correct service end according to the access address. The first control end can also be implemented as an SLB (Global Server Load Balance) for example, to distribute the received access requests to multiple service ends, avoid overloading of a single service end, and improve the overall processing capability of the disaster recovery system. Of course, the first control end can also be implemented as other forms of controllers and the like, to perform domain name resolution and traffic scheduling and the like, which are not limited in the present disclosure.

[0130] In some embodiments, the control system can specifically distribute the received access request of at least one client 107 to the first service end 103 and the second service end 105 according to the routing rule. The routing rule can include one or more of the following implementation manners: the corresponding traffic proportion of the first computing system 101 and the second computing system 102 respectively; the corresponding access area between the first computing system 101 and the second computing system 102 respectively; and the corresponding access type between the first computing system 101 and the second computing system 102 respectively.

[0132] That is, as an optional implementation manner, the control system can distribute the received access request to the first service end 103 and the second service end 105 according to the corresponding traffic proportion of the first computing system 101 and the second computing system 102 respectively. For example, 80% of the traffic can be distributed to the first service end 103 of the first computing system 101, and 20% of the traffic can be distributed to the first service end 103 of the second computing system 102, and the like, which are not limited in the present disclosure.

[0134] As another optional implementation, the control system can distribute the received access request to the first service end 103 and the second service end 105 according to the corresponding access area of the first computing system 101 and the second computing system 102 respectively. For example, the access area corresponding to the first computing system 101 and the second computing system 102 can be set according to the geographical location corresponding to the first computing system 101 and the second computing system 102 respectively. The service end to which the access request is distributed can be determined according to whether the source address in the access request conforms to the access area corresponding to the first computing system 101 and the second computing system 102 respectively. For example, the first computing system 101 is located in city A and is responsible for receiving access requests from the northern region, and the second computing system 102 is located in city B and is responsible for receiving access requests from the southern region. If the source address of the access request belongs to the northern region, the access request is distributed to the first service end 103 of the first computing system 101, and if the source address of the access request belongs to the southern region, the access request is distributed to the second service end 105 of the second computing system 102. As another implementation, the control system can distribute the received access request to the first service end 103 and the second service end 105 according to the access type corresponding to the first computing system 101 and the second computing system 102 respectively. For example, the access type can refer to the content type or protocol type of the access request, and the first computing system 101 and the second computing system 102 can correspond to access requests of different access types respectively. According to the access type to which the access request belongs, the access request is distributed to the corresponding service end.

[0136] The routing rule can be obtained by user configuration, so in some embodiments, the control system can further obtain the first configuration information configured by the user; the first configuration information can include the routing rule.

[0138] Optionally, the control system can provide a first control interface to obtain the first configuration information configured by the user through the control interface.

[0140] In some embodiments, the control system can be further configured to output a first fault prompt information in a case where the first computing system 101 or the first service end 103 fails; send the received access request to the second service end 105 in response to a first fault switching request triggered by the user; output a second fault prompt information in a case where the second computing system 102 or the second service end 105 fails; and send the received access request to the first service end 103 in response to a second fault switching request triggered by the user.

[0142] In this embodiment, the control system can automatically detect the fault, output a fault prompt information to the user, and in response to a fault switching request triggered by the user, timely switch the service end to which the access request is sent, so that the disaster recovery system can still process the access request in the fault condition and ensure the continuity of the access.

[0144] Alternatively, the target first control end 108 can output a first fault prompt information in the case of detecting a fault of the first computing system 101 or the first service end 103, send the received access request to the second service end 105 in response to a first fault switching request triggered by the user, output a second fault prompt information in the case of detecting a fault of the second computing system 102 or the second service end 105, and send the received access request to the first service end 103 in response to a second fault switching request triggered by the user.

[0146] Of course, the control system can further include a third control system, the third control system including at least one third control end, the at least one third control end can constitute a Raft cluster, and the target third control end among the at least one third control end can output a first fault prompt information in the case of detecting a fault of the first computing system 101 or the first service end 103, send the received access request to the second service end 105 in response to a first fault switching request triggered by the user, output a second fault prompt information in the case of detecting a fault of the second computing system 102 or the second service end 105, and send the received access request to the first service end 103 in response to a second fault switching request triggered by the user.

[0148] The at least one third control end can be configured to reselect any third control end as the target third control end in the case of a fault of the target third control end.

[0150] In some embodiments, the control system can be further configured to synchronize data in the first service resource 104 to the second service resource 106.

[0152] In addition, the control system can further migrate the data in the first service resource 104 to the second service resource 106 in the case of a fault of the first computing system.

[0154] Alternatively, the target third control end can synchronize the data in the first service resource 104 to the second service resource 106, and migrate the data in the first service resource 104 to the second service resource 106 in the case of a fault of the first computing system. In some embodiments, the control system can include a first data synchronization component deployed in the first computing system 101 and a second data synchronization component deployed in the second computing system 102.

[0156] The first data synchronization component can be configured to synchronize data in the first service resource 104 to the second service resource 106.

[0158] The second data synchronization component can be configured to migrate data in the second service resource 106 to the first service resource 104 in the case of recovery of the first service resource 104.

[0160] In the embodiment, the data synchronization is performed by the first data synchronization component, so that the data consistency can be ensured, and the second service resource can continue to provide services in the case of failure of the first service resource. In the case of recovery of the first service resource, the data of the second service resource is migrated to the first service resource by the second data synchronization component, so that the data consistency can be ensured, and the first service resource can provide services.

[0162] Optionally, the target third control end can call the first data synchronization component to synchronize data in the first service resource 104 to the second service resource 106, and call the second data synchronization component to migrate data in the second service resource 106 to the first service resource 104 in the case of recovery of the first service resource 104.

[0164] In some embodiments, in order to reduce the modification of the service end and the like, the first service resource can include a first storage resource, and the second service resource can include a second storage resource as a backup of the first storage resource. The first service end 103 can be further configured to save the cached data to the first storage resource, and the second service end 105 can be further configured to save the cached data to the first storage resource. For example, the first service end 103 and the second service end 105 can save the session state and the like to the first storage resource, so that the service end does not need to manage the session state and the like, which is helpful to implement stateless service.

[0166] In the cloud computing system, the first storage resource and the second storage resource can be cloud storage instances, that is, the first service resource 104 can include a first cloud storage instance, and the second service end 105 can include a second cloud storage instance. The first service end 103 can save the cached data to the first cloud storage instance, and the second service end 105 can save the cached data to the first cloud storage instance.

[0168] In some embodiments, the control system can be further configured to map the first access domain name of the first service resource 104 and the second access domain name of the second service resource 106 to the same access alias, and configure the weight proportion corresponding to the first access domain name and the second access domain name respectively; in response to the first resolution request of the first server 103, convert the access alias to the first access address of the first service resource 104 according to the weight proportion corresponding to the first access domain name and the second access domain name respectively; in response to the second resolution request of the second server 105, convert the access alias to the first access address of the first service resource 104 according to the weight proportion corresponding to the first access domain name and the second access domain name respectively.

[0170] The first server 103 can be further configured to configure the access alias, send the first resolution request to the control system based on the access alias, and establish the first connection with the first service resource 104 according to the first access address fed back by the control system; the second server 105 can be further configured to configure the access alias, send the second resolution request to the control system based on the access alias, and establish the first connection with the first service resource 104 according to the first access address fed back by the control system.

[0172] The access alias can be a CNAME (Canonical Name, alias). The first access domain name and the second access domain name are mapped to the same access alias, forming a first CNAME record of the first access domain name to the access alias and a second CNAME record of the second access domain name to the access alias. The CNAME record is a resource record type for pointing the access alias to the access domain name. The access address record mapped by the access domain name is an A record, that is, the A record points to the access address corresponding to the access domain name, and the CNAME record points to the access domain name corresponding to the access alias. By resolving the CNAME, the access domain name corresponding to the access alias can be determined, and by resolving the A record, the access address corresponding to the access domain name can be determined. In actual application, the access address can be an IP address (Internet Protocol Address, Internet Protocol Address) for example.

[0174] In addition, the weight proportion corresponding to the first access domain name and the second access domain name can be configured, for example, the weight proportion of the first access domain name can be configured as 100%, and the weight proportion of the second access domain name can be configured as 0%. Through the weight proportion, the access alias can be completely mapped to the first access domain name of the first service resource 104, so that the access request is completely directed to the first service resource 104.

[0176] The access alias is configured in the first service end 103 and the second service end 105, so that a corresponding resolution request can be initiated to the control system based on the access alias. The control system can determine the first access domain name and the second access domain name pointed by the access alias in response to the first resolution request of the first service end 103, and determine that the access request corresponds to the first access domain name according to the weight proportion corresponding to the first access domain name and the second access domain name, which can be 100% weight proportion corresponding to the first access domain name and 0% weight proportion corresponding to the second access domain name, and then determine the first access address pointed by the first access domain name according to the A record of the first access domain name. The first service end 103 can establish the first connection with the first service resource 104 based on the first access address fed back by the control system. The control system can determine the first access domain name and the second access domain name pointed by the access alias in response to the second resolution request of the second service end 105, and determine that the access request corresponds to the first access domain name according to the weight proportion corresponding to the first access domain name and the second access domain name, which can be 100% weight proportion corresponding to the first access domain name and 0% weight proportion corresponding to the second access domain name, and then determine the first access address pointed by the first access domain name according to the A record of the first access domain name. Then the second service end 105 can establish the first connection with the first service resource 104 based on the first access address fed back by the control system.

[0178] In the embodiment, by configuring the access alias and the weight proportion of the first access domain name and the second access domain name mapped to the access alias, the traffic distribution to the service resource can be realized, and the first service end and the second service end can access the first service resource.

[0180] The first access domain name of the first service resource and the second access domain name of the second service resource are mapped to the same access alias by the target first control end, and the weight proportion corresponding to the first access domain name and the second access domain name is configured. In response to the first resolution request of the first service end, the access alias is converted into the first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name. In response to the second resolution request of the second service end, the access alias is converted into the first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name.

[0182] In addition, in some embodiments, as shown in FIG. 2, the control system can further include a second control system, which can include at least one second control end 109, where the second control end can be implemented as a DNS or an SLB, etc. The at least one second control end 109 can be in the form of a Raft cluster, etc.

[0184] The at least one second control end 109 can be distributed and deployed in the first computing system 101 and the second computing system 102. A target second control end in the at least one second control end 109 can be configured to map a first access domain name of the first service resource 104 and a second access domain name of the second service resource 106 to the same access alias, and configure the weight proportions corresponding to the first access domain name and the second access domain name respectively. In response to a first resolution request of the first service end 103, the target second control end can convert the access alias to the first access address of the first service resource 104 according to the weight proportions corresponding to the first access domain name and the second access domain name respectively. In response to a second resolution request of the second service end 105, the target second control end can convert the access alias to the first access address of the first service resource 104 according to the weight proportions corresponding to the first access domain name and the second access domain name respectively. The at least one second control end 109 can be configured to select any second control end as a target second control end in the case of failure of the target second control end.

[0186] That is, the target first control end can distribute the access request of the at least one client 107 to the service end, and the target second control end can be configured to respond to the resolution request of the service end, resolve the access address of the service resource and feed back to the service end, so that the service end establishes a connection with the service resource based on the access address.

[0188] In some embodiments, the control system can further obtain second configuration information of the user, which can include the first access domain name and the second access domain name respectively corresponding to the weight ratio, etc. Optionally, the control system can provide a second control interface to obtain the second configuration information configured by the user through the second control interface. In addition, in some embodiments, the first configuration information and the second configuration information of the user can be obtained by a target third control terminal. For example, the control interface described above can be provided by the target third control terminal. At least one third control terminal can be set to select any third control terminal as a target third control terminal in the case of failure of the target third control terminal, etc. The target third control terminal can call the interface provided by the target first control terminal 108 and the target second control terminal 109. Optionally, the routing rule described above can be configured by the user on the target third control terminal, and the target third control terminal can call the interface provided by the target first control terminal 108 to send the routing rule to the target first control terminal 108, so that the target first control terminal 108 distributes the access request to the service terminal according to the routing rule.

[0190] Optionally, the access alias and the first access domain name and the second access domain name respectively corresponding to the weight ratio can be configured by the user on the target third control terminal and sent to the target second control terminal by the target third control terminal through calling the interface provided by the target second control terminal.

[0192] At present, since the first access domain name of the first service resource 104 is different from the second access domain name of the second service resource 106, when switching between service resources, the access domain name needs to be changed, and the first service terminal and the second service terminal need to be restarted, which is more modified and the switching process is cumbersome. In order to reduce the modification and simplify the switching process, in some embodiments, the control system can further update the weight ratio respectively corresponding to the first access domain name and the second access domain name in the case of failure of the first service resource 104, and according to the third resolution request of the first service terminal 103, convert the access alias to the second access address of the second service resource 106 according to the updated weight ratio; in response to the fourth resolution request of the second service terminal 105, convert the access alias to the second access address of the second service resource 106 according to the updated weight ratio.

[0194] The first service end 103 can also send a third resolution request to the control system in the case of failure of the first service resource 104, and establish a second connection with the second service resource 106 according to a second access address fed back by the control system. The second service end 105 can also send a fourth resolution request to the control system in the case of failure of the first service resource 104, and establish a second connection with the second service resource 106 according to a second access address fed back by the control system. For example, the weight proportion corresponding to the first access domain name of the first access resource can be updated from 100% to 0%, and the weight proportion corresponding to the second access domain name of the second service resource 106 can be updated from 0% to 100%, so that all access aliases are mapped to the second access domain name of the second service resource 106, and all access requests are directed to the second service resource 106.

[0196] In the case of failure of the first service resource 104, the connection between the first service end 103 and the first service resource 104 will be disconnected, and the first service end 103 can re-initiate a resolution request based on the access alias, that is, send a third resolution request to the control system. Similarly, the connection between the second service end 105 and the first service resource 104 will also be disconnected, and the second service end 105 can resend a fourth resolution request to the control system based on the access alias.

[0198] The control system can determine the first access domain name and the second access domain name to which the access alias points in response to the third resolution request of the first service end 103, and determine that the access request corresponds to the second access domain name according to the updated weight proportions corresponding to the first access domain name and the second access domain name, specifically, the first access domain name corresponds to a weight proportion of 0% and the second access domain name corresponds to a weight proportion of 100%, and then determine the second access address to which the second access domain name points according to the A record of the second access domain name, so that the second service end 105 can establish a second connection with the second service resource 106 based on the second access address fed back by the control system. The control system can determine the first access domain name and the second access domain name to which the access alias points in response to the fourth resolution request of the second service end 105, and determine that the access request corresponds to the second access domain name according to the updated weight proportions corresponding to the first access domain name and the second access domain name, specifically, the first access domain name corresponds to a weight proportion of 0% and the second access domain name corresponds to a weight proportion of 100%, and then determine the second access address to which the second access domain name points according to the A record of the second access domain name, so that the second service end 105 can establish a second connection with the second service resource 106 based on the second access address fed back by the control system.

[0200] Therefore, the first service end 103 and the second service end 105 can establish a second connection with the second service resource 106 in the case of failure of the first service resource 104, and access the second service resource 106, so as to avoid service interruption caused by failure of the first service resource 104, and ensure continuity and availability of the service. By configuring the access alias and the weight proportion of the first access domain name and the second access domain name mapped to the access alias, only the weight proportion needs to be modified, and the service resource switching can be realized, the modification is small, and the switching process is simplified.

[0202] Optionally, the target second control end can update the weight proportion corresponding to the first access domain name and the second access domain name in the case of failure of the first service resource, and convert the access alias into the second access address of the second service resource according to the updated weight proportion according to the third resolution request of the first service end; and convert the access alias into the second access address of the second service resource according to the updated weight proportion according to the fourth resolution request of the second service end.

[0204] In some embodiments, the first service end 103 can also disconnect the first connection established with the first service resource 104 in the case of failure of the first service resource 104, and establish a second connection with the second service resource 106; and in the case of recovery of the first service resource 104, the second connection with the second service resource 106 is disconnected, and the first connection with the first service resource 104 is recovered. The second service end 105 can also disconnect the first connection established with the first service resource 104 in the case of failure of the first service resource 104, and establish a second connection with the second service resource 106; and in the case of recovery of the first service resource 104, the second connection with the second service resource 106 is disconnected, and the first connection with the first service resource 104 is recovered.

[0206] In some embodiments, the control system can also be configured to output a recovery prompt information in the case of detecting recovery of the first service resource 104; and send a recovery switching request to the first service end 103 and the second service end 105 respectively in response to a failure recovery request triggered by a user. The first service end 103 and the second service end 105 can determine recovery of the first service resource 104 according to the recovery switching request.

[0208] Optionally, the target first control terminal, the target second control terminal or the target third control terminal can output a recovery prompt information in response to detection of the first service resource 104 recovery, and send a recovery switching request to the first service terminal 103 and the second service terminal 105 in response to a user triggered fault recovery request. The present disclosure does not limit this.

[0210] In the above embodiments, the control system can output a recovery prompt information to inform the user of the first service resource recovery, which helps the user to understand the status of the first service resource and perform operations. For example, the user can trigger a fault recovery request, and the control system can send a recovery switching request to the first service terminal 103 and the second service terminal 105 in response to the fault recovery request. Then, the first service terminal 103 and the second service terminal 105 can determine the first service resource 104 recovery according to the recovery switching request, and then the first service terminal 103 and the second service terminal 105 can disconnect the second connection with the second service resource 106 and restore the first connection with the first service resource 104. In this way, when the first service resource 104 is normal, the first service terminal 103 and the second service terminal 105 can access the first service resource 104 based on the access request through the first connection, which can improve the data consistency and improve the reliability and availability of the disaster recovery system. In some embodiments, multiple different service terminals can be deployed in the first computing system 101, as shown in the structural schematic diagram of FIG. 3. The first computing system 101 can further deploy a third service terminal 110, and the second computing system 102 can further deploy a fourth service terminal 111 as a backup of the third service terminal 110. The first computing system 101 can further deploy a third service resource 112, and the second computing system can further deploy a fourth service resource 113 as a backup of the third service resource 112. The third service resource 112 and the fourth service resource 113 can perform data backup through data synchronization.

[0212] The control system can further be configured to determine a third service terminal 110 associated with the first service terminal 103 and deployed in the first computing system 101, and a fourth service terminal 111 deployed in the second computing system 102

[0214] The third service end 110 can be configured to access the third service resource 112 based on the access request distributed by the control system through the third connection established with the third service resource 112 deployed in the first computing system 101; in the case of failure of the third service resource 112, access the fourth service resource 113 based on the access request distributed by the control system through the fourth connection established with the fourth service resource 113 deployed in the second computing system 102.

[0216] The fourth service end 111 can be configured to access the third service resource 112 based on the access request distributed by the control system through the third connection established with the third service resource 112; in the case of failure of the third service resource 112, access the fourth service resource 113 based on the access request distributed by the control system through the fourth connection established with the fourth service resource 113.

[0218] The control system can also be configured to control the third service end 110 and the fourth service end 111 to establish a fourth connection with the fourth service resource 113 deployed in the second computing system 102 in the case of failure of the first service resource 104 accessed by the first service end 103, so as to access the fourth service resource 113 based on the access request distributed by the control system through the fourth connection.

[0220] Optionally, the target first control end, the target second control end or the target control end can forward the access request sent to the third service end 110 to the fourth service end 111 in the case of failure of the first service end; in the case of failure of the first service resource 104 accessed by the first service end 103, control the third service end 110 and the fourth service end 111 to establish a fourth connection with the fourth service resource 113, so as to access the fourth service resource 113 based on the access request distributed by the control system through the fourth connection. The present disclosure does not limit this.

[0222] For example, as shown in FIG. 3, in the case of failure of the first service resource 104 accessed by the first service end 103, the first service end 103 and the second service end 105 are switched from accessing the first service resource 104 to the second service resource 106, and the third service end 110 and the fourth service end 111 are switched from accessing the third service resource 112 to the fourth service resource 113.

[0224] The first service resource 104 and the third service resource 112 can be the same or different. When the first service resource 104 accessed by the first service end 103 fails, if the third service resource 112 accessed by the third service end 110 and the fourth service end 111 does not fail, the control system can disable the third access address of the third service resource 112, disconnect the third service end 110 and the fourth service end 111 from the third service resource 112, and establish a fourth connection between the third service end 110 and the fourth service end 111 and the fourth service resource 113.

[0226] The control system can also be configured to forward the access request sent to the third service end 110 to the fourth service end 111 in the case of failure of the first service end 103.

[0228] For example, as shown in FIG. 4, the first control end deployed in the first computing system can send access requests to the first service end 103 and the third service end 110, and the first control end deployed in the second computing system can send access requests to the second service end 105 and the fourth service end 111. In the case of failure of the first service end 103, the access request sent to the first service end 103 can be forwarded to the second service end 105, and the access request sent to the third service end 110 can be forwarded to the fourth service end 111.

[0230] In this embodiment, the first server 103 is associated with the third server 110 and the fourth server 111, and the first server 103 and the third server 110 are deployed in the first computing system 101. In the case of failure of the first server 103, the access request sent to the first server 103 will be forwarded to the second server 105 in the second computing system 102, and the access request sent to the third server 110 will be forwarded to the fourth server 111 corresponding to the third server 110 in the second computing system 102. It can be ensured that the associated servers run in the same computing system, the data consistency can be improved, the data transmission delay between the associated servers can be reduced, and the system performance can be improved. In addition, in the case of failure of the first service resource 104 accessed by the first server 103, the first server 103 switches to access the second service resource 106 in the second computing system 102, and the third server 110 and the fourth server 111 switch from accessing the third service resource 112 to the fourth service resource 113 in the second computing system 102. It can be ensured that the associated servers access the service resources in the same computing system, cross-computing-system access to service resources can be avoided, data consistency can be improved, data transmission delay can be reduced, and system performance can be improved.

[0232] In actual application, in the case that the first service resource 104 or the second service resource 106 is not failed, there will be some service resource switching requirements, such as in the disaster recovery exercise scenario or in the service resource recovery scenario. In order to disconnect the connection with the service resource, especially in the case that the service resource is a database instance in a cloud product instance, the server often cannot automatically disconnect the connection with the database instance. Therefore, in some embodiments, the control system can also disable the first access address to disconnect the first connection in response to the first service resource 104 switching event; update the weight proportion corresponding to the first access domain name and the second access domain name respectively, and convert the access alias to the second access address of the second service resource 106 according to the updated weight proportion according to the fifth resolution request of the first server 103; and convert the access alias to the second access address of the second service resource 106 according to the updated weight proportion in response to the sixth resolution request of the second server 105. Alternatively, the target first control end, the target second control end or the target third control can perform the subsequent operation in response to the first service resource switching event, and the present disclosure does not limit this.

[0234] The first service end 103 can also send a fifth resolution request to the control system in the case of disconnection of the first connection, and establish a second connection with the second service resource 106 according to the second access address fed back by the control system.

[0236] The second service end 105 can also send a sixth resolution request to the control system in the case of disconnection of the first connection, and establish a second connection with the second service end 105 according to the second access address fed back by the control system.

[0238] In the service resource failure case, the connection between the service resource and the service end based on the access address will be automatically disconnected. In the service resource switching event, the service resource may not be able to automatically disconnect the connection with the service end based on the access address. Therefore, in this embodiment, in response to the service resource switching event of switching from the first service resource 104 to the second service resource 106, the control system can disconnect the first connection between the first service resource 104 and the first service end 103 and the second service end 105 by disabling the first access address of the first service resource 104. At the same time, the control system can update the weight proportion corresponding to the first access domain name and the second access domain name, for example, the weight proportion of the first access domain name of the first service resource 104 can be updated from 100% to 0%, and the weight proportion of the second access domain name of the second service resource 106 can be updated from 0% to 100%.

[0240] Further, after the first service end 103 is disconnected from the first service resource 104, the fifth resolution request can be sent to the control system, and the control system can determine the first access domain name and the second access domain name pointed by the access alias in response to the fifth resolution request. According to the first weight proportion corresponding to the first access domain name and the second access domain name after the update, specifically, the first access domain name corresponds to 0% weight proportion and the second access domain name corresponds to 100% weight proportion, it can be determined that the access request corresponds to the second access domain name, and the second access address pointed by the second access domain name can be determined according to the A record of the second access domain name. Therefore, the first service end 103 can establish a second connection with the second service resource 106 based on the second access address fed back by the control system. The control system can determine the first access domain name and the second access domain name pointed by the access alias in response to the sixth resolution request of the second service end 105. According to the first weight proportion corresponding to the first access domain name and the second access domain name after the update, specifically, the first access domain name corresponds to 0% weight proportion and the second access domain name corresponds to 100% weight proportion, it can be determined that the access request corresponds to the second access domain name, and the second access address pointed by the second access domain name can be determined according to the A record of the second access domain name. Therefore, the second service end 105 can establish a second connection with the second service resource 106 based on the second access address fed back by the control system.

[0242] Among them, the first service resource switching event may, for example, be receiving a switching request triggered by a user for the first service resource 104.

[0244] In addition, in order to ensure that the first service resource can be normally used in the recovery state, in some embodiments, the control system can also enable the first access address in the case of establishing the second connection.

[0246] In some embodiments, the control system can also disable the second access address to disconnect the second connection in response to the second service resource switching event; update the first weight proportion corresponding to the first access domain name and the second access domain name, and convert the access alias to the first access address of the first service resource 104 according to the first weight proportion according to the seventh resolution request of the first service end 103; convert the access alias to the first access address of the first service resource 104 according to the first weight proportion in response to the eighth resolution request of the second service end 105. Optionally, the target first control end, the target second control end or the target third control end can perform the subsequent operation in response to the second service resource switching event, and the present disclosure does not limit this.

[0248] The first service end 103 can also be configured to send a seventh resolution request to the control system in the case of disconnection of the second connection, and establish the first connection with the first service resource 104 according to the first access address fed back by the control system. The second service end 105 can also be configured to send an eighth resolution request to the control system in the case of disconnection of the second connection, and establish the first connection with the first service resource 104 according to the first access address fed back by the control system. The control system updates the weight proportion corresponding to the first access domain name and the second access domain name, for example, the weight of the first access domain name of the first service resource 104 can be restored from 0% to 100%, and the weight proportion of the second access domain name of the second service resource 106 can be restored from 100% to 0%.

[0250] The second service resource switching event may, for example, be receiving a user-triggered switching request for the second service resource or receiving a user-triggered fault recovery request for the first service resource.

[0252] For ease of understanding, taking the target first control end in the control system to implement traffic distribution and the target second control end to implement domain name mapping operation as an example, as shown in the control diagram of the disaster recovery system in FIG. 5, taking a cloud computing scenario as an example, assuming that the first service end 103 and the second service end 105 can be service programs deployed in a virtual machine such as ECS (Elastic Compute Service, cloud server), and the first service resource 104 and the second service resource 106 are database instances. The first computing system 101 is a host room, and the second computing system 102 is a disaster recovery room. The host room and the disaster recovery room are connected through optical cables and the like, and can access the network through switches such as ISW (Inter-Switch External Access Switch, external network access switch), CSW (Cloud Switch Internal Access Switch, internal network access switch), etc. to realize network intercommunication between the host room and the disaster recovery room.

[0254] The target first control end 108 can receive an access request from at least one client 107, and distribute the access request to the first service end 103 and the second service end 105 according to a routing rule, for example, a traffic ratio corresponding to the first service end 103 and the second service end 105, for example, the traffic ratio of the first service end 103 is 80%, and the traffic ratio of the second service end 105 is 20%. The disaster recovery system can receive an access request from at least one client 107. The first service end 103 and the second service end 105 can be respectively configured with an access alias, and the access alias points to a first access domain name of the first service resource 104 and a second access domain name of the second service resource 106.

[0256] The target second control end can determine the mapped first access domain name and the second access domain name by parsing the access alias, and determine the final first service resource corresponding to the access alias according to the weight ratio.

[0258] The first service end 103 and the second service end 105 can establish a connection with the first service resource 104 according to the first access address, so that the first service resource 104 can be accessed based on the access request.

[0260] In the case of failure of the first service resource 104, only the weight ratio needs to be updated, so that the access alias can be parsed to correspond to the second access address, so that the first service end 103 and the second service end 105 can reestablish a connection with the second service resource 106, so that the second service resource 106 can be accessed based on the access request.

[0262] In an actual application, the service resource can be a message queue. Referring to FIG. 6, FIG. 6 is a structural schematic diagram of another embodiment of the disaster recovery system provided by the present disclosure, which can include a first computing system 201 and a second computing system 202; the first computing system 201 is deployed with a first service end 203 and a first message queue 204; the second computing system 202 is deployed with a second service end 205 and a second message queue 206; the first message queue and the second message queue 206 are backed up through data synchronization.

[0264] The first service end 203 can be configured to publish a first message in the first message queue 204 based on a message publishing request and set a first label for the first message, and consume the first message with the first label from the first message queue 204 based on a message consumption request through the first connection established with the first message queue 204; in the case of failure of the second message queue 206, the second label is configured to consume the second message with the second label from the first message queue 204 based on the message consumption request. The second service end 205 can be configured to publish a second message in the second message queue 206 based on a message publishing request and set a second label for the second message, and consume the second message with the second label from the second message queue 206 based on a message consumption request through the second connection established with the second message queue 206; in the case of failure of the first message queue 204, the first label is configured to consume the first message with the first label from the second message queue 206 based on the message consumption request.

[0266] The first label can be configured to uniquely identify the first message in the first message queue 204, and the second label can be configured to uniquely identify the second message in the second message queue 206.

[0268] In the embodiment, the first computing system and the second computing system can simultaneously provide services to the outside, compared with the main computing system providing services to the outside, the disaster recovery computing system is idle on a daily basis and is only enabled in the case of failure, which improves the resource utilization. In addition, the service end can realize message filtering through the first label and the second label, so that the first service end can only access the first message with the first label, and the second service end can only access the second message with the second label. The first label and the second label can ensure data consistency and avoid data synchronization caused data coverage problem.

[0270] In the case of failure of the first message queue 204, the first tag can be configured in the second service end 205, so that the first message corresponding to the first tag can continue to be consumed. In the case of failure of the second message queue 206, the second tag can be configured in the first service end 203, so that the second message corresponding to the second tag can continue to be consumed. The first service end 203 can record the correspondence between the first message queue name and the first tag. In the case of failure of the first message queue 204, since the first message has been synchronized to the second message queue 206, the second service end 205 can record the correspondence between the second message queue name and the first tag, so that the first message can be consumed through the second service end 205. Similarly, the second service end 205 can record the correspondence between the second message queue name and the second tag. In the case of failure of the second message queue 206, since the second message has been synchronized to the first message queue 204, the first service end 203 can record the correspondence between the first message queue name and the second tag, so that the second message can be consumed through the first service end 203. The first service end 203 can access the first message queue 204 based on the first message queue name, and the second message queue 206 can access the second message queue 206 based on the second message queue name. Optionally, the message queue name can be the access domain name or access address of the message queue.

[0272] In addition, the message publishing request can also specify the topic of the message. In some embodiments, the first service end 203 publishes the first message in the first message queue 204 based on the message publishing request through the first connection, and sets the first tag for the first message. This can be publishing the first message in the first topic in the first message queue 204 based on the message publishing request through the first connection, and setting the first tag for the first message. The first service end can record the correspondence between the first message queue name, the topic name and the first tag.

[0274] The first service end 203 consumes the first message with the first tag from the first message queue 204 based on the message consumption request. This can be consuming the first message with the first tag from the first topic in the first message queue 204 based on the message consumption request.

[0276] The second service end 205 publishes the second message in the second message queue 206 and sets the second label for the second message based on the message publishing request through the second connection, and can publish the second message in the second topic of the second message queue 206 and set the second label for the second message based on the message publishing request through the second connection; the second service end can record the correspondence between the second message queue name, the topic name and the second label.

[0278] Optionally, the first message queue 204 can synchronize the first topic to the second message queue 206. The second message queue 206 can synchronize the second topic to the second message queue 206. In the case of failure of the first message queue 204, the correspondence between the first label, the first topic and the first message queue 204 can be configured in the second service end, so that the first service end can continue to consume the first message in the first topic. In the case of failure of the second message queue, the correspondence between the second label, the second topic and the first message queue can be configured in the first service end, so that the first service end can continue to consume the second message in the second topic.

[0280] In addition, the first topic and the second topic can also use the same topic name, so that the first message can only be synchronized to the second topic of the second message queue 206, or the second message can only be synchronized to the first topic of the first message queue 204.

[0282] In the embodiment, the service end only accesses the message queue deployed in the same computing system, the data transmission path is shorter, the delay can be reduced and the system performance can be improved. The consistency of the service end in producing and consuming messages can be ensured by setting the label, and different service ends correspond to different labels, so that the client 207 can avoid receiving duplicate messages. In the case of failure of the first message queue 204, the first message originally sent to the first service end 203 is forwarded to the second service end 205, the second message queue 206 can process the first message with the first label set by the second service end 205 through the configuration of the first label, in the case of failure of the second message queue 206, the second message originally sent to the second service end 205 is forwarded to the first service end 203, the first message queue 204 can process the second message with the second label set by the first service end 203 through the configuration of the second label, and the availability of the disaster recovery system is realized.

[0284] In some embodiments, the disaster recovery system can further include a control system.

[0286] The control system can be configured to distribute the message publishing request or the message consumption request for the target data to the first service end 203 and the second service end 205

[0288] The first server 203 can be configured to, in response to a message publishing request, publish a first message to the first message queue 204 and set a first tag; and in response to a message consumption request, determine a corresponding first tag and read a second message with the first tag set from the first message queue 204.

[0290] The control system can also be configured to synchronize the first message in the first message queue 204 to the second message queue 206, and synchronize the second message in the second message queue 206 to the first message queue 204.

[0292] In some embodiments, the control system can include a first message routing component 208 deployed in the first computing system 201 and a second message routing component 209 deployed in the second computing system 202. The first message routing component 208 can be configured to synchronize the first message in the first message queue 204 and its corresponding first tag to the second message queue 206. The first message can carry the first tag.

[0294] The second message routing component 209 can be configured to synchronize the second message in the second message queue 206 and its corresponding second tag to the first message queue 204. The second message can carry the second tag.

[0296] For example, in a cloud computing scenario, the first message queue 204 can refer to a message queue instance deployed in a primary cloud room, and the second message queue 206 can refer to a message queue instance deployed in a backup cloud room. The message queue instance can be, for example, RabbitMQ (an open source message broker and message queue server), RocketMQ (a distributed message middleware), MQTT (Message Queuing Telemetry Transport), or Kafka (a distributed stream processing platform).

[0298] In some embodiments, the control system can also be configured to, in the case of a failure of the first message queue 204, configure the first tag for the second server 205; and in the case of a failure of the second message queue 206, configure the second tag for the first server 203.

[0300] FIG. 7 is a flowchart of one embodiment of a disaster recovery processing method according to the present disclosure. The technical solution of the present embodiment can be applied to the disaster recovery system as shown in FIG. 1 or FIG. 2. The technical solution of the present embodiment can be executed by the first service end or the second service end. The method can include the following steps.

[0302] 701: Access the first service resource based on the access request through the first connection established with the first service resource.

[0304] In the present embodiment, the first service end and the second service end can both access the service resource based on the access request, which can reduce the pressure on a single service end and improve the performance of the system. Since the first computing system and the second computing system can provide services to the outside at the same time, compared with the main computing system providing services to the outside, the disaster recovery computing system is idle on a daily basis and is only enabled in the event of a failure, which improves the resource utilization. In addition, the first service end and the second service end both access the first service resource through the first connection, and in the event of a failure of the first service resource, the first service end and the second service end both access the second service resource through the second connection, which ensures that the two service ends access the same service resource and avoids the situation that simultaneous access to two service resources causes the two service resources to synchronize data and cause data to be overwritten, thereby ensuring the consistency of the data.

[0306] In some embodiments, when the technical solution of the embodiment shown in FIG. 7 is executed by the first service end, the above-mentioned establishing the first connection with the first service resource can include configuring an access alias and sending a first resolution request to the control system based on the access alias, and establishing the first connection with the first service resource according to the first access address fed back by the control system. The control system can map the first access domain name of the first service resource and the second access domain name of the second service resource to the same access alias, and configure the weight proportion corresponding to the first access domain name and the second access domain name respectively; in response to the first resolution request of the first service end, the access alias is converted into the first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name respectively.

[0308] In some embodiments, when the technical solution of the embodiment shown in FIG. 7 is executed by the second service end, the first connection with the first service resource can include: configuring an access alias, sending a second resolution request to the control system based on the access alias, and establishing the first connection with the first service resource according to the first access address fed back by the control system. The control system can map the first access domain name of the first service resource and the second access domain name of the second service resource to the same access alias, and configure the weight proportion corresponding to the first access domain name and the second access domain name respectively; in response to the second resolution request of the second service end, the access alias is converted into the first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name respectively.

[0310] In some embodiments, when the technical solution of the embodiment shown in FIG. 7 is executed by the first service end, the method can further include: in the case of failure of the first service resource, sending a third resolution request to the control system, and establishing a second connection with the second service resource according to the second access address fed back by the control system. The control system can update the weight proportion corresponding to the first access domain name and the second access domain name in the case of failure of the first service resource, and convert the access alias into the second access address of the second service resource according to the updated weight proportion according to the third resolution request.

[0312] In some embodiments, when the technical solution of the embodiment shown in FIG. 7 is executed by the second service end, the method can further include: in the case of failure of the first service resource, sending a fourth resolution request to the control system, and establishing a second connection with the second service resource according to the second access address fed back by the control system. The control system can update the weight proportion corresponding to the first access domain name and the second access domain name in the case of failure of the first service resource, and convert the access alias into the second access address of the second service resource according to the updated weight proportion according to the fourth resolution request.

[0314] In some embodiments, when the technical solution of the embodiment shown in FIG. 7 is executed by the first service end, the method can further include: in the case of disconnection of the first connection, sending a fifth resolution request to the control system, and establishing a second connection with the second service resource according to the second access address fed back by the control system.

[0316] In some embodiments, when the technical solution of the embodiment shown in FIG. 7 is executed by the second service end, the method can further include: in the case of disconnection of the first connection, sending a sixth resolution request to the control system, and establishing a second connection with the second service resource according to the second access address fed back by the control system.

[0318] In some embodiments, the method can further include: in the first service resource recovery case, disconnecting the second connection with the second service resource, and reconnecting the first connection with the first service resource.

[0320] In some embodiments, the method can further include: determining the first service resource recovery according to a recovery switching request sent by the control system.

[0322] In some embodiments, the first service resource can include a first cloud storage instance, and the second service resource can include a second cloud storage instance. The method can further include: saving the cache data to the first cloud storage instance.

[0324] FIG. 8 is a flowchart of one embodiment of a disaster recovery processing method according to the present disclosure. The technical solution of the present embodiment can be applied to the disaster recovery system as shown in FIG. 1 or FIG. 2. The technical solution of the present embodiment can be executed by the control system. The method can include the following steps:

[0326] 801: receiving an access request from at least one client.

[0328] 802: distributing the access request to a first service and a second service.

[0330] 803: in the first computing system failure case, sending the access request to the second service.

[0332] 804: in the second computing system failure case, sending the access request to the first service.

[0334] In the present embodiment, the control system distributes the access request to the first service and the second service. Both the first service and the second service can receive the access request, which can reduce the pressure on a single service and improve the performance of the system. Since the first computing system and the second computing system can provide services to the outside at the same time, compared with the main computing system providing services to the outside, the disaster recovery computing system is idle on a daily basis and is only enabled in the event of a failure, which improves the resource utilization.

[0336] In some embodiments, the method can further comprise: mapping the first access domain name of the first service resource and the second access domain name of the second service resource to the same access alias, and configuring the weight proportion corresponding to the first access domain name and the second access domain name respectively; in response to the first resolution request of the first service end, converting the access alias to the first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name respectively; in response to the second resolution request of the second service end, converting the access alias to the first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name respectively, and feeding back the first access address to the first service end and the second service end.

[0338] Therefore, the first service end and the second service end can both establish a connection with the first service resource according to the first access address, and access the first service resource through the first connection.

[0340] In some embodiments, the method can further comprise: in the case of failure of the first service resource, updating the weight proportion corresponding to the first access domain name and the second access domain name respectively, and in response to the third resolution request of the first service end, converting the access alias to the second access address of the second service resource according to the updated weight proportion; in response to the fourth resolution request of the second service end, converting the access alias to the second access address of the second service resource according to the updated weight proportion, and feeding back the second access address to the first service end and the second service end.

[0342] Therefore, the first service end and the second service end can both establish a connection with the second service resource according to the second access address, and access the second service resource through the second connection.

[0344] In the present embodiment, the method maps the first access domain name of the first service resource and the second access domain name of the second service resource to the same access alias, and configures the weight proportion corresponding to the first access domain name and the second access domain name respectively, and in response to the resolution request of the first service end or the second service end, feeds back the access address to the first service end or the second service end, so that the first service end and the second service end can both establish a connection to access the service resource, ensuring that the two service ends access the same service resource, avoiding data synchronization between the two service resources caused by simultaneous access to the two service resources, and ensuring data consistency.

[0346] In some embodiments, the method can further include: in response to the first service resource switching event, disabling the first access address to disconnect the first connection; updating the weight proportions corresponding to the first access domain name and the second access domain name respectively, and in response to a fifth resolution request of the first service end, converting the access alias to the second access address of the second service resource according to the updated weight proportions; and in response to a sixth resolution request of the second service end, converting the access alias to the second access address of the second service resource according to the updated weight proportions.

[0348] In the method, the first access address can be enabled in the case of the second connection being established.

[0350] In some embodiments, the distributing the access request to the first service end and the second service end can include: distributing the access request to the first service end and the second service end according to a routing rule. The routing rule can include one or more of the following implementation manners: a traffic proportion corresponding to the first computing system and the second computing system respectively; an access area corresponding to the first computing system and the second computing system respectively; and an access type corresponding to the first computing system and the second computing system respectively.

[0352] In some embodiments, the method can further include: determining a third service end associated with the first service end and deployed in the first computing system, and a fourth service end deployed in the second computing system.

[0354] The method can further include: in the case of the first service end being faulty, forwarding the access request sent to the third service end to the fourth service end; and in the case of the first service resource accessed by the first service end being faulty, controlling the third service end and the fourth service end to establish a fourth connection with a fourth service resource, so as to access the fourth service resource based on the access request distributed by the control system through the fourth connection. In some embodiments, the method can further include: in the case of the first computing system or the first service end being faulty, outputting a first fault prompt information; in response to a first fault switching request triggered by a user, sending the received access request to the second service end; in the case of the second computing system or the second service end being faulty, outputting a second fault prompt information; and in response to a second fault switching request triggered by a user, sending the received access request to the first service end.

[0356] In the embodiments, the fault can be automatically detected, the fault prompt information can be output to the user, the service end to which the access request is sent can be switched in response to the fault switching request triggered by the user, the access request can be processed in the case of the fault, and the continuity of the access can be ensured.

[0358] In some embodiments, the method can further output a recovery prompt information in the first resource recovery case; and in response to a user triggered fault recovery request, send a recovery switching request to the first server and the second server respectively.

[0360] In some embodiments, the control system can include a first control system; the first control system can include at least one first control end, and the at least one control end can be respectively deployed in the first computing system and the second computing system.

[0362] In some embodiments, the control system can include a first control system; the first control system can include at least one first control end, and the at least one control end can be respectively deployed in the first computing system and the second computing system.

[0364] In some embodiments, the control system can include a first control system; the first control system can include at least one first control end, and the at least one control end can be respectively deployed in the first computing system and the second computing system.

[0366] In some embodiments, the control system can include a second control system, and the second control system can include at least one second control end, and the at least one second control end can be distributed and deployed in the first computing system and the second computing system. The above-mentioned mapping of the first access domain name of the first service resource and the second access domain name of the second service resource to the same access alias, and configuring the weight proportion corresponding to the first access domain name and the second access domain name respectively; in response to the first resolution request of the first server, converting the access alias into the first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name respectively; and in response to the second resolution request of the second server, converting the access alias into the first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name respectively can include: using a target second control end in the at least one second control end, mapping the first access domain name of the first service resource and the second access domain name of the second service resource to the same access alias, and configuring the weight proportion corresponding to the first access domain name and the second access domain name respectively; in response to the first resolution request of the first server, converting the access alias into the first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name respectively; and in response to the second resolution request of the second server, converting the access alias into the first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name respectively.

[0368] In some embodiments, the control system can include a first control system; the first control system can include at least one first control end, and the at least one control end can be respectively deployed in the first computing system and the second computing system.

[0370] In some embodiments, the method can further include synchronizing the data in the first service resource to the second service resource. In some embodiments, the control system can include a first data synchronization component deployed in the first computing system and a second data synchronization component deployed in the second computing system.

[0372] The method can further include synchronizing, with the first data synchronization component, the data in the first service resource to the second service resource; and migrating, with the second data synchronization component, the data in the second service resource to the first service resource in the event of a recovery of the first service resource.

[0374] Embodiments of the present disclosure also provide a computing device, as shown in FIG. 9, which can include a storage component 901 and a processing component 902.

[0376] The storage component 901 stores one or more computer instructions, wherein the one or more computer instructions are called and executed by the processing component to implement the disaster recovery processing method as shown in FIG. 7 or the disaster recovery processing method as shown in FIG. 8.

[0378] Of course, the computing device can also include other components, such as an input / output interface, a display component, a communication component, etc.

[0380] The input / output interface provides an interface between the processing component and peripheral interface modules, which can be output devices, input devices, etc. The communication component is configured to facilitate wired or wireless communication between the computing device and other devices, etc.

[0382] The processing component 902 can include one or more processors to execute computer instructions to complete all or part of the steps in the above method. Of course, the processing component can also be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components, for executing the above method.

[0384] The storage component 901 is configured to store various types of data to support the operation of the terminal. The storage component can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0386] It should be noted that the computing device can be a physical device or an elastic computing host provided by a cloud computing platform. It can be implemented as a distributed cluster composed of multiple servers or terminal devices, or as a single server or a single terminal device.

[0388] It should be noted that when the computing device implements the disaster recovery processing method described in the embodiment shown in FIG. 7 or the disaster recovery processing method described in the embodiment shown in FIG. 8, the computing device can be a physical device or an elastic computing host provided by a cloud computing platform. It can be implemented as a distributed cluster composed of multiple servers or terminal devices, or as a single server or a single terminal device.

[0390] The embodiments of the present disclosure further provide a computer readable storage medium storing a computer program, which can implement the disaster recovery processing method described in the embodiment shown in FIG. 7 or the disaster recovery processing method described in the embodiment shown in FIG. 8 when executed by a computer. The computer readable medium can be included in the electronic device described in the above embodiments, or can exist separately and not be assembled into the electronic device.

[0392] The embodiments of the present disclosure further provide a computer program product including a computer program carried on a computer readable storage medium, which can implement the disaster recovery processing method described in the embodiment shown in FIG. 7 or the disaster recovery processing method described in the embodiment shown in FIG. 8 when executed by a computer. In such embodiments, the computer program can be downloaded and installed from a network, and / or installed from a removable medium. When the computer program is executed by a processor, various functions defined in the system of the present disclosure are executed.

[0394] The computer readable storage medium of the foregoing embodiments can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this disclosure, the computer readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.

[0396] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, apparatus and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be described here. The apparatus embodiments described above are only schematic, and the units described as separate components can or can not be physically separated, and the components displayed as units can or can not be physical units, i.e., they can be located in one place, or distributed on multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the embodiment scheme. Those skilled in the art can understand and implement without creative labor.

[0398] Through the description of the above embodiments, those skilled in the art can clearly understand that the embodiments can be realized by means of software and necessary general hardware platforms, and of course can also be realized by hardware. Based on such understanding, the above technical solutions can be embodied in the form of a software product, which can be stored in a computer readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute the methods described in each embodiment or some parts of the embodiments.

[0400] It should be noted that the above examples are only used to illustrate the technical solutions of the present disclosure, and not to limit them. Although the present disclosure has been described in detail with reference to the foregoing examples, those skilled in the art should understand that they can still modify the technical solutions recorded in the foregoing examples, or make equivalent replacements for some technical features. These modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure.

[0402] Industrial applicability

[0404] In the embodiments of the present disclosure, the first service end and the second service end can access the service resource based on the access request, which can reduce the pressure of a single service end and improve the performance of the system. Since the first computing system and the second computing system can provide services to the outside at the same time, compared with the main computing system providing services to the outside, the disaster recovery computing system is idle on a daily basis and is only enabled in the event of a failure, thereby improving the resource utilization rate. In addition, the first service end and the second service end access the first service resource through the first connection, and in the event of a failure of the first service resource, the first service end and the second service end access the second service resource through the second connection, which ensures that the two service ends access the same service resource, avoids the situation that simultaneous access to two service resources causes the two service resources to perform data synchronization and results in data coverage, and can ensure the consistency of the data.

Claims

1. Claim 2.1, A disaster recovery system, comprising a first computing system and a second computing system; a first service end and a first service resource are deployed in the first computing system; a second service end and a second service resource are deployed in the second computing system; the first service resource and the second service resource are backed up through data synchronization; 3. The first service end is configured to access the first service resource based on an access request through a first connection established with the first service resource, and access the second service resource based on the access request through a second connection established with the second service resource in the case of failure of the first service resource; 4. The second service end is configured to access the first service resource based on the access request through a first connection established with the first service resource, and access the second service resource based on the access request through a second connection established with the second service resource in the case of failure of the first service resource. 5.

2. The system of claim 1, wherein, The disaster recovery system further comprises a control system; 6. The control system is configured to receive an access request of at least one client and distribute the access request to the first service end and the second service end. 7.

3. The system of claim 2, wherein, The control system is further configured to map a first access domain name of the first service resource and a second access domain name of the second service resource to a same access alias, and configure a weight proportion corresponding to the first access domain name and the second access domain name respectively; in response to a first resolution request of the first service end, convert the access alias to a first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name respectively; in response to a second resolution request of the second service end, convert the access alias to a first access address of the first service resource according to the weight proportion corresponding to the first access domain name and the second access domain name respectively; 8. The first service end is further configured to configure the access alias, send a first resolution request to the control system based on the access alias, and establish a first connection with the first service resource according to the first access address fed back by the control system; 9. The second service end is further configured to configure the access alias, send a second resolution request to the control system based on the access alias, and establish a first connection with the first service resource according to the first access address fed back by the control system. 10.4、 The system of claim 3, wherein, The control system is further configured to update the weight proportion corresponding to the first access domain name and the second access domain name respectively in the case of failure of the first service resource, and convert the access alias to a second access address of the second service resource according to the weight proportion after the update according to a third resolution request of the first service end; in response to a fourth resolution request of the second service end, convert the access alias to a second access address of the second service resource according to the weight proportion after the update; 11. The first service end, further configured to, in the case of failure of the first service resource, send a third resolution request to the control system, and establish a second connection with the second service resource according to the second access address fed back by the control system; 12. The second service end, further configured to, in the case of failure of the first service resource, send a fourth resolution request to the control system, and establish a second connection with the second service resource according to the second access address fed back by the control system. 13.

5. The system of claim 3, wherein, The control system is further configured to, in response to a first service resource switching event, disable the first access address to disconnect the first connection; update the weight proportion corresponding to the first access domain name and the second access domain name respectively, and in response to a fifth resolution request of the first service end, convert the access alias to the second access address of the second service resource according to the updated weight proportion; in response to a sixth resolution request of the second service end, convert the access alias to the second access address of the second service resource according to the updated weight proportion; 14. The first service end, further configured to, in the case of disconnection of the first connection, send a fifth resolution request to the control system, and establish a second connection with the second service resource according to the second access address fed back by the control system; 15. The second service end, further configured to, in the case of disconnection of the first connection, send a sixth resolution request to the control system, and establish a second connection with the second service end according to the second access address fed back by the control system. 16.

6. The system of claim 5, wherein, The control system is further configured to, in the case of establishment of the second connection, enable the first access address. 17.7、 The system of claim 1, wherein, The first service end is further configured to, in the case of failure of the first service resource, disconnect the first connection established with the first service resource and establish a second connection with the second service resource; in the case of recovery of the first service resource, disconnect the second connection with the second service resource and recover the first connection with the first service resource; 18. The second service end is further configured to, in the case of failure of the first service resource, disconnect the first connection established with the first service resource and establish a second connection with the second service resource; in the case of recovery of the first service resource, disconnect the second connection with the second service resource and recover the first connection with the first service resource. 19.

8. The system of claim 2, wherein, The control system specifically distributes the access request of at least one client received to the first service end and the second service end according to a routing rule; 20. The routing rule includes one or more of the following implementation manners:

21. The traffic proportion corresponding to the first computing system and the second computing system respectively; 22. The access area corresponding to the first computing system and the second computing system respectively; 23. The access type corresponding to the first computing system and the second computing system respectively. 24.9、 The system of claim 2, wherein, The control system is further configured to determine a third service end associated with the first service end and deployed in the first computing system, and a fourth service end deployed in the second computing system; 25. The third service end is configured to access the third service resource based on the access request distributed by the control system through a third connection established with a third service resource deployed in the first computing system; and in the case of failure of the third service resource, access the fourth service resource based on the access request distributed by the control system through a fourth connection established with a fourth service resource deployed in the second computing system; 26. The fourth service end is configured to access the third service resource based on the access request distributed by the control system through the third connection established with the third service resource; and in the case of failure of the third service resource, access the fourth service resource based on the access request distributed by the control system through the fourth connection established with the fourth service resource; 27. The control system is further configured to, in the case of failure of the first service end, forward the access request sent to the third service end to the fourth service end; and in the case of failure of the first service resource accessed by the first service end, control the third service end and the fourth service end to establish a fourth connection with the fourth service resource, so as to access the fourth service resource based on the access request distributed by the control system through the fourth connection. 28.

10. The system of claim 2, wherein, The control system is further configured to, in the case of failure of the first computing system or the first service end, output a first failure prompt information; and in response to a first failure switching request triggered by a user, send the received access request to the second service end; and in the case of failure of the second computing system or the second service end, output a second failure prompt information. In response to a second failure switching request triggered by the user, send the received access request to the first service end. 29.

11. The system of claim 2, wherein, The control system comprises a first control system; the first control system comprises at least one first control end, and the at least one control end is respectively deployed in the first computing system and the second computing system; 30. A target first control end of the at least one first control end is configured to distribute the access request of the client to the first service end and the second service end; 31. The at least one first control end is configured to, in the case of failure of the target first control end, reselect any first control end as the target first control end. 32.

12. The system of claim 2, wherein, The control system comprises a first data synchronization component deployed in the first computing system and a second data synchronization component deployed in the second computing system; 33. The first data synchronization component is configured to synchronize data in the first service resource to the second service resource; 34. The second data synchronization component is configured to, in the case of recovery of the first service resource, migrate data in the second service resource to the first service resource. 35.

13. The system of any one of claims 1-12, wherein, The first service resource comprises a first cloud storage instance; and the second service resource comprises a second cloud storage instance.

36. The first service end is further configured to save the cache data to the first cloud storage instance; and the second service end is further configured to save the cache data to the first cloud storage instance. 37.

14. A disaster recovery system comprising a first computing system and a second computing system; the first computing system is deployed with a first service end and a first message queue; the second computing system is deployed with a second service end and a second message queue; the first message queue and the second message queue are backed up by data synchronization.

38. The first service end is configured to publish a first message in the first message queue based on a message publishing request via a first connection established with the first message queue, and set a first tag for the first message, and consume the first message with the first tag from the first message queue based on a message consuming request; In the case of failure of the second message queue, the second tag is configured to consume a second message with the second tag from the first message queue based on a message consuming request; 39. The second service end is configured to publish a second message in the second message queue based on a message publishing request via a second connection established with the second message queue, and set the second tag for the second message, and consume the second message with the second tag from the second message queue based on a message consuming request; in the case of failure of the first message queue, the first tag is configured to consume the first message with the first tag from the second message queue based on a message consuming request. 40.

15. The system of claim 14, wherein, Further comprising a control system; 41. The control system is configured to distribute a message publishing request or a message consuming request for target data to the first service end and the second service end. 42.

16. A method for disaster recovery processing, applied to a disaster recovery system, the disaster recovery system comprising a first computing system and a second computing system; the first computing system having a first service end and a first service resource deployed therein; the second computing system having a second service end and a second service resource deployed therein. The first service resource and the second service resource are backed up by data synchronization; the method comprises:

43. Accessing the first service resource based on an access request via a first connection established with the first service resource; In the case of failure of the first service resource, the first connection is disconnected, and the second service resource is accessed based on an access request via a second connection established with the second service resource. 44.

17. A method for disaster recovery processing, applied to a disaster recovery system, the disaster recovery system comprising a first computing system and a second computing system; the first computing system having a first service end and a first service resource deployed therein; the second computing system having a second service end and a second service resource deployed therein. The first service resource and the second service resource are backed up by data synchronization; the method comprises:

45. Receiving an access request of at least one client; 46. Distributing the access request to the first service end and the second service end; 47. In the case of failure of the first computing system, the access request is sent to the second service end; in the case of failure of the second computing system, the access request is sent to the first service end. 48.

18. A computing device, comprising a processing component, a storage component; the storage component stores one or more computer instructions; the one or more computer instructions are arranged to be invoked and executed by the processing component to implement the disaster recovery processing method of claim 16 or the disaster recovery processing method of claim 17. 49.

19. A computer storage medium, storing a computer program; the computer program, when executed by a computer, implements the disaster recovery processing method of claim 16 or the disaster recovery processing method of claim 17. 50.

20. A computer program product, comprising computer program / instructions; the computer program / instructions, when executed by a computer, implements the disaster recovery processing method of claim 16 or the disaster recovery processing method of claim 17.

Images