CN113992499A - Disaster recovery method, storage medium and system based on dynamic migration of services - Google Patents
Disaster recovery method, storage medium and system based on dynamic migration of services Download PDFInfo
- Publication number
- CN113992499A CN113992499A CN202111357668.8A CN202111357668A CN113992499A CN 113992499 A CN113992499 A CN 113992499A CN 202111357668 A CN202111357668 A CN 202111357668A CN 113992499 A CN113992499 A CN 113992499A
- Authority
- CN
- China
- Prior art keywords
- service
- disaster recovery
- node
- backup
- disaster
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
- G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5072—Grid computing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1034—Reaction to server failures by a load balancer
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
- Y02A10/00—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE at coastal zones; at river basins
- Y02A10/40—Controlling or monitoring, e.g. of flood or hurricane; Forecasting, e.g. risk assessment or mapping
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mathematical Physics (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention provides a disaster recovery method, a storage medium and a system based on dynamic migration of services, wherein the system comprises a plurality of service nodes, a disaster recovery management platform and disaster recovery nodes, and each service node is provided with a disaster recovery agent module; after the service system is migrated from the first service node to the second service node, the disaster recovery agent module of the second service node sends service disaster recovery service registration information and second service operation information to the disaster recovery management platform, the disaster recovery management platform sends the second service operation information to the disaster recovery node and returns disaster recovery node information to the disaster recovery agent module of the second service node according to the service disaster recovery service registration information, the disaster recovery agent module of the second service node sends service data to the disaster recovery node for backup according to the disaster recovery node information included in the service disaster recovery service registration information, and if the disaster recovery node detects that the second service node fails, the disaster recovery node performs service recovery by using the backup service data, so that the service can continuously operate.
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a disaster recovery method, a storage medium and a system based on dynamic migration of services.
Background
With the gradual maturity of the MEC (Multi-access Edge Computing) Edge cloud technology, a service dynamic migration scenario based on the MEC Edge cloud appears, in which a service system (including applications, data, and the like) is migrated from a service center to the MEC Edge cloud, and if a terminal application using the service system moves, the service system dynamically migrates between different MEC Edge cloud nodes along with the moving terminal application, so that the service system and the terminal application can maintain short-distance communication. For example, referring to fig. 1, in an internet of vehicles scenario, a terminal application using a vehicle network service system is loaded in a vehicle, and during movement of the vehicle, the internet of vehicles service system is made to dynamically migrate between different MEC edge cloud nodes along with the moving vehicle, so that the internet of vehicles service system and the terminal application of the vehicle maintain short-distance communication, thereby meeting the requirement of ultra-low latency for automatic driving and the like in the internet of vehicles scenario.
At present, a traditional disaster recovery solution is usually based on a fixed service node, that is, a disaster recovery center backs up service data of the fixed service node, and when a service node fails and cannot continuously operate, the service is restored to continuously operate by using the service data backed up by the disaster recovery center. However, in a service dynamic migration scenario, a service system performs dynamic migration between different MEC edge cloud nodes, and the MEC edge cloud node to which the service system migrates does not establish a data backup connection with a disaster recovery center, so that after the service system performs dynamic migration, if a fault occurs and a service cannot be continuously operated, the service needs to be continuously operated by using backup service data to restore the service, but the service system cannot continuously operate by using service data backed up by the disaster recovery center because the MEC edge cloud node to which the service system migrates does not establish a data backup connection with the disaster recovery center.
Disclosure of Invention
The technical problem to be solved by the invention is how to ensure the continuous operation of the service after the dynamic migration of the service system.
In order to solve the technical problem, the invention provides a disaster recovery system based on dynamic migration of services, which comprises a plurality of service nodes, a disaster recovery management platform and a disaster recovery node, wherein the plurality of service nodes comprise a first service node and a second service node, and each service node is provided with a disaster recovery agent module;
a service system initially runs on the first service node, the service system initiates a disaster recovery backup service registration request to the disaster recovery backup management platform through a disaster recovery backup agent module of the first service node, after the registration is successful, the service system sends first service running information to the disaster recovery backup management platform, the disaster recovery backup management platform sends the first service running information to the disaster recovery backup node and returns service disaster recovery backup service registration information containing disaster recovery node information to the disaster recovery backup agent module of the first service node, and the disaster recovery backup agent module of the first service node sends service data to the disaster recovery backup node for backup according to the disaster recovery backup node information contained in the service disaster recovery backup service registration information;
after the service system is dynamically migrated from the first service node to the second service node, the service system sends service disaster recovery backup service registration information and second service operation information to the disaster recovery backup management platform through a disaster recovery backup agent module of the second service node, the disaster recovery backup management platform sends the second service operation information to the disaster recovery backup node and returns disaster recovery backup node information to a disaster recovery backup agent module of the second service node according to the service disaster recovery backup service registration information, and the disaster recovery backup agent module of the second service node sends service data to the disaster recovery backup node for backup according to the disaster recovery backup node information;
and the disaster recovery backup node receives the service operation information from the disaster recovery backup management platform and the service data from the disaster recovery backup agent module, backs up the received service data, detects the service system operation condition on the corresponding service node according to the received service operation information, and performs service recovery by using the backed-up service data if the corresponding service node fails.
Preferably, the service operation information includes an IP address and/or a port number of the service.
Preferably, the disaster recovery node information includes an IP address and/or a port number of the disaster recovery node.
Preferably, the service disaster recovery service registration information includes a service ID.
Preferably, the service node supports running an automated driving service, an industrial control service and/or a telemedicine service.
Preferably, the plurality of service nodes comprises a plurality of MEC edge cloud nodes distributed at different locations.
The invention also provides a disaster recovery method based on the dynamic migration of the service, which is suitable for the condition that disaster recovery agent modules are respectively deployed on a plurality of service nodes, wherein the service nodes are used for operating the service system;
in a case where the service system initially operates on a service node, the disaster recovery proxy module of the first service node performs the following step A, B:
A. sending a disaster recovery service registration request of the service system to a disaster recovery management platform, so that the disaster recovery management platform completes registration of the service system according to the disaster recovery service registration request, and after the registration is successful, sending first service operation information to the disaster recovery management platform, so that the disaster recovery management platform sends the first service operation information to a disaster recovery node;
B. acquiring service disaster recovery backup service registration information which is returned by the disaster recovery backup management platform and contains disaster recovery backup node information, and sending service data to the disaster recovery backup node according to the disaster recovery backup node information contained in the service disaster recovery backup service registration information so that the disaster recovery backup node performs service recovery by using the backup service data when detecting that the first service node fails according to the first service operation information;
when the service system is dynamically migrated from the first service node to a second service node, the disaster recovery proxy module of the second service node performs the following step C, D:
C. sending the service disaster recovery service registration information and the second service operation information of the service system to the disaster recovery management platform, so that the disaster recovery management platform returns disaster recovery node information according to the service disaster recovery service registration information, and the disaster recovery management platform sends the second service operation information to the disaster recovery node;
D. and obtaining the disaster backup node information returned by the disaster backup management platform, and sending service data to the disaster backup node for backup according to the disaster backup node information, so that the disaster backup node performs service recovery by using the backup service data when detecting that the second service node has a fault according to the second service operation information.
Preferably, the service operation information includes an IP address and/or a port number of the service.
Preferably, the disaster recovery node information includes an IP address and/or a port number of the disaster recovery node.
Preferably, the service disaster recovery service registration information includes a service ID.
The invention also provides a computer-readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, realizes the steps in the disaster recovery method as described above.
The invention has the following beneficial effects: after the service system is dynamically migrated from the first service node to the second service node, the service system sends service disaster backup service registration information and second service operation information to the disaster backup management platform through the disaster backup agent module of the second service node, the disaster backup management platform sends the second service operation information to the disaster backup node and returns disaster backup node information to the disaster backup agent module of the second service node according to the service disaster backup service registration information, and the disaster backup agent module of the second service node sends service data to the disaster backup node for backup according to the disaster backup node information, so that if the service system fails after being migrated to the second service node and the service cannot be continuously operated, the service data backed up by the disaster backup node is subjected to service recovery, and the service can be continuously operated.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic diagram of dynamic migration of services in an Internet of vehicles scenario;
FIG. 2 is a schematic structural diagram of an embodiment of a disaster recovery system based on dynamic migration of services in the present invention;
fig. 3 is a flow diagram of an embodiment of the disaster recovery method based on dynamic migration of services in the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the present invention, the term "comprises" and any variation thereof is intended to cover a non-exclusive inclusion. For example, a process, method, apparatus, product, or apparatus that comprises a list of steps or elements is not limited to those listed but may alternatively include other steps or elements not listed or inherent to such process, method, product, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
In this embodiment, as shown in fig. 2, the system includes a disaster recovery and backup management platform 1, a disaster recovery and backup node 2, and a plurality of service nodes, where each service node is deployed with a disaster recovery and backup agent module, specifically, the plurality of service nodes include a first service node 3 and a second service node 4, the first service node 3 is deployed with a disaster recovery and backup agent module 5, the second service node 4 is deployed with a disaster recovery and backup agent module 6, and the disaster recovery and backup management platform 1 is respectively in communication connection with the disaster recovery and backup node 2, the first service node 3, and the second service node 4. The service nodes 3 and 4 are respectively MEC edge cloud nodes which are respectively arranged at different places and are used for operating a service system 7, and the service nodes 3 and 4 support and operate an automatic driving service, an industrial control service and a remote medical service by using the service system 7; the disaster recovery node 2 is used for backing up the service data of the service nodes 3 and 4 and for service restoration. The MEC edge cloud node is a cloud resource pool and a cloud platform which are arranged on the network edge side close to a production center, is wide in distribution and close to the production center, and performs operation in a local network where the production center is located, so that the waiting time and the network cost of data to and from terminal application are reduced, the congestion and the burden of an operator core network and a transmission network are greatly reduced, and the network delay and the bandwidth pressure when service data are transmitted to the terminal application can be greatly shortened.
In this embodiment, the disaster recovery system is provided with a computer-readable storage medium and a processor that are connected to each other, where the computer-readable storage medium stores computer programs of the disaster recovery agent modules 5 and 6, and when the computer programs are executed by the processor, the disaster recovery method based on dynamic service migration shown in fig. 3 is implemented, which is suitable for a case where the disaster recovery agent modules are respectively deployed on a plurality of service nodes, and specifically:
initially, the service system 7 runs on the first service node 3, and at this time, the disaster recovery proxy module 5 of the first service node 3 executes the following step A, B:
A. the disaster recovery agent module 5 of the first service node 3 sends the disaster recovery service registration request of the service system 7 to the disaster recovery management platform 1, so that the disaster recovery management platform 1 completes registration of the service system 7 according to the disaster recovery service registration request, and sends the first service operation information to the disaster recovery management platform 1 after successful registration, so that the disaster recovery management platform 1 sends the first service operation information to the disaster recovery node 2.
When the service system 7 operates on the first service node 3, the disaster recovery proxy module 5 of the first service node 3 sends a disaster recovery service registration request, and the disaster recovery proxy module 5 of the first service node 3 sends the disaster recovery service registration request from the service system 7 to the disaster recovery management platform 1, that is, the service system 7 sends the disaster recovery service registration request to the disaster recovery management platform 1 through the disaster recovery proxy module 5 of the first service node 3. The first service operation information comprises an IP address and a port number.
After receiving a disaster recovery and backup service registration request of a service system 7, the disaster recovery and backup management platform 1 registers the service system 7 according to the disaster recovery and backup service registration request, and after the registration is successful, the disaster recovery and backup management platform 1 generates service disaster recovery and backup service registration information, where the service disaster recovery and backup service registration information includes a service ID and disaster recovery and backup node information, and the disaster recovery and backup node information includes an IP address and a port number of a disaster recovery and backup node 2. After the registration is successful, the disaster recovery proxy module 5 of the first service node 3 sends first service operation information to the disaster recovery management platform 1, and the disaster recovery management platform 1 sends the first service operation information to the disaster recovery node 2 according to the disaster recovery node information included in the service disaster recovery service registration information and the IP address and the port number of the disaster recovery node 2 included in the disaster recovery node information.
B. The disaster recovery proxy module 5 of the first service node 3 obtains the service disaster recovery backup service registration information including the disaster recovery backup node information returned by the disaster recovery management platform 1, and sends the service data to the disaster recovery backup node 2 for backup according to the disaster recovery backup node information included in the service disaster recovery backup service registration information, so that the disaster recovery backup node 2 performs service recovery by using the backup service data when detecting that the first service node 3 has a fault according to the first service operation information.
After generating the service disaster recovery backup service registration information, the disaster recovery management platform returns the service disaster recovery backup service registration information to the disaster recovery proxy module 5 of the first service node 3, and since the service disaster recovery backup service registration information includes the disaster recovery node information, the disaster recovery proxy module 5 of the first service node 3 acquires the service disaster recovery backup service registration information including the disaster recovery node information, the disaster recovery proxy module 5 of the first service node 3 can obtain the IP address and the port number of the disaster recovery node 2 according to the disaster recovery node information included in the service disaster recovery backup service registration information, thereby sending service data to the disaster recovery node 2 for backup. After the service data backup is completed, the disaster recovery node 2 detects the operation condition of the service system 7 on the first service node 3 according to the first service operation information, and if the failure of the first service node 3 is detected to cause that the service cannot be continuously operated, the disaster recovery node 2 performs service recovery by using the backed-up service data, so that the service can be continuously operated.
In the case that the service system 7 is dynamically migrated from the first service node 3 to the second service node 4, the disaster recovery proxy module 6 of the second service node 4 performs the following step C, D:
C. the disaster recovery agent module 6 of the second service node 4 sends the service disaster recovery service registration information and the second service operation information of the service system 7 to the disaster recovery management platform 1, so that the disaster recovery management platform 1 returns disaster recovery node information according to the service disaster recovery service registration information, and the disaster recovery management platform 1 sends the second service operation information to the disaster recovery node 2.
After the service system 7 is dynamically migrated from the first service node 3 to the second service node 4, the service system sends service disaster recovery backup service registration information and second service operation information to the disaster recovery backup agent module 6 of the second service node 4, and the disaster recovery backup agent module 6 of the second service node 4 sends the service disaster recovery backup service registration information and the second service operation information from the service system 7 to the disaster recovery backup management platform 1, that is, the service system 7 sends the service disaster recovery backup service registration information and the second service operation information to the disaster recovery backup management platform 1 through the disaster recovery backup agent module 6 of the second service node 4. Wherein the second service operation information includes an IP address and a port number.
After receiving the service disaster recovery and backup service registration information and the second service operation information of the service system 7, the disaster recovery and backup management platform 1 sends the second service operation information to the disaster recovery and backup node 2 according to the disaster recovery and backup node information and the IP address and the port number of the disaster recovery and backup node 2 included in the disaster recovery and backup node information, because the service disaster recovery and backup service registration information includes the service ID and the disaster recovery and backup node information, and the disaster recovery and backup node information includes the IP address and the port number of the disaster recovery and backup node 2.
D. The disaster recovery agent module 6 of the second service node 4 obtains the disaster recovery backup node information returned by the disaster recovery management platform 1, and sends the service data to the disaster recovery backup node 2 for backup according to the disaster recovery backup node information, so that the disaster recovery backup node 2 performs service recovery by using the backup service data when detecting that the second service node 4 fails according to the second service operation information.
After the disaster recovery management platform 1 sends the second service operation information to the disaster recovery backup node 2, it returns the disaster recovery backup node information to the disaster recovery backup agent module 6 of the second service node 4, that is, the disaster recovery backup agent module 6 of the second service node 4 obtains the disaster recovery backup node information, so that the disaster recovery backup agent module 6 of the second service node 4 can obtain the IP address and the port number of the disaster recovery backup node 2 according to the disaster recovery backup node information, and can send the service data to the disaster recovery backup node 2 for backup. After the service data backup is completed, the disaster recovery node 2 detects the operation condition of the service system 7 on the second service node 4 according to the second service operation information, and if the service cannot be continuously operated due to the fact that the second service node 4 fails, the disaster recovery node 2 performs service recovery by using the backed-up service data, so that the service can be continuously operated.
For example, in the scenario of internet of vehicles, initially, a vehicle is networked with a first service node 3, and an automatic driving service is implemented by using a service system 7 in the first service node 3, and then the vehicle moves to a position closer to a second service node 4, so that the service system dynamically migrates from the first service node 3 to the second service node 4 along with the moving vehicle, so that the service system 7 and the vehicle maintain short-distance communication, and the requirement of the automatic driving service in the scenario of internet of vehicles on ultra-low delay is met. After the service system 7 is dynamically migrated to the second service node 4, the second service node 4 sends service data to the disaster recovery backup node 2 for backup, so that when the automatic driving service cannot continuously operate due to a failure of the second service node 4, the disaster recovery backup node 2 restores the automatic driving service to continuously operate by using the backup service data.
The embodiment of the disaster recovery system in the service live migration process described above is only illustrative, wherein the system modules may or may not be physically separated, and the components displayed as the modules may or may not be physical modules, and may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above detailed description of the embodiments, those skilled in the art will clearly understand that the embodiments may be implemented by software plus a necessary general hardware platform, and may also be implemented by hardware. Based on such understanding, the above technical solutions may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, where the storage medium includes a Read-Only Memory (ROM), a Random Access Memory (RAM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), a One-time Programmable Read-Only Memory (OTPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc-Read-Only Memory (CD-ROM), or other disk memories, CD-ROMs, or other magnetic disks, A tape memory, or any other medium readable by a computer that can be used to carry or store data.
Finally, it should be noted that: the disaster recovery system disclosed in the embodiment of the present invention is only a preferred embodiment of the present invention, and is only used to illustrate the technical solution of the present invention, not to limit the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art; the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (11)
1. A disaster recovery system based on dynamic migration of services is characterized in that:
the disaster recovery agent module comprises a plurality of service nodes, a disaster recovery management platform and a disaster recovery node, wherein the plurality of service nodes comprise a first service node and a second service node, and each service node is provided with the disaster recovery agent module;
a service system initially runs on the first service node, the service system initiates a disaster recovery backup service registration request to the disaster recovery backup management platform through a disaster recovery backup agent module of the first service node, after the registration is successful, the service system sends first service running information to the disaster recovery backup management platform, the disaster recovery backup management platform sends the first service running information to the disaster recovery backup node and returns service disaster recovery backup service registration information containing disaster recovery node information to the disaster recovery backup agent module of the first service node, and the disaster recovery backup agent module of the first service node sends service data to the disaster recovery backup node for backup according to the disaster recovery backup node information contained in the service disaster recovery backup service registration information;
after the service system is dynamically migrated from the first service node to the second service node, the service system sends service disaster recovery backup service registration information and second service operation information to the disaster recovery backup management platform through a disaster recovery backup agent module of the second service node, the disaster recovery management platform sends the second service operation information to the disaster recovery backup node and returns disaster recovery backup node information to a disaster recovery backup agent module of the second service node according to the service disaster recovery backup service registration information, and the disaster recovery backup agent module of the second service node sends service data to the disaster recovery backup node for backup according to the disaster recovery backup node information;
and the disaster recovery backup node receives the service operation information from the disaster recovery backup management platform and the service data from the disaster recovery backup agent module, backs up the received service data, detects the service system operation condition on the corresponding service node according to the received service operation information, and performs service recovery by using the backed-up service data if the corresponding service node fails.
2. The disaster recovery system based on dynamic migration of services as claimed in claim 1, wherein the service operation information comprises an IP address and/or a port number of the service.
3. The disaster recovery system based on dynamic service migration according to claim 1, wherein the disaster-tolerant backup node information includes an IP address and/or a port number of the disaster-tolerant backup node.
4. The disaster recovery system based on dynamic migration of services as claimed in claim 1, wherein said service disaster recovery service registration information includes a service ID.
5. Disaster recovery system based on dynamic migration of services according to claim 1, wherein said service nodes support running autonomous driving services, industrial control services and/or telemedicine services.
6. The disaster recovery system based on dynamic migration of services as claimed in claim 1, wherein said plurality of service nodes comprises a plurality of MEC edge cloud nodes distributed at different locations.
7. A disaster recovery method based on dynamic migration of services is suitable for the situation that disaster recovery agent modules are respectively deployed on a plurality of service nodes, and the service nodes are used for operating a service system, and is characterized in that:
in a case where the service system initially operates on a first service node, the disaster recovery proxy module of the first service node performs the following step A, B:
A. sending a disaster recovery service registration request of the service system to a disaster recovery management platform, so that the disaster recovery management platform completes registration of the service system according to the disaster recovery service registration request, and after the registration is successful, sending first service operation information to the disaster recovery management platform, so that the disaster recovery management platform sends the first service operation information to a disaster recovery node;
B. acquiring service disaster recovery backup service registration information which is returned by the disaster recovery backup management platform and contains disaster recovery backup node information, and sending service data to the disaster recovery backup node according to the disaster recovery backup node information contained in the service disaster recovery backup service registration information so that the disaster recovery backup node performs service recovery by using the backup service data when detecting that the first service node fails according to the first service operation information;
when the service system is dynamically migrated from the first service node to a second service node, the disaster recovery proxy module of the second service node performs the following step C, D:
C. sending the service disaster recovery service registration information and the second service operation information of the service system to the disaster recovery management platform, so that the disaster recovery management platform returns disaster recovery node information according to the service disaster recovery service registration information, and the disaster recovery management platform sends the second service operation information to the disaster recovery node;
D. and obtaining the disaster backup node information returned by the disaster backup management platform, and sending service data to the disaster backup node for backup according to the disaster backup node information, so that the disaster backup node performs service recovery by using the backup service data when detecting that the second service node has a fault according to the second service operation information.
8. The disaster recovery method based on dynamic migration of services as claimed in claim 7, wherein the service operation information comprises an IP address and/or a port number of the service.
9. The disaster recovery method based on dynamic service migration according to claim 7, wherein the disaster-tolerant backup node information includes an IP address and/or a port number of the disaster-tolerant backup node.
10. The disaster recovery method based on dynamic migration of services as claimed in claim 7, wherein said service disaster recovery service registration information includes a service ID.
11. Computer-readable storage medium, on which a computer program of a disaster recovery proxy module is stored, characterized in that the computer program realizes the steps in the disaster recovery method according to any of claims 7 to 10 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111357668.8A CN113992499B (en) | 2021-11-16 | 2021-11-16 | Disaster recovery method, storage medium and system based on service dynamic migration |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111357668.8A CN113992499B (en) | 2021-11-16 | 2021-11-16 | Disaster recovery method, storage medium and system based on service dynamic migration |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113992499A true CN113992499A (en) | 2022-01-28 |
| CN113992499B CN113992499B (en) | 2023-08-15 |
Family
ID=79748887
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111357668.8A Active CN113992499B (en) | 2021-11-16 | 2021-11-16 | Disaster recovery method, storage medium and system based on service dynamic migration |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113992499B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103309770A (en) * | 2013-06-07 | 2013-09-18 | 国家电网公司 | Disaster recovery virtualization method based on Kinmen database replication technology |
| CN104239164A (en) * | 2013-06-19 | 2014-12-24 | 国家电网公司 | Cloud storage based disaster recovery backup switching system |
| CN106354584A (en) * | 2016-08-30 | 2017-01-25 | 北京中科同向信息技术有限公司 | Technique based on cloud backup for disaster recovery |
| WO2020207266A1 (en) * | 2019-04-08 | 2020-10-15 | 阿里巴巴集团控股有限公司 | Network system, instance management method, device, and storage medium |
| CN112203290A (en) * | 2020-09-30 | 2021-01-08 | 中国联合网络通信集团有限公司 | MEC node deployment position determining method and MEC node deployment device |
| CN112711499A (en) * | 2021-01-18 | 2021-04-27 | 上海英方软件股份有限公司 | Unified backup management system and method based on cloud platform |
| WO2021093535A1 (en) * | 2019-11-11 | 2021-05-20 | 中国移动通信有限公司研究院 | Mobile edge computing application data migration method, device, and core network node |
| CN112965859A (en) * | 2021-03-09 | 2021-06-15 | 上海焜耀网络科技有限公司 | Data disaster recovery method and equipment based on IPFS cluster |
| CN113190378A (en) * | 2020-12-31 | 2021-07-30 | 华数云科技有限公司 | Edge cloud disaster recovery method based on distributed cloud platform |
| CN113535480A (en) * | 2021-07-16 | 2021-10-22 | 深圳华锐金融技术股份有限公司 | Data disaster recovery system and method |
-
2021
- 2021-11-16 CN CN202111357668.8A patent/CN113992499B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103309770A (en) * | 2013-06-07 | 2013-09-18 | 国家电网公司 | Disaster recovery virtualization method based on Kinmen database replication technology |
| CN104239164A (en) * | 2013-06-19 | 2014-12-24 | 国家电网公司 | Cloud storage based disaster recovery backup switching system |
| CN106354584A (en) * | 2016-08-30 | 2017-01-25 | 北京中科同向信息技术有限公司 | Technique based on cloud backup for disaster recovery |
| WO2020207266A1 (en) * | 2019-04-08 | 2020-10-15 | 阿里巴巴集团控股有限公司 | Network system, instance management method, device, and storage medium |
| WO2021093535A1 (en) * | 2019-11-11 | 2021-05-20 | 中国移动通信有限公司研究院 | Mobile edge computing application data migration method, device, and core network node |
| CN112203290A (en) * | 2020-09-30 | 2021-01-08 | 中国联合网络通信集团有限公司 | MEC node deployment position determining method and MEC node deployment device |
| CN113190378A (en) * | 2020-12-31 | 2021-07-30 | 华数云科技有限公司 | Edge cloud disaster recovery method based on distributed cloud platform |
| CN112711499A (en) * | 2021-01-18 | 2021-04-27 | 上海英方软件股份有限公司 | Unified backup management system and method based on cloud platform |
| CN112965859A (en) * | 2021-03-09 | 2021-06-15 | 上海焜耀网络科技有限公司 | Data disaster recovery method and equipment based on IPFS cluster |
| CN113535480A (en) * | 2021-07-16 | 2021-10-22 | 深圳华锐金融技术股份有限公司 | Data disaster recovery system and method |
Non-Patent Citations (1)
| Title |
|---|
| 姜杰;: "基于二层网络互通的跨数据中心电信私有云灾备体系研究", 互联网天地, no. 12 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113992499B (en) | 2023-08-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107809367B (en) | Device online method of SDN (software defined network), SDN controller and network device | |
| CN102355369B (en) | Virtual clustered system as well as processing method and processing device thereof | |
| CN108696581B (en) | Distributed information caching method and device, computer equipment and storage medium | |
| CN108306955B (en) | Large-scale interconnection clustering method for vehicle-mounted terminals | |
| JP6859340B2 (en) | Equipment, systems and methods for retrieving, processing and updating global information | |
| CN112463448B (en) | Distributed cluster database synchronization method, device, equipment and storage medium | |
| CN107729176B (en) | Disaster recovery method and disaster recovery system for configuration file management system | |
| CN113032085A (en) | Management method, device, server, management system and medium of cloud operating system | |
| CN111176888B (en) | Disaster recovery method, device and system for cloud storage | |
| WO2023082749A1 (en) | Service recovery method and system based on mec edge cloud, and storage medium | |
| CN113169895A (en) | N +1 redundancy for virtualization services with low latency failover | |
| US11153173B1 (en) | Dynamically updating compute node location information in a distributed computing environment | |
| CN112003896A (en) | Docking method, device and storage medium for OpenStack cloud management platform and object storage | |
| CN115277727A (en) | Data disaster recovery method, system, device and storage medium | |
| KR20090017595A (en) | Method and system for distributing data processing units in a communication network | |
| CN113992499A (en) | Disaster recovery method, storage medium and system based on dynamic migration of services | |
| CN111756800A (en) | Method and system for processing burst flow | |
| CN116192885A (en) | High-availability cluster architecture artificial intelligent experiment cloud platform data processing method and system | |
| CN114598711B (en) | Data migration method, device, equipment and medium | |
| CN113596195B (en) | Public IP address management method, device, main node and storage medium | |
| CN113391759B (en) | Communication method and equipment | |
| CN112422598A (en) | Resource scheduling method, intelligent front-end equipment, intelligent gateway and distributed system | |
| CN111488248A (en) | Control method, device and equipment for hosting private cloud system and storage medium | |
| CN111857761A (en) | Method and equipment for upgrading container cluster service application program | |
| CN114356214B (en) | Method and system for providing local storage volume for kubernetes system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room 1308, 13th floor, East Tower, 33 Fuxing Road, Haidian District, Beijing 100035 Applicant after: China Telecom Digital Intelligence Technology Co.,Ltd. Address before: Room 1308, 13th floor, East Tower, 33 Fuxing Road, Haidian District, Beijing 100035 Applicant before: CHINA TELECOM GROUP SYSTEM INTEGRATION Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |