CN113992499B - Disaster recovery method, storage medium and system based on service dynamic migration - Google Patents
Disaster recovery method, storage medium and system based on service dynamic migration Download PDFInfo
- Publication number
- CN113992499B CN113992499B CN202111357668.8A CN202111357668A CN113992499B CN 113992499 B CN113992499 B CN 113992499B CN 202111357668 A CN202111357668 A CN 202111357668A CN 113992499 B CN113992499 B CN 113992499B
- Authority
- CN
- China
- Prior art keywords
- service
- disaster recovery
- node
- information
- management platform
- 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.)
- Active
Links
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 service dynamic migration, wherein the system comprises a plurality of service nodes, a disaster recovery management platform and disaster recovery nodes, and a disaster recovery agent module is deployed on each service node; after the service system is migrated from the first service node to the second service node, service disaster recovery service registration information and second service operation information are sent to the disaster recovery management platform through the disaster recovery proxy module of the second service node, the disaster recovery management platform sends the second service operation information to the disaster recovery node, the disaster recovery node information is returned to the disaster recovery proxy module of the second service node according to the service disaster recovery service registration information, the disaster recovery proxy module of the second service node sends service data to the disaster recovery node for backup according to the disaster recovery node information contained 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 uses the backup service data for service recovery, so that the service can continuously operate.
Description
Technical Field
The present invention relates to the field of cloud computing technologies, and in particular, to a disaster recovery method, a storage medium, and a system based on service dynamic migration.
Background
As MEC (Multi-access Edge Computing ) edge cloud technology has matured, a business live migration scenario based on MEC edge cloud has emerged, in which a business system (including applications, data, etc.) migrates from a business center to the MEC edge cloud, and if a terminal application using the business system moves, the business system dynamically migrates between different MEC edge cloud nodes along with the moving terminal application, so that the business system and the terminal application can keep short-distance communication. For example, referring to fig. 1, in a car networking scenario, a vehicle is loaded with a terminal application using a car networking service system, and during movement of the vehicle, the car networking service system is caused to dynamically migrate between different MEC edge cloud nodes following the moving vehicle, so that the car networking service system and the terminal application of the vehicle keep short-distance communication, thereby meeting the requirements of automatic driving and the like under the car networking scenario on ultra-low time delay.
At present, the conventional disaster recovery scheme is generally based on a fixed service node, namely, a disaster recovery center backs up service data of the fixed service node, and when the service node fails and the service cannot run continuously, the service data backed up by the disaster recovery center is utilized to enable the service to resume continuous running. However, in a service dynamic migration scenario, the service system performs dynamic migration between different MEC edge cloud nodes, and the MEC edge cloud node migrated to by the service system does not establish a data backup connection with the disaster recovery center, so that after the service system performs dynamic migration, if the service system fails and causes service to be unable to continuously run, the service is required to resume continuous running by using the backup service data, but the service system cannot resume continuous running by using the service data backed up by the disaster recovery center because the MEC edge cloud node migrated to by the service system 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 that the service can run continuously after the service system is dynamically migrated.
In order to solve the technical problems, the invention provides a disaster recovery system based on service dynamic migration, which comprises a plurality of service nodes, a disaster recovery management platform and disaster recovery nodes, 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;
the service system initially operates on the first service node, the service system initiates a disaster recovery service registration request to the disaster recovery management platform through a disaster recovery proxy module of the first service node, after registration is successful, the service system sends first service operation information to the disaster recovery management platform, the disaster recovery management platform sends the first service operation information to the disaster recovery node, and returns service disaster recovery service registration information containing disaster recovery node information to the disaster recovery proxy module of the first service node, and the disaster recovery proxy module of the first service node sends service data to the disaster recovery node for backup according to the disaster recovery node information contained in the 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 service registration information and second service operation information to the disaster recovery management platform through a disaster recovery proxy module of the second service node, 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 proxy module of the second service node according to the service disaster recovery service registration information, and the disaster recovery proxy module of the second service node sends service data to the disaster recovery node for backup according to the disaster recovery node information;
and the disaster recovery node receives the service operation information from the disaster recovery management platform and the service data from the disaster recovery proxy 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 if the corresponding service node fails, the disaster recovery node performs service recovery by using the backed-up service data.
Preferably, the service operation information includes an IP address and/or a port number of the service.
Preferably, the disaster recovery node information comprises 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 autopilot service, an industrial control service and/or a telemedicine service.
Preferably, the plurality of service nodes include a plurality of MEC edge cloud nodes separately located at different sites.
The invention also provides a disaster recovery method based on service dynamic migration, which is suitable for the situation that disaster recovery agent modules are deployed on a plurality of service nodes respectively, wherein the service nodes are used for running a service system;
in the case where the service system is initially running on a service node, the disaster recovery proxy module of the first service node executes the following step A, B:
A. the disaster recovery service registration request of the service system is sent to a disaster recovery management platform, so that the disaster recovery management platform can complete registration of the service system according to the disaster recovery service registration request, and after the registration is successful, first service operation information is sent to the disaster recovery management platform, so that the disaster recovery management platform can send the first service operation information to a disaster recovery node;
B. acquiring service disaster recovery service registration information containing disaster recovery node information returned by the disaster recovery management platform, and sending service data to the disaster recovery node for backup according to the disaster recovery node information contained in the service disaster recovery service registration information so that the disaster recovery node can utilize the backup service data to carry out service recovery under the condition that the first service node is detected to be faulty according to the first service operation information;
in the case that the service system dynamically migrates from the first service node to the second service node, the disaster recovery proxy module of the second service node executes the following step C, D:
C. the service disaster recovery service registration information and the second service operation information of the service system are sent 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 acquiring the disaster recovery node information returned by the disaster recovery management platform, and sending service data to the disaster recovery node for backup according to the disaster recovery node information so that the disaster recovery node can utilize the backup service data to carry out service recovery under the condition that the second service node is detected to be faulty 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 comprises 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 having stored thereon a computer program which when executed by a processor implements 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 recovery service registration information and second service operation information to the disaster recovery management platform through the disaster recovery proxy module of the second service node, 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 proxy module of the second service node according to the service disaster recovery service registration information, and the disaster recovery proxy module of the second service node sends service data to the disaster recovery node according to the disaster recovery node information to backup, so that if the service system fails after migrating to the second service node and service cannot continuously operate, the disaster recovery node can utilize the backup service data to perform service recovery, and service can continuously operate.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of service live migration in a car networking scenario;
FIG. 2 is a schematic diagram illustrating the architecture of an embodiment of a disaster recovery system based on dynamic migration of traffic in accordance with the present invention;
FIG. 3 is a flow chart of an embodiment of a disaster recovery method based on dynamic migration of traffic in the present invention.
Detailed Description
In order to make the present invention better understood by those skilled in the art, the following description of the technical solutions of the present invention will be made in detail, but it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments of the present invention, with reference to the accompanying drawings in the embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In the present disclosure, the term "comprising" and any variations thereof is intended to cover a non-exclusive inclusion. For example, a process, method, apparatus, article, or device that comprises a list of steps or elements is not limited to the list of steps or elements but may, in the alternative, include other steps or elements not expressly listed or inherent to such process, method, article, or device.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the invention. The appearances of such phrases 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. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
The embodiment provides a disaster recovery system based on service dynamic migration, as shown in fig. 2, the system includes a disaster recovery management platform 1, a disaster recovery node 2 and a plurality of service nodes, each service node is deployed with a disaster recovery proxy 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 proxy module 5, the second service node 4 is deployed with a disaster recovery proxy module 6, and the disaster recovery management platform 1 is respectively in communication connection with the disaster recovery node 2, the first service node 3 and the second service node 4. The service nodes 3 and 4 are MEC edge cloud nodes respectively arranged at different places and are used for operating the service system 7, and the service nodes 3 and 4 support and operate automatic driving service, industrial control service and remote medical service by utilizing the service system 7; the disaster recovery node 2 is used for backing up the service data of the service nodes 3, 4 and for service restoration. The MEC edge cloud nodes are cloud resource pools and cloud platforms deployed on the network edge side close to the production center, are widely distributed and close to the production center, operate in a local network where the production center is located, reduce waiting time and network cost of data round-trip terminal application, greatly reduce congestion and burden on an operator core network and a transmission network, and further greatly shorten network delay and bandwidth pressure when service data are transmitted to the terminal application.
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 a computer program of the disaster recovery agent module 5, 6 is stored on the computer readable storage medium, and when the computer program is executed by the processor, a disaster recovery method based on service dynamic migration as shown in fig. 3 is implemented, which is applicable to a case where disaster recovery agent modules are deployed on a plurality of service nodes respectively, and the disaster recovery method specifically includes:
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 performs the following step A, B:
A. the disaster recovery proxy module 5 of the first service node 3 sends a 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 can complete registration of the service system 7 according to the disaster recovery service registration request, and after the registration is successful, the disaster recovery management platform 1 sends first service operation information so that the disaster recovery management platform 1 can send the first service operation information to the disaster recovery node 2.
When the service system 7 runs on the first service node 3, a disaster recovery service registration request is sent to the disaster recovery proxy module 5 of the first service node 3, 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. Wherein the first service operation information includes an IP address and a port number.
After receiving the disaster recovery service registration request of the service system 7, the disaster recovery management platform 1 registers the service system 7 according to the disaster recovery service registration request, and after the registration is successful, the disaster recovery management platform 1 generates service disaster recovery service registration information, wherein the service disaster recovery service registration information comprises a service ID and disaster recovery node information, and the disaster recovery node information comprises an IP address and a port number of the disaster recovery 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 contained in the service disaster recovery service registration information and the IP address and the port number of the disaster recovery node 2 contained in the disaster recovery node information.
B. The disaster recovery proxy module 5 of the first service node 3 obtains service disaster recovery service registration information containing disaster recovery node information returned by the disaster recovery management platform 1, and sends service data to the disaster recovery node 2 for backup according to the disaster recovery node information contained in the service disaster recovery service registration information, so that the disaster recovery node 2 can utilize the backup service data to carry out service recovery under the condition that the first service node 3 is detected to be faulty according to the first service operation information.
After generating the service disaster recovery service registration information, the disaster recovery management platform returns the service disaster recovery service registration information to the disaster recovery proxy module 5 of the first service node 3, and because the service disaster recovery service registration information contains the disaster recovery node information, the disaster recovery proxy module 5 of the first service node 3 acquires the service disaster recovery service registration information containing the disaster recovery node information, so that the disaster recovery proxy module 5 of the first service node 3 can acquire the IP address and the port number of the disaster recovery node 2 according to the disaster recovery node information contained in the service disaster recovery service registration information, and can send 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 continuously operate, the disaster recovery node 2 performs service recovery by using the backup service data, so that the service can continuously operate.
In case the service system 7 dynamically migrates 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 proxy 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, service disaster recovery service registration information and second service operation information are sent to the disaster recovery proxy module 6 of the second service node 4, and the disaster recovery proxy module 6 of the second service node 4 sends the service disaster recovery service registration information and the second service operation information from the service system 7 to the disaster recovery management platform 1, that is, the service system 7 sends the service disaster recovery service registration information and the second service operation information to the disaster recovery management platform 1 through the disaster recovery proxy 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 service registration information and the second service operation information of the service system 7, the disaster recovery management platform 1 sends the second service operation information to the disaster recovery node 2 according to the disaster recovery node information and the IP address and the port number of the disaster recovery node 2 included in the disaster recovery node information, because the service disaster recovery service registration information includes the service ID and the disaster recovery node information, and the disaster recovery node information includes the IP address and the port number of the disaster recovery node 2.
D. The disaster recovery agent module 6 of the second service node 4 obtains disaster recovery node information returned by the disaster recovery management platform 1, and sends service data to the disaster recovery node 2 for backup according to the disaster recovery node information, so that the disaster recovery node 2 can utilize the backup service data to perform service recovery under the condition that the second service node 4 is detected to be faulty according to the second service operation information.
After the disaster recovery management platform 1 sends the second service operation information to the disaster recovery node 2, the disaster recovery node information is returned to the disaster recovery proxy module 6 of the second service node 4, that is, the disaster recovery proxy module 6 of the second service node 4 obtains the disaster recovery node information, so that the disaster recovery proxy module 6 of the second service node 4 can obtain the IP address and the port number of the disaster recovery node 2 according to the disaster recovery node information, and thus service data can be sent 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 second service node 4 according to the second service operation information, and if the failure of the second service node 4 is detected to cause that the service cannot continuously operate, the disaster recovery node 2 performs service recovery by using the backup service data, so that the service can continuously operate.
For example, in the internet of vehicles scenario, the vehicle is initially networked with the first service node 3, and the automatic driving service is implemented by using the service system 7 in the first service node 3, and then the vehicle moves to a position closer to the second service node 4, so that the service system moves dynamically 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 keep short-distance communication, and the requirement of the automatic driving service in the internet of vehicles scenario on ultra-low time 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 node 2 for backup, so that when the second service node 4 fails and the automatic driving service cannot continuously run, the disaster recovery node 2 uses the backup service data to enable the automatic driving service to resume continuous running.
The embodiments of disaster recovery system in service live migration described above are merely illustrative, wherein system modules may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above detailed description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course by means of hardware. Based on such understanding, the foregoing technical solutions may be embodied essentially or in part in the form of a software product that may be stored in a computer-readable storage medium including Read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), programmable Read-Only Memory (Programmable Read-Only Memory, PROM), erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), one-time programmable Read-Only Memory (OTPROM), electrically erasable programmable Read-Only Memory (EEPROM), compact disc Read-Only Memory (Compact Disc Read-Only Memory, CD-ROM) or other optical disc Memory, magnetic disc Memory, tape Memory, or any other medium that can be used for computer-readable carrying or storing data.
Finally, it should be noted that: the disaster recovery system disclosed in the embodiment of the invention in the service dynamic migration process is only disclosed in the preferred embodiment of the invention, and is only used for illustrating the technical scheme of the invention, but not limiting the technical scheme; although the invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art will understand that; the technical scheme recorded in the various embodiments can be modified or part of technical features in the technical scheme can be replaced equivalently; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions.
Claims (11)
1. A disaster recovery system based on service dynamic migration is characterized in that:
the system comprises a plurality of service nodes, a disaster recovery management platform and disaster recovery nodes, wherein each service node comprises a first service node and a second service node, and a disaster recovery agent module is deployed on each service node;
the service system initially operates on the first service node, the service system initiates a disaster recovery service registration request to the disaster recovery management platform through a disaster recovery proxy module of the first service node, after registration is successful, the service system sends first service operation information to the disaster recovery management platform, the disaster recovery management platform sends the first service operation information to the disaster recovery node, and returns service disaster recovery service registration information containing disaster recovery node information to the disaster recovery proxy module of the first service node, and the disaster recovery proxy module of the first service node sends service data to the disaster recovery node for backup according to the disaster recovery node information contained in the 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 service registration information and second service operation information to the disaster recovery management platform through a disaster recovery proxy module of the second service node, 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 proxy module of the second service node according to the service disaster recovery service registration information, and the disaster recovery proxy module of the second service node sends service data to the disaster recovery node for backup according to the disaster recovery node information;
and the disaster recovery node receives the service operation information from the disaster recovery management platform and the service data from the disaster recovery proxy 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 if the corresponding service node fails, the disaster recovery node performs service recovery by using the backed-up service data.
2. The disaster recovery system based on dynamic migration of traffic of claim 1, wherein the traffic operation information comprises an IP address and/or a port number of the traffic.
3. The disaster recovery system based on service dynamic migration of claim 1, wherein the disaster recovery node information comprises an IP address and/or a port number of the disaster recovery node.
4. The disaster recovery system based on business dynamic migration of claim 1, wherein the business disaster recovery service registration information comprises a business ID.
5. The business-live migration-based disaster recovery system of claim 1, wherein the business node supports operation of an autopilot business, an industrial control business, and/or a telemedicine business.
6. The business-live migration-based disaster recovery system of claim 1, wherein the plurality of business nodes comprises a plurality of MEC edge cloud nodes separated at different sites.
7. The disaster recovery method based on service dynamic migration is suitable for the situation that disaster recovery proxy modules are deployed on a plurality of service nodes respectively, and the service nodes are used for running a service system, and is characterized in that:
in the case where the service system initially operates on the first service node, the disaster recovery proxy module of the first service node performs the following step A, B:
A. the disaster recovery service registration request of the service system is sent to a disaster recovery management platform, so that the disaster recovery management platform can complete registration of the service system according to the disaster recovery service registration request, and after the registration is successful, first service operation information is sent to the disaster recovery management platform, so that the disaster recovery management platform can send the first service operation information to a disaster recovery node;
B. acquiring service disaster recovery service registration information containing disaster recovery node information returned by the disaster recovery management platform, and sending service data to the disaster recovery node for backup according to the disaster recovery node information contained in the service disaster recovery service registration information so that the disaster recovery node can utilize the backup service data to carry out service recovery under the condition that the first service node is detected to be faulty according to the first service operation information;
in the case that the service system dynamically migrates from the first service node to the second service node, the disaster recovery proxy module of the second service node executes the following step C, D:
C. the service disaster recovery service registration information and the second service operation information of the service system are sent 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 acquiring the disaster recovery node information returned by the disaster recovery management platform, and sending service data to the disaster recovery node for backup according to the disaster recovery node information so that the disaster recovery node can utilize the backup service data to carry out service recovery under the condition that the second service node is detected to be faulty according to the second service operation information.
8. The disaster recovery method based on dynamic migration of traffic of claim 7, wherein the traffic operation information comprises an IP address and/or a port number of the traffic.
9. The disaster recovery method based on service dynamic migration of claim 7, wherein the disaster recovery node information comprises an IP address and/or a port number of the disaster recovery node.
10. The disaster recovery method based on service live migration of claim 7, wherein the service disaster recovery service registration information comprises a service ID.
11. A computer readable storage medium, on which a computer program of a disaster recovery proxy module is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the disaster recovery method according to any of claims 7 to 10.
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 CN113992499A (en) | 2022-01-28 |
| CN113992499B true 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 |
|---|
| 姜杰 ; .基于二层网络互通的跨数据中心电信私有云灾备体系研究.互联网天地.2015,(第12期),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113992499A (en) | 2022-01-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6859340B2 (en) | Equipment, systems and methods for retrieving, processing and updating global information | |
| CN107544783B (en) | Data updating method, device and system | |
| CN105407117A (en) | Distributed data backup method, device and system | |
| CN110716787A (en) | Container address setting method, apparatus, and computer-readable storage medium | |
| WO2023082749A1 (en) | Service recovery method and system based on mec edge cloud, and storage medium | |
| US20170155550A1 (en) | Cloud orchestrated cloud connector upgrades | |
| CN113132159B (en) | Storage cluster node fault processing method, equipment and storage system | |
| CN107872326B (en) | Method, device and system for releasing session resources | |
| CN112218342A (en) | Method, device and system for realizing core network sub-slice disaster tolerance | |
| CN113169895A (en) | N +1 redundancy for virtualization services with low latency failover | |
| CN115277727B (en) | Data disaster recovery method, system, device and storage medium | |
| CN114363334B (en) | Cloud system, network configuration method, device and equipment of cloud desktop virtual machine | |
| KR20150111608A (en) | Method for duplication of virtualization server and Virtualization control apparatus thereof | |
| CN113411363A (en) | Uploading method of image file, related equipment and computer storage medium | |
| CN113992499B (en) | Disaster recovery method, storage medium and system based on service dynamic migration | |
| EP4344259A1 (en) | Session binding relationship processing method and apparatus, electronic device, and readable medium | |
| CN114301842B (en) | Route searching method and device, storage medium, processor and network system | |
| CN111935029B (en) | Gateway load balancing method and device, storage medium and electronic equipment | |
| CN110677283B (en) | Method for fast switching network dual redundancy | |
| CN112422598A (en) | Resource scheduling method, intelligent front-end equipment, intelligent gateway and distributed system | |
| CN113691389A (en) | Configuration method of load balancer, server and storage medium | |
| CN112910675A (en) | Equipment management method, device and system | |
| CN111435320A (en) | Data processing method and device | |
| CN108712297B (en) | Method for autonomously switching gateway of node equipment of Internet of things | |
| CN112165519B (en) | Synchronous node realization method and system for synchronizing data according to needs |
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 |