Cloud computing platform business system offsite disaster recovery method, device, equipment and medium

Abstract

The technical scheme of the embodiment of the present application comprises: performing stress testing on each of the business systems before going online to obtain performance indexes of each of the business systems; comprehensively determining a response strategy of DNS load balancing based on regional indexes, delay indexes of each public IP address and performance difference indexes of each of the business systems; monitoring the DNS load balancing and performing cross-region disaster recovery processing based on the response strategy. The scheme of the embodiment of the present application constructs cloud centers in multiple regions, deploys the same business systems in each cloud center, routes client traffic to multiple business systems through DNS load balancing, and determines the response strategy of the DNS load balancing based on three indexes, performs cross-region disaster recovery processing through the DNS load balancing, and is suitable for large business scenarios with high requirements for business continuity and strict requirements for data protection.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a cloud computing platform business system offsite disaster recovery method, device, equipment and medium. BACKGROUND

[0002] Cloud computing is one of the hottest topics in the field of IT infrastructure in recent years. It provides users with a very convenient resource usage method and flexible resource expansion capability through the virtualization abstraction of various resources such as computing, network, and storage. As enterprises increase their dependence on cloud computing systems, data loss or service interruption can cause significant losses, and the demand for offsite disaster recovery is increasing. Offsite disaster recovery is a disaster recovery solution that ensures that an organization's critical business and services can quickly recover and continue to operate in the event of a catastrophic event (such as natural disasters, power failures, network attacks, etc.) by establishing a backup center geographically remote from the main data center.

[0003] There are many methods for offsite disaster recovery, and different methods are suitable for different business scenarios, but there is currently no offsite disaster recovery solution suitable for large business scenarios with high business continuity requirements and strict data protection requirements. SUMMARY

[0004] The embodiments of the present application provide a cloud computing platform business system offsite disaster recovery method, device, equipment and medium, which is suitable for offsite disaster recovery of large business scenarios with high business continuity requirements and strict data protection requirements.

[0005] According to an aspect of the present application, a cloud computing platform business system offsite disaster recovery method is provided, which is applied to at least two cloud centers meeting offsite conditions, and each cloud center is deployed with the same business system. The method comprises:

[0006] Performing stress testing on each business system to obtain the performance indicators of each business system before going online;

[0007] Combining the regional indicators, the delay indicators of each public IP address, and the performance difference indicators of each business system to determine the response strategy of DNS load balancing;

[0008] Monitoring the DNS load balancing and performing offsite disaster recovery processing based on the response strategy.

[0009] Optionally, the stress testing on each business system to obtain the performance indicators of each business system comprises:

[0010] Determining the public IP address used by each business system to provide services externally and the operator corresponding to the public IP address;

[0011] performing performance testing on each of the business systems to obtain RPS values.

[0012] Optionally, the performance difference indicators of each of the business systems are determined by the following method:

[0013] the number of times that the DNS resolver receives a DNS resolution request and returns an IP address within a preset time, and the performance difference indicators are determined based on the number of times and a set threshold value; the threshold value is determined according to the hardware and software configurations of each of the cloud centers and the business systems and the stress testing results.

[0014] Optionally, the region indicators are determined by the following method:

[0015] the result of domain name resolution is determined according to the distance between the region where the visitor is located and the cloud center; the region where the visitor is located is determined according to the IP address of the visitor.

[0016] Optionally, the delay indicators are determined by the following method:

[0017] the network delay between the visitor and each of the business systems is determined, and the public network IP address with the minimum network delay is determined.

[0018] Optionally, the comprehensive region indicators, the delay of each public network IP address, and the performance difference indicators of each of the business systems are used to determine a response strategy of DNS load balancing, including:

[0019] the domain name provided by each of the business systems for external services is determined;

[0020] the priority of the region indicators, the delay of the public network IP address, and the performance difference indicators is determined to determine the response strategy.

[0021] Optionally, the DNS load balancing is monitored, and off-site disaster recovery processing is performed based on the response strategy, including:

[0022] if one of the public network IP addresses in the DNS load balancing is invalid, the public network IP address is deleted from the DNS record;

[0023] a health check interface is set, and the health status of each of the business systems is detected periodically; if it is found through the health status detection that a certain business system is unreachable or the response is timed out, the public network IP address of the business system for providing external services is removed from the DNS record;

[0024] when an IP address in the DNS load balancing recovers from a down state, the IP address is re-added to the list of available servers;

[0025] When a business system recovers from a fault state, the public network IP address provided by the business system is added in the DNS record.

[0026] According to another aspect of the present application, a cloud computing platform business system off-site disaster recovery device is provided, comprising:

[0027] A test unit is configured to perform stress testing on each business system to obtain performance indicators of each business system before going online.

[0028] A determination unit is configured to determine a DNS load balancing response strategy by comprehensively considering regional indicators, delay indicators of each public network IP address, and performance difference indicators of each business system.

[0029] A processing unit is configured to monitor the DNS load balancing and perform off-site disaster recovery processing based on the response strategy.

[0030] According to another aspect of the present application, an electronic device is provided, comprising:

[0031] At least one processor; and a memory connected to the at least one processor in communication; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to perform the cloud computing platform business system off-site disaster recovery method according to any one of the embodiments of the present application.

[0032] According to another aspect of the present application, a computer readable storage medium is provided, which stores computer instructions for enabling a processor to perform the cloud computing platform business system off-site disaster recovery method according to any one of the embodiments of the present application.

[0033] The technical scheme of the embodiments of the present application comprises: performing stress testing on each business system to obtain performance indicators of each business system before going online; determining a DNS load balancing response strategy by comprehensively considering regional indicators, delay indicators of each public network IP address, and performance difference indicators of each business system; and monitoring the DNS load balancing and performing off-site disaster recovery processing based on the response strategy. The scheme of the embodiments of the present application constructs cloud centers in multiple regions, deploys the same business system in each cloud center, routes client traffic to multiple business systems through DNS load balancing, and determines the response strategy of the DNS load balancing by relying on three indicators, thereby performing off-site disaster recovery processing through DNS load balancing, which is suitable for large business scenarios with high requirements for business continuity and strict requirements for data protection.

[0034] It should be appreciated that the description set forth in this section is not intended to identify key or essential features of embodiments of the application, nor is it intended to limit the scope of the application. Other BRIEF DESCRIPTION OF DRAWINGS

[0035] In order to more clearly illustrate the technical solutions of the embodiments of the present application or the prior art, the drawings required to be used in the embodiments or the prior art description will be briefly introduced as follows. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor on the basis of these drawings.

[0036] Figure 1 is a flow chart of a cloud computing platform business system off-site disaster recovery method provided by an embodiment of the present application;

[0037] Figure 2 is an architecture diagram of a cloud computing platform business system off-site disaster recovery method provided by an embodiment of the present application;

[0038] Figure 3 is a structural schematic diagram of a cloud computing platform business system off-site disaster recovery device provided by an embodiment of the present application;

[0039] Figure 4 is a structural schematic diagram of an electronic device for implementing the cloud computing platform business system off-site disaster recovery method of the embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some embodiments of the present application, not all embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0041] It is to be understood that the terminology "first", "second" and the like used in the specification and the claims of the application as well as the foregoing drawings is merely intended to distinguish between similar objects and not necessarily for describing a special sequential order. It is to be understood that the use of such terms can be interchanged insofar as is appropriate for the given embodiment of the application to be described herein. Furthermore, the terms "comprising", "having", "including", and "containing" and any variations thereof used herein are intended to cover a non-exclusive inclusion such that a process, method, system, product, or apparatus that comprises, has, includes or contains a list of steps or elements, but not only those recited as essential to the process, method, system, product, or apparatus, can also include other steps or elements not expressly listed or inherent to such process, method, system, product, or apparatus.

[0042] As Figure 1 shown, the embodiment of the application provides a cloud computing platform business system off-site disaster recovery method, which is applied to at least two cloud centers meeting off-site conditions, and the same business system is deployed in each cloud center; the method can include the following steps:

[0043] S110, performing stress testing on each business system to obtain the performance index of each business system before going online.

[0044] Wherein, two or more cloud centers are required, and these cloud centers meet the off-site condition. When a catastrophic event occurs in one of the cloud centers, such as natural disasters, power failures, network attacks, etc., other cloud centers are avoided from being affected by the disaster in the same area. The same business system is deployed in all cloud centers, and the data is synchronized in real time or periodically between all cloud centers through network connection, to ensure the consistency of data between the cloud centers in different regions. Each cloud center is equipped with necessary hardware and software resources to meet the use of the business system.

[0045] In the embodiment of the application, step S110 specifically includes: determining the public network IP address of each business system for providing external services and the operator corresponding to the public network IP address.

[0046] The performance test is performed on each business system to obtain the RPS value.

[0047] The performance of the business systems deployed in the cloud centers in different regions can be different, and the stress test is performed on each business system separately before going online to obtain the performance index. The public network IP addresses of the business systems deployed in the cloud centers in different regions for providing external services can be public network IP addresses of different operators, which are dispersed as much as possible to reduce the influence of the failure of a single operator on the entire system. These factors will determine the domain name resolution strategy of DNS load balancing.

[0048] Exemplarily, there are three cloud centers, cloud center 1, cloud center 2 and cloud center 3, and the business systems deployed in each cloud center are business system 1, business system 2 and business system 3 respectively. The public network IP address of the business system 1 for providing services externally is 39.156.100.11, which is a public network IP address of an operator 1, and the RPS (Requests Per Second) value of the performance test stress test is 50000; the public network IP address of the business system 2 for providing services externally is 39.156.100.12, which is a public network IP address of the operator 1, and the RPS value of the performance test stress test is 100000; the public network IP address of the business system 3 for providing services externally is 39.156.100.13, which is a public network IP address of an operator 2, and the RPS value of the performance test stress test is 80000. The performance index will also become a decision factor of the domain name resolution strategy of the DNS load balancing.

[0049] S120, the delay index of each public network IP address and the performance difference index of each business system are determined to determine the response strategy of the DNS load balancing.

[0050] In the embodiment of the application, step S1220 specifically comprises:

[0051] determining the domain name for providing services externally of each business system;

[0052] The priority of the region, the delay of the public network IP address and the performance difference index determines the response strategy.

[0053] The region, the delay of each public network IP address and the performance difference index of each business system determine the response strategy of the DNS load balancing. It is assumed that the domain name for providing services externally of the business system is service.cloud.cn. The priority of each index is in turn the performance difference of each business system, the region and the delay to each public network IP address from high to low. The domain name resolution strategy of the DNS load balancing will be judged from high to low according to the priority of these indexes to respond to the domain name resolution request of service.cloud.cn.

[0054] In the embodiment of the application, the performance difference index of each business system is determined by the following method:

[0055] The number of times that the DNS resolver receives the DNS resolution request and returns a certain IP address within a preset time is determined based on the number of times and a set threshold value to determine the performance difference index; the threshold value is determined according to the hardware and software configuration of each cloud center and each business system and the stress test result.

[0056] The performance difference index of each business system refers to the number of times that the DNS resolver receives DNS resolution requests and returns a certain IP address within a certain time. If the number of times reaches the set threshold, the DNS resolver will not resolve the domain name to this IP address in the next period of time to reduce the access pressure of this IP address. For example, the DNS resolver responded to 100000 resolution requests of the service.cloud.cn domain name within 10 minutes, of which 50000 times were resolved to the public network IP address 39.156.100.12 of the business system 2, and the request threshold of the public network IP address 39.156.100.12 was set to 50000 times, which has reached the threshold. Therefore, in the next ten minutes, the DNS resolver will not resolve service.cloud.cn to 39.156.100.12 when receiving DNS resolution requests, so as to avoid the risk of failure or response timeout of the business system 2 due to excessive access pressure in a short period of time. The thresholds of various IP addresses can be different, and the specific values are determined by the hardware and software configurations of each cloud center and business system and the stress test results. If the number of domain name resolution requests of all public network IP addresses does not reach the threshold within a certain time, that is, there is no risk of failure, the domain name resolution request result is determined according to the next index.

[0057] In the embodiment of the application, the regional index is determined by the following method:

[0058] The result of domain name resolution is determined according to the proximity of the geographical location between the region where the visitor is located and the cloud center. The region where the visitor is located is determined according to the IP address of the visitor.

[0059] The regional index refers to determining the result of domain name resolution according to the proximity of the geographical location between the region where the visitor is located and the cloud center. Similar to geographical location-aware load balancing, it is a load balancing technology that intelligently distributes network traffic based on the geographical location of the visitor. The purpose of this index is to route user requests to the cloud center closest to the geographical location, thereby reducing latency and improving access speed and user experience. When a user requests the resolution record of the domain name service.cloud.cn, the DNS load balancing system will try to determine the geographical location of the user, which is usually achieved by the IP address of the visitor. However, this is not absolutely accurate because the IP address may be hidden by a proxy or VPN service. If the geographical location of the user is determined by the IP address, the DNS load balancing system will select the nearest server according to the preset strategy. If the geographical location of the user cannot be determined, the result of the domain name resolution request is determined according to the next index.

[0060] In the embodiment of the application, the delay index is determined by the following method:

[0061] determining network delay between the visitor and each of the service systems, and determining the public network IP address with the minimum network delay.

[0062] The delay to each public network IP address refers to the network delay between the visitor and each of the service systems. When the two indexes cannot determine which IP address to return to the DNS domain name resolution request, the network delay between the visitor and each of the service systems is used to determine the public network IP address with the minimum network delay.

[0063] S130, monitoring the DNS load balancing and performing disaster recovery processing based on the response strategy.

[0064] In the embodiment of the application, step S130 specifically comprises:

[0065] If one public network IP address in the DNS load balancing is invalid, the public network IP address is deleted from the DNS record;

[0066] A health check interface is set to periodically detect the health status of each of the service systems. If the health status detection finds that a service system is unreachable or the response is timed out, the public network IP address of the service system for providing external services is removed from the DNS record;

[0067] When an IP address in the DNS load balancing recovers from the down state, the IP address is re-added to the list of available servers;

[0068] When a service system recovers from the fault state, the public network IP address of the service system for providing external services is added to the DNS record.

[0069] A configuration monitoring module is configured. If one public IP address in the DNS load balancing is disabled, it needs to be removed from the DNS record in time, and it is ensured that the client can be guided to the healthy business system. According to the business needs, each business system provides a special health check interface for the monitoring module to call. The health check interface is used to monitor the running state of the business system, and the monitoring module periodically detects the health state of each business system. If the health check finds that a certain business system is unreachable or the response is timed out, the DNS load balancing system will automatically remove the public IP address provided by the business system from the DNS record, trigger and alarm mechanism, and notify the operation and maintenance personnel through email, telephone or other channels that the business system in a certain cloud center is in an unusable state, so as to be repaired as soon as possible. In order to ensure that the client quickly adapts to the change of the DNS record, the minimum TTL (Time-to-Live) value needs to be set. In the case of low TTL value, the DNS cache of the client will expire faster, so that the client will request the new record from the DNS server more frequently, so that when a certain business system fails, the fault switching time will be as short as possible.

[0070] When an IP address in the DNS load balancing recovers from the down state, it should be re-added to the list of available servers so that it can receive traffic again. When the monitoring module monitors that a certain business system recovers from the fault state, it will automatically add the public IP address provided by the business system to the DNS record. This process can rely on the health check system to automatically recover, or rely on the operation and maintenance personnel to manually recover. When the operation and maintenance personnel handles the fault of the business system and restores the operation of the business system, the configuration of the DNS provider needs to be updated, such as modifying A record, CNAME record or MX record, etc.

[0071] Figure 2 is an architecture diagram of a cloud computing platform business system off-site disaster recovery method provided by an embodiment of the application, as shown in Figure 2 When the client initiates an access, it first sends a domain name resolution query request to the DNS load balancing, and then the DNS resolver decides which IP address to respond to the request through the distribution strategy described in the technical solution. Then the client will access the business system corresponding to the IP address according to the result of the DNS load balancing response.

[0072] The present solution is mainly suitable for large business scenarios with high business continuity requirements and strict data protection requirements. For this scenario, an off-site disaster recovery solution is proposed, which constructs cloud centers in each city and deploys a set of business systems in each cloud center region to provide services to the outside, and finally connects these business systems of the cloud centers in parallel through DNS load balancing to provide services to the outside.

[0073] Compared with other off-site disaster recovery solutions, the present solution has the following advantages:

[0074] The business systems among several cloud centers are backed up to each other and simultaneously provide services externally, greatly improving the overall performance level of the system.

[0075] The disaster recovery capability is strong, and even if all cloud centers in a certain region are offline due to some reasons, the cloud centers in other regions will not be affected, and the entire system can still provide access capabilities externally.

[0076] The business system can be deployed in clusters and can be horizontally expanded, and can be dynamically increased or decreased according to requirements to meet the demand for different levels of access during peak and off-peak periods.

[0077] As shown in Figure 3 The embodiment of the present application provides an off-site disaster recovery device for a cloud computing platform business system, which can include the following units:

[0078] The test unit 310 is used to perform stress testing on each business system before going online to obtain the performance indicators of each business system.

[0079] The determination unit 320 is used to determine the response strategy of DNS load balancing by comprehensively considering the regional indicators, the delay indicators of each public IP address, and the performance difference indicators of each business system.

[0080] The processing unit 330 is used to monitor the DNS load balancing and perform off-site disaster recovery processing based on the response strategy.

[0081] Optionally, the test unit 310 is specifically used to perform:

[0082] Determine the public IP address used by each business system to provide services externally and the operator corresponding to the public IP address.

[0083] Perform performance testing on each business system to obtain the RPS value.

[0084] Optionally, the determination unit 320 is used to determine the performance difference indicators of each business system in the following manner:

[0085] Determine the number of times that the DNS resolver receives a DNS resolution request and returns a certain IP address within a preset time, and determine the performance difference indicators based on the number and a set threshold value; the threshold value is determined according to the software and hardware configurations of each cloud center and the business system and the stress testing results.

[0086] Optionally, the determination unit 320 is used to determine the regional indicators in the following manner:

[0087] The result of domain name resolution is determined according to the distance between the region where the visitor is located and the cloud center, and the region where the visitor is located is determined according to the IP address of the visitor.

[0088] Optionally, the determining unit 320 is configured to determine the delay index by the following manner:

[0089] The network delay between the visitor and each of the service systems is determined, and the public network IP address with the minimum network delay is determined.

[0090] Optionally, the determining unit 320 is specifically configured to perform the following steps:

[0091] The domain name provided by each of the service systems is determined;

[0092] The priority of the region, the delay of the public network IP address and the performance difference index determines the response strategy.

[0093] Optionally, the processing unit 330 is specifically configured to perform the following steps:

[0094] If one public network IP address in the DNS load balancing is invalid, the public network IP address is deleted from the DNS record;

[0095] A health check interface is set, and the health state of each of the service systems is detected periodically; if it is found through the health state detection that a service system is unreachable or the response is timed out, the public network IP address provided by the service system to the outside is removed from the DNS record;

[0096] When one IP address in the DNS load balancing is recovered from the down state, the IP address is added to the list of available servers again;

[0097] When a service system is recovered from the fault state, the public network IP address provided by the service system to the outside is added to the DNS record.

[0098] It can be understood that the structure of the embodiment of the present application does not constitute a specific limitation on the cloud computing platform service system off-site disaster recovery device. In other embodiments of the present application, the cloud computing platform service system off-site disaster recovery device can include more or fewer components than the diagram, or combine certain components, or split certain components, or different component arrangement. The components shown can be implemented in hardware, software or a combination of software and hardware.

[0099] The information interaction, execution process and the like between the units in the above device are based on the same concept as the method embodiments of the present application, and the specific content can be referred to the description in the method embodiments of the present application, which will not be described here.

[0100] Figure 4A structural diagram of an electronic device 10 that can be used to implement embodiments of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptops, desktops, tablets, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smartphones, wearable devices (e.g., headsets, glasses, watches, etc.), and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application described and / or claimed in this document.

[0101] As shown in Figure 4 The electronic device 10 includes at least one processor 11, and a memory, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., connected in communication with the at least one processor 11, where the memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes according to the computer programs stored in the read-only memory (ROM) 12 or loaded into the random access memory (RAM) 13 from the storage unit 18. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0102] Various components in the electronic device 10 are connected to the I / O interface 15, including an input unit 16, such as a keyboard, a mouse, etc., an output unit 17, such as various types of displays, speakers, etc., a storage unit 18, such as a magnetic disk, an optical disk, etc., and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network, such as the Internet, and / or various telecommunication networks.

[0103] The processor 11 can be various general and / or special purpose processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 performs various methods and processes described above, such as the cloud computing platform business system offsite disaster recovery method.

[0104] In some embodiments, the cloud computing platform business system offsite disaster recovery method can be implemented as a computer program tangibly embodied in a computer readable storage medium, e.g., storage unit 18. In some embodiments, parts or all of the computer program can be loaded and / or installed onto electronic device 10 via, e.g., ROM 12 and / or communication unit 19. When the computer program is loaded onto RAM 13 and executed by processor 11, one or more steps of the cloud computing platform business system offsite disaster recovery method described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to perform the cloud computing platform business system offsite disaster recovery method by way of other means (e.g., by way of firmware).

[0105] Various implementations of the systems and techniques described above can be realized in digital electronic circuitry, integrated circuitry, specially designed application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

[0106] Computer programs used to implement the methods of the application can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the computer program, when executed by the processor of the machine, implements the functions / acts specified in the flowcharts and / or block diagrams. The computer program can be executed entirely on a machine, partially on a machine, partially on a machine and partially on a remote machine or entirely on a remote machine or server.

[0107] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer-readable storage medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of a machine-readable storage medium will include one or more lines of a program of instructions in a transitory signal, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0108] To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

[0109] The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a user computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0110] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system, to solve the defects of large management difficulty and weak business scalability in traditional physical host and VPS service.

[0111] It should be understood that the various forms of flow shown above can be used to reorder, add or delete steps. For example, each step described in the present application can be executed in parallel, sequentially or in a different order, as long as the desired results of the technical solutions of the present application can be achieved, which is not limited herein.

[0112] The above detailed description does not constitute a limitation on the scope of protection of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A cloud computing platform business system off-site disaster recovery method, characterized in that, The method is applied to at least two cloud centers meeting the off-site condition, each of which is deployed with the same business system, and comprises the following steps: Before going online, each business system is stress tested to obtain the performance index of each business system; The regional index, the delay index of each public IP address, and the performance difference index of each business system are integrated to determine the response strategy of DNS load balancing; The DNS load balancing is monitored, and off-site disaster recovery is processed based on the response strategy; the performance difference index of each business system is determined by the following method: The number of times that a DNS resolver receives a DNS resolution request and returns a certain IP address within a preset time is determined based on the number of times and a set threshold to determine the performance difference index; the threshold is determined according to the hardware and software configuration of each cloud center and the business system and the stress test result; The regional index, the delay of each public IP address, and the performance difference index of each business system are integrated to determine the response strategy of DNS load balancing, which comprises the following steps: The domain name of each business system for providing external services is determined; The priority of the regional index, the delay of each public IP address, and the performance difference index is determined to determine the response strategy; The DNS load balancing is monitored, and off-site disaster recovery is processed based on the response strategy, which comprises the following steps: If one public IP address in the DNS load balancing is invalid, the public IP address is deleted from the DNS record; A health check interface is set to periodically detect the health status of each business system; if the health status detection finds that a business system is unreachable or the response is timed out, the public IP address of the business system for providing external services is removed from the DNS record; When an IP address in the DNS load balancing recovers from the down state, it is added to the list of available servers; When a business system recovers from the fault state, the public IP address of the business system for providing external services is added to the DNS record.

2. The method of claim 1, wherein, The performance index of each business system is obtained by stress testing each business system, which comprises the following steps: The public IP address of each business system for providing external services and the operator corresponding to the public IP address are determined; The performance of each business system is tested to obtain the RPS value.

3. The method of claim 1, wherein, The regional index is determined by the following method: The result of domain name resolution is determined according to the distance between the visitor's region and the geographic location of the cloud center; the visitor's region is determined according to the IP address of the visitor.

4. The method of claim 1, wherein, The delay index is determined by the following method: The network delay between the visitor and each business system is determined to determine the public IP address with the minimum network delay.

Images