CN107656705B - Computer storage medium and data migration method, device and system - Google Patents
Computer storage medium and data migration method, device and system Download PDFInfo
- Publication number
- CN107656705B CN107656705B CN201711007923.XA CN201711007923A CN107656705B CN 107656705 B CN107656705 B CN 107656705B CN 201711007923 A CN201711007923 A CN 201711007923A CN 107656705 B CN107656705 B CN 107656705B
- Authority
- CN
- China
- Prior art keywords
- volume
- data stored
- target
- target volume
- host
- 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.)
- Active
Links
- 238000003860 storage Methods 0.000 title claims abstract description 169
- 230000005012 migration Effects 0.000 title claims abstract description 123
- 238000013508 migration Methods 0.000 title claims abstract description 110
- 238000000034 method Methods 0.000 title claims abstract description 67
- 230000001360 synchronised effect Effects 0.000 claims abstract description 33
- 238000012544 monitoring process Methods 0.000 claims description 5
- 238000012545 processing Methods 0.000 claims description 2
- 230000000694 effects Effects 0.000 abstract description 4
- 238000005516 engineering process Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
Images
Classifications
-
- 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/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0614—Improving the reliability of storage systems
- G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
-
- 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
Abstract
The invention discloses a data migration method based on a storage virtual machine, wherein a path between a target volume and a host is a physical standby path under a logical path between a primary volume and the host, so that after historical data of the primary volume is synchronized to the target volume, if an original storage device is disconnected from the host, the host stores the data through the physical standby path without changing the logical path. Moreover, because the identification of the storage virtual machine of the target storage device is the same as the identification of the original storage device, and the virtual logical unit number of the target volume is the same as the physical logical unit number of the original volume, the host cannot detect that the used storage device is replaced, so that the data migration method inherits the advantages of transparent application and high migration efficiency of the storage layer for data migration, and can realize data migration without shutdown. In addition, the invention also discloses a computer storage medium, a data migration device and a data migration system based on the storage virtual machine, and the effects are as above.
Description
Technical Field
The present invention relates to the field of computers, and in particular, to a computer storage medium, and a data migration method, apparatus, and system.
Background
Data migration is a key part in data system integration to ensure smooth system upgrade and update. In the process of information-based construction, with the development of technology, an original information system is continuously replaced by a new system with stronger functions, and the original information system usually accumulates a large amount of precious historical data during the use period, wherein a lot of historical data are necessary for the smooth starting of the new system. In addition, the historical data is also an important basis for decision analysis.
At present, there are many methods for data migration, such as data migration based on a host logical volume mirroring technology, data migration based on a database backup recovery technology, data migration based on an application tool, data migration based on a disk array remote data replication technology, and data migration based on a storage virtualization technology, but all have their respective disadvantages. Data migration based on the storage virtualization technology is explained as an example. The data migration of the storage virtualization technology is mainly used for solving the problem of mass data migration between heterogeneous storages, and although the advantages of transparent application and high migration efficiency of the storage layer for data migration are inherited, because the method needs to implement virtualization on the original storage device and change the logic path of the stored data, and the host needs to re-identify the storage device and the Logic Unit Number (LUN), when the method is applied, a service shutdown window exists, and the data migration without shutdown cannot be realized.
Therefore, how to implement non-stop data migration is a technical problem that needs to be solved by those skilled in the art at present, while inheriting the advantages of transparent application and high migration efficiency of data migration performed by a storage layer.
Disclosure of Invention
The invention aims to provide a computer storage medium and a data migration method, device and system, which can realize non-stop data migration under the advantages of transparent application and high migration efficiency of inheriting a storage layer to perform data migration.
In order to solve the technical problem, the data migration method based on the storage virtual machine provided by the invention comprises the following steps:
creating a storage virtual machine with the same identification as that of an original storage device on a target storage device, and setting a target volume on the target storage device as a virtual volume with the virtual logical unit number of the storage virtual machine being the same as the physical logical unit number of the original volume;
establishing a path between the target volume and the host as a physical standby path under a logical path between the primary volume and the host;
and establishing a synchronization relation between the target volume and the original volume, and synchronizing the historical data stored by the original volume to the target volume according to the synchronization relation.
Preferably, after the synchronizing the historical data stored in the primary volume to the target volume according to the synchronization relationship, the data migration method further includes:
judging whether the historical data stored in the primary volume is completely consistent with the historical data stored in the target volume;
if yes, disconnecting the original storage device from the host, skipping the following steps, and if not, entering the following steps:
continuing to synchronize the historical data stored by the primary volume and not synchronized to the target volume;
and disconnecting the original storage equipment from the host.
Preferably, the determining whether the history data stored in the primary volume completely matches the history data stored in the target volume specifically includes:
counting the total amount of historical data stored in the primary roll in advance;
monitoring the data volume of the historical data synchronized to the target volume;
and when the data volume is the same as the total volume, determining that the historical data stored by the primary volume is completely consistent with the historical data stored by the target volume, otherwise, determining that the historical data stored by the primary volume is inconsistent with the historical data stored by the target volume.
Preferably, the determining whether the history data stored in the primary volume completely matches the history data stored in the target volume specifically includes:
monitoring a first total amount of data of the historical data stored by the primary volume and a second total amount of data of the historical data stored by the target volume;
and when the first total data amount and the second total data amount are equal, determining that the historical data stored by the primary volume is completely consistent with the historical data stored by the target volume, otherwise, determining that the historical data stored by the primary volume is inconsistent with the historical data stored by the target volume.
Preferably, the determining whether the history data stored in the primary volume completely matches the history data stored in the target volume specifically includes:
when no historical data is synchronized to the target volume, timing is started, and whether the historical data is synchronized to the target volume is judged in real time before the timing time reaches preset time;
if not, determining that the historical data stored by the primary volume is completely consistent with the historical data stored by the target volume; if so, determining that the historical data stored by the primary volume is inconsistent with the historical data stored by the target volume.
Preferably, the data migration method further includes:
and after the history data stored in the primary volume is successfully synchronized to the target volume, the host is set to output prompt information of successful synchronization of the history data.
Preferably, before the synchronizing the historical data stored in the primary volume to the target volume according to the synchronization relationship, the migration method further includes:
judging whether the host is idle at present;
if yes, the step of synchronizing the historical data stored by the primary volume to the target volume according to the synchronization relation is carried out, otherwise, the step of judging whether the host is idle at present is repeatedly carried out.
In order to solve the above technical problem, the present invention further provides a data migration apparatus based on a storage virtual machine, including:
the system comprises a setting module, a storage module and a processing module, wherein the setting module is used for creating a storage virtual machine with the same identification as that of an original storage device on a target storage device, and setting a target volume on the target storage device as a virtual volume with the same virtual logical unit number of the storage virtual machine and the same physical logical unit number of the original volume;
the establishing module is used for establishing a path between the target volume and the host as a physical standby path under a logic path between the original volume and the host;
and the synchronization module is used for establishing a synchronization relationship between the target volume and the original volume and synchronizing the historical data stored by the original volume to the target volume according to the synchronization relationship.
In order to solve the above technical problem, the present invention further provides a data migration system based on a storage virtual machine, including:
a memory for storing a data migration program;
a processor for implementing the steps of any of the data migration methods described above when executing the data migration program.
In order to solve the above technical problem, the present invention further provides a computer-readable storage medium, on which a data migration program is stored, and the data migration program, when executed by a processor, implements the steps of any one of the data migration methods described above.
According to the data migration method based on the storage virtual machine, the path between the target volume and the host is a physical standby path under the logical path between the primary volume and the host, so that after the historical data of the primary volume is synchronized to the target volume, if the primary storage device is disconnected from the host, the host can store the data through the physical standby path under the same logical path without changing the logical path. Moreover, because the identification of the storage virtual machine of the target storage device is the same as the identification of the original storage device, and the virtual logical unit number of the target volume is the same as the physical logical unit number of the original volume, the host cannot detect that the used storage device has been replaced by the target storage device, and thus the host does not need to re-identify the storage device and the LUN of the storage device, and does not have any influence on any operating system, virtual machine monitoring program, server cluster, storage network, and the like. Therefore, the data migration method not only inherits the advantages of transparent application and high migration efficiency of the storage layer for data migration, but also has no business shutdown window, and can realize data migration without shutdown. In addition, the invention also provides a computer storage medium, and a data migration device and system based on the storage virtual machine, and the effects are as above.
Drawings
In order to illustrate the embodiments of the present invention more clearly, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings can be obtained by those skilled in the art without inventive effort.
Fig. 1 is a flowchart of a data migration method based on a storage virtual machine according to an embodiment of the present invention;
fig. 2 is a flowchart of another data migration method based on a storage virtual machine according to an embodiment of the present invention;
fig. 3 is a flowchart of another data migration method based on a storage virtual machine according to an embodiment of the present invention;
fig. 4 is a structural diagram of a data migration apparatus based on a storage virtual machine according to an embodiment of the present invention;
fig. 5 is a structural diagram of a data migration system based on a storage virtual machine according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without any inventive step, are within the scope of the present invention.
The invention aims to provide a computer storage medium and a data migration method, device and system, which can realize non-stop data migration under the advantages of transparent application and high migration efficiency of inheriting a storage layer to perform data migration.
In order to make the technical solutions of the present invention better understood, the present invention will be further described in detail with reference to the accompanying drawings and specific embodiments.
Fig. 1 is a flowchart of a data migration method based on a storage virtual machine according to an embodiment of the present invention. As shown in fig. 1, the data migration method includes:
s10: and creating a storage virtual machine with the same identification as that of the original storage device on the target storage device, and setting the target volume on the target storage device as a virtual volume with the virtual logical unit number of the storage virtual machine being the same as the physical logical unit number of the original volume.
The target storage device is a target storage device with a storage virtual machine function; the original storage equipment comprises an original roll, wherein the original roll is used for storing history data output by the host; the identification of the target storage device and the original storage device may be the IDs of the storage devices.
In step S11, the logical connection between the host and the target volume may be established by setting the FC identification number of the storage virtual machine to correspond to the external storage FC port of the host, and the target volume may be set to be a virtual volume whose virtual logical number of the storage virtual machine is the same as the physical logical unit number of the primary volume. Moreover, since the identifier of the storage virtual machine of the target storage device is the same as the identifier of the original storage device, and the virtual logical unit number of the target volume is the same as the physical logical unit number of the original volume, if the original storage device is replaced with the target storage device, the host cannot detect the difference of the storage devices, and the LUN of the storage device does not need to be re-identified.
S11: under a logical path between a primary volume and a host, a path between a target volume and the host is established as a physical backup path.
Under the logical path between the primary volume and the host, a physical backup path is established, i.e., the path between the primary volume and the host (physical path) and the path between the target volume and the host (physical path) are under the same logical path. In this way, when the storage device of the host is replaced, the storage path of the host does not need to be changed.
S12: and establishing a synchronization relation between the target volume and the original volume, and synchronizing the historical data stored by the original volume to the target volume according to the synchronization relation.
After the target volume obtains the history data stored by the primary volume, the target volume can continuously store the fresh history data of the host instead of the primary volume, that is, the target storage device can continuously store the fresh history data of the host instead of the primary storage device. The method for replacing the original storage device with the target storage device may be as follows: after the history data stored by the primary volume is successfully synchronized to the target volume, the physical connection between the primary storage device and the host is directly disconnected.
In summary, according to the data migration method based on the storage virtual machine provided by the present invention, since the path between the target volume and the host is a physical backup path under the logical path between the primary volume and the host, after the history data of the primary volume is synchronized to the target volume, if the primary storage device is disconnected from the host, the host stores the data through the physical backup path under the same logical path without changing the logical path. Moreover, because the identification of the storage virtual machine of the target storage device is the same as the identification of the original storage device, and the virtual logical unit number of the target volume is the same as the physical logical unit number of the original volume, the host cannot detect that the used storage device has been replaced by the target storage device, and thus the host does not need to re-identify the storage device and the LUN of the storage device, and does not have any influence on any operating system, virtual machine monitoring program, server cluster, storage network, and the like. Therefore, the data migration method not only inherits the advantages of transparent application and high migration efficiency of the storage layer for data migration, but also has no business shutdown window, and can realize data migration without shutdown.
Fig. 2 is a flowchart of another data migration method based on a storage virtual machine according to an embodiment of the present invention. In order to ensure that all the historical data stored in the primary volume can be reliably synchronized to the target volume and improve the reliability of the data migration method, on the basis of the above embodiment, a second embodiment of the present invention provides another data migration method based on a storage virtual machine.
As shown in fig. 2, as a preferred implementation, after performing step S12, the data migration method further includes:
s20: it is determined whether the history data stored in the reel completely matches the history data stored in the target volume, and if not, the process proceeds to step S21, and if so, the process proceeds to step S22.
S21: and continuously synchronizing the historical data stored by the primary volume and not synchronized to the target volume.
S22: and disconnecting the original storage equipment from the host.
The disconnected original storage device is connected with the host in the following mode: and deleting the physical path between the original storage equipment and the host.
If the history data stored in the primary volume is not completely synchronized to the target volume, the history data that has not been successfully synchronized is only stored in the primary volume, which results in the history data stored in the primary volume being more than a part of the history data stored in the target volume, i.e. the history data stored in the primary volume does not completely coincide with the history data stored in the target volume, at this time, step S21 may be continued to synchronize the history data that has not been successfully synchronized to the target volume, and after the synchronization is completed, step S22 is performed, so that the new history data of the host is stored on the target storage device through the physical backup path under the original logical path. Of course, if the history data stored in the primary volume is completely synchronized to the target volume, the history data stored in the primary volume and the history data stored in the target volume completely match each other, and step S22 may be directly executed.
If comparing the history data stored in the target volume with the history data stored in the primary volume one by one, not only the time is long, but also more resources are occupied, therefore, on the basis of the second embodiment, as a preferred implementation manner, the step S20 specifically includes: counting the total amount of historical data stored in a primary roll in advance; monitoring the data volume of the historical data synchronized to the target volume; and when the data volume is the same as the total volume, determining that the data history stored by the primary volume is completely consistent with the history data stored by the target volume, otherwise, determining that the history data stored by the primary volume is inconsistent with the history data stored by the target volume. If the history data stored in the primary volume is not completely synchronized to the target volume, the data amount of the history data stored in the target volume is always smaller than the total amount of the history data counted in advance, and at this time, the history data stored in the primary volume is not consistent with the history data stored in the target volume. If the data amount of the history data stored in the target volume is equal to the total amount of the history data counted in advance, it means that the history data stored in the primary volume is completely synchronized to the target volume, that is, the history data stored in the primary volume and the history data stored in the target volume completely coincide with each other, in the case that the history data newly generated by the host computer during the synchronization of the history data is not counted. Therefore, in the embodiment, only by comparing the amount of data stored in the target volume with the total amount of data stored in the target volume, it can be determined whether the history data stored in the target volume is completely consistent with the history data stored in the target volume, so that the workload for determining whether the history data stored in the target volume is completely consistent with the history data stored in the target volume is reduced, and the time consumed for performing the determination operation is shortened.
Of course, in order to further improve the reliability of the migration method without losing the history data newly generated by the host during the synchronization of the history data, as another preferred embodiment, the step S20 specifically includes: monitoring a first data total amount of historical data stored by a primary volume and a second data total amount of historical data stored by a target volume; and when the first total data amount is equal to the second total data amount, determining that the historical data stored by the primary volume is completely consistent with the historical data stored by the target volume, otherwise, determining that the historical data stored by the primary volume is inconsistent with the historical data stored by the target volume. The first total data amount is the total amount of the historical data stored in the primary volume, and the second total data amount is the total amount of the historical data stored in the target volume. Since the embodiment simultaneously monitors the first total data amount and the second total data amount, if the host generates new history data during the synchronization of the history data and the monitored first total data amount is increased, it is determined that the history data stored in the primary volume is completely consistent with the history data stored in the target volume only if the second total data amount is the same as the increased first total amount. Thus, the present embodiment can ensure that new history data generated by the host during synchronization of the history data is not lost.
As another preferred embodiment, step S20 specifically includes: when no historical data is synchronized to the target volume, timing is started, and whether the historical data is synchronized to the target volume or not is judged in real time before the timing time reaches the preset time; if not, determining that the historical data stored in the primary volume is completely consistent with the historical data stored in the target volume; if so, it is determined that the history data stored by the primary volume does not match the history data stored by the target volume. The preset time can be preset according to practical application. If no data are synchronized to the target volume within the preset time, all the historical data stored by the primary volume are considered to be synchronized to the target volume, that is, the historical data stored by the primary volume and the historical data stored by the target volume are determined to be completely consistent.
In order to make the data migration method more friendly, after the history data stored in the primary volume is successfully synchronized to the target volume, the user can timely know that all the history data are successfully synchronized, as a preferred embodiment, the migration method further includes: and after the history data stored in the primary volume is successfully synchronized to the target volume, the host outputs prompt information of successful synchronization of the history data.
Fig. 3 is a flowchart of another data migration method based on a storage virtual machine according to an embodiment of the present invention. In order to further reduce the loss amount of the history data of the host and improve the reliability of the data migration method, on the basis of any one of the above embodiments, another embodiment of the present invention provides another data migration method based on a storage virtual machine.
As shown in fig. 3, as a preferred embodiment, the data migration method includes:
s10: and creating a storage virtual machine with the same identification as that of the original storage device on the target storage device, and setting the target volume on the target storage device as a virtual volume with the virtual logical unit number of the storage virtual machine being the same as the physical logical unit number of the original volume.
S11: under a logical path between a primary volume and a host, a path between a target volume and the host is established as a physical backup path.
S30: and establishing a synchronous relation between the target volume and the original volume.
Step S30 is the same as step S12, and will not be described herein again.
S31: and judging whether the host is idle currently, if so, entering the step S32, and if not, repeating the step S31.
In the present embodiment, although step S31 is arranged to be executed after step S30, this is only one embodiment, and in practical application, step S31 is arranged to be executed before step S32, and there is no requirement for the execution order of other steps.
S32: and synchronizing the historical data stored by the primary volume to the target volume according to the synchronization relationship.
In steps S32 and S12, the history data stored in the original volume is synchronized to the target volume according to the synchronization relationship, which is not described herein again. This example
It can be understood that, when the host traffic is small, the data migration is performed, which not only can reduce the loss amount of the historical data and improve the reliability of the data migration method, but also can complete the data migration at a faster speed.
In order to make those skilled in the art better understand the technical solution provided by the present invention, the following description will take as an example the migration of the history data stored on the primary volume (logical unit number is 10:00) of the primary storage device with ID 17500 to the target volume (logical unit number is 22:00) of the target storage device with ID 20700, where the target storage device with ID 20700 has a function of storing a virtual machine.
First, a storage virtual machine with an ID of 17500 is created on a target storage device with an ID of 20700, that is, the virtual ID of the target storage device is 17500. In addition, the FC identification number of the storage virtual machine is set to correspond to the external storage FC port of the host.
Next, the target volume with logical unit number 22:00 is defined as the virtual volume storing the virtual machine with ID 17500, and the logical unit number of the virtual volume is set to 10:00, that is, the virtual logical unit number of the target volume is 10: 00.
And establishing a path between the target volume with the virtual logical unit number of 10:00 and the host under the logical path between the original volume with the logical unit number of 10:00 and the host, and taking the path as a physical standby path of the logical path.
And finally, establishing a data synchronization relationship between the primary volume with the logical unit number of 10:00 and the target volume with the virtual logical unit number of 10:00, and after all data are successfully synchronized according to the data synchronization relationship, disconnecting the physical connection between the host and the primary storage device with the ID of 17500, namely, the data newly generated by the host is stored on the target volume (with the virtual logical unit number of 10:00) with the logical number of 22:00 of the target storage device (with the virtual ID of 17500) with the ID of 20700 through the physical standby path under the logical path.
Because the virtual ID of the target storage device and the ID of the original storage device are 17500, the virtual unit number of the target volume and the logical unit number of the original volume are 10:00, and the path between the target volume and the host and the path between the original volume and the host are in the same logical path, when the connection between the original volume and the host is disconnected, the host cannot detect that the original storage device has been replaced, and still continues to output data to the target volume of the target storage device through the original logical path. Therefore, in the data migration, the host does not need to be stopped, and the service of the host is not influenced.
The foregoing describes in detail an embodiment of a data migration method based on a storage virtual machine according to the present invention, and the present invention further provides a data migration apparatus corresponding to the data migration method.
Fig. 4 is a structural diagram of a data migration apparatus based on a storage virtual machine according to an embodiment of the present invention. As shown in fig. 4, the data migration apparatus includes:
a setting module 40, configured to create a storage virtual machine with an identifier that is the same as that of the original storage device on the target storage device, and set the target volume on the target storage device as a virtual volume with a virtual logical unit number of the storage virtual machine that is the same as a physical logical unit number of the original volume;
an establishing module 41, configured to establish, as a physical backup path, a path between a target volume and a host under a logical path between a primary volume and the host;
and the synchronization module 42 is configured to establish a synchronization relationship between the target volume and the original volume, and synchronize the history data stored in the original volume to the target volume according to the synchronization relationship.
In the data migration device based on the storage virtual machine, the path between the target volume and the host machine established by the establishing module is a physical standby path under the logical path between the primary volume and the host machine, so that after the historical data of the primary volume is synchronized to the target volume, if the primary storage device is disconnected from the host machine, the host machine can store the data through the physical standby path under the same logical path without changing the logical path. Moreover, because the identifier of the storage virtual machine of the target storage device set by the setting module is the same as the identifier of the original storage device, and the virtual logical unit number of the target volume is the same as the physical logical unit number of the original volume, the host cannot detect that the used storage device has been replaced by the target storage device, and thus the host does not need to re-identify the storage device and the LUN of the storage device, and does not have any influence on any operating system, virtual machine monitoring program, server cluster, storage network, and the like. Therefore, the data migration device not only inherits the advantages of transparent application and high migration efficiency of the storage layer for data migration, but also has no business shutdown window, and can realize data migration without shutdown.
The present invention further provides a data migration system based on a storage virtual machine corresponding to the data migration method, and since the embodiments of the system part and the method part correspond to each other, reference is made to the description of the embodiment of the method part for the embodiment of the system part, and details are not repeated here.
Fig. 5 is a structural diagram of a data migration system based on a storage virtual machine according to an embodiment of the present invention. As shown in fig. 5, the present data migration system includes:
a memory 50 for storing a data migration program;
the processor 51 is configured to implement the steps of the data migration method provided in any one of the above embodiments when executing the data migration program.
In the data migration system based on the storage virtual machine provided in this embodiment, since the processor can call the data migration program stored in the memory, and the steps of the data migration method provided in any of the above embodiments can be implemented, the system has the same practical effect as the above data migration method.
The present invention further provides a computer-readable storage medium, on which a data migration program is stored, and when executed by a processor, the data migration program implements the steps of the data migration method provided in any of the above embodiments.
The computer-readable storage medium provided in this embodiment may implement the steps of the data migration method provided in any of the above embodiments when the data migration program is executed by the processor, so that the computer-readable storage medium has the same practical effects as the data migration method.
The computer storage medium, the data migration method, the data migration device and the data migration system provided by the invention are described in detail above. The embodiments are described in a progressive mode in the specification, the emphasis of each embodiment is different from that of other embodiments, and the same and similar parts among the embodiments are referred to each other.
It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (9)
1. A data migration method based on a storage virtual machine is characterized by comprising the following steps:
creating a storage virtual machine with the same identification as that of an original storage device on a target storage device, and setting a target volume on the target storage device as a virtual volume with the virtual logical unit number of the storage virtual machine being the same as the physical logical unit number of the original volume;
establishing a path between the target volume and the host as a physical standby path under a logical path between the primary volume and the host;
and establishing a synchronization relation between the target volume and the original volume, and synchronizing the historical data stored by the original volume to the target volume according to the synchronization relation.
2. The data migration method according to claim 1, wherein after the synchronizing the history data stored in the primary volume to the target volume according to the synchronization relationship, further comprises:
judging whether the historical data stored in the primary volume is completely consistent with the historical data stored in the target volume;
if yes, disconnecting the original storage device from the host, skipping the following steps, and if not, entering the following steps:
continuing to synchronize the historical data stored by the primary volume and not synchronized to the target volume;
and disconnecting the original storage equipment from the host.
3. The data migration method according to claim 2, wherein the determining whether the history data stored in the primary volume completely matches the history data stored in the target volume specifically comprises:
monitoring a first total amount of data of the historical data stored by the primary volume and a second total amount of data of the historical data stored by the target volume;
and when the first total data amount and the second total data amount are equal, determining that the historical data stored by the primary volume is completely consistent with the historical data stored by the target volume, otherwise, determining that the historical data stored by the primary volume is inconsistent with the historical data stored by the target volume.
4. The data migration method according to claim 2, wherein the determining whether the history data stored in the primary volume completely matches the history data stored in the target volume specifically comprises:
when no historical data is synchronized to the target volume, timing is started, and whether the historical data is synchronized to the target volume is judged in real time before the timing time reaches preset time;
if not, determining that the historical data stored by the primary volume is completely consistent with the historical data stored by the target volume; if so, determining that the historical data stored by the primary volume is inconsistent with the historical data stored by the target volume.
5. The data migration method according to claim 1, further comprising:
and after the history data stored in the primary volume is successfully synchronized to the target volume, the host is set to output prompt information of successful synchronization of the history data.
6. The data migration method according to any one of claims 1 to 5, further comprising, before said synchronizing the history data stored in the primary volume to the target volume according to the synchronization relationship:
judging whether the host is idle at present;
if yes, the step of synchronizing the historical data stored by the primary volume to the target volume according to the synchronization relation is carried out, otherwise, the step of judging whether the host is idle at present is repeatedly carried out.
7. A data migration device based on a storage virtual machine is characterized by comprising:
the system comprises a setting module, a storage module and a processing module, wherein the setting module is used for creating a storage virtual machine with the same identification as that of an original storage device on a target storage device, and setting a target volume on the target storage device as a virtual volume with the same virtual logical unit number of the storage virtual machine and the same physical logical unit number of the original volume;
the establishing module is used for establishing a path between the target volume and the host as a physical standby path under a logic path between the original volume and the host;
and the synchronization module is used for establishing a synchronization relationship between the target volume and the original volume and synchronizing the historical data stored by the original volume to the target volume according to the synchronization relationship.
8. A data migration system based on a storage virtual machine, comprising:
a memory for storing a data migration program;
a processor for implementing the steps of the data migration method according to any one of claims 1 to 6 when executing the data migration program.
9. A computer-readable storage medium, having stored thereon a data migration program, which when executed by a processor implements the steps of the data migration method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711007923.XA CN107656705B (en) | 2017-10-25 | 2017-10-25 | Computer storage medium and data migration method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711007923.XA CN107656705B (en) | 2017-10-25 | 2017-10-25 | Computer storage medium and data migration method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107656705A CN107656705A (en) | 2018-02-02 |
| CN107656705B true CN107656705B (en) | 2020-10-23 |
Family
ID=61119391
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711007923.XA Active CN107656705B (en) | 2017-10-25 | 2017-10-25 | Computer storage medium and data migration method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107656705B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109189324B (en) | 2018-07-09 | 2021-01-08 | 华为技术有限公司 | Data migration method and device |
| CN112416652A (en) * | 2019-08-22 | 2021-02-26 | 华为技术有限公司 | Data backup method and data backup |
| CN110750521A (en) * | 2019-10-25 | 2020-02-04 | 北京浪潮数据技术有限公司 | Data migration method, device and equipment and computer readable storage medium |
| CN110989929A (en) * | 2019-11-22 | 2020-04-10 | 浪潮电子信息产业股份有限公司 | MON service migration method, device, equipment and readable storage medium |
| CN111104206B (en) * | 2019-12-25 | 2023-09-01 | 曙光信息产业(北京)有限公司 | Virtual machine storage migration method and device and computer equipment |
| CN111475104B (en) * | 2020-03-08 | 2023-01-10 | 苏州浪潮智能科技有限公司 | Storage device data online migration method, system, terminal and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103052938A (en) * | 2010-10-14 | 2013-04-17 | 株式会社日立制作所 | Data migration system and data migration method |
| CN104077239A (en) * | 2014-06-24 | 2014-10-01 | 华为技术有限公司 | IP hard disk, and memory system and data operation method thereof |
| CN105446662A (en) * | 2015-11-24 | 2016-03-30 | 华为技术有限公司 | Business cutover method, storage control device and storage device |
| CN105760109A (en) * | 2014-12-16 | 2016-07-13 | 华为技术有限公司 | Data migration method and storage array |
| CN106030500A (en) * | 2014-04-22 | 2016-10-12 | 株式会社日立制作所 | Data migration method of storage system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013046254A1 (en) * | 2011-09-27 | 2013-04-04 | Hitachi, Ltd. | Management server and data migration method |
| US9229648B2 (en) * | 2012-07-31 | 2016-01-05 | Hewlett Packard Enterprise Development Lp | Storage array reservation forwarding |
-
2017
- 2017-10-25 CN CN201711007923.XA patent/CN107656705B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103052938A (en) * | 2010-10-14 | 2013-04-17 | 株式会社日立制作所 | Data migration system and data migration method |
| CN106030500A (en) * | 2014-04-22 | 2016-10-12 | 株式会社日立制作所 | Data migration method of storage system |
| CN104077239A (en) * | 2014-06-24 | 2014-10-01 | 华为技术有限公司 | IP hard disk, and memory system and data operation method thereof |
| CN105760109A (en) * | 2014-12-16 | 2016-07-13 | 华为技术有限公司 | Data migration method and storage array |
| CN105446662A (en) * | 2015-11-24 | 2016-03-30 | 华为技术有限公司 | Business cutover method, storage control device and storage device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107656705A (en) | 2018-02-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107656705B (en) | Computer storage medium and data migration method, device and system | |
| JP6510112B2 (en) | Datastream Capture and Persistence Policy | |
| WO2017162032A1 (en) | Method and device for executing data recovery operation | |
| CA2930101C (en) | Partition-based data stream processing framework | |
| CN110309161B (en) | Data synchronization method and device and server | |
| JP5075736B2 (en) | System failure recovery method and system for virtual server | |
| US20190004908A1 (en) | Data protection using checkpoint restart for cluster shared resources | |
| US10346248B2 (en) | Failure resistant volume creation in a shared storage environment | |
| WO2021129733A1 (en) | Cloud operating system management method and apparatus, server, management system, and medium | |
| US10949401B2 (en) | Data replication in site recovery environment | |
| CN105843707B (en) | Database quick recovery method and equipment | |
| CA2929776A1 (en) | Client-configurable security options for data streams | |
| WO2018233630A1 (en) | Fault discovery | |
| US9400613B1 (en) | Intelligent pairing for snapshot based backups | |
| US9323760B1 (en) | Intelligent snapshot based backups | |
| US20190215363A1 (en) | Dynamic pool-based tiering for synchronization storage | |
| US10922305B2 (en) | Maintaining storage profile consistency in a cluster having local and shared storage | |
| CN113986450A (en) | Virtual machine backup method and device | |
| CN111078418B (en) | Operation synchronization method, device, electronic equipment and computer readable storage medium | |
| WO2017080362A1 (en) | Data managing method and device | |
| US9626117B2 (en) | Computer system and management method for computer system | |
| US9164691B1 (en) | Intelligent configuration for snapshot based backups | |
| CN110569231B (en) | Data migration method, device, equipment and medium | |
| US9355104B1 (en) | Intelligent pairing using a lookup database for snapshot based backups | |
| CN113238815A (en) | Interface access control method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200921 Address after: 215100 No. 1 Guanpu Road, Guoxiang Street, Wuzhong Economic Development Zone, Suzhou City, Jiangsu Province Applicant after: SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd. Address before: 450018 Henan province Zheng Dong New District of Zhengzhou City Xinyi Road No. 278 16 floor room 1601 Applicant before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |