Search

JP-2026514301-A - Remote disaster recovery methods, devices, equipment, and computer program products

JP2026514301AJP 2026514301 AJP2026514301 AJP 2026514301AJP-2026514301-A

Abstract

This application provides a remote disaster recovery method, apparatus, device, and storage medium. The method is used on any one node in a remote disaster recovery operation, the one node storing an environment for running the primary task of the primary node, the primary node being used to control network equipment to forward network messages, and the method includes determining first change information to indicate that the identity of the one node is changed from a standby node to the primary node for synchronizing data of the primary node, and stopping the synchronization of data of the primary node and running the primary task in the environment based on the first change information. [Selection Diagram] Figure 2

Inventors

  • シ，ウェイガン
  • ファン，ドンギュン

Assignees

  • ルイジェ ネットワークス カンパニー，リミテッド

Dates

Publication Date
20260508
Application Date
20241114
Priority Date
20231115

Claims (19)

  1. A remote disaster recovery method, wherein the method is used in a first node in a remote disaster recovery operation, the first node stores an environment for running the primary task of a primary node, the primary node is used to control network equipment to forward network messages, and the method is The identity of the first node determines first change information to instruct that the data of the primary node be changed from the standby node to the primary node for synchronization, A remote disaster recovery method comprising stopping data synchronization of the primary node and running the primary task in the environment based on the first change information.
  2. The first node includes at least one first disaster recovery microservice and at least one first business microservice, and the method is The at least one first disaster recovery microservice is used to determine the first change message, The method according to claim 1, wherein the at least one first business microservice is used to stop data synchronization on the primary node based on the first change information and to run the primary task in the environment.
  3. Before running the primary task in the aforementioned environment, the method Obtain the utilization rate of one or more resources of the first node, and load the environment if the maximum utilization rate of one or more resources is less than a threshold, or The method according to claim 1, further comprising loading the environment when the first node is started.
  4. Determining the first change information mentioned above is: If the time elapsed from the time the heartbeat information from the primary node was last received to the current time exceeds a predetermined time elapsed, then the first change information is determined, or Receiving the first change information from the mediation equipment for determining the first change information, or The method according to claim 1, comprising receiving first change information entered by an engineer.
  5. The environment includes a first communication channel established between the first node and the network equipment in accordance with the Southbound Interface Protocol, and/or a second communication channel established between the first node and the client in accordance with the Northbound Interface Protocol. After determining the first change information described above, and before running the primary task in the environment, the method: The method according to claim 1, further comprising changing the state of the first communication channel from a read-only state to a read-write state and/or changing the state of the second communication channel from a read-only state to a read-write state based on the first change information.
  6. After determining the first change information, The method according to claim 1, further comprising invoking a database change script for the first node based on the first change information, wherein the database change script for the first node is used to update the version of the database and/or update the table structure of the database.
  7. Based on the first change information, before stopping the synchronization of data on the primary node, the method The method according to claim 1, wherein the first node synchronizes the data of the primary node, the first node receiving data from the primary node and storing the data of the primary node in the database of any one of the nodes.
  8. Operating the primary task in the aforementioned environment involves periodically requesting configuration data from the network equipment according to a predetermined time interval, If the configuration data received in the first cycle differs from the configuration data corresponding to the network device stored in the database of the first node, the configuration data received in the first cycle is stored in the database of the first node. The method according to any one of claims 1 to 7, further comprising transmitting configuration change information to the network device to instruct it to update the configuration data with the configuration data corresponding to the network device stored in the database of the first node, if the configuration data received in the remaining cycles after the first cycle differs from the configuration data corresponding to the network device stored in the database of the first node.
  9. The fact that at least one first business microservice stops data synchronization on the primary node based on the first change information and is used to run the primary task in the environment is that The method according to claim 2, comprising changing the state of each of the first business microservices from a standby state to a primary state for performing the primary task, based on the first change information and a state conversion table corresponding to each of the first business microservices among the at least one first business microservices, wherein the state conversion table is used to instruct the state switching of each of the first business microservices.
  10. A remote disaster recovery method, wherein the method is used in a second node in a remote disaster recovery operation, the second node is used to control network equipment to forward network messages, and the method is Determining second change information to indicate that the identity of the second node is changed from the primary node to the standby node, A remote disaster recovery method, which includes stopping the operation of the primary task based on the second change information.
  11. The second node includes at least one second disaster recovery microservice and at least one second business microservice, and the method is The at least one second disaster recovery microservice is used to determine the second change message, The method according to claim 10, wherein at least one second business microservice is used to stop the operation of the primary task based on the second change information.
  12. Determining the second change information mentioned above is: Receiving second change information from mediation equipment for determining the second change information, or The method according to claim 10, comprising receiving a second change information entered by an engineer.
  13. The environment includes a third communication channel established between the second node and the network equipment in accordance with the Southbound Interface Protocol, and/or a fourth communication channel established between the second node and the client in accordance with the Northbound Interface Protocol, and the method is The method according to claim 10, further comprising changing the state of the third communication channel from a read-write state to a read-only state and/or changing the state of the fourth communication channel from a read-write state to a read-only state based on the second change information.
  14. The fact that at least one second business microservice is used to stop the operation of the primary task based on the second change information is: The method according to claim 11, comprising changing the state of each second business microservice from a primary state that performs the primary task to a standby state based on the second change information and a state conversion table corresponding to each second business microservice among the at least one second business microservice, wherein the state conversion table is used to instruct the state switching of each second business microservice.
  15. After determining the second change information, The method according to any one of claims 10 to 14, further comprising stopping the database change script of the first node based on the second change information, wherein the database change script of the first node is used to update the version of the database and/or update the table structure of the database.
  16. A remote disaster recovery device, wherein the device is used as a first node in remote disaster recovery operations, the first node stores an environment for running the primary task of the primary node, the primary node is used to control network equipment to forward network messages, and the device is, A decision module for determining first change information to instruct that the identity of the first node be changed from the standby node to the primary node for synchronizing data of the primary node, A remote disaster recovery device, comprising a processing module for stopping data synchronization of the primary node and running the primary task in the environment, based on the first change information.
  17. A remote disaster recovery device, wherein the device is used as a second node in remote disaster recovery operations, the second node is used to control network equipment to forward network messages, and the device is, A decision module for determining second change information to instruct that the identity of the second node be changed from the primary node to the standby node, A remote disaster recovery device, including a processing module for stopping the operation of the primary task based on the second change information.
  18. It is an electronic device, It includes at least one processor, and memory and a communication interface that are communicated to the at least one processor, Herein, the memory stores instructions that can be executed by the at least one processor, and the at least one processor causes the electronic device to perform the method according to any one of claims 1 to 15 via the communication interface by executing the instructions stored in the memory.
  19. A computer-readable storage medium, wherein computer instructions are stored in the computer-readable storage medium, and when the computer instructions are executed on a computer, the computer causes the computer to execute the method according to any one of claims 1 to 15.

Description

[Cross-reference of related applications] This application claims priority to a Chinese patent application filed with the China National Intellectual Property Administration on November 15, 2023, with application number 202311525842.4 and title "Remote Disaster Recovery Method, Apparatus, Device and Storage Medium," the entirety of which is incorporated into this application by reference. This application relates to the technical field of disaster recovery, and more specifically to remote disaster recovery methods, apparatus, devices, and storage media. A disaster recovery system involves establishing two or more identical systems in geographically separated locations, designating one system as the primary site and the others as the standby site. Disaster recovery strategies primarily aim to ensure system availability in the event of primary system upgrades or operating system upgrades, hardware failures, or disasters (e.g., fire, earthquake, tsunami, war), reducing service interruption and guaranteeing continuous and reliable service. If the primary site fails, the standby site switches to the primary site, allowing for continued service provision to external parties. In disaster recovery plans, manually switching between the primary and standby sites is necessary to ensure continued service provision to external parties. To more clearly illustrate the embodiments of this application or the technical concepts in the prior art, the following briefly introduces the drawings necessary for describing the embodiments. It is obvious that the drawings in the following description are only a few embodiments of this application, and those skilled in the art can obtain other drawings based on the provided drawings without expending any creative effort. This is a schematic diagram of a scenario according to the embodiment of this application. This is a flowchart of a remote disaster recovery method according to an embodiment of this application. This is a flowchart of another remote disaster recovery method according to an embodiment of this application. This is a structural diagram of a remote disaster recovery device according to an embodiment of this application. This is a structural diagram of an electronic device according to an embodiment of this application. To clarify the purpose, technical proposal, and advantages of this application, the technical proposal in the embodiments of this application will be described clearly and completely below with reference to the drawings of the embodiments. It is obvious that the embodiments described are only a selection of embodiments of this application, not all of them. All other embodiments derived from the embodiments of this application, without requiring any creative effort by a person skilled in the art, are all within the scope of protection of this application. The embodiments and features of the embodiments of this application can be combined in any order, as long as they do not contradict each other. While a logical order is shown in the flowchart, in some cases the steps shown or described may be performed in a different order than that presented herein. The terms "first" and "second" in the specification, claims, and drawings of this application are not intended to describe a specific order, but rather to distinguish different subjects. The term "including" and any variations thereof are intended to cover non-exclusive protection. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not limited to the listed steps or units, but may optionally further include steps or units not listed, or optionally further include other steps or units specific to those processes, methods, products, or apparatus. "Multiple" in this application may represent at least two, for example, two, three, or more, and does not limit the embodiments of this application. Furthermore, the terms "and/or" in this specification merely describe the relationship between related objects, indicating that three relationships are possible. For example, A and/or B may represent three cases: A alone, A and B as a combination, or B alone. Also, unless otherwise specified, the letter "/" in this specification generally indicates that the related objects before and after it are in an "or" relationship. Before introducing embodiments of this application, some technical features of this application will be introduced so that those skilled in the art can easily understand them. (1) Software-Defined Network (SDN): A network architecture that separates the control plane and data plane of network devices. (2) SDN Controller: In the SDN architecture, it enables unified management of all network devices through southbound interface protocols such as Openflow and Netconf, thereby facilitating rapid deployment, resource integration, unified planning, and on-demand calls. (3) Remote Disaster Recovery: This involves building one or more identical systems in differen