WO2020103627A1 - Procédé et dispositif d'auto-régénération de service fondés sur une reprise après sinistre de machine virtuelle et support d'informations - Google Patents

Procédé et dispositif d'auto-régénération de service fondés sur une reprise après sinistre de machine virtuelle et support d'informations

Info

Publication number
WO2020103627A1
WO2020103627A1 PCT/CN2019/112364 CN2019112364W WO2020103627A1 WO 2020103627 A1 WO2020103627 A1 WO 2020103627A1 CN 2019112364 W CN2019112364 W CN 2019112364W WO 2020103627 A1 WO2020103627 A1 WO 2020103627A1
Authority
WO
WIPO (PCT)
Prior art keywords
virtual machine
active
standby
healing
disaster recovery
Prior art date
Application number
PCT/CN2019/112364
Other languages
English (en)
Chinese (zh)
Inventor
周志军
李华
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2020103627A1 publication Critical patent/WO2020103627A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/1658—Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
    • 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the present invention relates to the field of computer technology, and in particular, to a service self-healing method, device, and storage medium based on virtual machine disaster recovery.
  • Cloud computing has the characteristics of dynamically adjusting resources, so many applications, especially cluster applications based on load balancing, such as web applications, support dynamic scaling, that is, dynamically adjust the application servers in the cluster according to the application load to improve Application reliability and availability.
  • applications that wish to support dynamic scaling that is, applications must be stateless.
  • stateful applications such as applications containing state data, applications containing file system data or database data, neither support dynamic scaling under load balancing.
  • business self-healing is generally used to improve the reliability and availability of applications.
  • the business self-healing method is usually implemented by regenerating a virtual machine.
  • This type of virtual machine mounts a cloud hard disk as a data storage disk, and then monitors the virtual machine status of the application. If the virtual machine status is abnormal, such as PING (Packet Internet Groper, Internet package Explorer) failed, URL (Uniform Resource Locator) access failure, etc., then restart the virtual machine with abnormal status, if the business is not restored, delete the virtual machine, re-create a same IP address (Internet Protocol) Address (Internet Protocol address) virtual machine, and mount the same cloud hard disk as a data storage disk to ensure data consistency, so as to achieve business self-healing.
  • this business self-healing method has the problem of deleting virtual machines and rebuilding virtual machines for a long time, which requires at least a few minutes, which will cause the problem of long service interruption.
  • the invention provides a business self-healing method based on virtual machine disaster recovery, which includes: monitoring the state of the active virtual machine during the operation of the active virtual machine; and monitoring the state of the active virtual machine
  • the service self-healing trigger condition is met, controlling the standby virtual machine corresponding to the active virtual machine to process the service of the active virtual machine; wherein the standby virtual machine and the active virtual machine are located in different data centers
  • the standby virtual machine is configured as a disaster recovery virtual machine of the active virtual machine.
  • the invention also provides a service self-healing device based on virtual machine disaster recovery.
  • the service self-healing device based on virtual machine disaster recovery includes a processor and a memory; the processor is used to execute the virtual machine-based storage stored in the memory Disaster recovery business self-healing program to achieve the above-mentioned business self-healing method based on virtual machine disaster recovery.
  • the present invention further provides a storage medium, where the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the above-mentioned virtual machine disaster recovery-based business self-service The healing method.
  • the present invention also provides a computer program product, the computer program product includes a computer program stored on a non-transitory computer-readable storage medium, the computer program includes program instructions, when the program instructions are executed by a computer, the The computer executes the method in any of the above method embodiments.
  • FIG. 1 is a flowchart of a method for self-healing services based on virtual machine disaster recovery according to a first embodiment of the present invention
  • FIG. 2 is a flowchart of a method for self-healing services based on virtual machine disaster recovery according to a second embodiment of the present invention
  • FIG. 3 is a structural diagram of a service self-healing device based on virtual machine disaster recovery according to a third embodiment of the present invention.
  • FIG. 4 is a structural diagram of a business self-healing system based on virtual machine disaster recovery according to a third embodiment of the present invention.
  • This embodiment provides a business self-healing method based on virtual machine disaster recovery.
  • FIG. 1 it is a flowchart of a service self-healing method based on virtual machine disaster recovery according to the first embodiment of the present invention.
  • Step S110 in the process of running the primary virtual machine, performing status monitoring on the primary virtual machine.
  • Monitoring the status of the active virtual machine includes: sending monitoring messages to the active virtual machine every preset time period; collecting return messages corresponding to the monitoring messages; and determining the active messages according to the return messages corresponding to the monitoring messages The state of the virtual machine.
  • the status of the active virtual machine includes: network status and / or access status.
  • the types of monitoring messages include but are not limited to: PING messages and URL access messages.
  • the PING message may be an ICMP (Internet Control Messages Protocol) message corresponding to the PING command.
  • ICMP Internet Control Messages Protocol
  • the return messages corresponding to the monitoring messages include: Time Out messages corresponding to PING messages, and URL access failure messages corresponding to URL access messages.
  • Step S120 when it is monitored that the state of the active virtual machine meets the service self-healing trigger condition, the standby virtual machine corresponding to the active virtual machine is controlled to process the service of the active virtual machine; the standby virtual machine and the active virtual machine are located in different data Center, and the standby virtual machine is configured as the disaster recovery virtual machine of the primary virtual machine.
  • the disaster recovery virtual machine refers to a virtual machine corresponding to the same service as the active virtual machine and used to replace the active virtual machine to process the service.
  • the service self-healing trigger condition is used to identify whether the current state of the active virtual machine needs to replace the active virtual machine with a standby virtual machine to realize the service self-healing.
  • the service self-healing trigger conditions include: network abnormality of the active virtual machine and / or service abnormality.
  • the state of the active virtual machine meets the service self-healing trigger condition. For example: when the state of the active virtual machine meets the service self-healing trigger condition, turn off the active virtual machine to make the device state of the active virtual machine in the standby state; turn on the standby virtual machine to make the device state of the standby virtual machine in active status. Since the standby virtual machine is the disaster recovery virtual machine of the active virtual machine, after the active virtual machine is turned off and the standby virtual machine is turned on, the standby virtual machine replaces the active virtual machine and begins to process the business of the active virtual machine. During the process, the active virtual machine is transformed into a disaster recovery virtual machine of the standby virtual machine.
  • the standby virtual machine is configured as the disaster recovery virtual machine of the active virtual machine, including: the standby virtual machine is configured to have the same IP address as the active virtual machine; the standby virtual machine is configured to synchronize data with the active virtual machine.
  • the standby virtual machine can replace the active virtual machine.
  • API Application Programming Interface
  • Data synchronization between the active virtual machine and the standby virtual machine is realized.
  • the data of the active virtual machine is stored in a storage device mounted on the active virtual machine
  • the data of the standby virtual machine is stored in a storage device mounted on the standby virtual machine.
  • the storage devices respectively mounted on the active virtual machine and the standby virtual machine may be cloud hard disks.
  • the data of the active virtual machine and the standby virtual machine need to be synchronized, during the operation of the active virtual machine, the data image in the storage device mounted by the active virtual machine is copied to the storage device mounted by the standby virtual machine In order to synchronize the data of the standby virtual machine and the active virtual machine (data mirroring synchronization).
  • the standby virtual machine is configured as the disaster recovery virtual machine of the active virtual machine, and when the state of the active virtual machine meets the service self-healing trigger condition, the standby virtual machine replaces the active virtual machine to complete the service self-healing
  • the process of business self-healing there is no need to restart the active virtual machine, let alone re-create the active virtual machine, directly control the standby virtual machine to replace the active virtual machine, and process the business of the active virtual machine, and the process takes time Shorter, can quickly achieve business self-healing, shortening business interruption time.
  • the active virtual machine and the standby virtual machine may be disaster recovery virtual machines. That is, after controlling the standby virtual machine corresponding to the active virtual machine to process the business of the active virtual machine, the active virtual machine that has stopped the business processing has been converted into the standby virtual machine, and the standby virtual machine that started the business processing has been converted into the active Use a virtual machine.
  • the original active virtual machine (converted standby virtual machine) can be troubleshooting, so that the state of the original active virtual machine can be processed normally, so that the original standby virtual machine (converted active virtual machine) is monitored
  • the original active virtual machine can replace the original standby virtual machine to complete the service self-healing.
  • FIG. 2 is a flowchart of a service self-healing method based on virtual machine disaster recovery according to a second embodiment of the present invention.
  • Step S210 a first virtual machine is set in the first data center, and a second virtual machine corresponding to the same service application as the first virtual machine is set in the second data center.
  • Deploying the first virtual machine and the second virtual machine corresponding to the same business application can distribute the business application in two different data centers, reduce the risk of business interruption, and achieve data center-level disaster tolerance.
  • Step S220 Configure a virtual machine disaster recovery strategy for the first virtual machine and the second virtual machine so that the first virtual machine serves as the active virtual machine and the second virtual machine serves as the standby virtual machine.
  • Configuring the virtual machine disaster recovery strategy includes: configuring the first virtual machine as the primary virtual machine and configuring the second virtual machine as the standby virtual machine, so that the second virtual machine serves as the disaster recovery virtual machine of the first virtual machine.
  • the second virtual machine is configured to have the same IP address as the first virtual machine; the second virtual machine is configured to synchronize data with the first virtual machine; the device state of the first virtual machine is configured as the main state, and The device state of the second virtual machine is the standby state, so that the first virtual machine becomes the active virtual machine, and the second virtual machine becomes the standby virtual machine.
  • the standby virtual machine can be used as the disaster recovery virtual machine of the primary virtual machine, and can replace the primary virtual machine for business processing.
  • the virtual machine can be adjusted as the active virtual machine or the standby virtual machine. In some cases, if the first virtual machine is the active virtual machine, the second virtual machine is the standby virtual machine; if the second virtual machine is the active virtual machine, the first virtual machine is the active virtual machine.
  • Configuring the first virtual machine and the second virtual machine to have the same IP address can be achieved by using VRRP (VirtualRouterRedundancyProtocol, virtual routing redundancy protocol) technology of the network switch.
  • VRRP VirtualRouterRedundancyProtocol, virtual routing redundancy protocol
  • the network switch connecting the first virtual machine (active virtual machine) and the second virtual machine (standby virtual machine) can be controlled by calling the API interface of the cloud resource management system, so that the network switch uses VRRP technology, Configure the second virtual machine with the same IP address as the first virtual machine.
  • Configuring the first virtual machine and the second virtual machine to synchronize data can ensure data consistency between the first virtual machine in the first data center and the second virtual machine in the second data center.
  • the data synchronization may be data mirroring synchronization.
  • the data in the storage device mounted by the first virtual machine (active virtual machine) and the storage device mounted by the second virtual machine (standby virtual machine) can be configured by calling the API interface of the cloud resource management system The data in the image is synchronized.
  • Step S230 Configure a service self-healing strategy for the first virtual machine and the second virtual machine.
  • Configuring the business self-healing strategy includes: configuring the state of the primary virtual machine to start the business self-healing process when the conditions for business self-healing are met.
  • the service self-healing trigger conditions include: network abnormality of the active virtual machine and / or service abnormality.
  • the network of the active virtual machine is abnormal, including but not limited to: the network of the active virtual machine is detected to be disconnected N times consecutively.
  • N is a positive integer greater than 1, and N can be an empirical value or an experimentally obtained value. For example, the number of consecutive PING failed to reach the main virtual machine N times.
  • the business of the active virtual machine is abnormal, including but not limited to: the service access to the active virtual machine fails for M consecutive times.
  • M is a positive integer greater than 1, M can be an empirical value or an experimentally obtained value.
  • URL access to the active virtual machine fails for M consecutive times.
  • Step S240 During the process of running the first virtual machine, perform status monitoring on the first virtual machine.
  • the device state of the first virtual machine is the active state (power-on state)
  • the first virtual machine can run as the active virtual machine and can process services
  • the device state of the second virtual machine is the standby state (off state)
  • the second virtual machine is temporarily unavailable as a standby virtual machine and cannot process business.
  • the monitoring message is sent to the first virtual machine that is the active virtual machine every preset time period, and the return message corresponding to the monitoring message is collected, for example, a URL access failure message indicating that the access fails is collected, and a collection message indicating that the connection is not pinged is collected.
  • Time Out messages, etc. to monitor the state of the first virtual machine accordingly; according to the configured business self-healing strategy, determine whether the state of the first virtual machine meets the business self-healing trigger condition, if it meets, then start the business self-healing process, if not If it matches, the state of the first virtual machine continues to be monitored.
  • monitoring messages include but are not limited to: PING messages and URL access messages.
  • the service self-healing trigger condition includes: the number of consecutive PING failures to the main virtual machine reaches 3 times, and the number of consecutive URL access failures to the main virtual machine reaches 3 times; send to the first virtual machine every 5 seconds PING message, and there is no PING connection for 3 consecutive times, and the URL access message is sent to the first virtual machine every 5 seconds, and the access fails for 3 consecutive times.
  • the status of the first virtual machine meets the service self-healing trigger condition , You can start the business self-healing process.
  • Step S250 when it is monitored that the state of the first virtual machine meets the service self-healing trigger condition in the service self-healing strategy, the second virtual machine is used as the active virtual machine, and the first virtual machine is used as the standby virtual machine.
  • the API interface of the cloud resource management system is called, the first virtual machine in the first data center is turned off, and the second virtual machine in the second data center is turned on.
  • the device state of the first virtual machine is turned off, that is, the first virtual machine enters the standby state; the device state of the second virtual machine is turned on, that is, the second virtual machine enters the active state, replacing the first The virtual machine starts processing the business of the first virtual machine.
  • the data of the first virtual machine and the second virtual machine are mirrored and the IP addresses of the first virtual machine and the second virtual machine are synchronized The same, so after the first virtual machine is turned off and the second virtual machine is turned on, there is no impact on the access to the service, thereby achieving self-healing of the service.
  • This embodiment provides a service self-healing device based on virtual machine disaster recovery.
  • FIG. 3 it is a structural diagram of a service self-healing device based on virtual machine disaster recovery according to a third embodiment of the present invention.
  • the service self-healing device based on virtual machine disaster recovery includes but is not limited to: a processor 310 and a memory 320.
  • the processor 310 is used to execute a service self-healing program based on virtual machine disaster recovery stored in the memory 320, so as to implement the above-mentioned service self-healing method based on virtual machine disaster recovery.
  • the processor 310 is used to execute a service self-healing program based on virtual machine disaster recovery stored in the memory 320 to implement the following steps of the service self-healing method based on virtual machine disaster recovery: running the active virtual machine During the process of monitoring the status of the active virtual machine; when it is detected that the state of the active virtual machine meets the service self-healing trigger condition, the standby virtual machine corresponding to the active virtual machine is controlled to process the active virtual machine Business using virtual machines; wherein the standby virtual machine and the active virtual machine are located in different data centers, and the standby virtual machine is configured as a disaster recovery virtual machine of the active virtual machine.
  • the standby virtual machine is configured as a disaster recovery virtual machine of the active virtual machine, including: the standby virtual machine is configured to be the same as the Internet protocol IP address of the active virtual machine; The standby virtual machine is configured to synchronize data with the active virtual machine.
  • the standby virtual machine is configured to be the same as the Internet protocol IP address of the active virtual machine, including: controlling the standby virtual machine and all the machines by calling an application programming interface API of the cloud resource management system The network switch between the active virtual machines, so that the network switch configures the standby virtual machine to have the same IP address as the active virtual machine.
  • the standby virtual machine is configured to synchronize data with the active virtual machine, including: configuring the data in the storage device on which the standby virtual machine is mounted by calling an API interface of the cloud resource management system To synchronize with the data mirror in the storage device mounted by the active virtual machine.
  • the data image in the storage device mounted by the active virtual machine is copied to the storage device mounted by the standby virtual machine, so that the standby virtual machine The data of the machine and the active virtual machine are synchronized.
  • the state monitoring of the active virtual machine includes: sending monitoring messages to the active virtual machine every preset time period; collecting return messages corresponding to the monitoring messages; according to the Monitor the return message corresponding to the message to determine the status of the active virtual machine.
  • controlling the standby virtual machine corresponding to the active virtual machine to process the service of the active virtual machine includes: shutting down the active virtual machine, so that the device state of the active virtual machine is in Standby state; turn on the standby virtual machine so that the device state of the standby virtual machine is in the active state.
  • the service self-healing trigger condition includes: a network abnormality and / or a service abnormality of the active virtual machine.
  • the above-mentioned business self-healing equipment based on virtual machine disaster recovery can be set on the side of the cloud resource management system, or can be set independently.
  • FIG. 4 it is a structural diagram of a service self-healing system based on virtual machine disaster recovery according to a third embodiment of the present invention.
  • the business self-healing equipment based on virtual machine disaster recovery and the cloud resource management system are set independently.
  • the business self-healing system based on virtual machine disaster recovery includes: a cloud resource management system 410, a business self-healing device 420 based on virtual machine disaster recovery, a first data center 430 and a second data center 440.
  • the cloud resource management system 410 includes a network switch (not shown in the figure), and the first data center 430 and the second data center 440 may be connected through the network switch.
  • the first virtual machine 431 and the third virtual machine 432 are installed in the first data center 430, and the second virtual machine 441 and the fourth virtual machine 442 are installed in the second data center 440.
  • the cloud resource management system 410 is used to manage virtual machines in the first data center 430 and virtual machines in the second data center 440.
  • the cloud resource management system 410 provides an API interface 411 that is connected to the first data center 430 and the second data center 440, respectively.
  • the service self-healing device 420 based on virtual machine disaster recovery can call the API interface 411 to configure the first virtual machine 431, the second virtual machine 441, the third virtual machine 432, and the fourth virtual machine 442, and convert the second virtual machine 441 is configured as a disaster recovery virtual machine of the first virtual machine 431, and makes the first virtual machine 431 and the second virtual machine 441 process the first service correspondingly, and configures the fourth virtual machine 442 as the disaster recovery virtual of the third virtual machine 432 Machine, and make the third virtual machine 432 and the fourth virtual machine 442 handle the second service correspondingly.
  • the service self-healing device 420 based on virtual machine disaster recovery can also call the API interface 411 to configure the first service self-healing trigger condition for the first virtual machine 431 and the second virtual machine 441, and the third virtual machine 432 and the fourth virtual machine Machine 442 configures the second service self-healing trigger condition.
  • the first virtual machine 431 is in the power-on state as the active virtual machine
  • the second virtual machine 441 is in the off state as the standby virtual machine
  • the third virtual machine 432 is used as the active
  • the virtual machine is in a power-on state
  • the fourth virtual machine 442 is in a power-off state as a standby virtual machine.
  • the service self-healing device 420 based on virtual machine disaster recovery can send monitoring messages to the first virtual machine 431 and the third virtual machine 432 respectively, and monitor the first virtual machine 431 and the third virtual machine respectively by collecting return messages corresponding to the monitoring messages 432 status;
  • the service self-healing device 420 based on virtual machine disaster recovery calls the API interface 411 of the cloud resource management system 410 to close the first virtual machine when it detects that the status of the first virtual machine 431 meets the first service self-healing trigger Machine 431 turns on the second virtual machine 441 to complete the service self-healing of the first service;
  • the service self-healing device 420 based on virtual machine disaster recovery monitors that the state of the third virtual machine 432 satisfies the trigger condition of the second service self-healing, Call the API interface 411 of the cloud resource management system 410, turn off the third virtual machine 432, turn on the fourth virtual machine 442, and complete the self-healing of the second service.
  • An embodiment of the present invention also provides a storage medium (computer-readable storage medium).
  • a storage medium (computer-readable storage medium).
  • the storage medium may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, hard disk, or solid-state hard disk; the memory may also include combination.
  • the processor is used to execute a service self-healing program based on virtual machine disaster recovery stored in the memory, so as to implement the following steps of a service self-healing method based on virtual machine disaster recovery: during the operation of the active virtual machine, The primary virtual machine performs status monitoring; when it is monitored that the status of the primary virtual machine meets the service self-healing trigger condition, the standby virtual machine corresponding to the primary virtual machine is controlled to process the business of the primary virtual machine; wherein , The standby virtual machine and the active virtual machine are located in different data centers, and the standby virtual machine is configured as a disaster recovery virtual machine of the active virtual machine.
  • the standby virtual machine is configured as a disaster recovery virtual machine of the active virtual machine, including: the standby virtual machine is configured to be the same as the Internet protocol IP address of the active virtual machine; The standby virtual machine is configured to synchronize data with the active virtual machine.
  • the standby virtual machine is configured to be the same as the Internet protocol IP address of the active virtual machine, including: controlling the standby virtual machine and all the machines by calling an application programming interface API of the cloud resource management system The network switch between the active virtual machines, so that the network switch configures the standby virtual machine to have the same IP address as the active virtual machine.
  • the standby virtual machine is configured to synchronize data with the active virtual machine, including: configuring the data in the storage device on which the standby virtual machine is mounted by calling an API interface of the cloud resource management system To synchronize with the data mirror in the storage device mounted by the active virtual machine.
  • the data image in the storage device mounted by the active virtual machine is copied to the storage device mounted by the standby virtual machine, so that the standby virtual machine The data of the machine and the active virtual machine are synchronized.
  • the state monitoring of the active virtual machine includes: sending monitoring messages to the active virtual machine every preset time period; collecting return messages corresponding to the monitoring messages; according to the Monitor the return message corresponding to the message to determine the status of the active virtual machine.
  • controlling the standby virtual machine corresponding to the active virtual machine to process the service of the active virtual machine includes: shutting down the active virtual machine, so that the device state of the active virtual machine is in Standby state; turn on the standby virtual machine so that the device state of the standby virtual machine is in the active state.
  • the service self-healing trigger condition includes: a network abnormality and / or a service abnormality of the active virtual machine.
  • An embodiment of the present invention also provides a computer program product.
  • the computer program product includes a computer program stored on a non-transitory computer-readable storage medium.
  • the computer program includes program instructions. When the program instructions are executed by a computer When, the computer is caused to execute the method in any of the above method embodiments.
  • Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
  • computer storage media includes both volatile and nonvolatile implemented in any method or technology for storing information such as computer readable instructions, data structures, program modules, or other data Sex, removable and non-removable media.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or may Any other medium for storing desired information and accessible by a computer.
  • the communication medium generally contains computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Hardware Redundancy (AREA)

Abstract

La présente invention porte sur un procédé et sur un dispositif d'auto-régénération de service fondés sur une reprise après sinistre de machine virtuelle, ainsi que sur un support d'informations. Le procédé consiste : pendant le processus d'exécution d'une machine virtuelle primaire, à réaliser une surveillance d'état sur la machine virtuelle primaire (S110) ; lorsqu'il est surveillé que l'état de la machine virtuelle primaire remplit une condition de déclenchement d'auto-régénération de service, à commander une machine virtuelle de secours correspondant à la machine virtuelle primaire pour traiter un service de la machine virtuelle primaire, la machine virtuelle de secours et la machine virtuelle primaire étant situées à différents centres de données et la machine virtuelle de secours étant configurée pour être une machine virtuelle de reprise après sinistre de la machine virtuelle primaire (S120).
PCT/CN2019/112364 2018-11-21 2019-10-21 Procédé et dispositif d'auto-régénération de service fondés sur une reprise après sinistre de machine virtuelle et support d'informations WO2020103627A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811393959.0 2018-11-21
CN201811393959.0A CN111209145A (zh) 2018-11-21 2018-11-21 一种基于虚机容灾的业务自愈方法、设备和存储介质

Publications (1)

Publication Number Publication Date
WO2020103627A1 true WO2020103627A1 (fr) 2020-05-28

Family

ID=70774552

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/112364 WO2020103627A1 (fr) 2018-11-21 2019-10-21 Procédé et dispositif d'auto-régénération de service fondés sur une reprise après sinistre de machine virtuelle et support d'informations

Country Status (2)

Country Link
CN (1) CN111209145A (fr)
WO (1) WO2020103627A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112202853B (zh) * 2020-09-17 2022-07-22 杭州安恒信息技术股份有限公司 数据同步方法、系统、计算机设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102497288A (zh) * 2011-12-13 2012-06-13 华为技术有限公司 一种双机备份方法和双机系统实现装置
CN104579791A (zh) * 2015-01-26 2015-04-29 浪潮电子信息产业股份有限公司 一种实现k-db主备自动切换容灾集群的方法
CN106817238A (zh) * 2015-11-30 2017-06-09 中兴通讯股份有限公司 虚拟机修复方法、虚拟机装置、系统及业务功能网元
US20170220371A1 (en) * 2014-03-28 2017-08-03 Ntt Docomo, Inc. Virtualized resource management node and virtual machine migration method
CN107171870A (zh) * 2017-07-17 2017-09-15 郑州云海信息技术有限公司 一种双机热备份方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9461881B2 (en) * 2011-09-30 2016-10-04 Commvault Systems, Inc. Migration of existing computing systems to cloud computing sites or virtual machines
CN204859222U (zh) * 2015-06-02 2015-12-09 郑州银行股份有限公司 同城数据中心双活高可用系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102497288A (zh) * 2011-12-13 2012-06-13 华为技术有限公司 一种双机备份方法和双机系统实现装置
US20170220371A1 (en) * 2014-03-28 2017-08-03 Ntt Docomo, Inc. Virtualized resource management node and virtual machine migration method
CN104579791A (zh) * 2015-01-26 2015-04-29 浪潮电子信息产业股份有限公司 一种实现k-db主备自动切换容灾集群的方法
CN106817238A (zh) * 2015-11-30 2017-06-09 中兴通讯股份有限公司 虚拟机修复方法、虚拟机装置、系统及业务功能网元
CN107171870A (zh) * 2017-07-17 2017-09-15 郑州云海信息技术有限公司 一种双机热备份方法及装置

Also Published As

Publication number Publication date
CN111209145A (zh) 2020-05-29

Similar Documents

Publication Publication Date Title
US11307943B2 (en) Disaster recovery deployment method, apparatus, and system
US10983880B2 (en) Role designation in a high availability node
CN110224871B (zh) 一种Redis集群的高可用方法及装置
CN105743692B (zh) 用于应用管理的基于策略的框架
CN105302661A (zh) 一种实现虚拟化管理平台高可用的系统和方法
US11153269B2 (en) On-node DHCP implementation for virtual machines
CN111314098A (zh) 一种ha系统中实现vip地址漂移的方法和装置
CN111400285B (zh) mySQL数据分片处理方法、装置、计算机设备和可读存储介质
CN111835685B (zh) 一种监控Nginx网络隔离空间的运行状态的方法和服务器
WO2009117946A1 (fr) Procédé de réalisation de serveurs de répartition principal - de secours et serveur de répartition
CN112860485A (zh) 基于keepalived的双机热备系统的控制方法
JPWO2019049433A1 (ja) クラスタシステム、クラスタシステムの制御方法、サーバ装置、制御方法、及びプログラム
WO2020103627A1 (fr) Procédé et dispositif d'auto-régénération de service fondés sur une reprise après sinistre de machine virtuelle et support d'informations
CN115190040B (zh) 虚拟机高可用的实现方法及装置
CN117421158A (zh) 数据库故障处理方法、系统及存储介质
JP2012014674A (ja) 仮想環境における故障復旧方法及びサーバ及びプログラム
WO2017092539A1 (fr) Procédé de réparation de machine virtuelle, dispositif de machine virtuelle, système et élément de réseau fonctionnel de service
JP5285044B2 (ja) クラスタシステム復旧方法及びサーバ及びプログラム
WO2020241032A1 (fr) Système tolérant aux pannes, serveur, procédé d'exploitation du système tolérant aux pannes, procédé d'exploitation du serveur et programme de procédé d'exploitation du serveur
CN110266790B (zh) 边缘集群管理方法、装置、边缘集群及可读存储介质
WO2020083271A1 (fr) Appareil et procédé de convergence de liaison agrégée, et support d'informations
JP2020205121A (ja) フォールトトレラントシステム、サーバ、それらの運用方法、及びプログラム
CN107783855B (zh) 虚拟网元的故障自愈控制装置及方法
JP2006229512A (ja) サーバ切替方法，サーバ及びサーバ切替プログラム
CN104702422A (zh) 实现通信设备高可用性的方法、装置和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19886518

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 29/09/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19886518

Country of ref document: EP

Kind code of ref document: A1