CN106484312A - A kind of magnetic disk of virtual machine data migration method and device - Google Patents

A kind of magnetic disk of virtual machine data migration method and device Download PDF

Info

Publication number
CN106484312A
CN106484312A CN201510552927.0A CN201510552927A CN106484312A CN 106484312 A CN106484312 A CN 106484312A CN 201510552927 A CN201510552927 A CN 201510552927A CN 106484312 A CN106484312 A CN 106484312A
Authority
CN
China
Prior art keywords
data
disk
virtual machine
machine
magnetic disk
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.)
Granted
Application number
CN201510552927.0A
Other languages
Chinese (zh)
Other versions
CN106484312B (en
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.)
Zhuhai Jinshan Cloud Technology Co., Ltd.
Beijing Kingsoft Cloud Network Technology Co Ltd
Beijing Kingsoft Cloud Technology Co Ltd
Original Assignee
Beijing Kingsoft Cloud Network Technology Co Ltd
Beijing Kingsoft Cloud Technology 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 Kingsoft Cloud Network Technology Co Ltd, Beijing Kingsoft Cloud Technology Co Ltd filed Critical Beijing Kingsoft Cloud Network Technology Co Ltd
Priority to CN201510552927.0A priority Critical patent/CN106484312B/en
Publication of CN106484312A publication Critical patent/CN106484312A/en
Application granted granted Critical
Publication of CN106484312B publication Critical patent/CN106484312B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Abstract

The embodiment of the invention discloses a kind of magnetic disk of virtual machine data migration method and device, it is related to field of computer technology, is applied to virtual machine, wherein, said method includes：Reception of magnetic disc Data Migration instructs, data in magnetic disk migration instruction in comprise to have moved to target physical machine described virtual machine Disk Backup data information, the Disk Backup data storage of described virtual machine is in the backup physical machine that physical machine corresponding with described virtual machine differs；Determine and generate the disk incremental data for this Disk Backup data producing of having moved to the Disk Backup data of the described virtual machine of described target physical machine；Will determined by disk incremental data migrate to described target physical machine so that described target physical machine according to determined by disk incremental data and have moved Disk Backup data acquisition described virtual machine whole data in magnetic disk.Apply scheme provided in an embodiment of the present invention, shorten the impact duration to user operation virtual machine for the magnetic disk of virtual machine Data Migration.

Description

A kind of magnetic disk of virtual machine data migration method and device
Technical field
The present invention relates to field of computer technology, particularly to a kind of magnetic disk of virtual machine data migration method and dress Put.
Background technology
Fast development recently as cloud computing technology is so that virtual machine technique has obtained more widely should With.In practical application, the demand of virtual hard disk, memory source is changed due to user, virtual machine The impact of the factors such as corresponding physical machine fault is it may be desirable to by the data in magnetic disk of virtual machine from present physical Machine migrates to the situation of other physical machine.
In prior art, during the data in magnetic disk of migration virtual machine, it is corresponding that virtual machine typically directly passes through it The I/O resource of physical machine sends its data in magnetic disk to target physical machine, until being sent completely the whole of virtual machine Data in magnetic disk.But it is generally the case that the data in magnetic disk amount of virtual machine is larger, sending out to target physical machine During sending the data in magnetic disk of whole virtual machine, the I/O resource of physical machine corresponding to this virtual machine can by long when Between take, so not only operation to current virtual machine for president's time effects user, or even president's time effects The operation of user couple other virtual machines corresponding with above-mentioned physical machine, Consumer's Experience is poor.
Content of the invention
The embodiment of the invention discloses a kind of magnetic disk of virtual machine data migration method and device, to shorten virtual machine The impact duration to user operation virtual machine for the data in magnetic disk migration, improves Consumer's Experience.
For reaching above-mentioned purpose, the embodiment of the invention discloses a kind of magnetic disk of virtual machine data migration method, should For virtual machine, methods described includes：
Reception of magnetic disc Data Migration instructs, and wherein, comprises to have moved to mesh in described data in magnetic disk migration instruction The information of the Disk Backup data of described virtual machine of mark physical machine, the Disk Backup data of described virtual machine is deposited It is stored in the backup physical machine that physical machine corresponding with described virtual machine differs；
Determine and generate generation of having moved to the Disk Backup data of the described virtual machine of described target physical machine Disk incremental data for this Disk Backup data；
Disk incremental data determined by inciting somebody to action migrates to described target physical machine, so that described target physical machine According to determined by disk incremental data and the Disk Backup data had moved obtain whole magnetic of described virtual machine Disk data.
In a kind of specific implementation of the present invention, described have moved to the described void of described target physical machine The Disk Backup data of plan machine is：To the Disk Backup data moment starting to migrate described virtual machine, use Latest edition in the described virtual machine storing storage in the backup physical machine of Disk Backup data of described virtual machine This Disk Backup data.
In a kind of specific implementation of the present invention, described magnetic disk of virtual machine data migration method also includes：
Receive the data modification operation instruction of the data in magnetic disk for described virtual machine；
Change the data in magnetic disk of described virtual machine；
Instructed according to described data modification operation, update the data modification record of described virtual machine.
In a kind of specific implementation of the present invention, described data modification record includes：According to described number According to modification operational order, the data block identifier of the data in magnetic disk of described virtual machine being modified；
Described determination generates product of having moved to the Disk Backup data of the described virtual machine of described target physical machine The raw disk incremental data for this Disk Backup data, including：
According to described data modification record, determine to generate and have moved to the described virtual machine of described target physical machine Disk Backup data after the data block identifier of the data in magnetic disk of described virtual machine that is modified；
According to the data block identifier finding, obtain the block content of data block corresponding with above-mentioned mark, and will Its disk incremental data for this Disk Backup data producing after being defined as generating above-mentioned Disk Backup data.
In a kind of specific implementation of the present invention, described according to described data modification record, determine and generate Have moved the described virtual machine being modified to the Disk Backup data of the described virtual machine of described target physical machine Data in magnetic disk data block identifier, including：
According to described data modification record, obtain and have moved to the described void of described target physical machine for generating The data bitmap of data in magnetic disk after the Disk Backup data of plan machine, wherein, described one mark of data bit in figure Position, generates, for representing, the institute to the Disk Backup data of the described virtual machine of described target physical machine that has moved Whether a data block stating the data in magnetic disk of virtual machine is modified；
Search described data bit in figure and represent the flag that data block has been modified；
Determine the corresponding data block identifier of flag finding.
In a kind of specific implementation of the present invention, described data modification operation instruction includes：Change The data in magnetic disk of described virtual machine data block identifier；
The described data modification record being instructed according to described data modification operation, updating described virtual machine, including：
Detect whether to have existed in the data modification record of described virtual machine in described data modification operation instruction and wrap The data block identifier of the data in magnetic disk of described virtual machine to be changed including；
If including, the above-mentioned data block identifier being included according to the instruction of described data modification operation, update described Data modification record.
In a kind of specific implementation of the present invention, described data modification record includes：According to described number According to modification operational order, the data block identifier of the data in magnetic disk of described virtual machine being modified and this data block Modification content；
Described determination generates product of having moved to the Disk Backup data of the described virtual machine of described target physical machine The raw disk incremental data for this Disk Backup data, including：
Search from described data modification record and generate the described virtual machine having moved to described target physical machine The data block identifier of the data in magnetic disk of described virtual machine being modified after Disk Backup data；
According to the data block identifier finding, obtain corresponding with above-mentioned mark from described data modification record The modification content of data block, and be defined as generating the described virtual machine having moved to described target physical machine Disk Backup data after produce the disk incremental data for this Disk Backup data.
In a kind of specific implementation of the present invention, described magnetic disk of virtual machine data migration method also includes：
During disk incremental data determined by inciting somebody to action migrates to described target physical machine, detect described void Whether the data in magnetic disk of plan machine is modified；
If it is, disk incremental data determined by updating.
For reaching above-mentioned purpose, the embodiment of the invention discloses a kind of magnetic disk of virtual machine data migration device, should For virtual machine, described device includes：
Command reception module, for the instruction of reception of magnetic disc Data Migration, wherein, described data in magnetic disk migration refers to Comprise in order to have moved to target physical machine described virtual machine Disk Backup data information, described virtual The Disk Backup data storage of machine is in the backup physical machine that physical machine corresponding with described virtual machine differs；
Disk incremental data determining module, has moved to the described void of described target physical machine for determining to generate The disk incremental data for this Disk Backup data producing after the Disk Backup data of plan machine；
Disk incremental data transferring module, migrates to described object for disk incremental data determined by general Reason machine so that described target physical machine according to determined by disk incremental data and the Disk Backup had moved Data obtains whole data in magnetic disk of described virtual machine.
In a kind of specific implementation of the present invention, described have moved to the described void of described target physical machine The Disk Backup data of plan machine is：To the Disk Backup data moment starting to migrate described virtual machine, use Latest edition in the described virtual machine storing storage in the backup physical machine of Disk Backup data of described virtual machine This Disk Backup data.
In a kind of specific implementation of the present invention, described command reception module, it is additionally operable to receive for institute State the data modification operation instruction of the data in magnetic disk of virtual machine；
Described device also includes：
Data in magnetic disk modified module, for changing the data in magnetic disk of described virtual machine；
Modification record update module, for instructing according to described data modification operation, updates described virtual machine Data modification record.
In a kind of specific implementation of the present invention, described data modification record includes：According to described number According to modification operational order, the data block identifier of the data in magnetic disk of described virtual machine being modified；
Described disk incremental data determining module, including：
Data block identifier determination sub-module, for according to described data modification record, determine generation have moved to The disk number of the described virtual machine being modified after the Disk Backup data of the described virtual machine of described target physical machine According to data block identifier；
First disk incremental data determination sub-module, for according to the data block identifier that finds, obtain with upper State the block content identifying corresponding data block, and produce after being defined as generating above-mentioned Disk Backup data Disk incremental data for this Disk Backup data.
In a kind of specific implementation of the present invention, described data block identifier determination sub-module, including：
Data bitmap obtaining unit, for according to described data modification record, obtain for generation have moved to The data bitmap of data in magnetic disk after the Disk Backup data of the described virtual machine of described target physical machine, wherein, Described one flag of data bit in figure, has moved to the described void of described target physical machine for representing to generate After the Disk Backup data of plan machine, whether a data block of the data in magnetic disk of described virtual machine is modified；
Flag searching unit, represents, for searching described data bit in figure, the flag that data block has been modified；
Data block identifier determining unit, for determining the corresponding data block identifier of flag finding.
In a kind of specific implementation of the present invention, described data modification operation instruction includes：Change The data in magnetic disk of described virtual machine data block identifier；
Described modification record update module, including：
Data block identifier detection sub-module, for detecting in the data modification record of described virtual machine whether deposit The data block mark of the data in magnetic disk of the described virtual machine to be changed including in the instruction of described data modification operation Know；
Modification record updates submodule, is yes for the testing result in described data block identifier detection sub-module In the case of, the above-mentioned data block identifier including is instructed according to described data modification operation, updates described number According to modification record.
In a kind of specific implementation of the present invention, described data modification record includes：According to described number According to modification operational order, the data block identifier of the data in magnetic disk of described virtual machine being modified and this data block Modification content；
Described disk incremental data determining module, including：
Data block identifier searches submodule, has moved to institute for searching generation from described data modification record The data in magnetic disk of the described virtual machine being modified after stating the Disk Backup data of the described virtual machine of target physical machine Data block identifier；
Second disk incremental data determination sub-module, for according to the data block identifier finding, from described number According to the modification content obtaining data block corresponding with above-mentioned mark in modification record, and it is defined as generating Migrate to the Disk Backup data of the described virtual machine of described target physical machine produce for this Disk Backup The disk incremental data of data.
In a kind of specific implementation of the present invention, described magnetic disk of virtual machine data migration device also includes：
Data modification detection module, for migrating to described target physical in disk incremental data determined by general During machine, detect whether the data in magnetic disk of described virtual machine is modified；
Disk incremental data update module, is yes for the testing result in described data modification detection module In the case of, disk incremental data determined by renewal.
As seen from the above, in scheme provided in an embodiment of the present invention, first migrate the Disk Backup data of virtual machine To target physical machine, then migrate produce after virtual machine generates this Disk Backup data standby for this disk again The disk incremental data of number evidence is to target physical machine so that target physical machine can be standby according to above-mentioned disk Number evidence and disk incremental data obtain whole data in magnetic disk of this virtual machine.Because the embodiment of the present invention provides Scheme in, above-mentioned Disk Backup data storage is in the backup physics different from the corresponding physical machine of virtual machine In machine, so, the corresponding thing of virtual machine will not be taken when migrating this Disk Backup data to target physical machine The I/O resource of reason machine, also would not affect user operation virtual machine.In addition, though moving to target physical machine The I/O resource of the corresponding physical machine of virtual machine can be taken, impact is used during moving above-mentioned disk incremental data Family operates virtual machine, but because above-mentioned disk incremental data is compared to whole data in magnetic disk of virtual machine Speech is much smaller, so, during to the target physical machine above-mentioned disk incremental data of migration, to user operation virtual machine Influence time shorter.Comprehensive visible above, apply scheme provided in an embodiment of the present invention, void can be shortened The impact duration to user operation virtual machine for the plan machine data in magnetic disk migration, improves Consumer's Experience.
Brief description
In order to be illustrated more clearly that the embodiment of the present invention or technical scheme of the prior art, below will be to enforcement Example or description of the prior art in required use accompanying drawing be briefly described it should be apparent that, below describe In accompanying drawing be only some embodiments of the present invention, for those of ordinary skill in the art, do not paying On the premise of going out creative work, other accompanying drawings can also be obtained according to these accompanying drawings.
Fig. 1 is the first schematic flow sheet of magnetic disk of virtual machine data migration method provided in an embodiment of the present invention；
Fig. 2 is a kind of structural representation of magnetic disk of virtual machine migratory system provided in an embodiment of the present invention；
Fig. 3 is the second schematic flow sheet of magnetic disk of virtual machine data migration method provided in an embodiment of the present invention；
Fig. 4 is the third schematic flow sheet of magnetic disk of virtual machine data migration method provided in an embodiment of the present invention；
Fig. 5 is the first structural representation of magnetic disk of virtual machine data migration device provided in an embodiment of the present invention；
Fig. 6 is the second structural representation of magnetic disk of virtual machine data migration device provided in an embodiment of the present invention；
Fig. 7 is the third structural representation of magnetic disk of virtual machine data migration device provided in an embodiment of the present invention.
Specific embodiment
Due in prior art to target physical machine migrate virtual machine data in magnetic disk when, can for a long time take should The I/O resource of the corresponding physical machine of virtual machine, and then the operation to this virtual machine for the president time effects user, be This, embodiments provide a kind of magnetic disk of virtual machine data migration method and device, to shorten virtual machine The impact duration to user operation virtual machine for the data in magnetic disk migration.
Introduce a kind of magnetic disk of virtual machine data migration method provided in an embodiment of the present invention first below on the whole, The method is applied to virtual machine, including：
Reception of magnetic disc Data Migration instructs, and wherein, comprises to have moved to mesh in described data in magnetic disk migration instruction The information of the Disk Backup data of described virtual machine of mark physical machine, the Disk Backup data of described virtual machine is deposited It is stored in the backup physical machine that physical machine corresponding with described virtual machine differs；
Determine and generate generation of having moved to the Disk Backup data of the described virtual machine of described target physical machine Disk incremental data for this Disk Backup data；
Disk incremental data determined by inciting somebody to action migrates to described target physical machine, so that described target physical machine According to determined by disk incremental data and the Disk Backup data had moved obtain whole magnetic of described virtual machine Disk data.
The Disk Backup data of above-mentioned virtual machine is for a certain moment it can be understood as at certain for the moment Inscribe the copy of whole data in magnetic disk of virtual machine.
The disk incremental data of virtual machine is for a certain Disk Backup data, for recording virtual machine After generating this Disk Backup data, user's modification situation on a virtual machine, for example, increase in data in magnetic disk Plus content, the content deleted, the content etc. changing.
Whole data in magnetic disk of virtual machine can be according to the Disk Backup data of virtual machine and this Disk Backup data Corresponding disk incremental data obtains.
In view of foregoing description, during the data in magnetic disk of migration virtual machine, two parts can be divided to carry out, that is,：First will The Disk Backup Data Migration being stored in backup physical machine is somebody's turn to do to target physical machine, then to the migration of target physical machine Disk Backup data corresponding disk incremental data, completes the migration of the whole data in magnetic disk of virtual machine whereby.
Because the Disk Backup data storage of above-mentioned virtual machine is in different from the corresponding physical machine of this virtual machine standby In part physical machine, so, migrate to target physical machine this virtual machine Disk Backup data when, shared I/O resource is the I/O resource of backup physical machine, rather than the I/O resource of the corresponding physical machine of this virtual machine, enters And the process of the Disk Backup data of this virtual machine is migrated to target physical machine, do not interfere with this void of user operation Plan machine.
The corresponding disk incremental data of above-mentioned Disk Backup data is stored in above-mentioned virtual machine, further Be stored in the corresponding physical machine of above-mentioned virtual machine, so, increase to the target physical machine above-mentioned disk of migration During amount data, shared I/O resource is the I/O resource of the corresponding physical machine of above-mentioned virtual machine, and then to mesh Mark physical machine migrates the process of above-mentioned disk incremental data, can affect this virtual machine of user operation.
But for the data volume of whole data in magnetic disk of virtual machine, for the magnetic of Disk Backup data The data volume of disk incremental data is much smaller, and therefore, applies above-mentioned magnetic disk of virtual machine data migration method to enter During row migration data in magnetic disk, the impact duration to user operation virtual machine can be shortened.
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is carried out clearly Chu, it is fully described by it is clear that described embodiment is only a part of embodiment of the present invention, rather than Whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art are not making creation Property work under the premise of the every other embodiment that obtained, broadly fall into the scope of protection of the invention.
Fig. 1 is the first schematic flow sheet of magnetic disk of virtual machine data migration method provided in an embodiment of the present invention, The method is applied in virtual machine, including：
S101：Reception of magnetic disc Data Migration instructs.
Wherein, comprise to have moved in above-mentioned data in magnetic disk migration instruction to the above-mentioned virtual machine of target physical machine The information of Disk Backup data, specifically, in the information of Disk Backup data of above-mentioned virtual machine, can wrap Include for representing that this Disk Backup data has moved the mark completing, the version of this Disk Backup data can be comprised This information, can comprise mark of target physical machine etc., the application is not defined to this.
What deserves to be explained is, the Disk Backup data of above-mentioned virtual machine need to be stored in thing corresponding with this virtual machine In the backup physical machine that reason machine differs, so in the Disk Backup migrating above-mentioned virtual machine to target physical machine During data, shared I/O resource is the I/O resource of backup physical machine, rather than the corresponding thing of above-mentioned virtual machine The I/O resource of reason machine, therefore, during the Disk Backup data migrating above-mentioned virtual machine, will not be due to The I/O resource of physical machine is occupied and affects the operation to this virtual machine for the user, does not also interfere with user to this void The operation of other virtual machines corresponding to the corresponding physical machine of plan machine.
From foregoing description it is known that above-mentioned virtual machine is to complete to migrate to target physical machine in backup physical machine The data in magnetic disk migration instruction just receiving after the Disk Backup data of virtual machine, is easier to expect, The instruction of this Data Migration can be above-mentioned backup physical machine transmission or one there is management function Physical machine is after determination backup physical machine has completed the migration of above-mentioned magnetic disk of virtual machine Backup Data to above-mentioned void Plan machine sends.
Those skilled in the art it is understood that generate virtual machine Disk Backup data be in order to When corresponding physical machine of virtual machine etc. breaks down, it is capable of the disk of this virtual machine of error recovery to try one's best little Data to current state, so, under normal circumstances virtual machine can fixed time intervals interval, for example, 6 hours, 12 hours etc., or meet pre-conditioned in the case of, for example, the corresponding physics of virtual machine is detected Situation of fluctuation of service etc. in machine, triggers Disk data backup function, generates the magnetic for current time Disk Backup Data, for ensureing Disk Backup data safety, in practical application, virtual machine can be by the disk being generated Backup Data sends to above-mentioned backup physical machine.As time goes on, may in above-mentioned backup physical machine Can there is the Disk Backup data of multiple versions of above-mentioned virtual machine.
Preferably, the above-mentioned Disk Backup data of above-mentioned virtual machine had moved to target physical machine can be： To the Disk Backup data moment starting to migrate above-mentioned virtual machine, for storing the disk of above-mentioned virtual machine The latest edition Disk Backup data of the above-mentioned virtual machine of storage in the backup physical machine of Backup Data.So, The data volume being stored in the disk incremental data for this Disk Backup data in above-mentioned virtual machine can be relatively Little, the time needing during migration disk incremental data is shorter, and then when above-mentioned virtual machine is carried out with disk migration The duration of impact user operation virtual machine is also just shorter.
S102：Determine and generate generation of having moved to the Disk Backup data of the above-mentioned virtual machine of target physical machine The disk incremental data for this Disk Backup data.
Whole data in magnetic disk due to above-mentioned virtual machine are located in the corresponding physical machine of this virtual machine, and generate void The Disk Backup data of plan machine needs whole data in magnetic disk of this virtual machine, so, under normal circumstances by above-mentioned Virtual machine generates its Disk Backup data and has higher work efficiency.
Specifically, when above-mentioned virtual machine generates its Disk Backup data, can be according to default time interval Generate, can also generate in the case of default condition detecting to meet, for example, detect and have Disk Backup data genaration instruction that the physical machine of management function sends, the selected disk of user is detected standby Part data genaration instructs, this virtual machine corresponding physical machine operation exception etc. is detected.
Those skilled in the art are it is understood that virtual machine can account for when generating its Disk Backup data With system resource, therefore, for preventing from affecting user operation virtual machine, virtual machine can not operated in user Disk Backup data is generated in period.
In the present embodiment, for preventing during the Disk Backup data migrating virtual machine to target physical machine because occupancy should The I/O resource of the corresponding physical machine of virtual machine and affect user operation virtual machine, generate its disk in this virtual machine After Backup Data, the Disk Backup being generated data is activation can be stored to backing up physical machine.In addition, The Disk Backup being generated data storage can also effectively be prevented the mistake to virtual machine for the user to backing up physical machine Damage of Disk Backup data operating and bringing etc..
It should be understood that virtual machine can take when sending, to backup physical machine, the Disk Backup data that it is generated The I/O resource of the corresponding physical machine of this virtual machine, therefore, during this period can the operation to this virtual machine for the user, The operation of user couple other virtual machines corresponding with the corresponding physical machine of this virtual machine even can be affected, in view of This, for ensureing Consumer's Experience, can select in the case that user does not operate this virtual machine to backup physical machine Send generated Disk Backup data.
It is well known that the data in magnetic disk of virtual machine can be divided into multiple data blocks, user is to virtual machine magnetic The operation of disk data is it can be understood as the operation of each data block to magnetic disk of virtual machine data.
Specifically, in the case of one kind, can include in the content that above-mentioned disk incremental data is recorded：Send out The information such as the data block identifier of the data block of changing and block content；
In the case of another kind, can include in the content that above-mentioned disk incremental data is recorded：Change The data block identifier of data block and modification content etc. information.
Two kinds of situations of the above-mentioned disk incremental data simply enumerated, are not that the application is defined.
In addition, the disk incremental data of virtual machine can store in one file it is also possible to for disk standby Number according to storing respectively, that is,：In each file, only record virtual machine generates a Disk Backup data and generation The information of the disk incremental data generating between next Disk Backup data.Certainly, the application be more than Illustrate as a example stating, in practical application, also there is the storage mode of other disk incremental datas, can basis Concrete condition determines.
S103：Disk incremental data determined by inciting somebody to action migrates to described target physical machine, so that target physical Machine according to determined by disk incremental data and the Disk Backup data had moved obtain the whole of above-mentioned virtual machine Data in magnetic disk.
By above description it is known that the information that under different situations, disk incremental data is comprised may be different, So, target physical machine, after the Disk Backup data obtaining above-mentioned virtual machine and disk incremental data, obtains The mode slightly difference of whole data in magnetic disk of this virtual machine, specifically may refer to shown in Fig. 3 and Fig. 4 below Embodiment, I will not elaborate.
Those skilled in the art are it is understood that above-mentioned virtual machine is migrating its magnetic to target physical machine During disk incremental data, user may operate to this virtual machine, then in this case needs to record The operation to this virtual machine for the lower user, so that target physical machine is obtained in that whole disk numbers of this virtual machine According to.
In view of foregoing description, in a preferred embodiment of the present invention, above-mentioned magnetic disk of virtual machine data is moved Shifting method can also include：
During disk incremental data determined by inciting somebody to action migrates to target physical machine, detect above-mentioned virtual machine Data in magnetic disk whether be modified, if being modified, update determined by disk incremental data.
In practical application, if above-mentioned virtual machine migrates to target physical machine in disk incremental data determined by general During, executed data modification operation instruction, then can be determined that the data in magnetic disk of this virtual machine was modified Cross, otherwise it can be determined that the data in magnetic disk of this virtual machine is not modified.
As seen from the above, in the scheme that the present embodiment provides, first the Disk Backup data of migration virtual machine is to mesh Mark physical machine, then migrate again virtual machine generate produce after this Disk Backup data for this Disk Backup number According to disk incremental data to target physical machine so that target physical machine can be according to above-mentioned Disk Backup number According to the whole data in magnetic disk obtaining this virtual machine with disk incremental data.In the scheme being provided due to the present embodiment, Above-mentioned Disk Backup data storage in the backup physical machine different from the corresponding physical machine of virtual machine, so, The I/O resource of the corresponding physical machine of virtual machine will not be taken when migrating this Disk Backup data to target physical machine, Also user operation virtual machine would not be affected.In addition, though increasing in the disk above-mentioned to the migration of target physical machine The I/O resource of the corresponding physical machine of virtual machine can be taken during amount data, affect user operation virtual machine, But because above-mentioned disk incremental data is much smaller compared to for whole data in magnetic disk of virtual machine, so, During to the target physical machine above-mentioned disk incremental data of migration, shorter to the influence time of user operation virtual machine. Comprehensive visible above, the scheme that application the present embodiment provides, can shorten magnetic disk of virtual machine Data Migration to Family operates the impact duration of virtual machine, improves Consumer's Experience.
Virtual below by a magnetic disk of virtual machine data migration method applying embodiment illustrated in fig. 1 to provide Machine data in magnetic disk migratory system, illustrates to above-mentioned magnetic disk of virtual machine data migration method.
Specifically, referring to Fig. 2, there is provided a kind of structural representation of magnetic disk of virtual machine data mover system.
Wherein, this system includes：Management physical machine, backup physical machine, target physical machine and above-mentioned virtual The corresponding physical machine of machine.
Management physical machine, has management function, manages other physical machine in this system, for example, backs up thing Reason machine, the corresponding physical machine of above-mentioned virtual machine, target physical machine etc.；
Backup physical machine, for storing the Disk Backup data of each virtual machine.
Above-mentioned management physical machine, backup physical machine are functionally being divided from machine, practical application In, management physical machine, backup physical machine and target physical machine can correspond to same physical machine it is also possible to Corresponding to multiple stage physical machine, the application is not defined to this, but, backup physical machine is virtual with above-mentioned The corresponding physical machine of machine is two different physical machine certainly.
When migrating the data in magnetic disk of above-mentioned virtual machine, management physical machine first can send number to backup physical machine According to migration instruction, in this instruction, need the information such as mark including above-mentioned virtual machine, the mark of target physical machine, After backup physical machine receives above-mentioned migration instruction, from the Disk Backup data of the above-mentioned virtual machine of wherein storage The middle Disk Backup data selecting a version, and migrate selected Disk Backup data to target physical machine, After backup physical machine determines and all migrates selected Disk Backup data to target physical machine, application The method that embodiment illustrated in fig. 1 provides migrates the disk incremental data of above-mentioned virtual machine to target physical machine.
In the case of one kind, backup physical machine determines by selected Disk Backup Data Migration to target physical machine Afterwards, migration can be sent to management physical machine and complete feedback command, management physical machine is according to this instruction to above-mentioned Virtual machine sends data in magnetic disk migration instruction.
In the case of another kind, backup physical machine determines by selected Disk Backup Data Migration to target physical After machine, can also be without completing feedback command to management physical machine transmission migration, but state virtual machine directly up Send data in magnetic disk migration instruction.
After the corresponding physical machine of above-mentioned virtual machine receives the migration instruction of this data in magnetic disk, recorded according to it Disk incremental data, determines to generate and has moved to the Disk Backup data of the above-mentioned virtual machine of target physical machine For the disk incremental data of this Disk Backup data, and disk incremental data determined by general migrates to target Physical machine.
Target physical machine after receiving above-mentioned Disk Backup data, in conjunction with the disk incremental data of receipt of subsequent Carry out the operation such as Data Synthesis, and then obtain whole data in magnetic disk of above-mentioned magnetic disk of virtual machine.
Further, during migration virtual machine in addition to whole data in magnetic disk that need migrate virtual machine, Also need to migrate the full memory data of virtual machine, have moved in management physical machine determination and complete the complete of virtual machine After portion's data in magnetic disk and full memory data, can also send, to target physical machine, the instruction starting virtual machine, Make above-mentioned virtual machine start to run on target physical machine, and the virtual machine to before migration sends shutdown Instruction is so that the virtual machine before migration stops at operation in its corresponding physical machine.
Certainly, because the disk incremental data of virtual machine and internal storage data are essentially all to be stored in this virtual machine In corresponding physical machine, the instruction of above-mentioned startup virtual machine can also be that this virtual machine is determining by it Disk incremental data and full memory Data Migration to target physical machine to target physical machine send so that This virtual machine starts to bring into operation on target physical machine, and stops its operation on present physical machine.
Because the disk incremental data of virtual machine is according to user, the operation of magnetic disk of virtual machine data to be obtained, For example, delete data in magnetic disk a data block in data, change data in magnetic disk a data block in Data etc., so, need to be recorded for its operation in user operation virtual machine.
Specifically, above-mentioned magnetic disk of virtual machine data migration method can also include：
Receive the data modification operation instruction of the data in magnetic disk for above-mentioned virtual machine；
Change the data in magnetic disk of above-mentioned virtual machine；
Instructed according to data modification operation, update the data modification record of above-mentioned virtual machine.
It should be noted that each step above-mentioned can through the whole process of magnetic disk of virtual machine Data Migration, So, the application does not limit above-mentioned execution sequence between each step and S101, S102 and S103.
Based on foregoing description, in a kind of specific implementation of the present invention, referring to Fig. 3, there is provided virtual machine The second schematic flow sheet of data in magnetic disk moving method, compared with previous embodiment, in the present embodiment,
Above-mentioned data modification record includes：Instructed according to above-mentioned data modification operation, be modified is above-mentioned The data block identifier of the data in magnetic disk of virtual machine.
Specifically, determine and generate product of having moved to the Disk Backup data of the above-mentioned virtual machine of target physical machine Step S102 of the raw disk incremental data for this Disk Backup data, including：
S102A：According to above-mentioned data modification record, determine generate have moved above-mentioned virtual to target physical machine The data block identifier of the data in magnetic disk of above-mentioned virtual machine being modified after the Disk Backup data of machine.
In this step, determine to generate and have moved to the Disk Backup data of the above-mentioned virtual machine of target physical machine During the data block identifier of the data in magnetic disk of above-mentioned virtual machine being modified, can first be remembered according to above-mentioned data modification Record, acquisition is directed to and generates the disk number to the Disk Backup data of the above-mentioned virtual machine of target physical machine of having moved According to data bitmap, wherein, one flag of this data bit in figure, for representing that generation has moved to target After the Disk Backup data of the above-mentioned virtual machine of physical machine, a data block of the data in magnetic disk of above-mentioned virtual machine is No be modified, then represent the flag that has been modified of data block in searching data bitmap again, and determine lookup The corresponding data block identifier of flag arriving, these data block identifier are generation and have moved to target physical machine The Disk Backup data of above-mentioned virtual machine after the data block identifier of the data in magnetic disk of above-mentioned virtual machine that is modified.
In addition, can also be directly upper from being modified of including of above-mentioned data modification record in practical application State the data block identifier of the data in magnetic disk of virtual machine.
It should be noted that the application simply taking above-mentioned as a example illustrates how to determine data block identifier, reality should With in be not limited to that.
S102B：According to the data block identifier finding, obtain the block content of data block corresponding with above-mentioned mark, And the disk increment for this Disk Backup data producing after being defined as generating above-mentioned Disk Backup data Data.
The modification of the data in magnetic disk of above-mentioned virtual machine being modified is not included in above-mentioned data modification record In the case of content, the disk for this Disk Backup data producing after generating above-mentioned Disk Backup data increases Amount data, can comprise the data block identifier being modified, and these data block identifier corresponding data blocks Amended piece of content.
Based on above-mentioned situation, to determined by the migration of target physical machine, during disk incremental data, migrated is interior Hold the data block identifier including being modified, and amended piece of these data block identifier corresponding data blocks Content.Accordingly, target physical machine according to determined by disk incremental data and the Disk Backup number had moved According to obtain above-mentioned virtual machine whole data in magnetic disk when, can the mark of data block that first basis has been modified, Find the corresponding data block of the data block identifier being modified in the Disk Backup data having moved, then will The content of this data block replaces with the amended of the above-mentioned mark corresponding data block comprising in disk incremental data Block content, and then obtain whole data in magnetic disk of this virtual machine.
In a kind of relatively good implementation of the present invention, can include in above-mentioned data modification operation instruction： The data block identifier of the data in magnetic disk of above-mentioned virtual machine to be changed.
In this case, instructed according to data modification operation, updating the data modification record of above-mentioned virtual machine When, can exist in the data modification record detect above-mentioned virtual machine in data modification operation instruction and wrap In the case of the data block identifier of the data in magnetic disk of above-mentioned virtual machine to be changed including, grasped according to data modification Instruct the above-mentioned data block identifier including, update the data modification record.
It is furthermore appreciated that, to target physical machine migrate above-mentioned virtual machine Disk Backup data when, by In Disk Backup data data volume is big, the low reason of the network bandwidth, required for migration Disk Backup data Time may be longer, and above-mentioned virtual machine may generate the Disk Backup data of redaction during this period, and Backup physical machine can be sent it to, in this case although generating the Disk Backup data of redaction, Due to during migration disk incremental data, once above-mentioned virtual machine is detected have received for disk The data modification operation instruction of data, can update the data modification record of above-mentioned virtual machine, even if so new The Disk Backup data of version and the Disk Backup data having moved exist different, also do not interfere with this virtual machine The migration of data in magnetic disk, in subsequent step can still according to the version of Disk Backup data had moved and Data modification record after renewal, determines the corresponding magnetic of Disk Backup data having moved to target physical machine Disk incremental data.
As seen from the above, in the scheme that the present embodiment provides, in the disk migrating virtual machine to target physical machine In the whole process of data, only migration disk incremental data can affect the operation to virtual machine for the user, and magnetic Disk incremental data is by the modification of the data block identifier being modified and these data block identifier corresponding data blocks Afterwards block Composition of contents it is seen that its data volume will be far smaller than the data volume of whole data in magnetic disk of virtual machine, Therefore, it is possible to shorten the impact duration to user operation virtual machine for the magnetic disk of virtual machine Data Migration.
Based on foregoing description, in another kind of specific implementation of the present invention, referring to Fig. 4, there is provided virtual The third schematic flow sheet of machine data in magnetic disk moving method, compared with previous embodiment, in the present embodiment,
Above-mentioned data modification record includes：Instructed according to above-mentioned data modification operation, be modified is above-mentioned The data block identifier of the data in magnetic disk of virtual machine and the modification content of this data block.
Specifically, determine and generate product of having moved to the Disk Backup data of the above-mentioned virtual machine of target physical machine Step S102 of the raw disk incremental data for this Disk Backup data, including：
S102C：From data modification record search generate have moved to target physical machine above-mentioned virtual machine magnetic The data block identifier of the data in magnetic disk of above-mentioned virtual machine being modified after disk Backup Data.
S102D：According to the data block identifier finding, obtain corresponding with above-mentioned mark from data modification record Data block modification content, and be defined as generating the above-mentioned virtual machine having moved to target physical machine The disk incremental data for this Disk Backup data producing after Disk Backup data.
The information including with reference to above-mentioned data modification record, the pin producing after generating above-mentioned Disk Backup data Disk incremental data to this Disk Backup data, can comprise the data block identifier being modified, and this The modification content of a little data block identifier corresponding data blocks.
Based on above-mentioned situation, to determined by the migration of target physical machine, during disk incremental data, migrated is interior Hold the data block identifier including being modified, and the modification content of these data block identifier corresponding data blocks. Accordingly, target physical machine according to determined by disk incremental data and the Disk Backup data had moved obtain During whole data in magnetic disk of above-mentioned virtual machine, first can find in the Disk Backup data having moved and be repaiied The corresponding data block of data block identifier changing, the then modification content modification according to above-mentioned mark corresponding data block The block content of above-mentioned mark corresponding data block in Disk Backup data, and then obtain whole disks of this virtual machine Data.
As seen from the above, in the scheme that the present embodiment provides, in the disk migrating virtual machine to target physical machine In the whole process of data, the data being migrated is only the data block identifier being modified, and these numbers According to the modification content of block identification corresponding data block, the modification with the data block identifier corresponding data block being modified Block content afterwards is compared, and data volume reduces further, and therefore, the scheme that application the present embodiment provides enters line number According to migration, the impact duration to user operation virtual machine for the magnetic disk of virtual machine Data Migration can be shortened further, And then Consumer's Experience can be improved further.
Corresponding with above-mentioned magnetic disk of virtual machine data migration method, the embodiment of the present invention additionally provides a kind of void Plan machine data in magnetic disk moving apparatus.
Fig. 5 is the first structural representation of magnetic disk of virtual machine data migration device provided in an embodiment of the present invention, This device is applied to virtual machine, including：
Command reception module 501, for the instruction of reception of magnetic disc Data Migration, wherein, described data in magnetic disk migration Comprise in instruction to have moved to target physical machine described virtual machine Disk Backup data information, described void The Disk Backup data storage of plan machine is in the backup physical machine that physical machine corresponding with described virtual machine differs；
Disk incremental data determining module 502, has moved to described in described target physical machine for determining to generate The disk incremental data for this Disk Backup data producing after the Disk Backup data of virtual machine；
Disk incremental data transferring module 503, migrates to described target for disk incremental data determined by general Physical machine so that described target physical machine according to determined by disk incremental data and the disk had moved standby Number is according to the whole data in magnetic disk obtaining described virtual machine.
Specifically, described have moved to described target physical machine described virtual machine Disk Backup data permissible For：To the Disk Backup data moment starting to migrate described virtual machine, for storing described virtual machine The latest edition Disk Backup data of the described virtual machine of storage in the backup physical machine of Disk Backup data.
In a kind of optional implementation of the present invention, described command reception module, it is additionally operable to receive for institute State the data modification operation instruction of the data in magnetic disk of virtual machine；
Described magnetic disk of virtual machine data migration device can also include：
Data in magnetic disk modified module, for changing the data in magnetic disk of described virtual machine；
Modification record update module, for instructing according to described data modification operation, updates described virtual machine Data modification record.
In the optional implementation of another kind of the present invention, described magnetic disk of virtual machine data migration device is acceptable Including：
Data modification detection module, for migrating to described target physical in disk incremental data determined by general During machine, detect whether the data of the data in magnetic disk of described virtual machine is modified；
Disk incremental data update module, for the testing result in described data modification instruction detection module be In the case of being, disk incremental data determined by renewal.
As seen from the above, in the scheme that the present embodiment provides, first the Disk Backup data of migration virtual machine is to mesh Mark physical machine, then migrate again virtual machine generate produce after this Disk Backup data for this Disk Backup number According to disk incremental data to target physical machine so that target physical machine can be according to above-mentioned Disk Backup number According to the whole data in magnetic disk obtaining this virtual machine with disk incremental data.In the scheme being provided due to the present embodiment, Above-mentioned Disk Backup data storage in the backup physical machine different from the corresponding physical machine of virtual machine, so, The I/O resource of the corresponding physical machine of virtual machine will not be taken when migrating this Disk Backup data to target physical machine, Also user operation virtual machine would not be affected.In addition, though increasing in the disk above-mentioned to the migration of target physical machine The I/O resource of the corresponding physical machine of virtual machine can be taken during amount data, affect user operation virtual machine, But because above-mentioned disk incremental data is much smaller compared to for whole data in magnetic disk of virtual machine, so, During to the target physical machine above-mentioned disk incremental data of migration, shorter to the influence time of user operation virtual machine. Comprehensive visible above, the scheme that application the present embodiment provides, can shorten magnetic disk of virtual machine Data Migration to Family operates the impact duration of virtual machine, improves Consumer's Experience.
In a kind of specific implementation of the present invention, referring to Fig. 6, there is provided magnetic disk of virtual machine Data Migration fills The second structural representation put, compared with previous embodiment, in the present embodiment,
Described data modification record includes：Instructed according to described data modification operation, be modified is described The data block identifier of the data in magnetic disk of virtual machine；
Described disk incremental data determining module 502, including：
Data block identifier determination sub-module 5021, moves for according to described data modification record, determining to generate The magnetic of the described virtual machine being modified after moving to the Disk Backup data of the described virtual machine of described target physical machine The data block identifier of disk data；
First disk incremental data determination sub-module 5022, for according to the data block identifier finding, obtaining The block content of data block corresponding with above-mentioned mark, and be defined as generating product after above-mentioned Disk Backup data The raw disk incremental data for this Disk Backup data.
Specifically, described data block identifier determination sub-module 5021 can include：
Data bitmap obtaining unit, for according to described data modification record, obtain for generation have moved to The data bitmap of data in magnetic disk after the Disk Backup data of the described virtual machine of described target physical machine, wherein, Described one flag of data bit in figure, has moved to the described void of described target physical machine for representing to generate After the Disk Backup data of plan machine, whether a data block of the data in magnetic disk of described virtual machine is modified；
Flag searching unit, represents, for searching described data bit in figure, the flag that data block has been modified；
Data block identifier determining unit, for determining the corresponding data block identifier of flag finding.
Specifically, can include in described data modification operation instruction：The disk of described virtual machine to be changed The data block identifier of data；
Described modification record update module can include：
Data block identifier detection sub-module, for detecting in the data modification record of described virtual machine whether deposit The data block mark of the data in magnetic disk of the described virtual machine to be changed including in the instruction of described data modification operation Know；
Modification record updates submodule, is yes for the testing result in described data block identifier detection sub-module In the case of, the above-mentioned data block identifier including is instructed according to described data modification operation, updates described number According to modification record.
As seen from the above, in the scheme that the present embodiment provides, in the disk migrating virtual machine to target physical machine In the whole process of data, only migration disk incremental data can affect the operation to virtual machine for the user, and magnetic Disk incremental data is by the modification of the data block identifier being modified and these data block identifier corresponding data blocks Afterwards block Composition of contents it is seen that its data volume will be far smaller than the data volume of whole data in magnetic disk of virtual machine, Therefore, it is possible to shorten the impact duration to user operation virtual machine for the magnetic disk of virtual machine Data Migration.
In another kind of specific implementation of the present invention, referring to Fig. 7, there is provided magnetic disk of virtual machine Data Migration The third structural representation of device, compared with previous embodiment, in the present embodiment,
Described data modification record includes：Instructed according to described data modification operation, be modified is described The data block identifier of the data in magnetic disk of virtual machine and the modification content of this data block；
Described disk incremental data determining module 502, including：
Data block identifier searches submodule 5023, has moved for searching generation from described data modification record The disk of the described virtual machine being modified to the Disk Backup data of described virtual machine of described target physical machine The data block identifier of data；
Second disk incremental data determination sub-module 5024, for according to the data block identifier finding, from institute State the modification content obtaining data block corresponding with above-mentioned mark in data modification record, and determined and make a living Become have moved to the Disk Backup data of the described virtual machine of described target physical machine produce for this disk The disk incremental data of Backup Data.
As seen from the above, in the scheme that the present embodiment provides, in the disk migrating virtual machine to target physical machine In the whole process of data, the data being migrated is only the data block identifier being modified, and these numbers According to the modification content of block identification corresponding data block, the modification with the data block identifier corresponding data block being modified Block content afterwards is compared, and data volume reduces further, and therefore, the scheme that application the present embodiment provides enters line number According to migration, the impact duration to user operation virtual machine for the magnetic disk of virtual machine Data Migration can be shortened further, And then Consumer's Experience can be improved further.
For device embodiment, because it is substantially similar to embodiment of the method, so the comparison of description is simple Single, in place of correlation, the part referring to embodiment of the method illustrates.
It should be noted that herein, such as first and second or the like relational terms be used merely to by One entity or operation are made a distinction with another entity or operation, and not necessarily require or imply these There is any this actual relation or order between entity or operation.And, term " inclusion ", "comprising" Or its any other variant is intended to comprising of nonexcludability, so that including a series of mistake of key elements Journey, method, article or equipment not only include those key elements, but also other including being not expressly set out Key element, or also include for this process, method, article or the intrinsic key element of equipment.Do not having In the case of more restrictions, the key element being limited by sentence "including a ..." is it is not excluded that including described wanting Also there is other identical element in the process of element, method, article or equipment.
One of ordinary skill in the art will appreciate that realizing all or part of step in said method embodiment The program that can be by complete come the hardware to instruct correlation, and described program can be stored in computer-readable Take in storage medium, the storage medium obtaining designated herein, such as：ROM/RAM, magnetic disc, CD etc..
The foregoing is only presently preferred embodiments of the present invention, be not intended to limit protection scope of the present invention. All any modification, equivalent substitution and improvement made within the spirit and principles in the present invention etc., are all contained in In protection scope of the present invention.

Claims (16)

1. a kind of magnetic disk of virtual machine data migration method, is applied to virtual machine it is characterised in that methods described Including：
Reception of magnetic disc Data Migration instructs, and wherein, comprises to have moved to mesh in described data in magnetic disk migration instruction The information of the Disk Backup data of described virtual machine of mark physical machine, the Disk Backup data of described virtual machine is deposited It is stored in the backup physical machine that physical machine corresponding with described virtual machine differs；
Determine and generate generation of having moved to the Disk Backup data of the described virtual machine of described target physical machine Disk incremental data for this Disk Backup data；
Disk incremental data determined by inciting somebody to action migrates to described target physical machine, so that described target physical machine According to determined by disk incremental data and the Disk Backup data had moved obtain whole magnetic of described virtual machine Disk data.
2. method according to claim 1 it is characterised in that
The described Disk Backup data of described virtual machine had moved to described target physical machine is：To starting to move Till the Disk Backup data moment moving described virtual machine, for storing the Disk Backup data of described virtual machine Backup physical machine in storage described virtual machine latest edition Disk Backup data.
3. method according to claim 1 is it is characterised in that methods described also includes：
Receive the data modification operation instruction of the data in magnetic disk for described virtual machine；
Change the data in magnetic disk of described virtual machine；
Instructed according to described data modification operation, update the data modification record of described virtual machine.
4. method according to claim 3 it is characterised in that
Described data modification record includes：Instructed according to described data modification operation, be modified is described The data block identifier of the data in magnetic disk of virtual machine；
Described determination generates product of having moved to the Disk Backup data of the described virtual machine of described target physical machine The raw disk incremental data for this Disk Backup data, including：
According to described data modification record, determine to generate and have moved to the described virtual machine of described target physical machine Disk Backup data after the data block identifier of the data in magnetic disk of described virtual machine that is modified；
According to the data block identifier finding, obtain the block content of data block corresponding with above-mentioned mark, and will Its disk incremental data for this Disk Backup data producing after being defined as generating above-mentioned Disk Backup data.
5. method according to claim 4 it is characterised in that described according to described data modification record, Determine and generate the institute being modified to the Disk Backup data of the described virtual machine of described target physical machine that has moved State the data block identifier of the data in magnetic disk of virtual machine, including：
According to described data modification record, obtain and have moved to the described void of described target physical machine for generating The data bitmap of data in magnetic disk after the Disk Backup data of plan machine, wherein, described one mark of data bit in figure Position, generates, for representing, the institute to the Disk Backup data of the described virtual machine of described target physical machine that has moved Whether a data block stating the data in magnetic disk of virtual machine is modified；
Search described data bit in figure and represent the flag that data block has been modified；
Determine the corresponding data block identifier of flag finding.
6. the method according to any one of claim 3-5 it is characterised in that
Described data modification operation instruction includes：The data block of the data in magnetic disk of described virtual machine to be changed Mark；
The described data modification record being instructed according to described data modification operation, updating described virtual machine, including：
Detect whether to have existed in the data modification record of described virtual machine in described data modification operation instruction and wrap The data block identifier of the data in magnetic disk of described virtual machine to be changed including；
If including, the above-mentioned data block identifier being included according to the instruction of described data modification operation, update described Data modification record.
7. method according to claim 3 it is characterised in that
Described data modification record includes：Instructed according to described data modification operation, be modified is described The data block identifier of the data in magnetic disk of virtual machine and the modification content of this data block；
Described determination generates product of having moved to the Disk Backup data of the described virtual machine of described target physical machine The raw disk incremental data for this Disk Backup data, including：
Search from described data modification record and generate the described virtual machine having moved to described target physical machine The data block identifier of the data in magnetic disk of described virtual machine being modified after Disk Backup data；
According to the data block identifier finding, obtain corresponding with above-mentioned mark from described data modification record The modification content of data block, and be defined as generating the described virtual machine having moved to described target physical machine Disk Backup data after produce the disk incremental data for this Disk Backup data.
8. method according to claim 1 is it is characterised in that methods described also includes：
During disk incremental data determined by inciting somebody to action migrates to described target physical machine, detect described void Whether the data in magnetic disk of plan machine is modified；
If it is, disk incremental data determined by updating.
9. a kind of magnetic disk of virtual machine data migration device, is applied to virtual machine it is characterised in that described device Including：
Command reception module, for the instruction of reception of magnetic disc Data Migration, wherein, described data in magnetic disk migration refers to Comprise in order to have moved to target physical machine described virtual machine Disk Backup data information, described virtual The Disk Backup data storage of machine is in the backup physical machine that physical machine corresponding with described virtual machine differs；
Disk incremental data determining module, has moved to the described void of described target physical machine for determining to generate The disk incremental data for this Disk Backup data producing after the Disk Backup data of plan machine；
Disk incremental data transferring module, migrates to described object for disk incremental data determined by general Reason machine so that described target physical machine according to determined by disk incremental data and the Disk Backup had moved Data obtains whole data in magnetic disk of described virtual machine.
10. device according to claim 9 it is characterised in that
The described Disk Backup data of described virtual machine had moved to described target physical machine is：To starting to move Till the Disk Backup data moment moving described virtual machine, for storing the Disk Backup data of described virtual machine Backup physical machine in storage described virtual machine latest edition Disk Backup data.
11. devices according to claim 9 it is characterised in that
Described command reception module, is additionally operable to receive the data modification behaviour of the data in magnetic disk for described virtual machine Instruct；
Described device also includes：
Data in magnetic disk modified module, for changing the data in magnetic disk of described virtual machine；
Modification record update module, for instructing according to described data modification operation, updates described virtual machine Data modification record.
12. devices according to claim 11 it is characterised in that
Described data modification record includes：Instructed according to described data modification operation, be modified is described The data block identifier of the data in magnetic disk of virtual machine；
Described disk incremental data determining module, including：
Data block identifier determination sub-module, for according to described data modification record, determine generation have moved to The disk number of the described virtual machine being modified after the Disk Backup data of the described virtual machine of described target physical machine According to data block identifier；
First disk incremental data determination sub-module, for according to the data block identifier that finds, obtain with upper State the block content identifying corresponding data block, and produce after being defined as generating above-mentioned Disk Backup data Disk incremental data for this Disk Backup data.
13. devices according to claim 12 are it is characterised in that described data block identifier determines submodule Block, including：
Data bitmap obtaining unit, for according to described data modification record, obtain for generation have moved to The data bitmap of data in magnetic disk after the Disk Backup data of the described virtual machine of described target physical machine, wherein, Described one flag of data bit in figure, has moved to the described void of described target physical machine for representing to generate After the Disk Backup data of plan machine, whether a data block of the data in magnetic disk of described virtual machine is modified；
Flag searching unit, represents, for searching described data bit in figure, the flag that data block has been modified；
Data block identifier determining unit, for determining the corresponding data block identifier of flag finding.
14. devices according to any one of claim 11-13 it is characterised in that
Described data modification operation instruction includes：The data block of the data in magnetic disk of described virtual machine to be changed Mark；
Described modification record update module, including：
Data block identifier detection sub-module, for detecting in the data modification record of described virtual machine whether deposit The data block mark of the data in magnetic disk of the described virtual machine to be changed including in the instruction of described data modification operation Know；
Modification record updates submodule, is yes for the testing result in described data block identifier detection sub-module In the case of, the above-mentioned data block identifier including is instructed according to described data modification operation, updates described number According to modification record.
15. devices according to claim 11 it is characterised in that
Described data modification record includes：Instructed according to described data modification operation, be modified is described The data block identifier of the data in magnetic disk of virtual machine and the modification content of this data block；
Described disk incremental data determining module, including：
Data block identifier searches submodule, has moved to institute for searching generation from described data modification record The data in magnetic disk of the described virtual machine being modified after stating the Disk Backup data of the described virtual machine of target physical machine Data block identifier；
Second disk incremental data determination sub-module, for according to the data block identifier finding, from described number According to the modification content obtaining data block corresponding with above-mentioned mark in modification record, and it is defined as generating Migrate to the Disk Backup data of the described virtual machine of described target physical machine produce for this Disk Backup The disk incremental data of data.
16. devices according to claim 9 are it is characterised in that described device also includes：
Data modification detection module, for migrating to described target physical in disk incremental data determined by general During machine, detect whether the data in magnetic disk of described virtual machine is modified；
Disk incremental data update module, is yes for the testing result in described data modification detection module In the case of, disk incremental data determined by renewal.
CN201510552927.0A 2015-09-01 2015-09-01 A kind of magnetic disk of virtual machine data migration method and device Active CN106484312B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201510552927.0A CN106484312B (en) 2015-09-01 2015-09-01 A kind of magnetic disk of virtual machine data migration method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510552927.0A CN106484312B (en) 2015-09-01 2015-09-01 A kind of magnetic disk of virtual machine data migration method and device

Publications (2)

Publication Number Publication Date
CN106484312A true CN106484312A (en) 2017-03-08
CN106484312B CN106484312B (en) 2019-07-26

Family

ID=58237667

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510552927.0A Active CN106484312B (en) 2015-09-01 2015-09-01 A kind of magnetic disk of virtual machine data migration method and device

Country Status (1)

Country Link
CN (1) CN106484312B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108446164A (en) * 2018-03-01 2018-08-24 深信服科技股份有限公司 A kind of data migration method of V2P, system and relevant apparatus
CN109062516A (en) * 2018-09-14 2018-12-21 成都云祺科技有限公司 Invalid data method for removing in a kind of windows virtual machine backup procedure
CN110866245A (en) * 2019-11-13 2020-03-06 哈尔滨工业大学 Detection method and detection system for maintaining file security of virtual machine

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101609419A (en) * 2009-06-29 2009-12-23 北京航空航天大学 The data back up method and the device of the migration of virtual machine consistently online
CN102073462A (en) * 2010-11-29 2011-05-25 华为技术有限公司 Virtual storage migration method and system and virtual machine monitor
CN102609361A (en) * 2012-01-16 2012-07-25 北京邮电大学 Method and device for transferring storage data of virtual machine
CN102646064A (en) * 2011-02-16 2012-08-22 微软公司 Incremental virtual machine backup supporting migration
JP2012185605A (en) * 2011-03-04 2012-09-27 Nec Corp Virtual machine system, virtual disk management method and virtual disk management program
CN103530167A (en) * 2013-09-30 2014-01-22 华为技术有限公司 Virtual machine memory data migration method and relevant device and cluster system

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101609419A (en) * 2009-06-29 2009-12-23 北京航空航天大学 The data back up method and the device of the migration of virtual machine consistently online
CN102073462A (en) * 2010-11-29 2011-05-25 华为技术有限公司 Virtual storage migration method and system and virtual machine monitor
CN102646064A (en) * 2011-02-16 2012-08-22 微软公司 Incremental virtual machine backup supporting migration
JP2012185605A (en) * 2011-03-04 2012-09-27 Nec Corp Virtual machine system, virtual disk management method and virtual disk management program
CN102609361A (en) * 2012-01-16 2012-07-25 北京邮电大学 Method and device for transferring storage data of virtual machine
CN103530167A (en) * 2013-09-30 2014-01-22 华为技术有限公司 Virtual machine memory data migration method and relevant device and cluster system

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108446164A (en) * 2018-03-01 2018-08-24 深信服科技股份有限公司 A kind of data migration method of V2P, system and relevant apparatus
CN108446164B (en) * 2018-03-01 2022-02-22 深信服科技股份有限公司 Data migration method, system and related device of V2P
CN109062516A (en) * 2018-09-14 2018-12-21 成都云祺科技有限公司 Invalid data method for removing in a kind of windows virtual machine backup procedure
CN109062516B (en) * 2018-09-14 2020-08-25 成都云祺科技有限公司 Method for eliminating invalid data in backup process of windows virtual machine
CN110866245A (en) * 2019-11-13 2020-03-06 哈尔滨工业大学 Detection method and detection system for maintaining file security of virtual machine
CN110866245B (en) * 2019-11-13 2023-11-07 哈尔滨工业大学 Detection method and detection system for maintaining file security of virtual machine

Also Published As

Publication number Publication date
CN106484312B (en) 2019-07-26

Similar Documents

Publication Publication Date Title
CN105528368B (en) A kind of database migration method and device
CN102707990B (en) Container based processing method and device
CN103970585B (en) Create the method and device of virtual machine
CN102981931B (en) Backup method and device for virtual machine
CN102917072B (en) For carrying out the equipment of Data Migration, system and method between data server cluster
CN102713856B (en) Method and system for recovering file system of computer system
CN102299904B (en) System and method for realizing service data backup
US8060703B1 (en) Techniques for allocating/reducing storage required for one or more virtual machines
US20150066857A1 (en) Replication of snapshots and clones
CN100498796C (en) Logic log generation method, database backup/ restoration method and system
CN102667703A (en) System and method for optimized reclamation processing in a virtual tape library system
CN103473277A (en) Snapshot method and device for file systems
CN106294387A (en) Data migration method and device
CN106484312A (en) A kind of magnetic disk of virtual machine data migration method and device
CN103605617A (en) Method and device for recording changes in stored data
CN105302671A (en) Automatic backup and rollback method and device
CN114721881B (en) Database management method, system, electronic device and storage medium
CN104636218B (en) Data reconstruction method and device
JPWO2007099636A1 (en) File system migration method, file system migration program, and file system migration apparatus
CN106682021A (en) Database migration method and device
US8214621B2 (en) Storage optimization across media with differing capabilities
CN105550230B (en) The method for detecting and device of distributed memory system node failure
CN104517067A (en) Method, device and system for data access
CN113672255A (en) Distributed storage software upgrading method and device
CN109471901A (en) A kind of method of data synchronization and device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20200423

Address after: 519015 Room 2, Block B, 10th floor, No. 8 Lianshan Lane, Jida Jingshan Road, Zhuhai City, Guangdong Province

Co-patentee after: BEIJING KINGSOFT CLOUD NETWORK TECHNIQUE Co.,Ltd.

Patentee after: Zhuhai Jinshan Cloud Technology Co., Ltd.

Co-patentee after: BEIJING KSYUN TECHNOLOGY Co.,Ltd.

Address before: Room 33, No. five 5F02 100085 Beijing City Xiaoying road Haidian District

Co-patentee before: BEIJING KSYUN TECHNOLOGY Co.,Ltd.

Patentee before: BEIJING KINGSOFT CLOUD NETWORK TECHNIQUE Co.,Ltd.

TR01 Transfer of patent right