Disaster recovery method, terminal device, and storage medium

Abstract

Embodiments of the present disclosure provide a disaster recovery method, a terminal device, and a storage medium. The disaster recovery method is applied to a first device of a first station, and the first station comprises the first device and a first disaster recovery component; a second station comprises a second device and a second disaster recovery component; a network device is communicatively connected to the first device and the second device; the first device interacts with the first disaster recovery component for first heartbeat information, generates first station information on the basis of the first heartbeat information, and sends the first station information to the network device; the second device interacts with the second disaster recovery component for second heartbeat information, generates second station information on the basis of the second heartbeat information, and sends the second station information to the network device.

Description

Disaster recovery methods, terminal devices, and storage media

[0001] This application claims priority to Chinese patent application No. 202311014095.8, filed on August 11, 2023, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present disclosure relates to the field of communication technology, and in particular to a disaster recovery method, terminal equipment, and storage medium. Background Art

[0003] With the development of 5G (5th generation) technology, the need for network data security management and disaster recovery is becoming increasingly urgent. Currently, deploying microservices and containers on Platform as a Service (PaaS) has become the foundational management architecture standard for 5G.

[0004] Summary of the Invention

[0005] In a first aspect, an embodiment of the present disclosure provides a disaster recovery method, which is applied to a first device at a first site, wherein the first site includes a first device and a first disaster recovery component, and the first device is communicatively connected to a network device; the second site includes a second device and a second disaster recovery component; the network device is communicatively connected to the second device; the first device exchanges first heartbeat information with the first disaster recovery component, generates first site information based on the first heartbeat information, and sends the first site information to the network device; the second device exchanges second heartbeat information with the second disaster recovery component, generates second site information based on the second heartbeat information, and sends the second site information to the network device; the first site is a backup site, and the second site is a primary site. The disaster recovery method includes: obtaining reception result information about the second site information fed back by the network device; and determining whether to switch the first site to the primary site based on the reception result information.

[0006] In a second aspect, an embodiment of the present disclosure provides a disaster recovery method, which is applied to a second device at a second site, wherein the second site includes a second device and a second disaster recovery component; the first site includes a first device and a first disaster recovery component, and the first device is communicatively connected to a network device; the network device is communicatively connected to the second device at the second site; the first device exchanges first heartbeat information with the first disaster recovery component, generates first site information based on the first heartbeat information, and sends the first site information to the network device; the second device exchanges second heartbeat information with the second disaster recovery component, generates second site information based on the second heartbeat information, and sends the second site information to the network device; the first site is a backup site, and the second site is a primary site. The disaster recovery method includes: sending an information query request to the network device, the information query request is used to obtain status information about the network device fed back by the network device; in response to not receiving status information fed back by the network device based on the information query request, switching the second site to a backup site.

[0007] In a third aspect, embodiments of the present disclosure provide a terminal device comprising: a processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for enabling communication between the processor and the memory. When the computer program is executed by the processor, the disaster recovery method provided in the first aspect or the disaster recovery method provided in the second aspect is implemented.

[0008] In a fourth aspect, an embodiment of the present disclosure provides a storage medium for computer-readable storage, wherein the storage medium stores at least one program, and the at least one program can be executed by at least one processor to implement the disaster recovery method provided in the first aspect, or to implement the disaster recovery method provided in the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] FIG1 is a schematic block diagram of the structure of a disaster recovery system according to an embodiment of the present disclosure.

[0010] FIG2 is a schematic diagram of an interface of arbitration agent software according to an embodiment of the present disclosure.

[0011] FIG3 is a schematic structural diagram of a device according to an embodiment of the present disclosure.

[0012] FIG4 is a schematic diagram of another operation of a disaster recovery system according to an embodiment of the present disclosure.

[0013] FIG5 is a schematic flow chart of a disaster recovery method according to an embodiment of the present disclosure.

[0014] FIG6 is a schematic flow chart of another disaster recovery method according to an embodiment of the present disclosure.

[0015] FIG7 is a schematic flowchart of a site switching method according to an embodiment of the present disclosure.

[0016] FIG8 is a schematic flowchart of a method for confirming a working status according to an embodiment of the present disclosure.

[0017] FIG9 is a schematic flowchart of another site switching method according to an embodiment of the present disclosure.

[0018] FIG10 is a schematic flow chart of another disaster recovery method according to an embodiment of the present disclosure.

[0019] FIG11 is a schematic block diagram of a terminal device according to an embodiment of the present disclosure.

[0020] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. DETAILED DESCRIPTION

[0021] The following will clearly and completely describe the technical solutions in the embodiments of the present disclosure in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present disclosure without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0022] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, combined, or partially merged, so the actual execution order may vary depending on the actual situation.

[0023] It should be understood that the terms used in this disclosure are for the purpose of describing particular embodiments only and are not intended to limit the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise.

[0024] It should be understood that, in order to clearly describe the technical solutions of the embodiments of the present disclosure, the words "first" and "second" are used in the embodiments of the present disclosure to distinguish between identical or similar items with substantially the same functions and effects. For example, the first site and the second site are merely used to distinguish different sites and do not limit their order. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean that they are different.

[0025] It will also be understood that the term "and / or" as used in this disclosure and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

[0026] To facilitate understanding of the embodiments of the present disclosure, some terms involved in the embodiments of the present disclosure are briefly explained below.

[0027] 1. Disaster Recovery

[0028] Disaster recovery is a relatively broad concept. In a broad sense, disaster recovery is a system engineering project that includes all aspects related to business continuity. For IT (Information Technology), disaster recovery is to provide a computer system that can prevent user business systems from being damaged by various disasters. Disaster recovery in a narrow sense refers to the establishment of two or more sets of IT systems with the same functions, which can monitor each other's health status and switch functions. When the primary site stops working due to an accident (such as fire, earthquake, city power outage, etc.), the entire application system can use the backup site to quickly recover and continue to work. The main purpose of disaster recovery is to ensure business continuity as much as possible when a disaster occurs in the production system due to natural or man-made reasons.

[0029] The component used to switch the working status of the primary site and the backup site is called a disaster recovery component.

[0030] 2. Network equipment

[0031] Network devices include common IT / CT (Information Technology / Communication Technology) devices found on networks, used for data record storage and supporting arbitration agents to write, update, and query such records. Data record storage can be structured database storage or unstructured data storage. Structured database storage includes, but is not limited to, relational databases and non-relational database data tables; unstructured data storage includes, but is not limited to, text, XML (Extensible Markup Language), HTML (Hyper Text Markup Language), JSON (JavaScript Object Notation), and various reports.

[0032] The following describes some embodiments of the present disclosure in detail with reference to the accompanying drawings. In the absence of conflict, the following embodiments and features therein may be combined with each other.

[0033] With the development of 5G technology, the need for network data security management and disaster recovery is becoming increasingly urgent. Currently, deploying microservices and containers on Platform as a Service (PaaS) has become the foundational management architecture for 5G telecoms. Disaster recovery technology must also evolve to meet the constraints of this infrastructure. However, existing disaster recovery technologies present the following challenges.

[0034] 1. High cost. A separate arbitration site needs to be deployed, which not only requires purchasing servers and software deployment, but also requires dedicated maintenance.

[0035] 2. Low reuse rate. The dedicated arbitration node cannot be used for other purposes. The reuse rate is extremely low, resulting in serious waste of resources.

[0036] 3. Single point failure: There is already active-standby disaster recovery control technology. After adding an arbitration site, a three-site model is formed, which enhances the reliability of disaster recovery status judgment. However, there is a single arbitration site failure, that is, if the arbitration site itself fails, the arbitration site will not be able to play the arbitration role.

[0037] 4. Low versatility. Although disaster recovery technologies exist that use network devices to perform arbitration functions, network devices require specialized design and upgrades, which have high barriers to entry. Not only are they not universally applicable, but they also have a significant impact on existing networks. To address the above issues, please refer to Figure 1, which shows a schematic block diagram of the structure of a disaster recovery system 10 according to an embodiment of the present disclosure. Disaster recovery system 10 includes a first site 11, a second site 12, and a network device 13. First site 11 includes a first device 111 and a first disaster recovery component 112, and the first device 111 is communicatively connected to network device 13. Second site 12 includes a second device 121 and a second disaster recovery component 122. Network device 13 is communicatively connected to second device 121. First device 111 exchanges first heartbeat information with first disaster recovery component 112, generates first site information based on the first heartbeat information, and sends the first site information to network device 13. Second device 121 exchanges second heartbeat information with second disaster recovery component 122, generates second site information based on the second heartbeat information, and sends the second site information to network device 13. The first site 11 is a backup site, and the second site 12 is an active site.

[0038] For example, first site 11 and second site 12 include multiple terminal devices. A terminal device is selected from each site and installed with arbitration agent software, serving as first device 111 and second device 121. Network device 13 is connected to first device 111 and second device 121, supporting first device 111 and second device 121 in writing, updating, and querying arbitration agent information.

[0039] It should be noted that the first device 111 and the second device 121 serve as arbitration agents in the disaster recovery system 10 and provide communication protocols compatible with common network devices, including but not limited to telent (remote terminal protocol), ssh (secure shell), netconf (network configuration), QX, jdbc (Java Database Connectivity), and TNS (Transparent Network Substrate). Through these protocols, the parsed heartbeat information of the device and the disaster recovery component is written or updated into the network device 13, and the written information is queried from the network device 13. At the same time, relevant interfaces are opened and interface commands can be edited by yourself.

[0040] It should be noted that the first device 111 and the second device 121 write (update) information of the network device 13, including but not limited to site identification (Internet Protocol, IP), site role, disaster recovery status, update time and arbitration agent status.

[0041] For example, as shown in FIG2 , FIG2 shows a schematic diagram of an interface of an arbitration agent software according to an embodiment of the present disclosure. In the arbitration agent software, the first device 111 as SITEA can obtain the reception result information about the second site information from the network device 13, and determine whether the second site 12 (SITEB) is in working state at this time, and then the first device 111 determines whether it is necessary to promote the first site 11 to the primary site. At the same time, the second device 121 can also send an information query request to any network device 13 in the disaster recovery system 10 according to the IP address. The information query request is used to obtain the status information about the network device 13 fed back by the network device 13. Then, the second device 121 determines whether it is necessary to promote the second site 12 to the primary site.

[0042] In some embodiments, as shown in FIG3 , FIG3 shows a schematic diagram of the structure of a device according to an embodiment of the present disclosure. As shown in FIG3 , the first device 111 and the second device 112 internally include four submodules. The four submodules include: a first communication module that communicates with the disaster recovery component, for information interaction with the disaster recovery component of this site, the information interaction including parsing and encapsulating heartbeat messages and sending disaster recovery switching messages; a second communication module that communicates with the network device 13, for information interaction with the network device 13, the information interaction including writing, updating, and querying information from the network device; a link building module for maintaining a communication connection with the network device 13; and an arbitration algorithm module for comprehensively judging based on the information parsed by the first communication module with the disaster recovery component and the second communication module with the network device 13, and giving a disaster recovery switching command for site switching.

[0043] In some embodiments, network device 13 may comprise a single network device or a network device cluster consisting of multiple network devices 13. The number of network devices 13 is set based on the operational requirements of disaster recovery system 10, and the disclosed embodiments do not limit the number of network devices. By designing a collection of network devices, the arbitration agent integrates the information transferred by multiple network devices and makes a fusion judgment design, thus completely eliminating single points of failure in arbitration.

[0044] For example, as shown in FIG4 , FIG4 illustrates a schematic diagram of the operation of a disaster recovery system 10 according to an embodiment of the present disclosure. Referring to FIG4 and FIG1 , the primary site is the second site 12, the backup site is the first site 11, the GR is the disaster recovery component, and the ARBs are the first device 111 and the second device 121. Disaster recovery system 10 includes multiple network devices 13. The first device 111 and the second device 121 at the primary and backup sites can write, update, and query arbitration agent information to each network device 13.

[0045] The disaster recovery system 10 provided by the embodiment of the present disclosure has the following four advantages by deploying the first device 111 and the second device 121 in the first site 11 and the second site 12 respectively.

[0046] 1. Low cost. The arbitration agent is designed as a dual-active application component, first device 111 and second device 121, running on a primary-backup disaster recovery system. No additional servers are required to deploy arbitration sites. Disaster recovery system 10 relays information via network device 13. Network device 13 only needs to store two pieces of information and support query and update. Generally speaking, the required functions are already available in network device 13, requiring little or no modification or upgrade.

[0047] 2. Improve resource reuse. The arbitration agent is designed as a component-level software module, running in an active-active configuration on the disaster recovery system 10. Resource usage is distributed across the primary and backup sites. Its lightweight design minimizes resource consumption and directly reuses existing site resources. Information is relayed through network device 13. Thanks to its lightweight design and the use of a component proxy for core logic, the resulting solution has a negligible impact on the primary functions of network device 13.

[0048] 3. Solve the single point of failure problem in arbitration. Through the design of network device aggregation, the arbitration agent integrates the information transferred by multiple network devices and makes a fusion judgment design, which completely solves the single point of failure in arbitration.

[0049] 4. Improved versatility. Avoiding excessive modification and design of the network device 13, using the existing communication protocol and communication capabilities of the network device 13, and adding an open design that allows for flexible configuration of custom scripts, greatly improving the versatility of the disaster recovery system 10.

[0050] Please refer to FIG. 5 , which shows a schematic flow chart of a disaster recovery method according to an embodiment of the present disclosure. The provided disaster recovery method is applied to the first device 111 in the first site 11 provided in any one of the embodiments in FIG. 1 to FIG. 4 .

[0051] As shown in FIG5 , the provided disaster recovery method includes S101 and S102 .

[0052] In S101, receiving result information about the second site information fed back by the network device is obtained.

[0053] For example, first site 11 serves as a backup site and is deployed with first device 111 as an arbitration device. During operation of disaster recovery system 10, first device 111 can initiate a request to network device 13 to obtain information regarding the receipt of information about second site 12. This information can be used to determine whether arbitration agent second device 121 within second site 12, serving as the primary site, is communicating properly with network device 13, thereby determining whether first site 11 needs to be promoted to the primary site to maintain normal operation of disaster recovery system 10.

[0054] For example, first device 111 obtains, from network device 13, reception result information regarding the second site information within a preset period. The preset period is set based on the operating requirements of disaster recovery system 10, thereby ensuring that disaster recovery system 10 can promptly upgrade first site 11 to the active site if an abnormal state occurs.

[0055] In some embodiments, please refer to Figure 6, which is a schematic flow chart of another disaster recovery method according to an embodiment of the present disclosure. Different from the method provided in Figure 5, the disaster recovery method provided in Figure 6 further includes S201.

[0056] In S201, message information is sent to a network device, where the message information is used to obtain reception result information of the network device regarding the second site information, and the network device responds to the message information.

[0057] The first device 111 sends message information to the network device 13 through the built-in arbitration agent software. When the network device 13 responds to the message information, the first device 111 can obtain the reception result information about the second site information, thereby greatly simplifying the disaster recovery method provided by the embodiment of the present disclosure.

[0058] In S102 , it is determined whether to switch the first site to the active site according to the received result information.

[0059] For example, by obtaining the reception result information about the second site information fed back by the network device 13, the first device 111 can determine the working status of the second site 12, which is currently the primary site. Furthermore, when it is determined that the second site 12 can continue to send the second site information to the network device 13 normally, the first site 11 still serves as the backup site. When the second site 12 cannot send the second site information to the network device 13 normally, the first device 111 controls the first site 11 to upgrade to the primary site. Furthermore, the provided method does not require the additional configuration of an arbitration site, thereby significantly reducing resource waste, while also simplifying the requirements for network equipment and improving the versatility of network equipment.

[0060] It should be noted that after the first device 111 switches the first site 11 to the primary site, whether the second site 12 should be downgraded to the backup site needs to be arbitrated by the second device 121 within the second site 12. After the first site 11 switches to the primary site, if the reception result information obtained by the first device 111 indicates that the second site 12 can normally send the second site information, the first device 111 will also downgrade the first site 11 back to the backup site to ensure the normal operation of the disaster recovery system 10.

[0061] In some embodiments, please refer to FIG7 , which is a schematic flow chart of a site switching method according to an embodiment of the present disclosure. The provided method includes S301 to S303 .

[0062] In S301, it is confirmed whether the second station is in a working state based on the received result information.

[0063] In S302, if the second site is not in a working state, first switching information is generated.

[0064] In S303, the first switching information is sent to the first disaster recovery component, so as to switch the first site to the active site.

[0065] Based on the reception result information fed back by network device 13, when it is confirmed that second site 12 is not in an operating state, to maintain the normal operation of disaster recovery system 10, first device 111 generates first switching information and sends the first switching information to first disaster recovery component 112. At this time, first disaster recovery component 112 starts to operate. Furthermore, first site 11 is switched to the active site, ensuring that the provided disaster recovery system can be in a normal operating state in real time.

[0066] Exemplarily, the reception result information includes the first time when the network device 13 receives the second site information. Referring to FIG8 , FIG8 is a schematic flow chart of a method for confirming a working status according to an embodiment of the present disclosure. The provided method includes S301a and S301b.

[0067] In S301a, it is determined based on the first time whether the second device sends the second site information to the network device within a preset period.

[0068] In S301b, if the second device does not send the second site information to the network device within the preset period, it is confirmed that the second site is not in a working state.

[0069] By comparing the first time and current time at which the second site information is received via the network device 13, the first device 111 can determine whether the second device 121 has sent the second site information to the network device 13 within a preset period. For example, if the preset period is 5 minutes, and the interval between the current time and the first time is 10 minutes, then the second device 121 has not sent the second site information to the network device 13 within the preset period. This allows the first device 111 to quickly confirm whether the second site 121 is in operation and switch the site status in a timely manner.

[0070] It should be noted that, in some embodiments, please refer to Figure 9, which is a schematic flow chart of another site switching method according to an embodiment of the present disclosure. Different from the method provided in Figure 7, the method provided in Figure 9 also includes S304 to S306.

[0071] In S304, sub-receiving result information about the second site information fed back by the network device is obtained, where the sub-receiving result information includes a second time when the network device receives the second site information.

[0072] In S305 , if the second time is after the first time, it is confirmed that the second site is in working state, and second switching information is generated.

[0073] In S306, the second switching information is sent to the first disaster recovery component for switching the first site to the standby site.

[0074] After the first device 111 upgrades the first site 11 from a backup site to a primary site, the first site 11 still needs to obtain sub-receiving result information about the second site information fed back by the network device 13. The sub-receiving result information includes the second time when the network device 13 receives the second site information. If the second time is later than the first time, it proves that the second site has been released from the abnormal recovery work. At this time, the first site 11 no longer needs to operate as the primary site. The first device 111 generates second switching information and sends the second switching information to the first disaster recovery component 112, thereby causing the first site 11 to be downgraded to a backup site again. The provided method enables both the primary site and the backup site in the disaster recovery system 10 to confirm the appropriate working status in a timely manner.

[0075] For example, in some embodiments, the first site 11 is in communication connection with the second site 12. Before generating the first switching information, the method further includes: determining whether the communication connection between the first site 11 and the second site 12 is disconnected based on the first site information, and generating the first switching information when the communication connection between the first site 11 and the second site 12 is disconnected. After sending the first switching information to the first disaster recovery component 112 for switching the first site 11 to the primary site, the method further includes: determining whether the communication connection between the first site 11 and the second site 12 is restored based on the first site information, and generating the second switching information for switching the first site 11 to the backup site when the communication connection between the first site 11 and the second site 12 is restored.

[0076] When the first device 111 analyzes the internal heartbeat information with the first disaster recovery component 112 and finds that the network between the first site 11 and the second site 12 is interrupted, the first device 111 is used to generate first switching information and send the first switching information to the first disaster recovery component 112, so as to switch the first site 11 to the primary site. Furthermore, when the first device 111 analyzes the internal heartbeat information with the first disaster recovery component 112 and finds that the network between the first site 11 and the second site 12 is restored, the first device 111 is used to generate second switching information and send the second switching information to the first disaster recovery component 112, so as to switch the first site 11 back to the backup site. This allows the first site 11 to promptly switch to the primary site to operate when a communication anomaly occurs at the second site 12.

[0077] Using the disaster recovery method provided in the embodiments of the present disclosure, the first device 111 at the backup site obtains information about the reception result of the second heartbeat message sent by the network device 13 from the primary site. This allows the backup site to confirm whether it needs to be upgraded to the primary site based on the reception of the second heartbeat message to ensure the normal operation of the disaster recovery method. The provided disaster recovery method eliminates the need for an additional arbitration site, significantly reducing resource waste, while also simplifying the requirements for network device 13 and improving the versatility of network device 13.

[0078] Please refer to FIG. 10 , which shows a schematic flow chart of another disaster recovery method provided according to an embodiment of the present disclosure. The provided disaster recovery method is applied to the second device 121 in the second site 12 provided in any one of the embodiments in FIG. 1 to FIG. 4 .

[0079] As shown in FIG10 , the provided disaster recovery method includes S401 and S402 .

[0080] In S401, an information query request is sent to a network device, where the information query request is used to obtain status information about the network device fed back by the network device.

[0081] For example, second site 12 serves as the primary site and is deployed with second device 121 as an arbitration device. During operation of disaster recovery system 10, second device 121 can initiate information query requests to network device 13 to obtain status information about network device 13. This status information is used to determine whether arbitration agent second device 121 within second site 12, serving as the primary site, is communicating properly with network device 13, thereby determining whether second site 12 needs to be downgraded to a backup site to maintain normal operation of disaster recovery system 10.

[0082] For example, the second device 121 initiates an information query request to the network device 13 within a preset period. The preset period is set according to the working requirements of the disaster recovery system 10, thereby ensuring that the disaster recovery system 10 can promptly reduce the second site 12 to a backup site if it is in an abnormal state.

[0083] In S402, if the state information fed back by the network device based on the information query request is not received, the second site is switched to a standby site.

[0084] For example, if the second device 121 sends an information query request to the network device 13 and does not receive status information from the network device 13 based on the information query request, it can be determined that the working status of the second site 12, which is currently the primary site, is abnormal. Then, the second device 121 controls the second site 12 to be downgraded to a backup site. Furthermore, the provided method does not require the establishment of an additional arbitration site, thereby significantly reducing resource waste, while also simplifying the requirements for network equipment and improving the versatility of network equipment.

[0085] It should be noted that after the second device 121 switches the second site 12 to the backup site, whether the first site 11 is promoted to the primary site is subject to arbitration by the first device 111 within the first site 11. After the second site 12 switches to the backup site, if the second device 121 sends an information query request to the network device again and receives status information based on the information query request from the network device, the second device 121 will also promote the second site 12 back to the primary site, ensuring the normal operation of the disaster recovery system 10.

[0086] In some embodiments, switching the second site to the backup site includes: generating third switching information, and sending the third switching information to the second disaster recovery component for switching the second site to the backup site. The first site is in communication with the second site, and before switching the second site to the backup site, the method further includes: determining whether the communication connection between the first site and the second site is disconnected based on the second site information, and generating the third switching information when the communication connection between the first site and the second site is disconnected.

[0087] When the second device 121 determines that it cannot receive the status information fed back by the network device based on the information query request, it generates third switching information and sends the third switching information to the second disaster recovery component 122, so as to switch the second site 12 to a backup site, thereby ensuring that the provided disaster recovery system 10 can be promptly downgraded to a backup site when the primary site cannot work normally.

[0088] By adopting the disaster recovery method provided in the embodiment of the present disclosure, when the second device 121 at the primary site is unable to obtain the status information of the feedback from the network device 13 regarding the information query request, the second device 121 can downgrade the primary site to a backup site. The provided disaster recovery method not only eliminates the need to set up an additional arbitration site, thereby significantly reducing resource waste, but also simplifies the requirements for network equipment and improves the versatility of network equipment.

[0089] Please refer to Figure 11, which illustrates a terminal device. As shown in Figure 11, a terminal device 200 according to an embodiment of the present disclosure includes a memory 220, a processor 210, a program stored in and executable on the memory 220, and a data bus 230 for enabling communication between the processor 210 and the memory 220. When the program is executed by the processor, the disaster recovery method described in any one of the embodiments of the present disclosure is implemented.

[0090] Embodiments of the present disclosure provide a storage medium for computer-readable storage. The storage medium may be a computer-readable storage medium, including a non-transitory computer-readable storage medium. The storage medium stores at least one program, which can be executed by at least one processor to implement any of the disaster recovery methods described in the embodiments of the present disclosure.

[0091] The disclosed embodiments provide a disaster recovery method, terminal device, and storage medium, which are intended to address the problem that during the development of related disaster recovery technologies, the reuse rate of independently deployed arbitration sites is extremely low, resulting in serious waste of resources, and that the use of network devices to assume arbitration functions requires design and upgrade based on communication protocols, resulting in a significant decrease in the versatility of network devices. The provided disaster recovery method is applied to a first device at a first site, the first site including a first device and a first disaster recovery component, the first device being communicatively connected to the network device; the second site including a second device and a second disaster recovery component, the network device being communicatively connected to the second device; the first device interacts with the first disaster recovery component to exchange first heartbeat information, generates first site information based on the first heartbeat information, and sends the first site information to the network device; the second device interacts with the second disaster recovery component to exchange second heartbeat information, generates second site information based on the second heartbeat information, and sends the second site information to the network device. The provided method obtains, through the first device, reception result information about the second heartbeat information fed back by the network device; and determines, based on the reception result information, whether to switch the first site to the primary site. By obtaining information about the network device's reception result regarding the second heartbeat message sent by the primary site through the first device at the backup site, the backup site can determine whether it needs to be upgraded to the primary site based on the receipt of the second heartbeat message, thereby ensuring the normal operation of the disaster recovery method. The provided disaster recovery method eliminates the need for an additional arbitration site, significantly reducing resource waste, while also simplifying the requirements for network equipment and improving the versatility of network equipment.

[0092] The preferred embodiments of the present disclosure are described above with reference to the accompanying drawings, but are not intended to limit the scope of the present disclosure. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and essence of the present disclosure shall fall within the scope of the present disclosure.

Claims

1. A disaster recovery method, applied to a first device at a first site, wherein: The first site includes the first device and a first disaster recovery component, and the first device is communicatively connected to a network device; the second site includes a second device and a second disaster recovery component, and the network device is communicatively connected to the second device; the first device and the first disaster recovery component exchange first heartbeat information, generate first site information based on the first heartbeat information, and send the first site information to the network device; The second device exchanges second heartbeat information with the second disaster recovery component, generates second site information based on the second heartbeat information, and sends the second site information to the network device, wherein the first site is a backup site and the second site is a primary site; the method includes: Acquire reception result information about the second site information fed back by the network device; According to the receiving result information, it is determined whether to switch the first site to the primary site.

2. The method according to claim 1, wherein: Before obtaining the reception result information about the second site information fed back by the network device, the method further includes: Send message information to the network device, the message information is used to obtain the network device's reception result information about the second site information, and the network device responds to the message information.

3. The method according to claim 1, wherein: The determining, according to the receiving result information, whether to switch the first site to a primary site includes: confirming whether the second station is in a working state based on the receiving result information; In response to the second station not being in the working state, generating first switching information; The first switching information is sent to the first disaster recovery component to switch the first site to the primary site.

4. The method according to claim 3, wherein: The receiving result information includes a first time when the network device receives the second site information; The confirming whether the second station is in a working state based on the receiving result information includes: determining, based on the first time, whether the second device sends the second site information to the network device within a preset period; In response to the second device not sending the second site information to the network device within the preset period, it is confirmed that the second site is not in the working state.

5. The method according to claim 4, wherein: After sending the first switching information to the first disaster recovery component for switching the first site to the primary site, the method further includes: Acquire sub-receiving result information about the second site information fed back by the network device, where the sub-receiving result information includes a second time when the network device receives the second site information; In response to the second time being after the first time, confirming that the second station is in the working state, generating second switching information; The second switching information is sent to the first disaster recovery component to switch the first site to the standby site.

6. The method according to claim 3, wherein: The first site is communicatively connected with the second site; Before generating the first switching information, the method further includes: determining, based on the first site information, whether a communication connection between the first site and the second site is disconnected, and generating the first switching information if the communication connection between the first site and the second site is disconnected; After sending the first switching information to the first disaster recovery component for switching the first site to the primary site, the method further includes: Based on the first site information, it is determined whether the communication connection between the first site and the second site is restored, and when the communication connection between the first site and the second site is restored, second switching information is generated to switch the first site to the standby site.

7. A disaster recovery method, applied to a second device at a second site, wherein: The second site includes the second device and a second disaster recovery component; the first site includes a first device and a first disaster recovery component, the first device is communicatively connected to a network device; the network device is communicatively connected to the second device of the second site; the first device and the first disaster recovery component exchange first heartbeat information, generate first site information based on the first heartbeat information, and send the first site information to the network device; The second device exchanges second heartbeat information with the second disaster recovery component, generates second site information based on the second heartbeat information, and sends the second site information to the network device, wherein the first site is a backup site and the second site is a primary site; the method includes: Sending an information query request to the network device, wherein the information query request is used to obtain status information about the network device fed back by the network device; In response to not receiving the state information fed back by the network device based on the information query request, switching the second site to a standby site.

8. The method according to claim 7, wherein: The switching the second site to a standby site includes: Generate third switching information, and send the third switching information to the second disaster recovery component, so as to switch the second site to the standby site; The first site is in communication connection with the second site, and before the second site is switched to the standby site, the method further includes: Based on the second site information, it is determined whether the communication connection between the first site and the second site is disconnected, so as to generate the third switching information when the communication connection between the first site and the second site is disconnected.

9. A terminal device, comprising: A processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for realizing connection and communication between the processor and the memory, wherein when the computer program is executed by the processor, the disaster recovery method according to any one of claims 1 to 6 is implemented, or the disaster recovery method according to any one of claims 7 to 8 is implemented.

10. A storage medium for computer-readable storage, wherein: The storage medium stores at least one program, and the at least one program can be executed by at least one processor to implement the disaster recovery method according to any one of claims 1 to 6, or to implement the disaster recovery method according to any one of claims 7 to 8.

Images