Disaster recovery system, method, computer equipment and medium for multiple data centers

By using a combination of DNS servers, firewalls and load devices in the data center, monitoring and distributing client requests and selecting a healthy data center, the problem of high maintenance costs of disaster recovery systems in the existing technology is solved, and efficient request distribution is achieved and disaster recovery efficiency improves.

CN113242299BActive Publication Date: 2024-11-22CORMORANT TECH (SHENZHEN) CO LTD
View PDF 10 Cites 0 Cited by

Patent Information

Application Number
CN202110510229.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-05-11
Publication Date
2024-11-22
Estimated Expiration
2041-05-11

AI Technical Summary

Technical Problem

The existing data center disaster recovery system has high maintenance costs and is difficult to effectively reduce.

Method used

The disaster recovery system adopts a multi-data center, including a DNS server, a firewall and at least two load devices. The domain name is converted into a private network IP address through the DNS server. The firewall maps the private network IP address to a public network IP, and the load device monitors the data center. Health status, and select healthy data centers according to the DNS distribution algorithm to avoid the impact of downtime and improve load efficiency and disaster recovery efficiency.

Benefits of technology

It realizes rapid request distribution, reduces the interference of data center downtime on requests, improves data disaster recovery efficiency, and saves public IP application and maintenance costs through internal and external network mapping.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113242299B_ABST
    Figure CN113242299B_ABST
Patent Text Reader

Abstract

The present invention discloses a multi-data center disaster recovery system, method, computer equipment and medium. The method comprises: when receiving a client access request, obtaining a target domain name from the access request, and then sending a private network IP corresponding to the target domain name to a load device through a DNS server, and then using a firewall to map the private network IP and virtual service IP in the load device to a public network IP, so as to obtain the public network IP of the data center corresponding to the load device, and monitoring the health status of the data center through the load device, and using a DNS distribution algorithm to select a target data center from data centers with a healthy health status, and then feeding back the public network IP of the target data center to the client. The present invention is conducive to saving the cost of data disaster recovery and improving the efficiency of data disaster recovery.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of data processing, and in particular to a multi-data center disaster recovery system, method, computer equipment and medium. Background Art

[0002] With the rapid development of computer technology, the demand for data processing is increasing. In order to better meet the demand for data processing, some institutions or enterprises have built data centers to store and process data. However, due to the particularity of data, in order to ensure data security, it is often necessary to back up the data center. Disaster recovery is to ensure that the information system can operate normally in the event of a disaster, helping enterprises achieve the goal of business continuity, and backup is to deal with data loss problems caused by disasters.

[0003] In order to ensure data integrity, it is often necessary to perform data disaster recovery in the data center. The existing data disaster recovery methods mainly use disaster recovery replication solutions based on the storage layer or disaster recovery replication solutions based on logical volumes, which makes the cost of the data center high and the maintenance cost of the disaster recovery system high. Summary of the invention

[0004] The embodiment of the present invention provides a multi-data center disaster recovery system, method, computer equipment and storage medium to reduce the maintenance cost of the current disaster recovery system.

[0005] In order to solve the above technical problems, the embodiment of the present application provides a multi-data center disaster recovery system, including:

[0006] DNS server, firewall and at least two load devices;

[0007] The DNS server is used to convert the domain name into a private IP address;

[0008] The firewall is used to map the private IP address monitored by the DNS server to a public IP carrying a first port number, and at the same time, map the virtual service IP address of the load device to a public IP with a second port number;

[0009] The load device is used to monitor the health status of the data center corresponding to the load device. When the health status of each data center corresponding to the load device is healthy, the target data center is determined according to the DNS distribution algorithm. When the health status of the data center corresponding to the load device is a detection failure, DNS is polled to obtain the data center with a healthy health status, and the target data center is determined from the data centers with a healthy health status, and the public network IP corresponding to the target data center is sent to the client.

[0010] Optionally, the load device includes a first network port and a second network port, the first network port is used to carry services and management, and the second network port is used to carry DNS monitoring.

[0011] Optionally, the load device includes a global load module and a server load module.

[0012] Optionally, the global load modules of all the load devices constitute a global load DNS cluster, and the global load DNS cluster stores the public IP of each data center in an A record.

[0013] Optionally, the server load module distributes the client's requests according to the performance status of each server corresponding to the data center.

[0014] In order to solve the above technical problems, the embodiment of the present application further provides a multi-data center disaster recovery method, including:

[0015] When receiving a client access request, obtaining a target domain name from the access request;

[0016] Send the private network IP corresponding to the target domain name to the load device through the DNS server;

[0017] Use a firewall to map the private IP and virtual service IP in the load device to a public IP, and obtain the public IP of the data center corresponding to the load device;

[0018] The health status of the data center is monitored by the load device, and a DNS distribution algorithm is used to select a target data center from the data centers with healthy health status;

[0019] The public IP address of the target data center is fed back to the client.

[0020] Optionally, after feeding back the public IP address of the target data center to the client, the multi-data center disaster recovery method further includes:

[0021] Obtain performance data of application servers corresponding to each data center;

[0022] Perform server load based on the performance data and determine a target server;

[0023] Distribute the client's request to the target server.

[0024] Optionally, after feeding back the public IP address of the target data center to the client, the multi-data center disaster recovery method further includes:

[0025] If it is detected that the health status of the data center is a detection failure, a data center with a healthy health status is obtained through DNS polling, and an updated target data center is determined from the data centers with a healthy health status.

[0026] In order to solve the above technical problems, an embodiment of the present application also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above multi-data center disaster recovery method when executing the computer program.

[0027] In order to solve the above technical problems, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above multi-data center disaster recovery method are implemented.

[0028] The multi-data center disaster recovery system, method, computer device and medium provided by the embodiment of the present invention obtain the target domain name from the access request when receiving the client access request, and then send the private network IP corresponding to the target domain name to the load device through the DNS server, and then use the firewall to map the private network IP and virtual service IP in the load device to the public network IP, so as to obtain the public network IP of the data center corresponding to the load device, and then monitor the health status of the data center through the load device, and use the DNS distribution algorithm to select the target data center from the data centers with healthy health status, and then feed back the public network IP of the target data center to the client, so as to realize fast distribution of the client request, which is beneficial to improve the load efficiency, and also avoid the interference of the downed data center on the request distribution, so as to improve the data disaster recovery efficiency. At the same time, through the mapping of the internal and external networks, there is no need to apply for the public network IP, and the existing public network IP of the data center is directly used, and the health status of the data center is detected by load device integration, which is beneficial to save the cost of data disaster recovery. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0030] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;

[0031] Figure 2 is a flow chart of an embodiment of the multi-data center disaster recovery method of the present application;

[0032] Figure 3 It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION

[0033] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by technicians in the technical field of the present application; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit the present application; the terms "including" and "having" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of the present application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0034] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0035] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0036] See also Figure 1 , Figure 1 A multi-data center disaster recovery system provided by an embodiment of the present invention is shown, and the multi-data center disaster recovery system includes: a DNS server, a firewall, and at least two load devices;

[0037] DNS server is used to convert domain names into private IP addresses;

[0038] The firewall is used to map the private IP address monitored by the DNS server to a public IP carrying the first port number, and at the same time, map the virtual service IP address of the load device to a public IP with the second port number;

[0039] The load device is used to monitor the health status of the data center corresponding to the load device. When the health status of each data center corresponding to the load device is healthy, the target data center is determined according to the DNS distribution algorithm. When the health status of the data center corresponding to the load device is detection failure, DNS polling is performed to obtain the data center with a healthy health status, and the target data center is determined from the data centers with a healthy health status, and the public network IP corresponding to the target data center is sent to the client.

[0040] Optionally, the load device includes a first network port and a second network port, the first network port is used to carry services and management, and the second network port is used to carry DNS monitoring.

[0041] Optionally, the load device includes a global load module and a server load module.

[0042] Optionally, the global load modules of all load devices constitute a global load DNS cluster, and the global load DNS cluster storage stores the public IP of each data center in an A record.

[0043] Optionally, the server load module distributes the client's requests according to the performance status of each server corresponding to the data center.

[0044] It should be noted that in addition to monitoring the health status of the data center, the load device also monitors performance data such as throughput, data packets, number of requests, latency, and RTT of the data center and business servers.

[0045] Furthermore, the Layer 4 connections and Layer 7 sessions of the two load devices are automatically mirrored in real time.

[0046] Furthermore, the DNS server supports DNS requests for both IPv4 and IPv6.

[0047] The first port number and the second port number can be set according to actual needs. For example, the first port number is set to 53 and the second port number is set to 80 or 443, which is not specifically limited here.

[0048] Among them, DNS (Domain Name Server) is a server that converts domain names and their corresponding IP addresses. DNS stores a table of domain names and their corresponding IP addresses to resolve the domain names of messages. A domain name is the name of a computer or group of computers on the Internet, which is used to identify the electronic location (sometimes also the geographical location) of the computer during data transmission. A domain name is a string of names separated by dots, usually including the name of an organization, and always includes a two- to three-letter suffix to indicate the type of organization or the country or region where the domain is located.

[0049] Among them, the A (Address) record is used to specify the IP address record corresponding to the host name (or domain name). Users can point the website server under the domain name to their own web server. At the same time, you can also set the subdomain of the domain name. In other words, the A record is the IP of the server. The domain name binding A record tells the DNS that when you enter the domain name, it will guide you to the server corresponding to the A record set in the DNS.

[0050] Among them, the four-layer connection refers to the network interface layer, internetwork layer, transport layer, and application layer in the protocol layering model.

[0051] The Layer 7 session refers to the Layer 7 (HTTP / HTTPS protocol) service, and the load balancing system is based on cookie-based session persistence. The maximum duration of a cookie-implanted session is 86400 seconds (24 hours).

[0052] In the process of load balancing, the fourth layer is the load balancing based on IP+port; the seventh layer is the load balancing based on application layer information such as URL; that is, the second layer load balancing will receive requests through a virtual MAC address and then distribute them to the real MAC address; the third layer load balancing will receive requests through a virtual IP address and then distribute them to the real IP address; the fourth layer receives requests through the virtual IP+port and then distributes them to the real server; the seventh layer receives requests through the virtual URL or host name and then distributes them to the real server.

[0053] A specific example of this embodiment is as follows: a user accesses the domain name erp.test.com, and a DNS request for the domain name is sent to the DNS server. The DNS server delegates the DNS request to the load device, that is, the public IP addresses of the two loads (for example, 100.100.100.100 and 200.200.200.200). In order to save public IP addresses, the two loads are deployed in the DMZ area of ​​the firewall or PAT is performed through a router to map the private IPs of the DNS listening ports of the two loads, that is, port 53 of the public IP is mapped to port 53 of the private IP of the load; the private IP of the virtual service on the load device (for example, 10.10.10.200) is mapped to a public IP (for example, 100.100.100.100), and the port is 80 or 443 (depending on the requirements of the business system).

[0054] The configurations of the two loads are synchronized, so a cluster is formed. Therefore, the public IP address of erp.test.com returned by the DNS request for any load is the same. If any load goes down (data center network interruption or link failure, etc.), DNS will poll another load, which will not affect the DNS request. The load device will detect the health status of the data center. If both are healthy, it will decide which data center to distribute to based on the DNS distribution algorithm, such as polling, weighted polling (based on the link and server performance of the data center, etc.). If any data center fails to detect, the public IP corresponding to erp.test.com of that data center will not be returned to the user. The switching time for detection failure is 10 seconds.

[0055] When the user receives the public IP of erp.test.com, this public IP is the IP address of the virtual service, followed by the internal IP mapped to the server. At this stage, the load device starts to do the work of server load. According to the performance of the server (such as the number of connections, response time, etc.), the request is distributed to the most suitable server.

[0056] The above process realizes the entire connection from user to server, and services can be provided uninterruptedly regardless of whether the data center is disconnected or the server is down.

[0057] It should be noted that the multi-data center disaster recovery method provided in the embodiment of the present application is executed by a server.

[0058] See also Figure 2 , Figure 2 A multi-data center disaster recovery method provided by an embodiment of the present invention is shown and described in detail as follows:

[0059] When receiving a client access request, obtain the target domain name from the access request;

[0060] Send the private IP corresponding to the target domain name to the load device through the DNS server;

[0061] Use a firewall to map the private IP and virtual service IP in the load device to a public IP, and obtain the public IP of the data center corresponding to the load device;

[0062] The health status of the data center is monitored through load devices, and the DNS distribution algorithm is used to select the target data center from the data centers with healthy health status;

[0063] Feedback the public IP address of the target data center to the client.

[0064] In this embodiment, when a client access request is received, the target domain name is obtained from the access request, and then the private IP corresponding to the target domain name is sent to the load device through the DNS server, and then the firewall is used to map the private IP and virtual service IP in the load device to a public IP, and the public IP of the data center corresponding to the load device is obtained. Then, the health status of the data center is monitored through the load device, and a DNS distribution algorithm is used to select a target data center from data centers with a healthy health status, and then the public IP of the target data center is fed back to the client, so as to achieve rapid distribution of client requests, which is beneficial to improving load efficiency, avoiding interference with request distribution caused by a downed data center, and improving data disaster recovery efficiency. At the same time, through the mapping of the internal and external networks, there is no need to apply for a public IP, and the existing public IP of the data center can be used directly, and the health status of the data center can be detected by load device integration, which is beneficial to saving the cost of data disaster recovery.

[0065] In a specific optional implementation manner, after the public network IP address of the target data center is fed back to the client, the multi-data center disaster recovery method further includes:

[0066] Obtain performance data of application servers corresponding to each data center;

[0067] Perform server load based on performance data and determine target servers;

[0068] Distribute the client's request to the target server.

[0069] In this embodiment, based on the collected application server performance data, a server load device is used to load the business server, determine the target server, and then use the target server to interact with the client, which is beneficial to improving the efficiency of load balancing and improving the utilization of system resources.

[0070] In a specific optional implementation manner, after the public network IP address of the target data center is fed back to the client, the multi-data center disaster recovery method further includes:

[0071] If it is detected that the health status of the data center is a detection failure, a data center with a healthy health status is obtained through DNS polling, and an updated target data center is determined from the data centers with a healthy health status.

[0072] In this embodiment, when it is detected that the health status of the data center is a detection failure, that is, when the data center is down or otherwise unable to provide services, an updated target data center is determined from all data centers with a healthy health status through DNS polling to ensure the normal use of the target data center, thereby achieving maintenance of the disaster recovery system in a relatively simple manner.

[0073] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0074] To solve the above technical problems, the present application also provides a computer device. Figure 3 , Figure 3 This is a basic structural block diagram of the computer device in this embodiment.

[0075] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 4 with components connected to the memory 41, the processor 42, and the network interface 43, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc.

[0076] The computer device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The computer device may interact with a user through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device.

[0077] The memory 41 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or D interface display memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 41 can be an internal storage unit of the computer device 4, such as a hard disk or memory of the computer device 4. In other embodiments, the memory 41 can also be an external storage device of the computer device 4, such as a plug-in hard disk equipped on the computer device 4, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Of course, the memory 41 can also include both the internal storage unit of the computer device 4 and its external storage device. In this embodiment, the memory 41 is generally used to store the operating system and various application software installed on the computer device 4, such as the program code for controlling electronic files, etc. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or are to be output.

[0078] The processor 42 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 42 is generally used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to run the program code stored in the memory 41 or process data, such as running the program code for controlling the electronic file.

[0079] The network interface 43 may include a wireless network interface or a wired network interface. The network interface 43 is generally used to establish a communication connection between the computer device 4 and other electronic devices.

[0080] The present application also provides another implementation, namely, providing a computer-readable storage medium, wherein the computer-readable storage medium stores an interface display program, and the interface display program can be executed by at least one processor to enable the at least one processor to perform the steps of the multi-data center disaster recovery method as described above.

[0081] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0082] Obviously, the embodiments described above are only some embodiments of the present application, rather than all embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application is described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific implementation methods, or to perform equivalent replacement of some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of this application, directly or indirectly used in other related technical fields, is similarly within the scope of patent protection of this application.

Claims

1. A multi-data center disaster recovery system, characterized in that: include: DNS server, firewall, and at least two load devices; The DNS server is used to convert the domain name into a private IP address; The firewall is used to map the private IP address monitored by the DNS server to a public IP carrying a first port number, and at the same time, map the virtual service IP address of the load device to a public IP with a second port number; The load device is used to monitor the health status of the data center corresponding to the load device. When the health status of each data center corresponding to the load device is healthy, the target data center is determined according to the DNS distribution algorithm. When the health status of the data center corresponding to the load device is detection failure, the DNS is polled to obtain the data center with a healthy health status, and the target data center is determined from the data centers with a healthy health status. The public network IP corresponding to the target data center is sent to the client. The public network IP is the existing public network IP of the data center. The four-layer connection and the seven-layer session of each load device are automatically mirrored in real time, the configuration of each load device is synchronized, and the global load module of each load device constitutes a global load DNS cluster. The load device also monitors the performance data of the data center and the business server. The performance data is used to select a server in the data center to respond to the access request. The performance data includes throughput, data packets, number of requests, delay and RTT; When receiving an access request from a client, the target domain name is obtained from the access request, and the private IP corresponding to the target domain name is sent to the load device through the DNS server, and then the private IP and virtual service IP in the load device are mapped to a public IP by a firewall to obtain the public IP of the data center corresponding to the load device, and then the health status of the data center is monitored by the load device, and a DNS distribution algorithm is used to select a target data center from data centers with a healthy health status, and then the public IP of the target data center is fed back to the client, so as to achieve rapid distribution of client requests, which is conducive to improving load efficiency, avoiding interference with request distribution caused by a downed data center, and improving data disaster recovery efficiency. At the same time, through the mapping of the internal and external networks, there is no need to apply for a public IP, and the existing public IP of the data center can be used directly, and the health status of the data center can be detected by load device integration, which is conducive to saving the cost of data disaster recovery; When a user accesses the domain name erp.test.com, the DNS request of the domain name is sent to the DNS server. The DNS server delegates the DNS request to the load device, that is, the public IP addresses of the two loads. To save public IP addresses, the two loads are deployed in the DMZ area of ​​the firewall or PAT is performed through the router to map the private IP of the DNS listening network port of the two loads, that is, the 53th port of the public IP is mapped to the 53th port of the private IP of the load; the private IP of the virtual service on the load device is mapped to the public IP, and the port is 80 or 443; The configurations of the two loads are synchronized, so a cluster is formed. Therefore, the public IP address of erp.test.com returned by the DNS request to any load is the same. If any load fails, the DNS will poll the other load, which will not affect the DNS request. The load device will detect the health status of the data center. If both are healthy, it will decide which data center to distribute to based on the DNS distribution algorithm, polling or weighted polling. If any data center fails to detect, the public IP corresponding to erp.test.com of the data center will not be returned to the user. The switching time for detection failure is 10 seconds. When the user receives the returned public IP of erp.test.com, this public IP is the IP address of the virtual service, followed by the intranet IP mapped to the server. At this stage, the load device starts to do the work of server load; it distributes the request to the most suitable server according to the performance of the server.

2. The multi-data center disaster recovery system according to claim 1, characterized in that: The load device includes a first network port and a second network port, the first network port is used to carry services and management, and the second network port is used to carry DNS monitoring.

3. The multi-data center disaster recovery system according to claim 1, characterized in that: The load device includes a global load module and a server load module.

Citation Information

Patent Citations

  • Load sharing method and equipment of double outlets at data center

    CN101572676A

  • Intelligent DNS message processing method and processing device

    CN101969478A

  • Streaming media distribution and transmission network system

    CN102404378A

  • State monitoring method and device, data center and multi-active data center

    CN106789435A

  • Network resource access method and device

    CN109302498A