Nothing Special   »   [go: up one dir, main page]

CN114116136A - Synchronization method and system of virtual machine data, electronic device and storage medium - Google Patents

Synchronization method and system of virtual machine data, electronic device and storage medium Download PDF

Info

Publication number
CN114116136A
CN114116136A CN202111464762.3A CN202111464762A CN114116136A CN 114116136 A CN114116136 A CN 114116136A CN 202111464762 A CN202111464762 A CN 202111464762A CN 114116136 A CN114116136 A CN 114116136A
Authority
CN
China
Prior art keywords
cluster
data
storage
virtual machine
storage volume
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.)
Pending
Application number
CN202111464762.3A
Other languages
Chinese (zh)
Inventor
陈仲涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Topsec Technology Co Ltd
Beijing Topsec Network Security Technology Co Ltd
Beijing Topsec Software Co Ltd
Original Assignee
Beijing Topsec Technology Co Ltd
Beijing Topsec Network Security Technology Co Ltd
Beijing Topsec Software Co Ltd
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 Beijing Topsec Technology Co Ltd, Beijing Topsec Network Security Technology Co Ltd, Beijing Topsec Software Co Ltd filed Critical Beijing Topsec Technology Co Ltd
Priority to CN202111464762.3A priority Critical patent/CN114116136A/en
Publication of CN114116136A publication Critical patent/CN114116136A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0662Virtualisation aspects
    • G06F3/0665Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/4557Distribution of virtual machine instances; Migration and load balancing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45579I/O management, e.g. providing access to device drivers or storage
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45595Network integration; Enabling network access in virtual machine instances

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application provides a virtual machine data synchronization method and system, electronic equipment and a computer readable storage medium, wherein the method comprises the following steps: aiming at a first storage volume of a target virtual machine on a first cluster, creating a corresponding second storage volume on a second cluster; when the first storage volume receives write data, the write data is transmitted to a second access layer process of the second cluster through a first access layer process of the first cluster; writing, by the second access stratum process, the write data to the second storage volume. According to the scheme, the target virtual machine in the first cluster can be directly synchronized to the second cluster every time the target virtual machine receives newly written data; the incremental data are not required to be repeatedly synchronized after being written into the storage host of the first cluster, so that the real-time synchronization of the IO data is realized, the synchronization process is simplified, the migration time is shortened, and the consumption of network resources is reduced.

Description

Virtual machine data synchronization method and system, electronic device and storage medium
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a method and a system for synchronizing virtual machine data, an electronic device, and a computer-readable storage medium.
Background
In desktop cloud and super-converged clusters, virtual machine migration operations often occur for resource balanced use. The migration operations are all generated between different hosts in the cluster, and because the same storage resources are used in the cluster, the storage data does not need to be copied during the migration, and only the memory data needs to be synchronized. And when the cluster is upgraded or disaster-tolerant, the migration of the virtual machines across the cluster needs to be realized. In this case, both the memory data and the storage data of the virtual machine need to be synchronized. Because the data volume of the stored data is large, and the virtual machine continuously writes new data, online migration of the stored data is a continuously converging process, and newly written incremental data needs to be continuously synchronized until the incremental data is zero.
In the migration process of the virtual machine, incremental data needs to be continuously synchronized, so that the migration time is too long, and the consumption of network resources is large.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method and a system for synchronizing data of a virtual machine, an electronic device, and a computer-readable storage medium, which are used to shorten a duration of data synchronization during migration of the virtual machine and reduce consumption of network resources by the data synchronization.
In one aspect, the present application provides a method for synchronizing virtual machine data, including:
aiming at a first storage volume of a target virtual machine on a first cluster, creating a corresponding second storage volume on a second cluster;
when the first storage volume receives write data, the write data is transmitted to a second access layer process of the second cluster through a first access layer process of the first cluster;
writing, by the second access stratum process, the write data to the second storage volume.
In an embodiment, prior to said passing said write data to a second access stratum process of said second cluster, said method further comprises:
issuing an IO synchronization instruction to the first access layer process; wherein the IO synchronization instruction instructs the first access stratum process to synchronize the write data to the second access stratum process.
In an embodiment, after the creating the corresponding second storage volume at the second cluster, the method further comprises:
and the first storage host corresponding to the first storage volume transmits the target data of the first storage volume to the second storage host corresponding to the second storage volume.
In one embodiment, the first storage volume corresponds to at least two first storage hosts;
the method for transferring the target data of the first storage volume to the second storage host corresponding to the second storage volume by the first storage host corresponding to the first storage volume includes:
and the at least two first storage hosts transmit the target data of the first storage volume stored by the first storage hosts to the second storage host in parallel.
In an embodiment, before the transferring the target data of the first storage volume to the second storage host corresponding to the second storage volume, the method further includes:
issuing a data synchronization instruction to the first storage host; wherein the data synchronization instruction instructs the first storage host to synchronize the target data to the second storage host.
In an embodiment, the method further comprises:
and after the target virtual machine is migrated to the second cluster, closing the target virtual machine of the first cluster.
In an embodiment, after the shutting down the target virtual machine of the first cluster, the method further comprises:
issuing an IO synchronous termination instruction to the first access layer process; wherein the IO synchronization termination instruction instructs the first access stratum process to stop synchronizing data to the second access stratum process.
In another aspect, the present application provides a system for synchronizing virtual machine data, including:
a first cluster;
a second cluster connected with the first cluster;
the first cluster is used for transmitting the write data to a second access layer process of the second cluster through a first access layer process of the first cluster when a first storage volume receives the write data;
the second cluster is used for locally creating a corresponding second storage volume aiming at a first storage volume of a target virtual machine on the first cluster; writing, by the second access stratum process, the write data to the second storage volume.
Further, the present application also provides an electronic device, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute the synchronization method of the virtual machine data.
In addition, the present application also provides a computer readable storage medium, wherein the storage medium stores a computer program, and the computer program can be executed by a processor to complete the synchronization method of the virtual machine data.
According to the scheme, after the corresponding second storage volume is created for the first storage volume of the target virtual machine on the first cluster, when the write-in data of the first storage volume is received, the write-in data can be transmitted to the second access layer process of the second cluster through the first access layer process of the first cluster, and further, the write-in data can be written into the second storage volume through the second access layer process;
the target virtual machine in the first cluster can directly synchronize to the second cluster every time the target virtual machine receives newly written data; the incremental data are not required to be repeatedly synchronized after being written into the storage host of the first cluster, so that the real-time synchronization of the IO data is realized, the synchronization process is simplified, the migration time is shortened, and the consumption of network resources is reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments of the present application will be briefly described below.
Fig. 1 is a schematic diagram of an architecture for synchronizing virtual machine data according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a method for synchronizing virtual machine data according to an embodiment of the present application;
FIG. 4 is a block diagram illustrating an architecture for synchronization of virtual machine data according to another embodiment of the present disclosure;
FIG. 5 is a schematic diagram of a thin provisioning mode storage volume according to an embodiment of the present application;
FIG. 6 is a schematic diagram of target data synchronization provided by an embodiment of the present application;
FIG. 7 is a schematic diagram of target data synchronization according to another embodiment of the present application;
fig. 8 is a block diagram of a virtual machine data synchronization apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
The system comprises a hyper-convergence or desktop cloud cluster, a super-convergence or desktop cloud cluster and a computing cluster, wherein the storage cluster mainly provides distributed storage service and provides a virtual data disk for a virtual machine on the computing cluster; the computing cluster mainly provides virtualization services, including life cycle management of Virtual machines, and Virtual machines carried by the computing cluster are managed by Virtual Machine Managers (VMMs) on host machines where the Virtual machines are located. In the related art, virtual machine data is synchronized using a virtual machine manager when migrating virtual machines across a cluster.
Referring to fig. 1, which is a schematic diagram of an architecture for synchronizing virtual machine data provided in an embodiment of the present application, as shown in fig. 1, a computing cluster a and a storage cluster a form a desktop cloud cluster; the computing cluster B and the storage cluster B form another desktop cloud cluster. And migrating the virtual machine VM-C of the first desktop cloud cluster to the second desktop cloud cluster to become the virtual machine VM-C'. The data of the virtual machine VM-C is stored in a data disk of the storage host A; the data of the virtual machine VM-C' is stored on the data disk of the storage host C.
And establishing network connection between a virtual machine manager VMM-A and a virtual machine manager VMM-B on the host machine where the virtual machines on the two desktop cloud clusters are located. In synchronizing virtual machine data, data is first passed from storage host a to access layer process a of storage cluster a. And the access layer process A transfers the data to the virtual machine VM-C. The virtual machine VM-C passes the daA to the virtual machine manager VMM-a. Virtual machine manager VMM-a passes the daA to virtual machine manager VMM-B. The virtual machine manager VMM-B passes the data to virtual machine VM-C'. The virtual machine VM-C passes the data to the access layer process B of the storage cluster B. And the access layer process B writes the data into the storage host C.
As can be seen, the IO (Input/Output) path of the synchronous data is: storage host a-access layer process a-virtual machine VM-C-virtual machine manager VMM-a-virtual machine manager VMM-B-virtual machine VM-C' -access layer process B-storage host C.
The whole IO path is extremely long and spans different hosts, and therefore, the consumption of network resources is large. In addition, when the virtual machine manager synchronizes data, all data in the virtual disk corresponding to the virtual machine is copied to the cluster after the virtual machine is migrated, and only part of the data may be written in the virtual disk, so that the synchronization of the whole virtual disk is inefficient, and a large amount of network resources and computing resources are occupied.
As shown in fig. 2, the present embodiment provides an electronic apparatus 1 including: at least one processor 11 and a memory 12, one processor 11 being exemplified in fig. 2. The processor 11 and the memory 12 are connected by a bus 10, and the memory 12 stores instructions executable by the processor 11, and the instructions are executed by the processor 11, so that the electronic device 1 can execute all or part of the flow of the method in the embodiments described below. In an embodiment, the electronic device 1 may be a virtual machine manager or a storage host in a hyper-converged or desktop cloud cluster, for executing a synchronization method of virtual machine data.
The Memory 12 may be implemented by any type of volatile or non-volatile Memory device or combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk or optical disk.
The present application also provides a computer-readable storage medium storing a computer program executable by the processor 11 to perform the method for synchronizing virtual machine data provided by the present application.
Referring to fig. 3, a flowchart of a method for synchronizing virtual machine data according to an embodiment of the present application is shown, and as shown in fig. 3, the method may include the following steps 310 to 330.
Step 310: and aiming at a first storage volume of a target virtual machine on the first cluster, creating a corresponding second storage volume in the second cluster.
Wherein the first cluster and the second cluster may be desktop clouds or hyper-converged clusters. The target virtual machine is a virtual machine to be migrated on the first cluster. The target virtual machine needs to be migrated from the first cluster to the second cluster.
Each virtual machine on the first cluster and the second cluster corresponds to one storage volume in one storage cluster. The first storage volume is a storage volume corresponding to a target virtual machine in a storage cluster of the first cluster.
Before beginning to migrate the target virtual machine, the virtual machine manager on the second cluster may create a second storage volume for the target virtual machine, the second storage volume corresponding to the first storage volume. Alternatively, the virtual machine manager on the first cluster may notify the virtual machine manager of the second cluster to create the second storage volume.
Referring to fig. 4, which is a schematic diagram of an architecture for synchronizing virtual machine data according to another embodiment of the present disclosure, as shown in fig. 4, a storage cluster a is a storage cluster in a first cluster, and a storage cluster B is a storage cluster in a second cluster. The storage volume A is a first storage volume of a target virtual machine on a first cluster; storage volume B is a second storage volume corresponding to the first storage volume.
Step 320: when the first storage volume receives the written data, the written data is transmitted to a second access layer process of a second cluster through a first access layer process of the first cluster.
During the migration of the target virtual machine, the target virtual machine is still running, and at this time, new data may be written to the first storage volume of the target virtual machine. When the first storage volume receives the write-in data, the first cluster can write the write-in data into a plurality of storage hosts corresponding to the first storage volume through the first access layer process. Further, the first access process may pass the write data to a second access stratum process of a second cluster.
Step 330: and writing the write data into the second storage volume through the second access layer process.
After receiving the write data, the second access stratum process may write the write data to the second storage volume. In other words, the second access stratum process may write the write data to a number of storage hosts corresponding to the second storage volume.
By the measures, the real-time synchronization of the IO data is realized, and the target virtual machine in the first cluster can be directly synchronized to the second cluster every time the target virtual machine receives newly written data; the incremental data are not required to be repeatedly synchronized after being written into the storage host of the first cluster, and the synchronization process is simplified. In addition, when the real-time synchronization is carried out, the IO path is a storage host of the first access layer process, the second access layer process and the second cluster, compared with the related technology, the IO path is greatly shortened, and a large amount of network resources and computing resources are saved.
In an embodiment, before the first access stratum process transfers the write data to the second access stratum process, the virtual machine controller of the first cluster may issue an IO synchronization instruction to the first access stratum process. And the IO synchronous instruction is used for indicating the first access layer process to synchronize the written data to the second access layer process. The IO synchronization instruction may include an identification of the first storage volume (e.g., a port number of the target virtual machine) and may also include an identification of the second access stratum process (e.g., an IP address and a port number).
By the measures, the IO synchronization function can be started, so that new data can be written into the second cluster of the migration target virtual machine in real time subsequently.
In one embodiment, after the second storage volume is created, the first cluster and the second cluster only need to synchronize the data written on the first storage volume since the newly added data is synchronized in real time by turning on the IP synchronization function.
The first storage host corresponding to the first storage volume may transfer target data of the first storage volume to the second storage host corresponding to the second storage volume. The target data is data written into the first storage volume before the target virtual machine is migrated. The first storage host is a storage host on the first cluster; the second storage host is a storage host on a second cluster. Taking fig. 4 as an example, the first storage host may be storage host a and/or storage host B; the second storage host may be storage host C and/or storage host D.
The first storage host on the first cluster directly transmits the target data to the second storage host on the second cluster, and at this time, the IO path is: first storage host-second storage host. The data synchronization process only needs one-time network transmission, thereby reducing the consumption of network resources to the maximum extent and improving the synchronization efficiency.
In addition, the first storage volume of the target virtual machine may only write a small amount of data, and the first storage host may skip a plurality of all-zero data blocks by virtue of the thin configuration characteristics of the storage volume in the process of transferring the target data, so that the workload of data synchronization is reduced, and the occupation of network resources and computing resources is reduced.
Referring to fig. 5, a schematic diagram of a storage volume in thin provisioning mode according to an embodiment of the present application is provided, where, as shown in fig. 5, white portions represent data blocks of all zeros, and gray portions represent data blocks of write target data. As can be seen in FIG. 5, only a portion of the data blocks in the storage volume are occupied. The data block which is not written with data can not occupy the storage space during synchronization, and the database is only recorded to be empty through the metadata.
Referring to fig. 6, which is a schematic diagram of target data synchronization provided in an embodiment of the present application, as shown in fig. 6, a new volume is created in a first step, that is, a second storage volume corresponding to a first storage volume on a first cluster is created in a second cluster, where data blocks in the second storage volume are all zero. The second step synchronizes data block 1 for the first storage volume shown in FIG. 5. The third step is to synchronize the data block 2; the fourth sync block 3. Through the synchronization process, the target data actually stored in the first storage volume can be synchronized to the second storage volume.
Under the condition, when the target data is synchronized, the virtual disk corresponding to the target virtual machine does not need to be copied integrally, so that the workload of data synchronization is greatly reduced, and the synchronization efficiency is improved.
In an embodiment, the first storage volume corresponds to at least two first storage hosts, and at this time, when the target data is transferred to the second storage volume, the at least two first storage hosts may transfer the target data of the first storage volume stored by the at least two first storage hosts to the second storage host in parallel.
Referring to fig. 7, a schematic diagram of target data synchronization according to another embodiment of the present application is shown in fig. 7, in which a first storage volume corresponds to a storage host a and a storage host B, and the storage host a stores data of data blocks a1, a2, and A3 on the first storage volume; storage host B stores data for data blocks B1, B2, B3 on the first storage volume. Storage host a and storage host B may synchronize data on the first storage volume in parallel.
By the measures, data synchronization can be carried out more quickly, the synchronization efficiency is improved, and the migration time of the virtual machine is shortened.
In one embodiment, the virtual machine manager of the first cluster may issue a data synchronization instruction to the first storage host before transferring target data of the first storage volume to the second storage volume. The data synchronization command may include an identifier (e.g., IP and port number) of the second storage host, and may be used to indicate the second storage host.
By this measure, a synchronization task for the stored data in the first storage volume can be started.
In an embodiment, after the target virtual machine is migrated to the second cluster, the target virtual machine of the first cluster may be shut down. At this time, the target virtual machine does not exist on the subsequent first cluster, and the first cluster does not need to process the write data of the target virtual machine.
In an embodiment, after the target virtual machine of the first cluster is closed, the virtual machine manager of the first cluster may issue an IO synchronization termination instruction to the first access layer process. And the IO synchronization termination instruction is used for indicating the first access stratum process to stop synchronizing data to the second access stratum process.
Because the target virtual machine stops running in the first cluster and the subsequent first cluster does not receive the data written in the first storage volume any more, an IO synchronization termination instruction can be issued to close the IO synchronization function.
In an embodiment, the present application provides a system for synchronizing virtual machine data, where the system includes a first cluster and a second cluster. The first cluster and the second cluster may both be super-converged or desktop cloud clusters. The first cluster and the second cluster may be connected by a network.
The first cluster hosts a target virtual machine that needs to be migrated to the second cluster.
The second cluster may create a corresponding second storage volume locally for the first storage volume of the target virtual machine.
When the first storage volume receives the write data, the first cluster can transmit the write data to a second access layer process of a second cluster through a first access layer process of the first cluster.
The second cluster may write the write data to a local second storage volume through a second access stratum process.
The specific execution steps of the virtual machine data synchronization system may refer to the related description, and are not described herein again.
According to the scheme, the IO data are synchronized in real time, when the target virtual machine to be migrated is written with new data, the data can be written into the two cluster storages simultaneously, and under the condition, the written data does not need to be synchronized again subsequently, so that the situation that the target virtual machine continuously has new data in the migration process, convergence is difficult to occur, and the migration time is too long is avoided. In addition, the data synchronization is completed by means of a storage volume mechanism, so that IO paths can be greatly shortened, the consumption of network resources and computing resources in the data synchronization process is reduced, the data volume needing to be synchronized is greatly reduced, and the data synchronization efficiency is improved.
Fig. 8 is a block diagram of an apparatus for synchronizing virtual machine data according to an embodiment of the present invention, and as shown in fig. 8, the apparatus may include:
a creating module 810, configured to create, for a first storage volume of a target virtual machine on a first cluster, a corresponding second storage volume in a second cluster;
a transferring module 820, configured to transfer, when the first storage volume receives write data, the write data to a second access stratum process of the second cluster through a first access stratum process of the first cluster;
a writing module 830, configured to write the write data into the second storage volume through the second access stratum process.
The implementation process of the function and the action of each module in the above device is specifically detailed in the implementation process of the corresponding step in the above synchronization method for virtual machine data, and is not described herein again.
In the embodiments provided in the present application, the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

Claims (10)

1. A method for synchronizing data of a virtual machine is characterized by comprising the following steps:
aiming at a first storage volume of a target virtual machine on a first cluster, creating a corresponding second storage volume on a second cluster;
when the first storage volume receives write data, the write data is transmitted to a second access layer process of the second cluster through a first access layer process of the first cluster;
writing, by the second access stratum process, the write data to the second storage volume.
2. The method of claim 1, wherein prior to the passing the write data to the second access stratum process of the second cluster, the method further comprises:
issuing an IO synchronization instruction to the first access layer process; wherein the IO synchronization instruction instructs the first access stratum process to synchronize the write data to the second access stratum process.
3. The method of claim 1, wherein after the creating the corresponding second storage volume at the second cluster, the method further comprises:
and the first storage host corresponding to the first storage volume transmits the target data of the first storage volume to the second storage host corresponding to the second storage volume.
4. The method of claim 3, wherein the first storage volume corresponds to at least two first storage hosts;
the method for transferring the target data of the first storage volume to the second storage host corresponding to the second storage volume by the first storage host corresponding to the first storage volume includes:
and the at least two first storage hosts transmit the target data of the first storage volume stored by the first storage hosts to the second storage host in parallel.
5. The method of claim 3, wherein before the transferring the target data of the first storage volume to the second storage host corresponding to the second storage volume, the method further comprises:
issuing a data synchronization instruction to the first storage host; wherein the data synchronization instruction instructs the first storage host to synchronize the target data to the second storage host.
6. The method of claim 1, further comprising:
and after the target virtual machine is migrated to the second cluster, closing the target virtual machine of the first cluster.
7. The method of claim 6, wherein after the shutting down the target virtual machine of the first cluster, the method further comprises:
issuing an IO synchronous termination instruction to the first access layer process; wherein the IO synchronization termination instruction instructs the first access stratum process to stop synchronizing data to the second access stratum process.
8. A system for synchronizing data of a virtual machine, comprising:
a first cluster;
a second cluster connected with the first cluster;
the first cluster is used for transmitting the write data to a second access layer process of the second cluster through a first access layer process of the first cluster when a first storage volume receives the write data;
the second cluster is used for locally creating a corresponding second storage volume aiming at a first storage volume of a target virtual machine on the first cluster; writing, by the second access stratum process, the write data to the second storage volume.
9. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the method of synchronizing virtual machine data of any of claims 1-7.
10. A computer-readable storage medium, characterized in that the storage medium stores a computer program executable by a processor to perform the method of synchronizing virtual machine data according to any one of claims 1 to 7.
CN202111464762.3A 2021-12-03 2021-12-03 Synchronization method and system of virtual machine data, electronic device and storage medium Pending CN114116136A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111464762.3A CN114116136A (en) 2021-12-03 2021-12-03 Synchronization method and system of virtual machine data, electronic device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111464762.3A CN114116136A (en) 2021-12-03 2021-12-03 Synchronization method and system of virtual machine data, electronic device and storage medium

Publications (1)

Publication Number Publication Date
CN114116136A true CN114116136A (en) 2022-03-01

Family

ID=80365795

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111464762.3A Pending CN114116136A (en) 2021-12-03 2021-12-03 Synchronization method and system of virtual machine data, electronic device and storage medium

Country Status (1)

Country Link
CN (1) CN114116136A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114896221A (en) * 2022-06-09 2022-08-12 北京天融信网络安全技术有限公司 File synchronization method and system

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9946569B1 (en) * 2016-02-08 2018-04-17 Nutanix, Inc. Virtual machine bring-up with on-demand processing of storage requests
US10083057B1 (en) * 2016-03-29 2018-09-25 EMC IP Holding Company LLC Migration of active virtual machines across multiple data centers
CN109376010A (en) * 2018-09-28 2019-02-22 上海思询信息科技有限公司 A method of across cluster resource migration is realized based on Openstack
CN111078127A (en) * 2018-10-22 2020-04-28 阿里巴巴集团控股有限公司 Data migration method, system and device
CN112445570A (en) * 2019-09-03 2021-03-05 中移(苏州)软件技术有限公司 Cloud platform resource migration method and device and storage medium
CN112527452A (en) * 2020-12-03 2021-03-19 北京浪潮数据技术有限公司 Virtual machine migration method, device and medium across OpenStack
CN112711498A (en) * 2020-12-29 2021-04-27 北京浪潮数据技术有限公司 Virtual machine disaster recovery backup method, device, equipment and readable storage medium

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9946569B1 (en) * 2016-02-08 2018-04-17 Nutanix, Inc. Virtual machine bring-up with on-demand processing of storage requests
US10083057B1 (en) * 2016-03-29 2018-09-25 EMC IP Holding Company LLC Migration of active virtual machines across multiple data centers
CN109376010A (en) * 2018-09-28 2019-02-22 上海思询信息科技有限公司 A method of across cluster resource migration is realized based on Openstack
CN111078127A (en) * 2018-10-22 2020-04-28 阿里巴巴集团控股有限公司 Data migration method, system and device
CN112445570A (en) * 2019-09-03 2021-03-05 中移(苏州)软件技术有限公司 Cloud platform resource migration method and device and storage medium
CN112527452A (en) * 2020-12-03 2021-03-19 北京浪潮数据技术有限公司 Virtual machine migration method, device and medium across OpenStack
CN112711498A (en) * 2020-12-29 2021-04-27 北京浪潮数据技术有限公司 Virtual machine disaster recovery backup method, device, equipment and readable storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114896221A (en) * 2022-06-09 2022-08-12 北京天融信网络安全技术有限公司 File synchronization method and system
CN114896221B (en) * 2022-06-09 2024-12-17 北京天融信网络安全技术有限公司 File synchronization method and system

Similar Documents

Publication Publication Date Title
US10073747B2 (en) Reducing recovery time in disaster recovery/replication setup with multitier backend storage
CN108664496B (en) Data migration method and device
US8949182B2 (en) Continuous and asynchronous replication of a consistent dataset
US8407182B1 (en) Systems and methods for facilitating long-distance live migrations of virtual machines
CN113032085A (en) Management method, device, server, management system and medium of cloud operating system
US8799602B2 (en) Automated migration to a new target volume via merged bitmaps to maintain consistency
CN104216793B (en) Application Backup, the method and apparatus recovered
CN104468521B (en) Online moving method, device and system
CN103503414A (en) Computing storage integration cluster system
CN110673941B (en) Migration method of micro-services in multiple computer rooms, electronic equipment and storage medium
CN109408115A (en) A kind of method and computing system based on migrating objects in container environment
CN111679889B (en) Conversion migration method and system of virtual machine
US10606489B2 (en) Sidefiles for management of data written via a bus interface to a storage controller during consistent copying of data
US10142424B2 (en) Two-level cloud system migration
CN114116136A (en) Synchronization method and system of virtual machine data, electronic device and storage medium
US9904600B2 (en) Generating initial copy in replication initialization
WO2017000586A1 (en) Method and device for upgrading virtual network element, and computer storage medium
CN111465920B (en) Management of data written to a storage controller via a bus interface during remote copy operations
US10680890B2 (en) Non-disruptively splitting a coordinated timing network
US20240232022A1 (en) Backing up database files in a distributed system
CN108733460B (en) Method and apparatus for maintaining sessions for network storage devices
CN112506583B (en) An example control method, device, equipment, storage medium and program product
US10642703B2 (en) Configuring a secondary storage system for data mirroring
CN103838639A (en) Method, device and system for recovering metadata of virtual disk
CN114327820A (en) Method and device for processing offline tasks

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