WO2022021856A1 - 一种多磁盘虚拟机在线迁移到不同存储池的方法及装置 - Google Patents

一种多磁盘虚拟机在线迁移到不同存储池的方法及装置 Download PDF

Info

Publication number
WO2022021856A1
WO2022021856A1 PCT/CN2021/076954 CN2021076954W WO2022021856A1 WO 2022021856 A1 WO2022021856 A1 WO 2022021856A1 CN 2021076954 W CN2021076954 W CN 2021076954W WO 2022021856 A1 WO2022021856 A1 WO 2022021856A1
Authority
WO
WIPO (PCT)
Prior art keywords
disk
migrated
tree
disks
virtual machine
Prior art date
Application number
PCT/CN2021/076954
Other languages
English (en)
French (fr)
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 苏州浪潮智能科技有限公司
Priority to US18/016,998 priority Critical patent/US11740925B2/en
Publication of WO2022021856A1 publication Critical patent/WO2022021856A1/zh

Links

Images

Classifications

    • 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
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/11—File system administration, e.g. details of archiving or snapshots
    • G06F16/128—Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input 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/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0638—Organizing or formatting or addressing of data
    • G06F3/0644—Management of space entities, e.g. partitions, extents, pools
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input 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/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0647—Migration mechanisms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input 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/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0662—Virtualisation aspects
    • G06F3/0665—Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input 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/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0683—Plurality of storage devices
    • G06F3/0689—Disk arrays, e.g. RAID, JBOD
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
    • 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/45579—I/O management, e.g. providing access to device drivers or storage
    • 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 application relates to the field of virtual machine disk migration, and in particular, to a method and device for online migration of a multi-disk virtual machine to different storage pools.
  • virtual machine migration can only be done by migrating all the disks of the virtual machine as a whole. If the current virtual machine occupies too many storage resources and the target environment does not have a storage pool suitable for virtual machine migration, the migration process cannot be completed, which is not conducive to Improve resource utilization and migration efficiency.
  • the present application innovatively proposes a method and device for online migration of a multi-disk virtual machine to different storage pools, which effectively solves the problem of low resource utilization and migration efficiency of virtual machine migration caused by the prior art. It effectively improves the efficiency and reliability of virtual machine migration.
  • a first aspect of the present application provides a method for online migration of a multi-disk virtual machine to different storage pools, including:
  • a disk tree is constructed from each active state disk of the virtual machine to be migrated and multiple snapshot disks corresponding to each active state disk to be migrated, and each disk tree at least includes the active state disk to be migrated.
  • the generated multiple snapshot disks are used to record the generation time sequence relationship of multiple disks in the disk tree;
  • the memory snapshot file is migrated, and the memory snapshot file of the virtual machine boot disk is migrated to the target storage pool of the boot disk; wherein, the boot disk is the disk where the virtual machine operating system is located;
  • a target storage pool corresponding to each active state disk to be migrated is determined, and multiple disk trees are respectively migrated to the corresponding target storage pools according to the generation time sequence relationship of the disks to be migrated in the disk tree.
  • the number of disk trees corresponds to the number of active disks to be migrated.
  • the disk tree further includes active state disks to be migrated.
  • migrating the multiple disk trees to the corresponding target storage pools specifically includes:
  • the disk to be migrated is not the disk with the earliest generation time in the current disk tree, then according to the chronological relationship between the disks recorded in the current disk tree, determine the disk to be migrated at the next level from the disk with the earliest generation time in the current disk tree. Create a new disk in the target storage pool by reference and link. The content of the newly created disk is the same as that of the disk that has been migrated before the current disk to be migrated. The difference data between the current disk to be migrated and the previously migrated disk is migrated to In the newly created disk in the target storage pool;
  • the disks to be migrated in the current disk tree and all the disk trees to be migrated are all migrated, it also includes: judging whether the disk to be migrated is an active state disk, and if it is an active state disk, the current active state to be migrated.
  • the difference data between the disk and the previously migrated disk is synchronized with the data in the newly created disk in the target storage pool.
  • the active state disks to be migrated are part or all of the disks in the virtual machine.
  • the processes of migrating different disk trees to corresponding target storage pools are independent of each other.
  • the snapshot disk is a disk generated by a snapshot operation of a disk in the virtual machine.
  • the disk format is RAW or QCOW2.
  • a second aspect of the present application provides an apparatus for online migration of multi-disk virtual machines to different storage pools, including:
  • the disk tree building module constructs a disk tree from each active state disk of the virtual machine to be migrated and a plurality of snapshot disks correspondingly generated by each active state disk to be migrated, wherein each disk tree at least includes Multiple snapshot disks generated by the migrated active disk are used to record the generation time sequence relationship of multiple disks in the disk tree;
  • the memory snapshot file migration module migrates the memory snapshot file, and migrates the memory snapshot file of the virtual machine boot disk to the target storage pool of the boot disk; wherein, the boot disk is the disk where the virtual machine operating system is located;
  • the disk tree migration module determines the target storage pool corresponding to each active disk to be migrated, and migrates multiple disk trees to the corresponding target storage pools according to the generation time sequence of the disks to be migrated in the disk tree.
  • the present application effectively solves the problems of low utilization rate of virtual machine migration resources and low migration efficiency caused by the prior art.
  • the disk to be migrated can be migrated to a different target storage pool according to the actual situation, effectively The efficiency and reliability of virtual machine migration are improved.
  • the virtual machine disk of this application When the virtual machine disk of this application is migrated, it may be all the disks of the virtual machine, or part of the disks of the virtual machine.
  • the storage pool capacity of the original virtual machine When the storage pool capacity of the original virtual machine is insufficient, or the storage pressure is too large, The disk tree corresponding to one or several disks is migrated to other storage pools, freeing up space for the virtual machine source storage pool and reducing the pressure; when the original storage of the virtual machine has security risks, it needs to be migrated to other storage pools, and the size of the virtual machine
  • dynamic scheduling can be performed through this solution, multiple target storage pools can be selected, and resources can be allocated reasonably, which is more flexible.
  • the disk migration can be performed by means of reference link and differential data migration, which ensures the consistency of the disk data.
  • a snapshot disk is generated from the disk to be migrated.
  • Each snapshot disk contains all the data at the moment when the virtual machine takes a snapshot, and will not affect each other.
  • Fig. 1 is the schematic flow chart of the method of Example 1 in the scheme of the application;
  • FIG. 2 is a schematic flow chart of step S3 of the first method in the solution of the application;
  • FIG. 3 is another schematic flow chart of step S3 of the first method in the solution of the application.
  • FIG. 4 is a schematic diagram of a possible disk tree structure in Embodiment 1 of the solution of the application;
  • FIG. 5 is a schematic structural diagram of the device of Example 2 in the solution of the application.
  • the present application provides a method for online migration of multi-disk virtual machines to different storage pools, including:
  • S1 construct a disk tree for each active state disk of the virtual machine to be migrated and a plurality of snapshot disks corresponding to each active state disk to be migrated, wherein each disk tree at least includes the active state disk to be migrated
  • Multiple snapshot disks generated by the state disk are used to record the generation time sequence relationship of multiple disks in the disk tree;
  • S3 Determine the target storage pool corresponding to each active state disk to be migrated, and migrate the multiple disk trees to the corresponding target storage pools according to the generation time sequence of the disks to be migrated in the disk tree.
  • the number of disk trees corresponds to the number of active state disks to be migrated; the disk tree further includes active state disks to be migrated.
  • the active disks to be migrated can be some or all of the disks in the virtual machine.
  • a snapshot disk is a disk generated by mapping a disk in a virtual machine through a snapshot operation. When an active disk (active disk) exists, both the active disk and the snapshot disk correspond.
  • the snapshot disk records the status of the active disk at a certain moment, including all the data at the corresponding moment; the snapshot may not have a corresponding active disk. For example, if an active disk is deleted after the snapshot is taken, then the snapshot disk does not have a corresponding active disk.
  • the snapshot disk is independent, and a separate disk tree needs to be built.
  • the disk format can be RAW or QCOW2.
  • step S2 the memory snapshot file is migrated, and the memory snapshot file of the boot disk of the virtual machine is migrated to the target storage pool of the boot disk; wherein, the boot disk is the disk where the virtual machine operating system is located; the boot disk is one of the active disks A disk, each virtual machine has one and only one boot disk, similar to the C drive of a computer.
  • step S3 as shown in Figure 2- Figure 3, it specifically includes:
  • S34 determine the disk to be migrated at the next level from the disk with the earliest generation time in the current disk tree, and create a new disk in the target storage pool by means of a reference link,
  • the content of the newly created disk is the same as that of the disk that has been migrated before the current disk to be migrated, and the difference data between the current disk to be migrated and the previously migrated disk is migrated to the newly created disk in the target storage pool;
  • step S35 determine whether all the disks in the current disk tree have been migrated, if the determination result is yes, then step S36 is performed, if the determination result is no, then step S32 is performed;
  • step S36 judge whether all the disk trees to be migrated are all migrated, if the judgement result is yes, then go to step S37; if the judgement result is no, go to step S31;
  • A1, A2, A3, A4, and A5 are 5 snapshot disks generated by snapshot mapping of the active disk (active disk).
  • A1 is the first snapshot disk generated by snapshot mapping of the active disk (active disk).
  • A2 and A3 are both active disks (active disks).
  • snapshot mapping is used to generate a second-level snapshot disk.
  • A2 and A3 include all the data in A1, and the generation time sequence of A2 and A3 can be arbitrary;
  • A4 and A5 are active disks.
  • snapshot mapping is used to generate a third-level snapshot disk.
  • A4 and A5 include all the data in A3.
  • the generation time sequence of A4 and A5 can be arbitrary; By analogy, the generation time of the previous level disk is earlier than the generation time of the next level disk, specifically, the generation time of the first level disk is earlier than the generation time of the second level disk, and the generation time of the second level disk is earlier than the generation time of the third level disk.
  • the disk with the earliest generation time in the current disk tree is the first disk in the current disk tree, that is, the snapshot disk A1.
  • step S33 an empty volume (volume) is created in advance in the target storage of the selected current disk, and the data of the original disk will be copied to the current volume; the data migration port is opened, the disk is ready to be copied, and all data of the original disk is migrated to On pre-created volumes, storage space can be saved by migrating in the form of volumes.
  • step S34 if the current disk to be migrated is not the earliest generation time in the disk tree, that is, it is not the first disk in the disk tree, for example, other disks in the disk tree except S1, such as A2, A3, A4 , A5, take A5 as an example:
  • the corresponding disk that has been migrated before namely A3 is used to generate a new disk A5* in the target storage pool corresponding to the disk tree by reflink (reference link).
  • A5* remains consistent;
  • the data of A5 is consistent with A5*, that is, the current disk A5 of the disk tree has been migrated.
  • the first-level disk A1 is migrated first
  • the second-level disks A2 and A3 are migrated respectively (A2 and A3 can be partially sequential)
  • the third-level disks A4 and A5 are migrated respectively (A4 and A5 can be partially sequential) , and so on, until all the disks in the same disk tree are migrated, that is, the disks at different levels in the disk tree are migrated in the order of the disks, and the migration order of the disks at the same level can be arbitrary.
  • the disk from reflink is just an index node of the original disk, which retains all the information of the original disk. When the original disk exists, it does not occupy space; when the original disk is deleted, the disk from reflink is not affected. exist independently.
  • step S3 specifically includes:
  • S34 determine the disk to be migrated at the next level from the disk with the earliest generation time in the current disk tree, and create a new disk in the target storage pool by means of a reference link,
  • the content of the newly created disk is the same as that of the disk that has been migrated before the current disk to be migrated, and the difference data between the current disk to be migrated and the previously migrated disk is migrated to the newly created disk in the target storage pool;
  • step S35 determine whether the disk to be migrated is an active disk, if the determination result is yes, then step S36 is performed; if the determination result is no, then step S37 is performed;
  • step S37 determine whether all the disks in the current disk tree have been migrated, if the determination result is yes, then step S38 is performed, if the determination result is no, then step S32 is performed;
  • step S38 judge whether all the disk trees to be migrated are all migrated, if the judgement result is yes, then go to step S39; if the judgement result is no, go to step S31;
  • step S36 since the service on the virtual machine is running, the active disk may be writing data all the time, resulting in inconsistent data between the disk after migration and the previous active disk. At this time, the current active state to be migrated is changed to The difference data between the disk and the previously migrated disk is synchronized with the data in the newly created disk in the target storage pool. That is, the difference data between the active disk to be migrated and the newly created disk in the target storage pool are synchronized to keep the data consistency.
  • the snapshot disk in the disk tree is migrated, and finally, the active disk (active disk) in the migration disk tree, if the active disk has been deleted in the virtual machine, only need to be migrated
  • the snapshot disk generated by the original active disk mapping in the disk tree is sufficient.
  • the active disks to be migrated are some or all of the disks in the virtual machine.
  • the process of migrating different disk trees to the corresponding target storage pools is independent of each other.
  • the technical solution of this application is mainly applied to ICS (InCloud Sphere, Inspur virtualization platform).
  • the source storage pool and the target storage pool can be NFS, CFS or local storage pools, or other types of storage pools, which are not covered in this application. limit.
  • the present application effectively solves the problems of low utilization rate of virtual machine migration resources and low migration efficiency caused by the prior art.
  • the disks to be migrated can be migrated to different target storage pools according to the actual situation, which effectively improves the performance of the virtual machine.
  • Efficiency and reliability of virtual machine migration are effectively solved.
  • the virtual machine disk of this application When the virtual machine disk of this application is migrated, it may be all the disks of the virtual machine, or part of the disks of the virtual machine. When the capacity of the original virtual machine storage pool is insufficient or the storage pressure is too large, one of the multiple disks of the virtual machine will be transferred to the virtual machine. Or the disk trees corresponding to several disks are migrated to other storage pools to free up space for the virtual machine source storage pool and reduce the pressure. , when a satisfactory target storage pool cannot be found, dynamic scheduling can be performed through this solution, multiple target storage pools can be selected, and resources can be allocated reasonably, which is more flexible.
  • different disk trees are migrated to the corresponding target storage pools.
  • the target storage pools of different disk trees are different, and they are independent of each other during the migration process and do not affect each other. Even if a certain disk tree fails to migrate, other disk trees can still be migrated to other Storage pool with high fault tolerance.
  • the disk migration can be performed by means of reference links and differential data migration, so as to ensure the consistency of the disk data.
  • snapshot disks are generated from the disks to be migrated.
  • Each snapshot disk contains all the data at the time when the virtual machine is snapshotted, and will not affect each other.
  • snapshot disks without corresponding active disks you can also Build a disk tree (only snapshot disks are included in the disk tree), perform disk migration, and expand the applicable scenarios of disk migration.
  • the technical solution of the present application also provides a device for online migration of multi-disk virtual machines to different storage pools, including:
  • the disk tree building module 101 builds a disk tree with each active state disk of the virtual machine to be migrated and a plurality of snapshot disks correspondingly generated by each active state disk to be migrated, wherein each disk tree at least includes Multiple snapshot disks generated by the active disk to be migrated, used to record the generation time sequence relationship of multiple disks in the disk tree;
  • the memory snapshot file migration module 102 migrates the memory snapshot file, and migrates the memory snapshot file of the virtual machine boot disk to the target storage pool of the boot disk; wherein, the boot disk is the disk where the virtual machine operating system is located;
  • the disk tree migration module 103 determines a target storage pool corresponding to each active disk to be migrated, and migrates multiple disk trees to the corresponding target storage pools according to the generation time sequence relationship of the to-be-migrated disks in the disk tree.
  • the present application effectively solves the problems of low utilization rate of virtual machine migration resources and low migration efficiency caused by the prior art.
  • the disks to be migrated can be migrated to different target storage pools according to the actual situation, which effectively improves the performance of the virtual machine.
  • Efficiency and reliability of virtual machine migration are effectively solved.
  • the virtual machine disk of this application When the virtual machine disk of this application is migrated, it may be all the disks of the virtual machine, or part of the disks of the virtual machine. When the capacity of the original virtual machine storage pool is insufficient or the storage pressure is too large, one of the multiple disks of the virtual machine will be transferred to the virtual machine. Or the disk trees corresponding to several disks are migrated to other storage pools to free up space for the virtual machine source storage pool and reduce the pressure. , when a satisfactory target storage pool cannot be found, dynamic scheduling can be performed through this solution, multiple target storage pools can be selected, and resources can be allocated reasonably, which is more flexible.
  • different disk trees are migrated to the corresponding target storage pools.
  • the target storage pools of different disk trees are different, and they are independent of each other during the migration process and do not affect each other. Even if a certain disk tree fails to migrate, other disk trees can still be migrated to other Storage pool with high fault tolerance.
  • the disk migration can be performed by means of reference links and differential data migration, so as to ensure the consistency of the disk data.
  • snapshot disks are generated from the disks to be migrated.
  • Each snapshot disk contains all the data at the time when the virtual machine is snapshotted, and will not affect each other.
  • snapshot disks without corresponding active disks you can also Build a disk tree (only snapshot disks are included in the disk tree), perform disk migration, and expand the applicable scenarios of disk migration.

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)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种多磁盘虚拟机在线迁移到不同存储池的方法及装置，该方法包括：将虚拟机每个待迁移的活动状态磁盘以及由每个待迁移的活动状态磁盘对应产生的多个快照盘构建磁盘树，用于记录磁盘树中多个磁盘的生成时间先后关系；迁移内存快照文件；确定每个待迁移的活动状态磁盘对应的目标存储池，根据磁盘树中待迁移磁盘的生成时间先后关系，将多个磁盘树分别迁移至对应的目标存储池。解决了由于现有技术造成虚拟机迁移资源利用率以及迁移效率不高的问题，在虚拟机磁盘迁移时，可以根据实际情况将待迁移磁盘迁移至不同的目标存储池，提高了虚拟机迁移的效率以及可靠性。

Description

一种多磁盘虚拟机在线迁移到不同存储池的方法及装置
本申请要求于2020年07月30日提交至中国专利局、申请号为202010748839.9、发明名称为“一种多磁盘虚拟机在线迁移到不同存储池的方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及虚拟机磁盘迁移领域，尤其是涉及一种多磁盘虚拟机在线迁移到不同存储池的方法及装置。
背景技术
随着云计算技术飞快的发展，越来越多的公司推出了用于提供云计算基础功能的虚拟化管理系统，这些虚拟化管理系统部署在服务器上，使得所有虚拟机可在多种环境下共享该服务器的资源。
当虚拟机当前所在的主机负载过大，资源不足，或者需要对当前环境进行开发维护，通常需要将虚拟机迁移到其他主机或者存储来减小压力，或者等待当前环境维护完成后再将虚拟机迁移回来。
而且，虚拟机迁移只能是将虚拟机的所有磁盘进行整体迁移，如果当前虚拟机占用存储资源过多，出现目标环境没有适合虚拟机迁移的存储池的情况，就无法完成迁移过程，不利于提高资源利用率以及迁移效率。
发明内容
本申请为了解决现有技术中存在的问题，创新提出了一种多磁盘虚拟机在线迁移到不同存储池的方法及装置，有效解决由于现有技术造成虚拟机迁移资源利用率以及迁移效率不高的问题，有效的提高了虚拟机迁移的效率以及可靠性。
本申请第一方面提供了一种多磁盘虚拟机在线迁移到不同存储池的方法，包括：
将虚拟机每个待迁移的活动状态磁盘以及由每个待迁移的活动状态磁盘对应产生的多个快照盘构建磁盘树，所述每个磁盘树中至少包括由所述 待迁移的活动状态磁盘产生的多个快照盘，用于记录磁盘树中多个磁盘的生成时间先后关系；
迁移内存快照文件，将虚拟机引导盘的内存快照文件，迁移到引导盘的目标存储池；其中，引导盘为虚拟机操作系统所在磁盘；
确定每个待迁移的活动状态磁盘对应的目标存储池，根据磁盘树中待迁移磁盘的生成时间先后关系，将多个磁盘树分别迁移至对应的目标存储池。
可选地，磁盘树的数量与待迁移的活动状态磁盘的数量对应相同。
可选地，所述磁盘树还包括待迁移的活动状态磁盘。
可选地，根据磁盘树中待迁移的活动状态磁盘以及多个快照盘的生成时间先后关系，将多个磁盘树分别迁移至对应的目标存储池具体包括：
确定当前待迁移的磁盘树；
判断当前磁盘树中待迁移的磁盘是否是当前磁盘树中生成时间最早的，如果是当前磁盘树中的生成时间最早的磁盘，在所述当前磁盘树对应的目标存储池中预先建立空的卷，将待迁移的磁盘中的数据复制到目标存储池中预先建立空的卷；
如果不是当前磁盘树中的生成时间最早的磁盘，则根据当前磁盘树中记录的磁盘之间的时间先后关系，确定距离当前磁盘树中的生成时间最早磁盘的下一级待迁移的磁盘，在目标存储池中通过引用链接方式新建一个磁盘，新建的磁盘与当前待迁移的磁盘之前已经迁移完成的磁盘内容一致，将当前待迁移的磁盘与之前已经迁移完成的磁盘之间的差异数据迁移到目标存储池中新建的磁盘中；
直至当前磁盘树中待迁移的磁盘以及所有待迁移的磁盘树全部迁移完成。
进一步地，直至当前磁盘树中待迁移的磁盘以及所有待迁移的磁盘树全部迁移完成之前还包括：判断待迁移的磁盘是否是活动状态磁盘，如果是活动状态磁盘，将当前待迁移的活动状态磁盘与之前已经迁移完成的磁盘之间的差异数据与目标存储池中新建的磁盘中的数据进行同步。
可选地，待迁移的活动状态磁盘为虚拟机中部分或全部磁盘。
可选地，不同磁盘树分别迁移至对应的目标存储池的过程相互独立。
可选地，快照盘为虚拟机中的磁盘通过打快照操作生成的磁盘。
可选地，磁盘格式为RAW或QCOW2。
本申请第二方面提供了一种多磁盘虚拟机在线迁移到不同存储池的装置，包括：
磁盘树构建模块，将虚拟机每个待迁移的活动状态磁盘以及由每个待迁移的活动状态磁盘对应产生的多个快照盘构建磁盘树，所述每个磁盘树中至少包括由所述待迁移的活动状态磁盘产生的多个快照盘，用于记录磁盘树中多个磁盘的生成时间先后关系；
内存快照文件迁移模块，迁移内存快照文件，将虚拟机引导盘的内存快照文件，迁移到引导盘的目标存储池；其中，引导盘为虚拟机操作系统所在磁盘；
磁盘树迁移模块，确定每个待迁移的活动状态磁盘对应的目标存储池，根据磁盘树中待迁移磁盘的生成时间先后关系，将多个磁盘树分别迁移至对应的目标存储池。
本申请采用的技术方案包括以下技术效果：
1、本申请有效解决由于现有技术造成虚拟机迁移资源利用率以及迁移效率不高的问题，在虚拟机磁盘迁移时，可以根据实际情况将待迁移磁盘迁移至不同的目标存储池，有效的提高了虚拟机迁移的效率以及可靠性。
2、本申请虚拟机磁盘迁移时，可以是虚拟机全部磁盘，也可以是虚拟机部分磁盘，当原虚拟机存储池容量不足，或者存储压力过大时，将虚拟机的多个磁盘中的某一个或者几块盘对应的磁盘树迁移到其它存储池，为虚拟机源存储池腾出空间，减小压力；当虚拟机原存储存在安全隐患，需要迁移到其它存储池，而虚拟机体量过大，无法找到满足的目标存储池时，可以通过本方案进行动态的调度，选择多个目标存储池，进行资源的合理分配，更加灵活。
3、本申请不同磁盘树分别迁移至对应的目标存储池，不同磁盘树的目标存储池不同，在迁移过程中相互独立，互不影响，即使某个磁盘树迁移失败，其他磁盘树依然可以迁移到其他存储池，具有很高的容错性。
4、本申请磁盘树在迁移过程中针对生成时间不是最早的磁盘，可以通过引用链接以及差异数据迁移的方式进行磁盘迁移，保证了磁盘数据的一 致性。
5、本申请磁盘树在创建过程中由待迁移磁盘产生快照盘，每个快照盘都包含着虚拟机打快照时刻的所有数据，并不会相互影响，并且对于没有对应active盘的快照盘，也可以构建磁盘树(磁盘树中仅包括快照盘)，进行磁盘迁移，扩大磁盘迁移的适用场景。
应当理解的是以上的一般描述以及后文的细节描述仅是示例性和解释性的，并不能限制本申请。
附图说明
为了更清楚说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单介绍，显而易见的，对于本领域普通技术人员而言，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请方案中实施例一方法的流程示意图；
图2为本申请方案中实施例一方法步骤S3的一流程示意图；
图3为本申请方案中实施例一方法步骤S3的另一流程示意图；
图4为本申请方案中实施例一中一种可能的磁盘树结构示意图；
图5为本申请方案中实施例二装置的结构示意图。
具体实施方式
为能清楚说明本方案的技术特点，下面通过具体实施方式，并结合其附图，对本申请进行详细阐述。下文的公开提供了许多不同的实施例或例子用来实现本申请的不同结构。为了简化本申请的公开，下文中对特定例子的部件和设置进行描述。此外，本申请可以在不同例子中重复参考数字和/或字母。这种重复是为了简化和清楚的目的，其本身不指示所讨论各种实施例和/或设置之间的关系。应当注意，在附图中所图示的部件不一定按比例绘制。本申请省略了对公知组件和处理技术及工艺的描述以避免不必要地限制本申请。
实施例一
如图1所示，本申请提供了一种多磁盘虚拟机在线迁移到不同存储池的方法，包括：
S1，将虚拟机每个待迁移的活动状态磁盘以及由每个待迁移的活动状态磁盘对应产生的多个快照盘构建磁盘树，所述每个磁盘树中至少包括由所述待迁移的活动状态磁盘产生的多个快照盘，用于记录磁盘树中多个磁盘的生成时间先后关系；
S2，迁移内存快照文件，将虚拟机引导盘的内存快照文件，迁移到引导盘的目标存储池；其中，引导盘为虚拟机操作系统所在磁盘；
S3，确定每个待迁移的活动状态磁盘对应的目标存储池，根据磁盘树中待迁移磁盘的生成时间先后关系，将多个磁盘树分别迁移至对应的目标存储池。
其中，在步骤S1中，磁盘树的数量与待迁移的活动状态磁盘的数量对应相同；磁盘树还包括待迁移的活动状态磁盘。待迁移的活动状态磁盘可以为虚拟机中部分或全部磁盘。快照盘为虚拟机中的磁盘通过打快照操作映射生成的磁盘。当某个活动状态磁盘(active盘)存在时，active盘和快照盘都是对应的，快照盘记录的是active盘在某个时刻的状态，包含对应时刻的所有数据；快照可能没有对应的active盘，比如在打完快照之后把某个active删除了，那么这时快照盘没有对应的active盘，快照盘是独立的，需要构建单独的磁盘树。磁盘格式可以为RAW或QCOW2。
在步骤S2中，迁移内存快照文件，将虚拟机引导盘的内存快照文件，迁移到引导盘的目标存储池；其中，引导盘为虚拟机操作系统所在磁盘；引导盘是活动状态磁盘中的某一个磁盘，每个虚拟机有且仅有一个引导盘，和电脑的C盘类似。
在步骤S3中，如图2-图3所示，具体包括：
S31，确定当前待迁移的磁盘树；
S32，判断当前磁盘树中待迁移的磁盘是否是当前磁盘树中生成时间最早的，如果判断结果为是，则执行步骤S33；如果判断结果为否，则执行步骤S34；
S33，在当前磁盘树对应的目标存储池中预先建立空的卷，将待迁移的磁盘中的数据复制到目标存储池中预先建立空的卷；
S34，根据当前磁盘树中记录的磁盘之间的时间先后关系，确定距离当前磁盘树中的生成时间最早磁盘的下一级待迁移的磁盘，在目标存储池中 通过引用链接方式新建一个磁盘，新建的磁盘与当前待迁移的磁盘之前已经迁移完成的磁盘内容一致，将当前待迁移的磁盘与之前已经迁移完成的磁盘之间的差异数据迁移到目标存储池中新建的磁盘中；
S35，判断当前磁盘树中的磁盘是否全部迁移完毕，如果判断结果为是，则执行步骤S36，如果判断结果为否，则执行步骤S32；
S36，判断所有待迁移的磁盘树是否全部迁移完毕，如果判断结果为是，则执行步骤S37；如果判断结果为否，则执行步骤S31；
S37，虚拟机磁盘迁移完成。
图3中A1、A2、A3、A4、A5为活动状态磁盘(active盘)打快照映射生成的5个快照盘，其中，A1为活动状态磁盘(active盘)打快照映射生成第一个快照盘，A2、A3均为活动状态磁盘(active盘)在快照盘A1基础上，打快照映射生成第二级快照盘，A2、A3中包括A1中的全部数据，A2、A3生成时间顺序可以任意；A4、A5均为活动状态磁盘(active盘)在快照盘A3基础上，打快照映射生成第三级快照盘，A4、A5中包括A3中的全部数据，A4、A5生成时间顺序可以任意；依次类推，上一级别磁盘生成时间早于下一级别磁盘生成时间，具体地，第一级别磁盘生成时间早于第二级别磁盘生成时间，第二级别磁盘生成时间早于第三级别生成时间。在步骤S32中，当前磁盘树中生成时间最早的磁盘即为当前磁盘树中的第一个磁盘，即为快照盘A1。
在步骤S33中，在选定的当前磁盘的目标存储预先创建空volume(卷)，原磁盘的数据将要复制到当前volume中；开启数据迁移端口，准备复制磁盘，将原磁盘的所有数据迁移到预先创建的volume上，通过以卷的形式进行迁移，可以节省存储空间。
在步骤S34中，如果当前待迁移的磁盘，不是磁盘树中生成时间最早的，即不是磁盘树的第一块磁盘，例如磁盘树中的除S1之外的其他磁盘，如A2、A3、A4、A5，以A5为例：
根据磁盘树中记录的磁盘生成时间先后关系，将之前已经迁移完成的对应磁盘即A3，使用reflink(引用链接)方式在磁盘树对应的目标存储池生成一个新的磁盘A5*，S3的数据与A5*保持一致；
将A5与A3的差异数据迁移到A5*，当前时刻A5的数据与A5*已经 保持一致，即磁盘树的当前磁盘A5迁移完毕。
在同一磁盘树中，第一级别磁盘A1首先进行迁移，第二级磁盘A2以及A3分别迁移(A2以及A3可以部分先后)，第三级磁盘A4以及A5分别迁移(A4以及A5可以部分先后)，依次类推，直到同一磁盘树中所有磁盘完成迁移，即磁盘树中处于不同级别的磁盘按照磁盘先后顺序依次进行迁移，同一级别的磁盘迁移顺序可以任意。
使用reflink方式生成一个新的磁盘，再迁移差异数据的方式，相比传统的磁盘的拷贝迁移，不仅节省空间，并且reflink磁盘的速度非常快，也可以节省时间。具体地，reflink出来的磁盘，只是原磁盘的一个索引节点，保留着原磁盘的所有信息，当原磁盘存在时，不占用空间；当原磁盘被删除时，reflink出来的磁盘不受影响，可以独立存在。
进一步地，如图4所示，步骤S3具体包括：
S31，确定当前待迁移的磁盘树；
S32，判断当前磁盘树中待迁移的磁盘是否是当前磁盘树中生成时间最早的，如果判断结果为是，则执行步骤S33；如果判断结果为否，则执行步骤S34；
S33，在当前磁盘树对应的目标存储池中预先建立空的卷，将待迁移的磁盘中的数据复制到目标存储池中预先建立空的卷；
S34，根据当前磁盘树中记录的磁盘之间的时间先后关系，确定距离当前磁盘树中的生成时间最早磁盘的下一级待迁移的磁盘，在目标存储池中通过引用链接方式新建一个磁盘，新建的磁盘与当前待迁移的磁盘之前已经迁移完成的磁盘内容一致，将当前待迁移的磁盘与之前已经迁移完成的磁盘之间的差异数据迁移到目标存储池中新建的磁盘中；
S35，判断待迁移的磁盘是否是活动状态磁盘，如果判断结果为是，则执行步骤S36；如果判断结果为否，则执行步骤S37；
S36，将当前待迁移的活动状态磁盘与之前已经迁移完成的磁盘之间的差异数据与目标存储池中新建的磁盘中的数据进行同步；
S37，判断当前磁盘树中的磁盘是否全部迁移完毕，如果判断结果为是，则执行步骤S38，如果判断结果为否，则执行步骤S32；
S38，判断所有待迁移的磁盘树是否全部迁移完毕，如果判断结果为是， 则执行步骤S39；如果判断结果为否，则执行步骤S31；
S39，虚拟机磁盘迁移完成。
在步骤S36中，由于虚拟机上的业务正在运行，active盘可能时时刻刻都在写数据，就会造成迁移之后磁盘与之前的active盘，数据不一致，此时，将当前待迁移的活动状态磁盘与之前已经迁移完成的磁盘之间的差异数据与目标存储池中新建的磁盘中的数据进行同步即将当前待迁移的活动状态磁盘与目标存储池中新建的磁盘的差异数据同步，保持数据的一致性。
在当前磁盘树迁移过程中，首先，磁盘树中的快照盘进行迁移，最后，在迁移磁盘树中的活动状态磁盘(active盘)，如果活动状态磁盘在虚拟机中已删除，则只需要迁移磁盘树中由原活动状态磁盘映射生成的快照盘即可。
待迁移的活动状态磁盘为虚拟机中部分或全部磁盘。不同磁盘树分别迁移至对应的目标存储池的过程相互独立。
需要说明的是，本方案不同磁盘树的迁移没有先后顺序，谁先迁移或者后迁移都可以，并且每个磁盘树迁移到任意存储池都可以。迁移时先随机选一个先迁移就行；不同磁盘树的目标存储池可以相同，可以不同，但每个磁盘树中的目标存储池必须相同。
本申请技术方案主要应用于ICS(InCloud Sphere，浪潮虚拟化平台)，源存储池以及目标存储池类型可以是NFS、CFS或者本地存储池，也可以是其他类型存储池，本申请在此不做限制。
本申请有效解决由于现有技术造成虚拟机迁移资源利用率以及迁移效率不高的问题，在虚拟机磁盘迁移时，可以根据实际情况将待迁移磁盘迁移至不同的目标存储池，有效的提高了虚拟机迁移的效率以及可靠性。
本申请虚拟机磁盘迁移时，可以是虚拟机全部磁盘，也可以是虚拟机部分磁盘，当原虚拟机存储池容量不足，或者存储压力过大时，将虚拟机的多个磁盘中的某一个或者几块盘对应的磁盘树迁移到其它存储池，为虚拟机源存储池腾出空间，减小压力；当虚拟机原存储存在安全隐患，需要迁移到其它存储池，而虚拟机体量过大，无法找到满足的目标存储池时，可以通过本方案进行动态的调度，选择多个目标存储池，进行资源的合理 分配，更加灵活。
本申请不同磁盘树分别迁移至对应的目标存储池，不同磁盘树的目标存储池不同，在迁移过程中相互独立，互不影响，即使某个磁盘树迁移失败，其他磁盘树依然可以迁移到其他存储池，具有很高的容错性。
本申请磁盘树在迁移过程中针对生成时间不是最早的磁盘，可以通过引用链接以及差异数据迁移的方式进行磁盘迁移，保证了磁盘数据的一致性。
本申请磁盘树在创建过程中由待迁移磁盘产生快照盘，每个快照盘都包含着虚拟机打快照时刻的所有数据，并不会相互影响，并且对于没有对应active盘的快照盘，也可以构建磁盘树(磁盘树中仅包括快照盘)，进行磁盘迁移，扩大磁盘迁移的适用场景。
实施例二
如图5所示，本申请技术方案还提供了一种多磁盘虚拟机在线迁移到不同存储池的装置，包括：
磁盘树构建模块101，将虚拟机每个待迁移的活动状态磁盘以及由每个待迁移的活动状态磁盘对应产生的多个快照盘构建磁盘树，所述每个磁盘树中至少包括由所述待迁移的活动状态磁盘产生的多个快照盘，用于记录磁盘树中多个磁盘的生成时间先后关系；
内存快照文件迁移模块102，迁移内存快照文件，将虚拟机引导盘的内存快照文件，迁移到引导盘的目标存储池；其中，引导盘为虚拟机操作系统所在磁盘；
磁盘树迁移模块103，确定每个待迁移的活动状态磁盘对应的目标存储池，根据磁盘树中待迁移磁盘的生成时间先后关系，将多个磁盘树分别迁移至对应的目标存储池。
本申请有效解决由于现有技术造成虚拟机迁移资源利用率以及迁移效率不高的问题，在虚拟机磁盘迁移时，可以根据实际情况将待迁移磁盘迁移至不同的目标存储池，有效的提高了虚拟机迁移的效率以及可靠性。
本申请虚拟机磁盘迁移时，可以是虚拟机全部磁盘，也可以是虚拟机部分磁盘，当原虚拟机存储池容量不足，或者存储压力过大时，将虚拟机的多个磁盘中的某一个或者几块盘对应的磁盘树迁移到其它存储池，为虚 拟机源存储池腾出空间，减小压力；当虚拟机原存储存在安全隐患，需要迁移到其它存储池，而虚拟机体量过大，无法找到满足的目标存储池时，可以通过本方案进行动态的调度，选择多个目标存储池，进行资源的合理分配，更加灵活。
本申请不同磁盘树分别迁移至对应的目标存储池，不同磁盘树的目标存储池不同，在迁移过程中相互独立，互不影响，即使某个磁盘树迁移失败，其他磁盘树依然可以迁移到其他存储池，具有很高的容错性。
本申请磁盘树在迁移过程中针对生成时间不是最早的磁盘，可以通过引用链接以及差异数据迁移的方式进行磁盘迁移，保证了磁盘数据的一致性。
本申请磁盘树在创建过程中由待迁移磁盘产生快照盘，每个快照盘都包含着虚拟机打快照时刻的所有数据，并不会相互影响，并且对于没有对应active盘的快照盘，也可以构建磁盘树(磁盘树中仅包括快照盘)，进行磁盘迁移，扩大磁盘迁移的适用场景。
上述虽然结合附图对本申请的具体实施方式进行了描述，但并非对本申请保护范围的限制，所属领域技术人员应该明白，在本申请的技术方案的基础上，本领域技术人员不需要付出创造性劳动即可做出的各种修改或变形仍在本申请的保护范围以内。

Claims (10)

  1. 一种多磁盘虚拟机在线迁移到不同存储池的方法，其特征是，包括：
    将虚拟机每个待迁移的活动状态磁盘以及由每个待迁移的活动状态磁盘对应产生的多个快照盘构建磁盘树，所述每个磁盘树中至少包括由所述待迁移的活动状态磁盘产生的多个快照盘，用于记录磁盘树中多个磁盘的生成时间先后关系；
    迁移内存快照文件，将虚拟机引导盘的内存快照文件，迁移到引导盘的目标存储池；其中，引导盘为虚拟机操作系统所在磁盘；
    确定每个待迁移的活动状态磁盘对应的目标存储池，根据磁盘树中待迁移磁盘的生成时间先后关系，将多个磁盘树分别迁移至对应的目标存储池。
  2. 根据权利要求1所述的多磁盘虚拟机在线迁移到不同存储池的方法，其特征是，磁盘树的数量与待迁移的活动状态磁盘的数量对应相同。
  3. 根据权利要求1所述的多磁盘虚拟机在线迁移到不同存储池的方法，其特征是，所述磁盘树还包括待迁移的活动状态磁盘。
  4. 根据权利要求1所述的多磁盘虚拟机在线迁移到不同存储池的方法，其特征是，根据磁盘树中待迁移的活动状态磁盘以及多个快照盘的生成时间先后关系，将多个磁盘树分别迁移至对应的目标存储池具体包括：
    确定当前待迁移的磁盘树；
    判断当前磁盘树中待迁移的磁盘是否是当前磁盘树中生成时间最早的，如果是当前磁盘树中的生成时间最早的磁盘，在所述当前磁盘树对应的目标存储池中预先建立空的卷，将待迁移的磁盘中的数据复制到目标存储池中预先建立空的卷；
    如果不是当前磁盘树中的生成时间最早的磁盘，则根据当前磁盘树中记录的磁盘之间的时间先后关系，确定距离当前磁盘树中的生成时间最早磁盘的下一级待迁移的磁盘，在目标存储池中通过引用链接方式新建一个磁盘，新建的磁盘与当前待迁移的磁盘之前已经迁移完成的磁盘内容一致，将当前待迁移的磁盘与之前已经迁移完成的磁盘之间的差异数据迁移到目标存储池中新建的磁盘中；
    直至当前磁盘树中待迁移的磁盘以及所有待迁移的磁盘树全部迁移完 成。
  5. 根据权利要求4所述的多磁盘虚拟机在线迁移到不同存储池的方法，其特征是，直至当前磁盘树中待迁移的磁盘以及所有待迁移的磁盘树全部迁移完成之前还包括：判断待迁移的磁盘是否是活动状态磁盘，如果是活动状态磁盘，将当前待迁移的活动状态磁盘与之前已经迁移完成的磁盘之间的差异数据与目标存储池中新建的磁盘中的数据进行同步。
  6. 根据权利要求1所述的多磁盘虚拟机在线迁移到不同存储池的方法，其特征是，待迁移的活动状态磁盘为虚拟机中部分或全部磁盘。
  7. 根据权利要求1所述的多磁盘虚拟机在线迁移到不同存储池的方法，其特征是，不同磁盘树分别迁移至对应的目标存储池的过程相互独立。
  8. 根据权利要求1所述的多磁盘虚拟机在线迁移到不同存储池的方法，其特征是，快照盘为虚拟机中的磁盘通过打快照操作生成的磁盘。
  9. 根据权利要求1-8任一所述的多磁盘虚拟机在线迁移到不同存储池的方法，其特征是，磁盘格式为RAW或QCOW2。
  10. 一种多磁盘虚拟机在线迁移到不同存储池的装置，其特征是，包括：
    磁盘树构建模块，将虚拟机每个待迁移的活动状态磁盘以及由每个待迁移的活动状态磁盘对应产生的多个快照盘构建磁盘树，所述每个磁盘树中至少包括由所述待迁移的活动状态磁盘产生的多个快照盘，用于记录磁盘树中多个磁盘的生成时间先后关系；
    内存快照文件迁移模块，迁移内存快照文件，将虚拟机引导盘的内存快照文件，迁移到引导盘的目标存储池；其中，引导盘为虚拟机操作系统所在磁盘；
    磁盘树迁移模块，确定每个待迁移的活动状态磁盘对应的目标存储池，根据磁盘树中待迁移磁盘的生成时间先后关系，将多个磁盘树分别迁移至对应的目标存储池。
PCT/CN2021/076954 2020-07-30 2021-02-19 一种多磁盘虚拟机在线迁移到不同存储池的方法及装置 WO2022021856A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/016,998 US11740925B2 (en) 2020-07-30 2021-02-19 Method and apparatus for online migration of multi-disk virtual machine into different storage pools

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010748839.9A CN111984370B (zh) 2020-07-30 2020-07-30 一种多磁盘虚拟机在线迁移到不同存储池的方法及装置
CN202010748839.9 2020-07-30

Publications (1)

Publication Number Publication Date
WO2022021856A1 true WO2022021856A1 (zh) 2022-02-03

Family

ID=73445868

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/076954 WO2022021856A1 (zh) 2020-07-30 2021-02-19 一种多磁盘虚拟机在线迁移到不同存储池的方法及装置

Country Status (3)

Country Link
US (1) US11740925B2 (zh)
CN (1) CN111984370B (zh)
WO (1) WO2022021856A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117093332A (zh) * 2023-10-20 2023-11-21 杭州优云科技有限公司 一种虚拟机克隆的实现方法和装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111984370B (zh) * 2020-07-30 2022-10-25 苏州浪潮智能科技有限公司 一种多磁盘虚拟机在线迁移到不同存储池的方法及装置
CN112988066B (zh) * 2021-02-23 2022-08-30 新华三大数据技术有限公司 一种数据处理方法及装置
CN114138197B (zh) * 2021-11-28 2022-10-18 北京大道云行科技有限公司 一种在线跨池数据迁移方法及电子设备
CN114895849B (zh) * 2022-04-29 2024-11-01 重庆紫光华山智安科技有限公司 数据迁移存储方法、装置和管理节点

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120110237A1 (en) * 2009-12-01 2012-05-03 Bin Li Method, apparatus, and system for online migrating from physical machine to virtual machine
CN105739918A (zh) * 2016-01-07 2016-07-06 杭州华三通信技术有限公司 虚拟机的存储在线迁移方法及装置
CN110688200A (zh) * 2019-09-29 2020-01-14 北京浪潮数据技术有限公司 一种在线迁移虚拟机磁盘树的方法及装置
CN110941476A (zh) * 2019-11-14 2020-03-31 济南浪潮数据技术有限公司 一种虚拟机热迁移的控制方法、控制装置及控制设备
CN111090399A (zh) * 2019-12-13 2020-05-01 北京浪潮数据技术有限公司 一种磁盘数据的在线迁移方法、装置、设备及介质
CN111984370A (zh) * 2020-07-30 2020-11-24 苏州浪潮智能科技有限公司 一种多磁盘虚拟机在线迁移到不同存储池的方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5455723A (en) * 1994-06-02 1995-10-03 International Business Machines Corporation Method and apparatus for ramp load and unload
US10809935B2 (en) * 2018-12-17 2020-10-20 Vmware, Inc. System and method for migrating tree structures with virtual disks between computing environments

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120110237A1 (en) * 2009-12-01 2012-05-03 Bin Li Method, apparatus, and system for online migrating from physical machine to virtual machine
CN105739918A (zh) * 2016-01-07 2016-07-06 杭州华三通信技术有限公司 虚拟机的存储在线迁移方法及装置
CN110688200A (zh) * 2019-09-29 2020-01-14 北京浪潮数据技术有限公司 一种在线迁移虚拟机磁盘树的方法及装置
CN110941476A (zh) * 2019-11-14 2020-03-31 济南浪潮数据技术有限公司 一种虚拟机热迁移的控制方法、控制装置及控制设备
CN111090399A (zh) * 2019-12-13 2020-05-01 北京浪潮数据技术有限公司 一种磁盘数据的在线迁移方法、装置、设备及介质
CN111984370A (zh) * 2020-07-30 2020-11-24 苏州浪潮智能科技有限公司 一种多磁盘虚拟机在线迁移到不同存储池的方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117093332A (zh) * 2023-10-20 2023-11-21 杭州优云科技有限公司 一种虚拟机克隆的实现方法和装置
CN117093332B (zh) * 2023-10-20 2024-02-27 杭州优云科技有限公司 一种虚拟机克隆的实现方法和装置

Also Published As

Publication number Publication date
US20230214250A1 (en) 2023-07-06
US11740925B2 (en) 2023-08-29
CN111984370B (zh) 2022-10-25
CN111984370A (zh) 2020-11-24

Similar Documents

Publication Publication Date Title
WO2022021856A1 (zh) 一种多磁盘虚拟机在线迁移到不同存储池的方法及装置
CN104506589B (zh) 一种基于超融合存储的资源迁移调度方法
EP3138010B1 (en) System and method for optimized signature comparisons and data replication
US9558194B1 (en) Scalable object store
US9116737B2 (en) Conversion of virtual disk snapshots between redo and copy-on-write technologies
CN101398770B (zh) 迁移一个或多个虚拟机的系统和方法
CN104216801B (zh) 一种面向虚拟化环境的数据复制方法及系统
WO2023197670A1 (zh) 一种分布式存储系统控制方法、装置及可读存储介质
US10353872B2 (en) Method and apparatus for conversion of virtual machine formats utilizing deduplication metadata
CN105022656B (zh) 虚拟机快照管理方法和装置
CN109408115B (zh) 一种基于容器环境中迁移对象的方法及计算系统
CN101945131B (zh) 一种基于存储虚拟化的数据迁移方法
CN110046026B (zh) 云主机指定虚拟磁盘限速方法、计算设备及云平台
CN103491144A (zh) 一种广域网虚拟平台的构建方法
WO2019061352A1 (zh) 数据加载方法及装置
US11199972B2 (en) Information processing system and volume allocation method
CN113032356B (zh) 一种客舱分布式文件存储系统及实现方法
CN113849137B (zh) 一种面向申威容器平台的可视化块存储方法和系统
CN106469117A (zh) 一种用于虚拟机存储迁移的存储资源管理方法及装置
CN113806300B (zh) 数据存储方法、系统、装置、设备及存储介质
CN110825543B (zh) 在故障存储设备上快速恢复数据的方法
CN109933312A (zh) 一种有效降低容器化关系型数据库i/o消耗的方法
US10558373B1 (en) Scalable index store
CN112328697A (zh) 一种基于大数据的数据同步方法
US10169343B2 (en) Deferring the cost of virtual storage

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: 21851011

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21851011

Country of ref document: EP

Kind code of ref document: A1