Remote disaster recovery method, device and equipment for cloud computing platform service system and medium

Abstract

According to the technical scheme of the embodiment of the invention, the method comprises the steps: carrying out a pressure test on each business system before the business system is online, and obtaining a performance index of each business system; a domain index, the delay index of each public network IP address and the performance difference index of each service system are integrated, and a DNS load balancing response strategy is determined; and monitoring the DNS load balance, and carrying out remote disaster recovery processing based on the response strategy. According to the scheme of the embodiment of the invention, the cloud centers are constructed in a plurality of regions, the same service system is deployed in each cloud center, the client traffic is routed to a plurality of service systems through DNS load balancing, the response strategy of DNS load balancing depends on three indexes for judgment, remote disaster recovery processing is carried out through DNS load balancing, and the disaster recovery efficiency is improved. The method is suitable for large-scale business scenes with high business continuity requirements and strict requirements for data protection.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, equipment and medium for off-site disaster recovery of a cloud computing platform business system. Background Art

[0002] Cloud computing is one of the hottest topics in the field of IT infrastructure in recent years. Its virtualization and abstraction of various resources such as computing, networking, and storage provide users with extremely convenient resource usage and flexible resource expansion capabilities. As enterprises become more dependent on cloud computing systems, data loss or service interruptions may lead to significant losses, and the demand for off-site disaster recovery is increasing. Off-site disaster recovery is a disaster recovery solution that ensures that an organization's key businesses and services can be quickly restored and continue to operate in the event of a catastrophic event (such as a natural disaster, power failure, or cyber attack).

[0003] There are many methods of off-site disaster recovery at present, and different methods are applicable to different business scenarios. However, there is currently no off-site disaster recovery solution suitable for large-scale business scenarios with high requirements for business continuity and strict requirements for data protection. Summary of the invention

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

[0005] According to one aspect of the present invention, a remote disaster recovery method for a business system of a cloud computing platform is provided, which is applied to at least two cloud centers that meet remote conditions, and each of the cloud centers has the same business system deployed therein, and the method comprises:

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

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

[0008] The DNS load balancing is monitored, and remote disaster recovery is performed based on the response strategy.

[0009] Optionally, the stress testing of each of the business systems to obtain a performance indicator of each of the business systems includes:

[0010] Determine the public IP address of each business system used to provide external services and the operator corresponding to the public IP address;

[0011] A performance test is performed on each of the business systems to obtain an RPS value.

[0012] Optionally, the performance difference index of each of the business systems is determined in the following manner:

[0013] The number of times the DNS resolver receives a DNS resolution request and returns a certain IP address within a preset time, and the performance difference index is determined based on the number and a set threshold; the threshold is determined based on the software and hardware configuration of each of the cloud centers and the business system and the stress test results.

[0014] Optionally, the regional indicator is determined by:

[0015] The result of the domain name resolution is determined according to the geographical location distance between the visitor's location and the cloud center, and the visitor's location is determined according to the visitor's IP address.

[0016] Optionally, the delay indicator is determined in the following manner:

[0017] Determine the network delay between the visitor and each of the business systems, and determine the public IP address with the smallest network delay.

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

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

[0020] The response strategy is determined by determining the region, the delay of the public IP address, and the priority of the performance difference indicator.

[0021] Optionally, the monitoring of the DNS load balancing and performing remote disaster recovery processing based on the response strategy include:

[0022] If a public IP address in DNS load balancing fails, delete the public IP address from the DNS record;

[0023] Set up a health check interface to regularly check the health status of each business system; if the health status check finds that a business system is unreachable or the response has timed out, remove the public IP address of the business system that provides services to the outside world from the DNS record;

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

[0025] When a business system recovers from a faulty state, the public IP address provided by the business system to the outside world is added to the DNS record.

[0026] According to another aspect of the present invention, a remote disaster recovery device for a cloud computing platform business system is provided, comprising:

[0027] A testing unit, used to perform a stress test on each of the business systems before going online to obtain performance indicators of each of the business systems;

[0028] A determination unit, configured to determine a DNS load balancing response strategy based on a comprehensive regional indicator, a delay indicator of each public IP address, and a performance difference indicator of each of the business systems;

[0029] The processing unit is used to monitor the DNS load balancing and perform remote disaster recovery processing based on the response strategy.

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

[0031] At least one processor; and a memory communicatively connected to the at least one processor; 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 so that the at least one processor can execute the off-site disaster recovery method for a cloud computing platform business system as described in any embodiment of the present invention.

[0032] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the off-site disaster recovery method for a cloud computing platform business system described in any embodiment of the present invention when executed.

[0033] The technical solution of the embodiment of the present invention includes: stress testing each of the business systems before going online to obtain the performance indicators of each of the business systems; comprehensively considering the regional indicators, the delay indicators of each public IP address and the performance difference indicators of each of the business systems to determine the response strategy of DNS load balancing; monitoring the DNS load balancing and performing off-site disaster recovery based on the response strategy. The solution of the embodiment of the present invention builds cloud centers in multiple regions, each cloud center deploys the same business system, and routes client traffic to multiple business systems through DNS load balancing. The response strategy of DNS load balancing relies on three indicators to judge, and off-site disaster recovery is performed through DNS load balancing, which is suitable for large-scale business scenarios with high requirements for business continuity and strict requirements for data protection.

[0034] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0036] Figure 1 It is a flow chart of a remote disaster recovery method for a cloud computing platform business system provided by an embodiment of the present invention;

[0037] Figure 2 This is an architecture diagram of a remote disaster recovery method for a cloud computing platform business system provided by an embodiment of the present invention;

[0038] Figure 3 It is a schematic diagram of the structure of a remote disaster recovery device for a cloud computing platform business system provided by an embodiment of the present invention;

[0039] Figure 4 It is a structural schematic diagram of an electronic device for implementing the remote disaster recovery method of a cloud computing platform business system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0040] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

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

[0042] like Figure 1 As shown, an embodiment of the present invention provides a remote disaster recovery method for a cloud computing platform business system, which is applied to at least two cloud centers that meet remote conditions, and each of the cloud centers has the same business system deployed; the method may include the following steps:

[0043] S110 . Perform a stress test on each of the business systems before going online to obtain performance indicators of each of the business systems.

[0044] Among them, two or more cloud centers are required, and these cloud centers meet the remote conditions. When a catastrophic event such as natural disasters, power failures, network attacks, etc. occurs in one of the cloud centers, other cloud centers are prevented from being affected by the disaster in the same area. The same business system is deployed in all cloud centers, and data is synchronized in real time or regularly through network connections between all cloud centers to ensure data consistency between cloud centers in various regions. Each cloud center is equipped with necessary hardware and software resources to meet the use of business systems.

[0045] In the embodiment of the present invention, step S110 specifically includes: determining a public network IP address used by each of the business systems to provide services externally and an operator corresponding to the public network IP address;

[0046] A performance test is performed on each of the business systems to obtain an RPS value.

[0047] The performance of business systems deployed in cloud centers in different regions can vary. Before going online, each business system is stress-tested to obtain performance indicators. The public IP addresses of business systems deployed in cloud centers in different regions that provide services to the outside world can be public IP addresses of different operators, and they should be dispersed as much as possible to reduce the impact of a single operator's failure on the entire system. These factors will determine the domain name resolution strategy of DNS load balancing.

[0048] For example, there are currently three cloud centers, Cloud Center 1, Cloud Center 2, and Cloud Center 3; the business systems deployed in each cloud center are Business System 1, Business System 2, and Business System 3. The public IP address of Business System 1 for providing services to the outside is 39.156.100.11, which is the public IP address of Operator 1, and the RPS (Requests Per Second) value measured by performance test is 50,000; the public IP address of Business System 2 for providing services to the outside is 39.156.100.12, which is the public IP address of Operator 1, and the RPS value measured by performance test is 100,000; the public IP address of Business System 3 for providing services to the outside is 39.156.100.13, which is the public IP address of Operator 2, and the RPS value measured by performance test is 80,000. Performance indicators will also become the determining factors of the domain name resolution strategy of DNS load balancing.

[0049] S120, determining a DNS load balancing response strategy based on the regional index, the delay index of each public IP address, and the performance difference index of each of the business systems.

[0050] In the embodiment of the present invention, step S1220 specifically includes:

[0051] Determine the domain name for external services provided by each of the business systems;

[0052] The response strategy is determined by determining the region, the delay of the public IP address, and the priority of the performance difference indicator.

[0053] The DNS load balancing response strategy is determined based on the region, the latency of each public IP address, and the performance difference indicators of each business system. Assume that the service domain name provided by the business system to the outside world is service.cloud.cn. The priority of each indicator is from high to low, which is the performance difference of each business system, the region, and the latency to each public IP address. The DNS load balancing domain name resolution strategy will respond to the domain name resolution request of service.cloud.cn based on the priority of these indicators, from high to low.

[0054] In the embodiment of the present invention, the performance difference index of each of the business systems is determined in the following manner:

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

[0056] The performance difference index of each business system refers to the number of times the DNS resolver receives DNS resolution requests and returns a certain IP address within a certain period of time. If the number reaches the set threshold, the DNS resolver will no longer 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 100,000 resolution requests for the domain name service.cloud.cn within 10 minutes, of which 50,000 were resolved to the public IP address 39.156.100.12 that business system 2 provides services to the outside world. The request threshold for the public IP address 39.156.100.12 is set to 50,000 times, which has reached the threshold. In the next ten minutes, when the DNS resolver receives DNS resolution requests, it will no longer resolve service.cloud.cn to 39.156.100.12, so as to avoid the risk of failure due to excessive access pressure on business system 2 in a short period of time, or response time timeout. The thresholds for each IP address can be different, and the specific values ​​are determined by the software and hardware configurations of each cloud center and business system and the stress test results. If the number of domain name resolution requests for all public IP addresses does not reach the threshold within a certain period of time, that is, there is no risk of failure, the domain name resolution request result is judged according to the next indicator.

[0057] In the embodiment of the present invention, the regional index is determined in the following manner:

[0058] The result of the domain name resolution is determined according to the geographical location distance between the visitor's location and the cloud center, and the visitor's location is determined according to the visitor's IP address.

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

[0060] In the embodiment of the present invention, the delay index is determined by:

[0061] Determine the network delay between the visitor and each of the business systems, and determine the public IP address with the smallest network delay.

[0062] The delay to each public IP address refers to the network delay between the visitor and each business system. When the current two indicators cannot determine which IP address to return to the DNS domain name resolution request, the network delay between the visitor and each business system is used to determine and return the public IP address with the smallest network delay.

[0063] S130: Monitor the DNS load balancing and perform remote disaster recovery based on the response strategy.

[0064] In the embodiment of the present invention, step S130 specifically includes:

[0065] If a public IP address in DNS load balancing fails, delete the public IP address from the DNS record;

[0066] Set up a health check interface to regularly check the health status of each business system; if the health status check finds that a business system is unreachable or the response has timed out, remove the public IP address of the business system that provides services to the outside world from the DNS record;

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

[0068] When a business system recovers from a faulty state, the public IP address provided by the business system to the outside world is added to the DNS record.

[0069] Configure the monitoring module. If a public IP address in the DNS load balancing fails, it needs to be removed from the DNS record in time, and ensure that the client can be directed to a healthy business system. According to business needs, each business system provides a special health check interface for the monitoring module to call. This health check interface is used to monitor the operating status of the business system. The monitoring module regularly checks the health status of each business system. If the health check finds that a business system is unreachable or the response is timed out, the DNS load balancing system will automatically remove the public IP address of the business system that provides services to the outside world from the DNS record, and trigger the alarm mechanism to notify the operation and maintenance personnel through email, phone or other channels that a business system in a cloud center is unavailable, so as to repair it as soon as possible. In order to ensure that the client can quickly adapt to changes in DNS records, it is necessary to set the lowest TTL (Time-to-Live) value. In the case of a low TTL value, the client's DNS cache will expire faster, so that new records will be requested from the DNS server more frequently. In this way, when a business system fails, the failover time will be as short as possible.

[0070] When an IP address in DNS load balancing recovers from the down state, it should be added back to the list of available servers so that it can receive traffic again. When the monitoring module detects that a business system has recovered from a faulty state, it will automatically add the public IP address provided by the business system to the DNS record. This process can be automatically restored by the health check system or manually restored by the operation and maintenance personnel. After the operation and maintenance personnel have handled the business system failure and restored the business system to operation, they need to update the DNS provider's configuration, such as modifying the A record, CNAME record, or MX record.

[0071] Figure 2 is an architecture diagram of a remote disaster recovery method for a cloud computing platform business system provided by an embodiment of the present invention, such as Figure 2 As shown in the figure, when the client initiates access, it first sends a domain name resolution query request to the DNS load balancer, and then the DNS resolver uses the distribution strategy described in the technical solution to decide which IP address to use to respond to the request. The client then accesses the business system of the corresponding IP address based on the result of the DNS load balancer's response.

[0072] This solution is mainly applicable to large-scale business scenarios with high requirements for business continuity and strict requirements for data protection. For this scenario, a remote disaster recovery solution is proposed, which builds cloud centers in various cities, and deploys a business system in each cloud center region to provide external services. Finally, the business systems of these cloud centers are connected in parallel through DNS load balancing to provide unified external services.

[0073] Compared with other remote disaster recovery solutions, this solution has the following advantages:

[0074] The business systems between several cloud centers back up each other and provide services to the outside world at the same time, greatly improving the overall performance level of the system.

[0075] The disaster recovery capability is strong. Even if a cloud center in a certain place is completely offline for some reason, it will not affect the cloud centers in other regions, and the entire system can still provide external access capabilities.

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

[0077] like Figure 3 As shown, an embodiment of the present invention provides a remote disaster recovery device for a cloud computing platform business system, which may include the following units:

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

[0079] A determination unit 320, configured to determine a DNS load balancing response strategy by comprehensively considering the regional index, the delay index of each public IP address, and the performance difference index of each of the business systems;

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

[0081] Optionally, the testing unit 310 is specifically configured to perform:

[0082] Determine the public IP address of each business system used to provide external services and the operator corresponding to the public IP address;

[0083] A performance test is performed on each of the business systems to obtain an RPS value.

[0084] Optionally, the determining unit 320 is configured to determine the performance difference index of each business system in the following manner:

[0085] The number of times the DNS resolver receives a DNS resolution request and returns a certain IP address within a preset time, and the performance difference index is determined based on the number and a set threshold; the threshold is determined based on the software and hardware configuration of each of the cloud centers and the business system and the stress test results.

[0086] Optionally, the determining unit 320 is configured to determine the regional indicator in the following manner:

[0087] The result of the domain name resolution is determined according to the geographical location distance between the visitor's location and the cloud center, and the visitor's location is determined according to the visitor's IP address.

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

[0089] Determine the network delay between the visitor and each of the business systems, and determine the public IP address with the smallest network delay.

[0090] Optionally, the determining unit 320 is specifically configured to execute:

[0091] Determine the domain name for external services provided by each of the business systems;

[0092] The response strategy is determined by determining the region, the delay of the public IP address, and the priority of the performance difference indicator.

[0093] Optionally, the processing unit 330 is specifically configured to execute:

[0094] If a public IP address in DNS load balancing fails, delete the public IP address from the DNS record;

[0095] Set up a health check interface to regularly check the health status of each business system; if the health status check finds that a business system is unreachable or the response has timed out, remove the public IP address of the business system that provides services to the outside world from the DNS record;

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

[0097] When a business system recovers from a faulty state, the public IP address provided by the business system to the outside world is added to the DNS record.

[0098] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the off-site disaster recovery device of the cloud computing platform business system. In other embodiments of the present invention, the off-site disaster recovery device of the cloud computing platform business system may include more or fewer components than those shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0099] The information interaction, execution process and other contents between the units in the above-mentioned device are based on the same concept as the embodiment of the method of the present invention. For specific contents, please refer to the description in the embodiment of the method of the present invention, and no further description is given here.

[0100] Figure 4A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0101] like Figure 4 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. 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] A number of 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 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 may be a variety of general and / or special 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 artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The processor 11 executes the various methods and processes described above, such as a remote disaster recovery method for a cloud computing platform business system.

[0104] In some embodiments, the off-site disaster recovery method for a cloud computing platform business system may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the off-site disaster recovery method for a cloud computing platform business system described above may be executed. Alternatively, in other embodiments, the processor 11 may be configured to execute the off-site disaster recovery method for a cloud computing platform business system in any other appropriate manner (e.g., by means of firmware).

[0105] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0106] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0107] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0108] To provide interaction with a user, the systems and techniques described herein may 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 trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0109] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may 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] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may 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 difficult management and weak business scalability in traditional physical hosts and VPS services.

[0111] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0112] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A remote disaster recovery method for a cloud computing platform business system, characterized in that: Applied to at least two cloud centers that meet remote conditions, each of which has the same business system deployed, the method includes: Performing stress testing on each of the business systems before going online to obtain performance indicators of each of the business systems; Determine the DNS load balancing response strategy based on the regional indicators, the delay indicators of each public IP address, and the performance difference indicators of each business system; The DNS load balancing is monitored, and remote disaster recovery is performed based on the response strategy.

2. The method according to claim 1, characterized in that The stress testing of each of the business systems to obtain the performance indicators of each of the business systems includes: Determine the public IP address of each business system used to provide external services and the operator corresponding to the public IP address; A performance test is performed on each of the business systems to obtain an RPS value.

3. The method according to claim 1, characterized in that The performance difference index of each of the business systems is determined in the following manner: The number of times the DNS resolver receives a DNS resolution request and returns a certain IP address within a preset time, and the performance difference index is determined based on the number and a set threshold; the threshold is determined based on the software and hardware configuration of each of the cloud centers and the business system and the stress test results.

4. The method according to claim 1, characterized in that: The regional indicators are determined in the following way: The result of the domain name resolution is determined according to the geographical location distance between the visitor's location and the cloud center, and the visitor's location is determined according to the visitor's IP address.

5. The method according to claim 1, characterized in that The delay index is determined in the following way: Determine the network delay between the visitor and each of the business systems, and determine the public IP address with the smallest network delay.

6. The method according to claim 1, characterized in that The comprehensive region, the delay of each public IP address and the performance difference index of each business system determine the DNS load balancing response strategy, including: Determine the domain name for external services provided by each of the business systems; The response strategy is determined by determining the region, the delay of the public IP address, and the priority of the performance difference indicator.

7. The method according to claim 1, characterized in that The monitoring of the DNS load balancing and performing remote disaster recovery processing based on the response strategy include: If a public IP address in DNS load balancing fails, delete the public IP address from the DNS record; Set up a health check interface to regularly check the health status of each business system; if the health status check finds that a business system is unreachable or the response has timed out, remove the public IP address of the business system that provides services to the outside world from the DNS record; When an IP address in DNS load balancing recovers from the down state, it is re-added to the list of available servers; When a business system recovers from a faulty state, the public IP address provided by the business system to the outside world is added to the DNS record.

8. A remote disaster recovery device for a cloud computing platform business system, characterized in that: include: A testing unit, used to perform a stress test on each of the business systems before going online to obtain performance indicators of each of the business systems; A determination unit, configured to determine a DNS load balancing response strategy based on a comprehensive regional indicator, a delay indicator of each public IP address, and a performance difference indicator of each of the business systems; The processing unit is used to monitor the DNS load balancing and perform remote disaster recovery processing based on the response strategy.

9. An electronic device, characterized in that include: at least one processor; And a memory communicatively connected to the at least one processor; 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 so that the at least one processor can execute the off-site disaster recovery method for a cloud computing platform business system as described in any one of claims 1-7.

10. A computer readable medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the off-site disaster recovery method for a cloud computing platform business system according to any one of claims 1 to 7 when executed.

Images