Virtual machine high availability method and device based on storage synchronous replication and medium

Abstract

The invention discloses a virtual machine high availability method and device based on storage synchronous replication, and a medium, belongs to the technical field of virtual machine high availability in cloud computing, and aims to solve the technical problem of how to ensure that when a single-point fault of a virtual machine, a host machine or a storage layer occurs in the process of using the virtual machine by a user, the virtual machine is not available. The technical scheme includes that a continuous data flow channel is established between a main storage and a standby storage, data of a virtual machine is continuously copied to the position of the standby storage, and when the main storage fails, the data of the virtual machine is continuously copied to the position of the standby storage. Switching to the standby storage and recovering the running state of the virtual machine; wherein the main storage and the standby storage are respectively deployed in different available areas, and the main virtual machine and the standby virtual machine run in the different available areas, so that the risk of a single point of failure is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of high availability of virtual machines in cloud computing, and in particular to a method, device and medium for high availability of virtual machines based on storage synchronous replication. Background Art

[0002] Storage synchronous replication refers to the real-time or near-real-time replication of data between two or more storage devices to ensure that the data on all storage nodes is consistent. It can be used between primary storage and backup storage, or between multiple data centers in different geographical locations.

[0003] Virtual machine high availability is achieved by using cluster management software (such as VMware vSphere HA and Red Hat Virtualization HA) to monitor the physical host status in real time. When a host failure (such as hardware damage or power outage) is detected, the system automatically migrates the affected virtual machines to other healthy hosts in the cluster and quickly restarts them. This process relies on shared storage (such as SAN and NAS) and a heartbeat network (which monitors host liveness in real time) to ensure virtual machine data integrity and operational continuity.

[0004] High availability refers to designing and implementing a system so that it can maintain continuous service provision during failures or maintenance. The goal of a high-availability system is to minimize service interruptions and improve system reliability and stability.

[0005] However, the current high availability methods for virtual machines may cause single point failures at the virtual machine, host machine or storage level when users use the virtual machine. When a failure occurs, it may cause serious consequences such as data loss and business interruption.

[0006] Therefore, how to ensure that when a single point failure occurs at the virtual machine, host machine or storage level during the user's use of the virtual machine, can respond in a timely manner and continue to provide external services, and effectively avoid data loss and business interruption when a failure occurs is a technical problem that needs to be solved urgently. Summary of the Invention

[0007] The technical task of the present invention is to provide a high-availability method, device and medium for virtual machines based on storage synchronous replication to solve the problem of how to ensure that when a single point failure occurs at the virtual machine, host machine or storage level during the user's use of the virtual machine, it can respond in a timely manner and continue to provide service capabilities to the outside world, effectively avoiding data loss and business interruption when a failure occurs.

[0008] The technical task of the present invention is achieved in the following manner: a method for high availability of virtual machines based on storage synchronous replication, wherein the method establishes a continuous data flow channel between primary storage and backup storage, continuously replicates the virtual machine data to the backup storage location, and when the primary storage fails, switches to the backup storage and restores the operating status of the virtual machine; wherein the primary storage and backup storage are respectively deployed in different availability zones, and the primary virtual machine and the backup virtual machine run in different availability zones, thereby reducing the risk of single point failure;

[0009] At the same time, by creating protection groups, instance pairs, and disk pairs, the high availability process of virtual machines is abstracted and encapsulated, simplifying the formulation and execution of fault strategies.

[0010] Among them, availability zones refer to independent physical locations within the same geographical area, usually consisting of one or more data centers. These data centers have independent power supply, network and cooling systems to ensure that when a data center fails, other data centers can still operate normally.

[0011] As preferred, the method is as follows:

[0012] Create a protection group: Divide the protection group into groups based on your actual business systems. Define the primary and backup availability zones, the range of protected virtual machines, and the RPO value for each protection group. A protection group can contain multiple protected virtual machines. RPO stands for Recovery Point Objective, which refers to the maximum amount of data loss that the business system can tolerate after a failure. Specifically, it is the amount of data that may be lost from the last successful backup or data synchronization until the failure occurs.

[0013] Create instance pairs and disk pairs: Instance pairs are virtual machines that correspond to the primary and backup availability zones. The virtual machines in the protection group use the primary virtual machine as a template to create virtual machines on the backup side with the same mounted disk type, quantity, and size. After the backup virtual machine is created, it is shut down. A virtual machine in active-standby mode only provides external services on the primary side, and the backup virtual machine does not provide management functions, ensuring that the backup virtual machine disk data is fully synchronized with the backup instance. After the instance pair is created, the disks mounted on the instance automatically form a disk pair relationship.

[0014] Enable protection: Call the storage service to create a replication relationship between disks. Asynchronous data replication between disk pairs is enabled through the replication relationship.

[0015] Failover and Failback: When a failure occurs (or is planned), the virtual machines in the primary protection group are shut down, while the corresponding virtual machines on the backup side are powered on. The backup virtual machines continue to provide services, while the primary virtual machines are in maintenance mode. After protection is enabled, if a failure occurs on the primary side, services are switched to the disaster recovery site. When the primary side recovers, the service site is automatically switched to the primary side, and the virtual machines at the disaster recovery site are shut down, with the primary side providing services.

[0016] Asynchronous replication status monitoring for protection group instances: This function monitors the status of disk-pair replication relationships. Combined with the monitoring tool Prometheus, the service side provides status data for all disk replication relationships and pushes the data to Prometheus. If abnormalities are found in the status of consecutive disk replication relationships within a set time, an alarm is triggered and pushed to users and operation and maintenance administrators.

[0017] Preferably, the failover includes automatic switching and manual switching, with manual switching being the default. The user can choose whether to enable the automatic switching function as needed.

[0018] Among them, automatic switching is based on protection groups, using the monitoring and alarm capabilities provided by the monitoring tool Prometheus to collect monitoring indicators of all virtual machines, and push alarm messages and trigger automatic switching logic according to the monitoring indicator thresholds required for automatic switching; virtual machine monitoring indicators include CPU utilization (%), memory usage (%), disk I / O (iops) and network throughput (kbps).

[0019] More optimally, the fault recovery strategy is as follows: virtual machines are grouped by priority, and virtual machines with the same priority are started in the same batch. The larger the value, the lower the priority. Within the same priority, the trigger time of the delay queue is set according to the delay time, and virtual machines are started after the delay time is reached.

[0020] The priority value is 1-10, and the delay time value is 0-1800s.

[0021] Preferably, after enabling protection, the storage system ensures that the data has been persisted before feeding back to the application a successful write. Even if a failure occurs during the write process (such as a power outage), the data will not be lost, and the write operation is either completed in full or not completed at all, ensuring that the data remains consistent even in the event of a partial failure. However, in order to ensure data persistence, synchronous writes may require more system resources, such as CPU, memory, and I / O bandwidth, and performance will be reduced to a certain extent.

[0022] Preferably, a protection group is a logical space of virtual machines that can be protected by the master within the constraints. The same protection group cannot contain the same virtual machine, and virtual machines added to the protection group cannot be arbitrarily destroyed.

[0023] After protection is enabled, the virtual machines in the protection group periodically synchronize data and have the ability to failover and failback.

[0024] Preferably, the instance pair is a virtual machine corresponding to the primary and backup availability zones, and the two virtual machines are exactly the same in storage type, disk size, and number of blocks, and all mounted disk data is kept consistent.

[0025] Preferably, the disk pair is part of an instance pair, that is, the disks are in one-to-one correspondence with the primary and backup availability zones, and the two disks are consistent in type, size, and data.

[0026] An electronic device comprising: a memory and at least one processor;

[0027] wherein the memory stores computer-executable instructions;

[0028] The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the above-mentioned method for high availability of a virtual machine based on storage synchronous replication.

[0029] A computer-readable storage medium stores computer-executable instructions, and when a processor executes the computer-executable instructions, the above-mentioned method for high availability of a virtual machine based on storage synchronous replication is implemented.

[0030] The virtual machine high availability method, device, and medium based on storage synchronous replication of the present invention have the following advantages:

[0031] (1) The present invention utilizes existing storage replication technology to establish a continuous data flow channel between primary storage and backup storage, continuously replicating virtual machine data to the backup storage location. When the primary storage fails, it can quickly switch to the backup storage and restore the virtual machine's operating status, thereby improving system stability and availability.

[0032] (2) The primary and backup storage systems of the present invention are deployed in different availability zones, which improves the reliability and availability of the system while reducing the risk of single point failures. Similarly, the primary and backup virtual machines also run in different availability zones.

[0033] (3) The present invention aims to address the single point failure characteristics of virtual machines, host machines, or storage layers that may exist when users use virtual machines, and provide a high-availability solution at the virtual machine instance level to ensure timely response and continued external service capabilities after the above problems occur;

[0034] (4) The present invention abstracts and streamlines the process of virtual machine high availability, and globally manages and monitors instances based on the concepts of protection groups, instance pairs, and disk pairs, bringing great convenience and efficiency improvements to users. This centralized management approach not only simplifies daily operation and maintenance work, but also facilitates rapid problem identification and implementation in emergency situations.

[0035] (5) The global monitoring of the present invention can also help users promptly identify potential risk points, such as data synchronization delays, insufficient storage resources, and other issues, so that preventive measures can be taken in advance to avoid data loss and business interruption when failures occur;

[0036] (6) The high availability of virtual machines in the present invention relies on synchronous replication technology at the storage level, allowing data to be synchronized between primary and backup storage in different availability zones. This ensures that even if a failure occurs in the primary data center, data can be restored at the backup site, ensuring business continuity. In terms of business implementation, the present invention abstracts and encapsulates the virtual machine high availability process through three core concepts: "protection group," "instance pair," and "disk pair," thereby simplifying the formulation and execution of failure strategies.

[0037] (7) By building high availability capabilities into the virtual machine layer, rather than requiring users to implement them separately at the application or system level, this innovation significantly reduces the burden on users, allowing them to focus more on developing and optimizing their core business without having to worry too much about high availability management of their services.

[0038] (8) In actual production environments, the present invention not only simplifies the process of high-availability operation of virtual machines by abstracting and optimizing the process of high-availability of virtual machines, but also improves the stability and efficiency of the production environment in multiple dimensions such as data consistency, flexible fault strategies, and improved fault response speed, bringing significant operational advantages to users;

[0039] (9) The present invention establishes an asynchronous data replication link between the primary and backup availability zones to ensure that when the primary side encounters an unforeseen failure or disaster, the backup side can quickly take over the business and ensure service continuity. The key steps include protection group creation, instance pair establishment, disk pair mapping, failover, and recovery.

[0040] (10) The present invention monitors the disk replication relationship and storage in the protection group to ensure that any problems with the storage or any abnormalities in the replication relationship between a certain disk pair can be responded to and handled in a timely manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The present invention will be further described below with reference to the accompanying drawings.

[0042] Attachment Figure 1A schematic diagram of a virtual machine high availability method based on storage synchronous replication. DETAILED DESCRIPTION

[0043] The following is a detailed description of the virtual machine high availability method, device and medium based on storage synchronous replication of the present invention with reference to the accompanying drawings and specific embodiments.

[0044] Example 1:

[0045] This embodiment provides a method for high availability of virtual machines based on storage synchronous replication. The method establishes a continuous data flow channel between primary storage and backup storage, continuously replicating the virtual machine's data to the backup storage location. When the primary storage fails, the backup storage is switched to restore the virtual machine's operating status. The primary storage and backup storage are deployed in different availability zones, and the primary virtual machine and the backup virtual machine run in different availability zones, reducing the risk of single point failure.

[0046] At the same time, by creating protection groups, instance pairs, and disk pairs, the high availability process of virtual machines is abstracted and encapsulated, simplifying the formulation and execution of fault strategies.

[0047] Among them, availability zones refer to independent physical locations within the same geographical area, usually consisting of one or more data centers. These data centers have independent power supply, network and cooling systems to ensure that when a data center fails, other data centers can still operate normally.

[0048] As attached Figure 1 As shown, this embodiment provides a method for high availability of virtual machines based on storage synchronous replication, the method is specifically as follows:

[0049] S1. Create protection groups: Divide protection groups based on your actual business systems and define the primary and backup availability zones, the range of protected virtual machines, and the RPO value for each protection group. A protection group can contain multiple protected virtual machines. Generally speaking, protection groups can be divided based on your actual business systems. In other words, all virtual machines in a business system can be grouped together to facilitate unified management of their failover and recovery strategies. RPO stands for Recovery Point Objective and refers to the maximum amount of data loss that the business system can tolerate after a failure. Specifically, it is the amount of data that may be lost from the last successful backup or data synchronization until the failure occurs.

[0050] S2. Create instance pairs and disk pairs: Instance pairs are virtual machines that correspond to the primary and backup availability zones. The virtual machines in the protection group use the primary virtual machine as a template to create virtual machines on the backup side with the same mounted disk type, quantity, and size. After the backup virtual machine is created, it is shut down. A virtual machine in active-standby mode provides external services only on the primary side, and the backup virtual machine does not provide management functions, ensuring that the backup virtual machine disk data is fully synchronized with the backup instance. After the instance pair is created, the disks mounted on the instance automatically form a disk pair relationship.

[0051] S3. Enable protection: This calls the storage service to create a replication relationship between disks. Asynchronous data replication between disk pairs is enabled through the replication relationship. Once enabled, the storage system must ensure data persistence before notifying the application of a successful write. This ensures data is not lost even if a failure (such as a power outage) occurs during the write process. Write operations are either fully completed or not completed, ensuring data consistency even in the event of partial failures. However, to ensure data persistence, synchronous writes may require additional system resources, such as CPU, memory, and I / O bandwidth, resulting in a certain degree of performance degradation.

[0052] S4. Failover and Failback: When a failure occurs (or is planned), the virtual machines in the protection group on the primary side are shut down, while the corresponding virtual machines on the backup side are powered on. The backup virtual machines continue to provide services, while the primary virtual machines are in maintenance mode. After protection is enabled, if a failure occurs on the primary side, services are switched to the disaster recovery site. When the primary side recovers, the service site automatically switches to the primary side, and the virtual machines at the disaster recovery site are shut down, with the primary side providing services.

[0053] S5. Asynchronous replication status monitoring of protection group instances: This monitors the status of disk-pair replication relationships. Combined with the monitoring tool Prometheus, the service side provides status data for all disk replication relationships and pushes the data to Prometheus. If abnormalities are found in the status of consecutive disk replication relationships within a set time, an alarm is triggered and pushed to users and operation and maintenance administrators.

[0054] The fault switching in this embodiment includes automatic switching and manual switching. The default is manual switching. The user can choose whether to turn on the automatic switching function according to the needs;

[0055] Among them, automatic switching is based on protection groups, using the monitoring and alarm capabilities provided by the monitoring tool Prometheus to collect monitoring indicators of all virtual machines, and push alarm messages and trigger automatic switching logic according to the monitoring indicator thresholds required for automatic switching; virtual machine monitoring indicators include CPU utilization (%), memory usage (%), disk I / O (iops) and network throughput (kbps).

[0056] The failover strategy in this embodiment specifies the order in which the service provider site starts virtual machines during a failover or recovery. Generally speaking, all virtual machines in a protection group represent a single service system. System modules are distributed across different virtual machines, and modules have dependencies. Therefore, a startup sequence is required. This embodiment provides two conditions: priority and delayed startup time, to limit the startup order of virtual machines.

[0057] The fault recovery strategy in this embodiment is as follows: virtual machines are grouped by priority, and virtual machines with the same priority are started in the same batch. The larger the value, the lower the priority. The trigger time of the delay queue is set according to the delay time within the same priority, and the virtual machines are started after the delay time is reached.

[0058] The priority value is 1-10, and the delay time value is 0-1800s.

[0059] In this embodiment, after protection is enabled, the storage system ensures that the data has been persisted before feedback is given to the application that the write is successful. Even if a failure occurs during the write process (such as a power outage), the data will not be lost, and the write operation is either completed in full or not completed at all, ensuring that the data remains consistent even in the event of a partial failure. However, in order to ensure data persistence, synchronous writes may require more system resources, such as CPU, memory, and I / O bandwidth, and performance will be reduced to a certain extent.

[0060] In this embodiment, the protection group is a logical space of virtual machines that can be protected by the master within the constraints. The same protection group cannot contain the same virtual machine, and virtual machines added to the protection group cannot be arbitrarily destroyed.

[0061] After protection is enabled, the virtual machines in the protection group periodically synchronize data and have the ability to failover and failback.

[0062] The instance pair in this embodiment is a virtual machine corresponding to the primary and backup availability zones. The two virtual machines are exactly the same in storage type, disk size, and number of blocks, and all mounted disk data is kept consistent.

[0063] The disk pair in this embodiment is part of an instance pair, that is, a disk that corresponds one-to-one to the primary and backup availability zones, and the two disks are consistent in type, size, and data.

[0064] Example 2:

[0065] This embodiment also provides an electronic device, including: a memory and at least one processor;

[0066] wherein the memory stores computer-executable instructions;

[0067] The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the virtual machine high availability method based on storage synchronous replication according to any one of the present inventions.

[0068] The processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor may be a microprocessor or any conventional processor, etc.

[0069] The memory can be used to store computer programs and / or modules. The processor implements various functions of the electronic device by running or executing the computer programs and / or modules stored in the memory, and calling the data stored in the memory. The memory can mainly include a program storage area and a data storage area. The program storage area can store an operating system, at least one application required for a function, etc.; the data storage area can store data created based on the use of the terminal, etc. In addition, the memory can also include high-speed random access memory and non-volatile memory, such as a hard disk, internal memory, a plug-in hard disk, a smart memory card (SMC), a secure digital (SD) card, a flash memory card, at least one disk storage period, a flash memory device, or other volatile solid-state memory devices.

[0070] Example 3:

[0071] This embodiment further provides a computer-readable storage medium storing a plurality of instructions, which are loaded by a processor to cause the processor to execute the virtual machine high availability method based on storage synchronous replication according to any embodiment of the present invention. Specifically, a system or device equipped with a storage medium can be provided, wherein the storage medium stores software program code that implements the functions of any of the above-described embodiments, and a computer (or CPU or MPU) of the system or device can read and execute the program code stored in the storage medium.

[0072] In this case, the program code itself read from the storage medium can realize the function of any one of the above-mentioned embodiments, and thus the program code and the storage medium storing the program code constitute part of the present invention.

[0073] Examples of storage media for providing program code include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), magnetic tapes, non-volatile memory cards, and ROMs. Alternatively, the program code can be downloaded from a server computer via a communication network.

[0074] In addition, it should be clear that the functions of any of the above embodiments can be achieved not only by executing the program code read by the computer, but also by enabling the operating system operating on the computer to complete part or all of the actual operations based on the instructions of the program code.

[0075] In addition, it can be understood that the program code read from the storage medium is written into the memory provided in the expansion board inserted into the computer or into the memory provided in the expansion unit connected to the computer, and then based on the instructions of the program code, the CPU installed on the expansion board or expansion unit is enabled to perform part or all of the actual operations, thereby realizing the functions of any of the above embodiments.

[0076] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for high availability of virtual machines based on storage synchronous replication, characterized in that: This method establishes a continuous data flow channel between primary storage and backup storage, continuously replicating virtual machine data to the backup storage location. When the primary storage fails, the backup storage is switched to restore the virtual machine's operating status. The primary storage and backup storage are deployed in different availability zones, and the primary and backup virtual machines run in different availability zones, reducing the risk of single point failures. At the same time, by creating protection groups, instance pairs, and disk pairs, the high availability process of virtual machines is abstracted and encapsulated, simplifying the formulation and execution of fault strategies.

2. The method for high availability of virtual machines based on storage synchronous replication according to claim 1, characterized in that: The method is as follows: Create a protection group: Divide the protection group into groups based on your actual business systems. Define the primary and backup availability zones, the range of protected virtual machines, and the RPO value for each protection group. A protection group can contain multiple protected virtual machines. RPO stands for Recovery Point Objective, which refers to the maximum amount of data loss that the business system can tolerate after a failure. Specifically, it is the amount of data that may be lost from the last successful backup or data synchronization until the failure occurs. Create instance pairs and disk pairs: Instance pairs are virtual machines that correspond to the primary and backup availability zones. The virtual machines in the protection group use the primary virtual machine as a template to create virtual machines on the backup side with the same mounted disk type, quantity, and size. After the backup virtual machine is created, it is shut down. A virtual machine in active-standby mode only provides external services on the primary side, and the backup virtual machine does not provide management functions, ensuring that the backup virtual machine disk data is fully synchronized with the backup instance. After the instance pair is created, the disks mounted on the instance automatically form a disk pair relationship. Enable protection: Call the storage service to create a replication relationship between disks. Asynchronous data replication between disk pairs is enabled through the replication relationship. Failover and Failback: When a failure occurs, the virtual machines in the primary protection group are shut down, while the corresponding virtual machines on the backup side are powered on. The backup virtual machines continue to provide services, while the primary virtual machines are in maintenance mode. After protection is enabled, if a failure occurs on the primary side, services are switched to the disaster recovery site. When the primary side recovers, the service site is automatically switched to the primary side, and the virtual machines at the disaster recovery site are shut down, with the primary side providing services. Asynchronous replication status monitoring for protection group instances: This function monitors the status of disk-pair replication relationships. Combined with the monitoring tool Prometheus, the service side provides status data for all disk replication relationships and pushes the data to Prometheus. If abnormalities are found in the status of consecutive disk replication relationships within a set time, an alarm is triggered and pushed to users and operation and maintenance administrators.

3. The method for high availability of virtual machines based on storage synchronous replication according to claim 2, characterized in that: Failure switching includes automatic switching and manual switching. The default is manual switching. Users can choose whether to turn on the automatic switching function according to their needs. Among them, automatic switching is based on protection groups. It uses the monitoring and alarm capabilities provided by the monitoring tool Prometheus to collect monitoring indicators of all virtual machines, push alarm messages and trigger automatic switching logic based on the monitoring indicator thresholds required for automatic switching; virtual machine monitoring indicators include CPU utilization, memory usage, disk I / O and network throughput.

4. The method for high availability of virtual machines based on storage synchronous replication according to claim 2, characterized in that: The specific fault recovery strategy is: group virtual machines by priority, start them in the same batch with the same priority, the larger the value, the lower the priority, set the delay queue trigger time according to the delay time within the same priority, and start the virtual machine after the delay time is reached; The priority value is 1-10, and the delay time value is 0-1800s.

5. The method for high availability of virtual machines based on storage synchronous replication according to claim 1, characterized in that: After protection is enabled, the storage system ensures that the data is persisted before reporting a successful write to the application.

6. The method for high availability of virtual machines based on storage synchronous replication according to claim 1, characterized in that: A protection group is a logical space on the master side that can protect virtual machines within certain restrictions. The same protection group cannot contain the same virtual machines, and virtual machines in a protection group cannot be arbitrarily destroyed. After protection is enabled, the virtual machines in the protection group periodically synchronize data and have the ability to failover and failback.

7. The method for high availability of virtual machines based on storage synchronous replication according to claim 1, characterized in that: An instance pair is a virtual machine corresponding to the primary and backup availability zones. The two virtual machines are exactly the same in storage type, disk size, and number of blocks, and all mounted disk data is kept consistent.

8. The method for high availability of virtual machines based on storage synchronous replication according to claim 1, characterized in that: A disk pair is part of an instance pair. It is a one-to-one correspondence between the primary and standby availability zones. The two disks are identical in type, size, and data.

9. An electronic device, characterized in that: include: memory and at least one processor; wherein the memory stores computer-executable instructions; The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the virtual machine high availability method based on storage synchronous replication according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, and when the processor executes the computer-executable instructions, the virtual machine high availability method based on storage synchronous replication as described in any one of claims 1 to 8 is implemented.

Images