A data migration method, device, product, equipment and medium

Abstract

The present invention discloses a data migration method, device, product, equipment and medium, and relates to the field of virtualization technology. The method converts the physical disk file generated by the data to be migrated into a virtual disk file in the physical machine, that is, the disk file conversion is performed locally to obtain the disk file used by the cloud computing platform. Since the file conversion is performed locally, no network transmission is required, so the influence of network fluctuations during network transmission is avoided; and the files formed by the data to be migrated are mounted on the blank virtual machine as a unit, rather than mounting the data to be migrated as a unit, so the parallelism of data transmission is improved, the efficiency of data migration is improved, and the file-level migration usually supports the breakpoint resume function. Even if the network connection is interrupted, the transmission can be resumed from the interruption point instead of starting over, which improves the stability and reliability of the migration process. It can be seen that the data can be efficiently and stably migrated to the cloud computing platform.

Description

Technical Field

[0001] The present invention relates to the field of virtualization technology, and in particular to a data migration method, device, product, equipment and medium. Background Art

[0002] With the rapid development and increasing maturity of cloud computing technology, cloud computing has been widely used and popularized in the market, and more and more users are deploying or migrating their business systems to cloud computing platforms. Most of the users' original businesses are deployed on physical servers, and the core business systems cannot be redeployed and configured. Therefore, these business applications and business data need to be migrated from physical servers to virtualized platforms.

[0003] In the related data migration method, the physical machine disk data is copied to the corresponding virtual machine of the cloud computing platform through network transmission. The data copying period is relatively long and is easily affected by the network stability, resulting in low data transmission efficiency and poor stability during the migration process.

[0004] It can be seen that how to efficiently and stably migrate data to a cloud computing platform is a technical problem that people in this field urgently need to solve. Summary of the invention

[0005] The purpose of the present invention is to provide a data migration method, device, product, equipment and medium to solve the technical problems that when copying physical machine disk data to the virtual machine corresponding to the cloud computing platform through network transmission, the data copying time period is relatively long and is easily affected by network stability, resulting in low data transmission efficiency and poor stability during the migration process.

[0006] In order to solve the above technical problems, the present invention provides a data migration method, which is applied to a physical machine. The method comprises:

[0007] Obtaining a physical disk file generated by the data to be migrated;

[0008] Generate a virtual partition according to the physical disk partition information to which the physical disk file belongs;

[0009] Copying the content of the virtual partition into a virtual disk image file to convert the physical disk file into a virtual disk file;

[0010] The virtual disk file is mounted on a blank virtual machine preset on the cloud computing platform.

[0011] On the one hand, before obtaining the physical disk file generated by the data to be migrated, the method further includes:

[0012] Identify data on the physical disk and mark the data type; wherein the data type includes operating system data type and business application data type;

[0013] transmitting an identification of the data type to the data collection tool;

[0014] The data acquisition tool acquires the data on the physical disk according to the data type identifier, and uses the acquired data on the physical disk as the data to be migrated.

[0015] On the other hand, obtaining the physical disk file generated by the data to be migrated includes:

[0016] Get the data type corresponding to the data to be migrated;

[0017] Integrating the data to be migrated that are of the same data type into a data file in a data integration tool according to the data types corresponding to the data to be migrated;

[0018] The data file is converted into a disk file to obtain the physical disk file.

[0019] On the other hand, after obtaining the physical disk file generated by the data to be migrated and before generating the virtual partition according to the physical disk partition information to which the physical disk file belongs, the method further includes:

[0020] Performing a data consistency check on the data on the physical disk and the physical disk file;

[0021] If the data is verified to be consistent, the step of generating a virtual partition according to the physical disk partition information to which the physical disk file belongs is entered;

[0022] If data inconsistency is detected and the physical disk generates new data, the data type of the new data is marked; the new data is collected in the data collection tool according to the data type of the new data, and the new data is transmitted to the data integration tool; the new data is integrated into an incremental data file in the data integration tool; the incremental data file is converted into a physical disk file corresponding to the incremental data, and the step of performing data consistency check on the data on the physical disk and the physical disk file is returned.

[0023] On the other hand, generating a virtual partition according to the physical disk partition information to which the physical disk file belongs includes:

[0024] Using a disk file collector to obtain the physical disk file to be converted from all the physical disk files;

[0025] Identify the disk information of the physical disk file to be converted by a disk type identifier, determine the physical disk partition to which the physical disk file to be converted belongs according to the disk information, and transmit the mark corresponding to the physical disk partition to which the physical disk file to be converted belongs to the disk format converter;

[0026] In the disk format converter, data conversion is performed on the physical disk file to be converted according to the physical disk file to be converted and the physical disk partition to which the physical disk file to be converted belongs, so as to generate the virtual partition.

[0027] On the other hand, copying the content of the virtual partition into a virtual disk image file to convert the physical disk file into a virtual disk file includes:

[0028] Obtaining a preset first target virtual disk format and a storage path corresponding to the virtual disk file;

[0029] Copying the contents of the plurality of virtual partitions to corresponding virtual disk image files respectively;

[0030] The plurality of virtual disk image files are merged to generate the virtual disk file in the first target virtual disk format, and the virtual disk file in the first target virtual disk format is stored according to the storage path to convert the physical disk file into the virtual disk file stored according to the storage path.

[0031] On the other hand, generating a virtual partition according to the physical disk partition information to which the physical disk file belongs includes:

[0032] Get the preset disk conversion rate;

[0033] The virtual partition is generated according to the physical disk partition information to which the physical disk file belongs and according to the disk conversion rate.

[0034] On the other hand, after copying the content of the virtual partition into the virtual disk image file to convert the physical disk file into the virtual disk file, before mounting the virtual disk file to the blank virtual machine preset on the cloud computing platform, it also includes:

[0035] Obtaining a source physical disk file corresponding to the virtual disk file;

[0036] Performing a data consistency check on the virtual disk file and the source physical disk file;

[0037] If the data is verified to be consistent, the step of mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform is entered;

[0038] If the data is inconsistent, the data in the virtual disk file is synchronized with the data in the source physical disk file; and the process returns to the step of performing data consistency check on the virtual disk file and the source physical disk file.

[0039] On the other hand, after merging the plurality of virtual disk image files to generate the virtual disk file in the first target virtual disk format, and storing the virtual disk file in the first target virtual disk format according to the storage path, and before mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform, the method further includes:

[0040] Obtaining a virtual disk format supported by the blank virtual machine;

[0041] Determine whether the first target virtual disk format is a virtual disk format supported by the blank virtual machine;

[0042] If yes, then proceed to the step of mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform;

[0043] If not, prompting the user to select a virtual disk format from the virtual disk formats supported by the blank virtual machine as the second target virtual disk format; receiving the second target virtual disk format input by the user; performing a virtual disk format conversion operation to convert the virtual disk file in the first target virtual disk format into the virtual disk file in the second target virtual disk format;

[0044] The step of mounting the virtual disk file to a blank virtual machine preset on a cloud computing platform includes:

[0045] The virtual disk file in the second target virtual disk format is mounted on a blank virtual machine preset on the cloud computing platform.

[0046] On the other hand, before obtaining the physical disk file generated by the data to be migrated, the method further includes:

[0047] Receive disk conversion tasks;

[0048] Obtaining hard disk information of the operating system corresponding to the disk conversion task;

[0049] When it is determined according to the hard disk information that the physical disk data conversion to be performed in the disk conversion task is to be performed, the step of obtaining the physical disk file generated by the data to be migrated is entered.

[0050] On the other hand, in the case where the virtual disk data conversion to be performed in the disk conversion task is determined according to the hard disk information, the method further includes:

[0051] Obtaining a current virtual disk format corresponding to the virtual disk file to be converted and a third target virtual disk format input by a user; wherein the third target virtual disk format includes at least one virtual disk format, and the third target virtual disk format is a virtual disk format supported by the blank virtual machine;

[0052] In the case where it is detected that the current virtual disk format is different from the third target virtual disk format, performing a virtual disk format conversion operation to convert the to-be-converted virtual disk file in the current virtual disk format into the virtual disk file in the third target virtual disk format;

[0053] The virtual disk file in the third target virtual disk format is mounted on a blank virtual machine preset on a cloud computing platform.

[0054] On the other hand, the performing of the virtual disk format conversion operation includes:

[0055] Parsing the virtual disk file to be converted and obtaining metadata of the virtual disk file to be converted;

[0056] Creating an empty target image file according to the converted virtual disk format and the metadata;

[0057] The read data of the to-be-converted virtual disk file is written into the target image file according to the converted virtual disk format to perform a virtual disk format conversion operation.

[0058] On the other hand, after performing the virtual disk format conversion operation and before mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform, the method further includes:

[0059] Performing a data consistency check on the virtual disk file to be converted and the converted virtual disk file; wherein the converted virtual disk file is a virtual disk file obtained after performing a virtual disk format conversion operation on the virtual disk file to be converted;

[0060] If the data is verified to be consistent, the step of mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform is entered;

[0061] If the data is inconsistent, the data in the virtual disk file to be converted is used to synchronize the data in the converted virtual disk file, and the process returns to the step of checking the data consistency between the virtual disk file to be converted and the converted virtual disk file.

[0062] On the other hand, the data consistency verification method includes at least one of the following:

[0063] Method 1: Obtain the bitmap information of the same data block on the disk where the source data is located and the disk where the destination data is located;

[0064] If it is detected that the bitmap information of the same data block is inconsistent, it is determined that the data is inconsistent;

[0065] If the bitmap information of the same data block is detected to be consistent, it is determined that the data is consistent;

[0066] Method 2: using a preset checksum algorithm to obtain a first checksum of the source data;

[0067] Using the preset checksum algorithm to obtain a second checksum of the destination data;

[0068] In the case where it is detected that the first checksum is different from the second checksum, determining that the checked data is inconsistent;

[0069] When detecting that the first checksum is the same as the second checksum, determining that the checked data are consistent;

[0070] Method three: obtaining a first data volume of the source data and a second data volume of the destination data;

[0071] In the case where it is detected that the first data amount is different from the second data amount, determining that the data is inconsistent;

[0072] In the case where it is detected that the first data amount is the same as the second data amount, determining that the data are verified to be consistent;

[0073] Method 4: Obtaining the number of first files corresponding to the source data and the number of second files corresponding to the target data;

[0074] In the case where it is detected that the number of the first files is different from the number of the second files, determining that the verified data is inconsistent;

[0075] When it is detected that the number of the first files is the same as the number of the second files, it is determined that the verified data is consistent.

[0076] On the other hand, the method of mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform includes at least one of the following:

[0077] Method 1: Upload the virtual disk file to a blank virtual machine preset on a cloud computing platform via the network;

[0078] Method 2: storing the virtual disk file on a mobile storage device;

[0079] The mobile storage device containing the virtual disk file is mounted on a blank virtual machine preset on a cloud computing platform.

[0080] On the other hand, after mounting the virtual disk file to a blank virtual machine preset on a cloud computing platform, the method further includes:

[0081] Responding to the user's operation of starting the virtual machine;

[0082] Checking the information of the virtual machine; wherein the information of the virtual machine includes at least system configuration, application program and business data;

[0083] If the verification is passed, the virtual machine is controlled to switch to the target network, and business applications are provided through the target network; wherein the target network is a network used by the virtual machine to provide business applications.

[0084] In order to solve the above technical problems, the present invention further provides a data migration device, which is applied to a physical machine, and the device comprises:

[0085] A first acquisition module, used for acquiring a physical disk file generated by the data to be migrated;

[0086] A generating module, used for generating a virtual partition according to the physical disk partition information to which the physical disk file belongs;

[0087] A copy module, used for copying the content of the virtual partition into a virtual disk image file to convert the physical disk file into a virtual disk file;

[0088] The mounting module is used to mount the virtual disk file to a blank virtual machine preset on the cloud computing platform.

[0089] In order to solve the above technical problem, the present invention also provides a computer program product, including a computer program / instruction, which implements the steps of the above data migration method when executed by a processor.

[0090] In order to solve the above technical problems, the present invention further provides a data migration device, comprising:

[0091] Memory for storing computer programs;

[0092] A processor is used to implement the steps of the above-mentioned data migration method when executing the computer program.

[0093] In order to solve the above technical problem, the present invention also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above data migration method are implemented.

[0094] The beneficial effect of the present invention is that, in the method, first, the physical disk file generated by the data to be migrated is converted into a virtual disk file in the physical machine, and the generated virtual disk file is used by the cloud computing platform, so that the data is migrated from the physical machine to the cloud computing platform. Secondly, compared with the method of copying the physical machine disk data to the virtual machine corresponding to the cloud computing platform through network transmission, the method provided by the present invention converts the physical disk file generated by the data to be migrated into a virtual disk file in the physical machine, that is, the disk file conversion is performed locally to obtain the disk file used by the cloud computing platform. Since the file conversion is performed locally, the network does not need to be transmitted, so the influence of network fluctuations during network transmission is avoided; and after the disk file conversion is performed locally to obtain the disk file used by the cloud computing platform in the method, the file formed by the data to be migrated is uploaded to the blank virtual machine as a unit, instead of uploading it to the blank virtual machine as a unit of the data to be migrated, so the parallelism of data transmission is improved, that is, the efficiency of data migration is improved, and the file-level migration usually supports the breakpoint resume function, even if the network connection is interrupted, the transmission can be resumed from the interruption point, instead of restarting, which improves the stability and reliability of the migration process. It can be seen that the method provided by the present invention realizes efficient and stable migration of data to the cloud computing platform.

[0095] In addition, the data types corresponding to the data on the physical disk are marked, and the data collection tool collects the data on the physical disk according to the data type, thereby realizing the classified collection and differentiation of the data.

[0096] In the data integration tool, the data to be migrated of the same data type are integrated into data files according to the data types corresponding to the data to be migrated, and then the integrated data files are converted into disk files, that is, the scattered data are integrated into files, and the data is subsequently migrated in units of files, thereby avoiding the situation where the scattered data is easily lost during the migration process and is easily affected by network fluctuations. And because the data types include operating system data types and business application data types, the physical disk files finally obtained in the present invention include system disk files and data disk files, thereby realizing the classification of physical disk files.

[0097] After the data on the physical disk is converted into a physical disk file, a data consistency check is performed. In the event that data inconsistency is detected, the data on the physical disk file is synchronized with the data on the physical disk, thereby ensuring data integrity as much as possible. When data inconsistency is detected and new data is detected on the physical disk, the new data is further collected and processed to form a physical disk file corresponding to the incremental data. The physical disk file corresponding to the incremental data is distinguished from the system disk file and data disk file obtained previously. The physical disk file corresponding to the incremental data is further checked for consistency with the data on the physical disk, thereby ensuring data integrity as much as possible.

[0098] In the process of converting the physical disk file into the virtual disk file, the contents of multiple virtual partitions are copied to the corresponding virtual disk image files respectively; the multiple virtual disk image files are merged to generate a virtual disk file in the first target virtual disk format, so as to realize the integration of the virtual disk image files and store the integrated virtual disk file in the required format. In the conversion process, the physical disk partition is controlled to perform data conversion according to the preset disk conversion rate, so that the disk conversion rate can be flexibly adjusted.

[0099] After converting the physical disk file into a virtual disk file, a data consistency check is performed on the virtual disk file and the source physical disk file. If the data is inconsistent, the data in the virtual disk file is synchronized with the data in the source physical disk file, thereby ensuring that the data in the virtual disk file is consistent with the data in the source physical disk file as much as possible.

[0100] After the virtual disk file in the first target virtual disk format is stored according to the storage path, before the virtual disk file is mounted on the blank virtual machine preset by the cloud computing platform, it is further determined whether the first target virtual disk format is a virtual disk format supported by the blank virtual machine. If it is not a virtual disk format supported by the virtual machine, the second target virtual disk format (i.e., the virtual disk format supported by the virtual machine) input by the user is received, and the virtual disk file in the first target virtual disk format is converted to a virtual disk file in the second target virtual disk format, and then the virtual disk file in the second target virtual disk format is uploaded to the blank virtual machine preset by the cloud computing platform. By performing the virtual disk file format conversion, it is ensured that the virtual machine disk file uploaded to the virtual machine can be adapted by the virtual machine.

[0101] Obtain the hard disk information of the operating system corresponding to the disk conversion task; when it is determined based on the hard disk information that the physical disk data to be converted in the disk conversion task is to be converted, enter the step of obtaining the physical disk file generated by the data to be migrated. The hard disk information is used to achieve accurate judgment of the disk conversion task.

[0102] When the virtual disk data conversion to be performed in the disk conversion task is determined based on the hard disk information, the current virtual disk format corresponding to the virtual disk file to be converted is converted into a third target virtual disk format input by the user to adapt to user needs and virtual machines, thereby achieving the replacement of the cloud computing platform and meeting user needs.

[0103] The virtual disk file to be converted and the converted virtual disk file are checked for data consistency. If the data is inconsistent, the data in the converted virtual disk file is synchronized with the data in the converted virtual disk file using the data in the virtual disk file to be converted, and the process returns to the step of checking the data consistency between the virtual disk file to be converted and the converted virtual disk file. The consistency of the data in the converted virtual disk file and the data in the virtual disk file to be converted is ensured as much as possible.

[0104] Data consistency verification can be performed by one or more of a disk bitmap comparison method, a disk file verification method, a disk data volume comparison method, and a file data comparison method, thereby achieving flexible verification of data consistency.

[0105] When mounting a virtual disk file on a blank virtual machine preset on a cloud computing platform, the virtual disk file can be uploaded to the blank virtual machine preset on the cloud computing platform through the network. The file is transmitted in units, and the impact of network fluctuations in the middle is small and the transmission can be continued. The virtual disk file can also be stored on a mobile storage device; the mobile storage device containing the virtual disk file is mounted on the blank virtual machine preset on the cloud computing platform. Since the network is not required in the process of uploading the virtual disk file to the virtual machine through the mobile storage device, it is not affected by the network stability, and the requirements of high transmission efficiency, high speed and high stability are achieved.

[0106] In addition, the present invention also provides a data migration device, a computer program product, a data migration equipment and a computer-readable storage medium, which have the same or corresponding technical features as the above-mentioned data migration method and have the same effects as above. BRIEF DESCRIPTION OF THE DRAWINGS

[0107] In order to more clearly illustrate the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0108] Figure 1 A schematic diagram of a data migration scenario provided by an embodiment of the present invention;

[0109] Figure 2A flow chart of a data migration method applied to a physical machine provided by an embodiment of the present invention;

[0110] Figure 3 A schematic diagram of an architecture for integrating physical disk data of a server provided by an embodiment of the present invention;

[0111] Figure 4 A flow chart of a method for integrating server physical disk data provided by an embodiment of the present invention;

[0112] Figure 5 A schematic diagram of an architecture for converting a physical disk to a virtual disk provided by an embodiment of the present invention;

[0113] Figure 6 A schematic diagram of the operation of a disk conversion tool provided by an embodiment of the present invention;

[0114] Figure 7 A schematic diagram of the operation of a disk format converter provided by an embodiment of the present invention;

[0115] Figure 8 A schematic diagram of a virtual machine disk format conversion provided by an embodiment of the present invention;

[0116] Fig. 9 A flowchart of a virtual disk converter provided by an embodiment of the present invention;

[0117] Fig.10 A schematic diagram of a process of processing a virtual machine during a data migration process provided by an embodiment of the present invention;

[0118] Fig.11 A schematic diagram of disk data integrity check and synchronization provided by an embodiment of the present invention;

[0119] Fig.12 An overall flow chart of a disk conversion task processing provided by an embodiment of the present invention;

[0120] Fig.13 This is a structural diagram of a data migration device provided in another embodiment of the present invention. DETAILED DESCRIPTION

[0121] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0122] The core of the present invention is to provide a data migration method, device, product, equipment and medium to solve the technical problems that when copying physical machine disk data to the virtual machine corresponding to the cloud computing platform through network transmission, the data copying time cycle will be relatively long and easily affected by network stability, resulting in low data transmission efficiency and poor stability during the migration process.

[0123] In order to enable those skilled in the art to better understand the solution of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. Figure 1 A schematic diagram of a data migration scenario provided by an embodiment of the present invention, such as Figure 1 As shown in FIG. 1 , the scenario includes a physical machine (a bare server without a virtualization platform deployed on the server) and a cloud computing platform. In the physical machine, the data on the physical disk is converted into a virtual disk file, and then the virtual disk file is uploaded to a blank virtual machine preset on the cloud computing platform. Figure 2 A flow chart of a data migration method applied to a physical machine provided by an embodiment of the present invention is as follows: Figure 2 As shown, the method includes:

[0124] S10: Acquire a physical disk file generated by the data to be migrated;

[0125] S11: Generate a virtual partition according to the physical disk partition information to which the physical disk file belongs;

[0126] S12: copying the content of the virtual partition into the virtual disk image file to convert the physical disk file into a virtual disk file;

[0127] S13: Mount the virtual disk file to a blank virtual machine preset on the cloud computing platform.

[0128] Before obtaining the physical disk file generated by the data to be migrated, a disk conversion task is received. Since the disk conversion task may be a physical disk conversion task or a virtual disk conversion task. Therefore, the hard disk information of the operating system corresponding to the disk conversion task is obtained; when it is determined based on the hard disk information that the physical disk data conversion to be performed in the disk conversion task, the step of obtaining the physical disk file generated by the data to be migrated is entered. Specifically, the command: lsblk-o MODEL can be used to view the hard disk information. If the output information is: VIRTUAL-DISK, it is a virtual disk, otherwise it is a physical hard disk of a physical machine.

[0129] The following first describes the process of the physical disk conversion task. Before performing data migration, it is necessary to determine the data to be migrated. When determining the data to be migrated, in order to achieve classified collection of data, in the implementation, the data on the physical disk is identified and the data type is marked; wherein the data type includes the operating system data type and the business application data type;

[0130] transmitting an identification of the data type to the data collection tool;

[0131] The data on the physical disk is collected in the data collection tool according to the data type identifier, and the collected data on the physical disk is used as the data to be migrated.

[0132] There is no limit on the frequency of the data acquisition tool collecting data on the physical disk, which is determined according to the actual situation. After the data to be migrated is obtained, the physical disk file is generated by the data to be migrated.

[0133] Specifically, obtain the data type corresponding to the data to be migrated;

[0134] In the data integration tool, the data to be migrated that belong to the same data type are integrated into a data file according to the data types corresponding to the data to be migrated;

[0135] Convert data files to disk files to obtain physical disk files.

[0136] In the data integration tool, the data to be migrated of the same data type are integrated into data files according to the data types corresponding to the data to be migrated, and then the integrated data files are converted into disk files, that is, the scattered data are integrated into files, and the data is subsequently migrated in units of files, thereby avoiding the situation where the scattered data is easily lost during the migration process and is easily affected by network fluctuations. And because the data types include operating system data types and business application data types, the physical disk files finally obtained in the present invention include system disk files and data disk files, thereby realizing the classification of physical disk files.

[0137] In order to ensure the consistency between the data of the physical disk file and the data on the physical disk, a data consistency check is performed between the data on the physical disk and the physical disk file;

[0138] If the data is verified to be consistent, the step of generating a virtual partition according to the physical disk partition information to which the physical disk file belongs is entered;

[0139] If data inconsistency is detected and the physical disk generates new data, the data type of the new data is marked; the new data is collected according to the data type of the new data in the data collection tool and the new data is transmitted to the data integration tool; the new data is integrated into an incremental data file in the data integration tool; the incremental data file is converted into a physical disk file corresponding to the incremental data, and the step of performing data consistency verification on the data on the physical disk and the physical disk file is returned.

[0140] The above-mentioned conversion of the data on the physical disk into a physical disk file can be considered as a process of integrating the server physical disk data. In order to enable those skilled in the art to better understand the server physical disk data integration method of the present invention, the following will continue to be described in conjunction with the accompanying drawings and specific embodiments. Figure 3 A schematic diagram of a server physical disk data integration architecture provided by an embodiment of the present invention, such as Figure 3 As shown, the operating system data, application data, system configuration information, account and authorization information in the server physical disk data are integrated through the data integration program to generate a system disk file, the business data is integrated through the data integration program to generate a data disk file, and the incremental data is synchronized to generate an incremental data file. The disk integration program is used to integrate the data of the server physical disk. The disk integration program can automatically identify the operating system data and business application data, and integrate the system data and business data into a complete disk file or into a system disk file and multiple data disk files according to customer needs. After completing the disk data integration, the user can choose to automatically perform the disk conversion or manually perform the disk conversion. During the waiting period, if there is a new data increment on the physical disk, the data verification program will perform an integrity comparison and call the data capture program to synchronize the incremental data of the physical disk to the data disk file to form an incremental data block. The data verification synchronization will continue. After the customer issues the disk file conversion task, the data verification synchronization will be performed again. Figure 4 A flow chart of a method for integrating server physical disk data provided by an embodiment of the present invention is shown in FIG. Figure 4 As shown in the figure, after the data integration program is started, in process ①, the data identification program will be called to automatically identify the operating system data and business application data, and the system data and business data will be marked. In process ②, the data identification will be passed to the data collection tool, and the data collection task ③ will be started. The data collection tool will collect data on the physical disk according to the data type identification, and in process ④, the classified data will be passed to the data integration tool in the form of data blocks. The data integration tool will integrate the data blocks into data files and package multiple data files. In process ⑤, the packaged data files will be passed to the disk file generator, and the disk generator will generate the corresponding disk file ⑥ according to the packaged data files, and store them in the disk file transfer platform.

[0141] After the disk file is generated, the data verification program is started. In process ⑨, the data consistency of the physical disk and the integrated disk file is compared periodically. In process ⑦, it is verified that new data is generated on the physical disk. In process ⑧, the data acquisition tool is called, and the data recognition program is called to mark the newly added data type. The data acquisition task is started to capture the incremental data on the disk, and in process ④, the incremental data is passed to the data integration tool. The data integration tool integrates the incremental data blocks into incremental data files, and through ⑤, the data file is generated by the disk file generator, and in process ⑩, a disk incremental data file is generated and stored in the disk file transfer platform.

[0142] In the above, the physical disk data is integrated into a physical disk file. The physical disk file is further converted into a virtual disk file in the physical machine. Generating a virtual partition according to the physical disk partition information to which the physical disk file belongs includes:

[0143] Using a disk file collector to obtain the physical disk file to be converted from all physical disk files;

[0144] Identify the disk information of the physical disk file to be converted by a disk type identifier, determine the physical disk partition to which the physical disk file to be converted belongs according to the disk information, and transmit the mark corresponding to the physical disk partition to which the physical disk file to be converted belongs to the disk format converter;

[0145] In the disk format converter, data conversion is performed on the physical disk file to be converted according to the physical disk file to be converted and the physical disk partition to which the physical disk file to be converted belongs, so as to generate a virtual partition.

[0146] In the process of converting a physical disk file into a virtual disk file, in order to meet the needs of users, the content of the virtual partition is copied into the virtual disk image file to convert the physical disk file into the virtual disk file, including:

[0147] Obtaining a preset first target virtual disk format and a storage path corresponding to the virtual disk file;

[0148] Copy the contents of multiple virtual partitions to corresponding virtual disk image files respectively;

[0149] A plurality of virtual disk image files are merged to generate a virtual disk file in a first target virtual disk format, and the virtual disk file in the first target virtual disk format is stored according to a storage path, so as to convert a physical disk file into a virtual disk file stored according to the storage path.

[0150] During the process of converting a physical disk file into a virtual disk file, a preset disk conversion rate may be obtained; and a virtual partition may be generated according to the physical disk partition information to which the physical disk file belongs and in accordance with the disk conversion rate.

[0151] There is no limitation on the format, storage path and conversion rate of the first target virtual disk, which are determined according to user requirements.

[0152] In order to ensure the consistency of the virtual disk file and the physical disk file data, after the content of the virtual partition is copied to the virtual disk image file to convert the physical disk file into a virtual disk file, before the virtual disk file is mounted on the blank virtual machine preset by the cloud computing platform, the following steps are also included:

[0153] Get the source physical disk file corresponding to the virtual disk file;

[0154] Perform data consistency check on the virtual disk file and the source physical disk file;

[0155] If the data is verified to be consistent, the step of mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform is entered;

[0156] If the data is inconsistent, the data in the virtual disk file is synchronized with the data in the source physical disk file; and the process returns to the step of performing data consistency check on the virtual disk file and the source physical disk file.

[0157] The above process is the process of converting a physical disk file into a virtual disk file. In order to enable those skilled in the art to better understand the process of converting a physical disk file into a virtual disk file of the present invention, the following will continue to explain it in conjunction with the accompanying drawings and specific embodiments. After the physical disk completes data integration, the user can choose to manually or automatically execute the disk format conversion task at the task issuing node. When the task is started, the disk conversion tool starts working. After the physical disk is converted to a virtual disk, the user only needs to create a blank virtual machine on the cloud computing platform, and can directly mount the converted virtual machine disk file, complete the disk mounting and virtual machine resource configuration, and then start the virtual machine. The user confirms the application startup status and data integrity in the virtual machine operating system, and switches the virtual machine to the production network to provide production services to the outside world. Figure 5 A schematic diagram of a physical disk conversion virtual disk architecture provided by an embodiment of the present invention, such as Figure 5As shown, physical disk conversion mainly uses the disk format conversion tool to perform tasks. The physical disk file conversion tool is started and automatically performs the disk format conversion task according to the customer's selection. The disk file collector built into the disk conversion tool obtains the disk file to be converted according to the user's specified, compares the disk identification (Identity, ID) to confirm, and then finds the path of the disk file. After the disk file collector obtains the disk file, the disk type identifier accesses the disk information of the extracted disk file, confirms that the physical disk file to be converted is a system disk partition or a data disk partition, and after integrating the disk information, marks the disk type information and passes it to the disk format converter.

[0158] The disk format converter obtains the original disk file delivered by the disk collector, and starts to execute the disk file conversion task in combination with the disk type information obtained by the disk type identifier. During the disk format conversion, users can use the conversion rate regulator to adjust the disk conversion rate by themselves, or set a fixed conversion rate value at the task delivery node. After the physical disk is converted to a virtual machine disk temporary file, the user can select the target virtual disk format for conversion, which supports: qcow2, raw, vmdk, vhd and vhdx virtual disk formats. It is necessary to provide the storage path of the virtual disk file on the cloud computing platform for storing the converted virtual disk file. After the virtual disk format conversion task is completed, the disk data integrity checker is started to check the data consistency between the converted virtual disk file and the source physical disk. If there is inconsistency between the data of the target disk and the source disk, the disk conversion tool calls the data synchronization tool of the disk converter to start the data synchronization task. The data synchronization work will continue to run until the data consistency check passes and the disk format conversion task is completed.

[0159] Figure 6 A schematic diagram of the operation of a disk conversion tool provided by an embodiment of the present invention. Figure 6 As shown, after the user specifies the source physical disk, the intelligent identification program starts the identification program to authenticate whether the disk is the first operating system or the second operating system. When the user performs the first operating system physical disk conversion task, the disk converter will identify partitions such as / dev / sda and / dev / sdb. The intelligent identification program will scan the files in the partition, confirm that / dev / sda is a system partition and mark it, start the / dev / sda partition data conversion through the data conversion program, generate a virtual system partition of / dev / vda, and then copy the virtual partition vdb to v_disk1 as the system disk. According to the virtual disk format set by the customer as qcow2, a virtual disk file in qcow2 format is generated.

[0160] When the user performs the second operating system disk file conversion task, the intelligent recognition program confirms the following devices based on the file information in the disk: C drive, D drive, CD-ROM drive, Universal Serial Bus (USB) disk, floppy drive, etc., and identifies the C drive as the system disk. The data conversion program starts to convert the \C drive data, generates a virtual \C drive temporary file, and then copies the virtual C drive temporary file to v_disk1 as the system C drive. According to the virtual disk format set by the customer as vmdk, a virtual disk file in vmdk format is generated. After the intelligent recognition program identifies the external CD-ROM drive, USB device, floppy drive, etc. of the second operating system of the source physical machine, the user will be prompted to choose whether to convert this part of the data, and the conversion program will be automatically executed or this part of the device will be filtered according to the customer's choice.

[0161] Figure 7 A schematic diagram of the operation of a disk format converter provided by an embodiment of the present invention is shown in FIG. Figure 7 As shown, the first operating system or the second operating system is identified according to the physical disk file, and the partitions corresponding to the first operating system and the second operating system are queried, such as the first operating system includes the first system disk partition and the first data disk partition; the second operating system includes the second system disk partition and the second data disk partition and an optional conversion device (such as an optical drive, a USB device, and a floppy drive). The first system disk partition is converted into the first virtual system partition, the first data disk partition is converted into the first virtual data partition, the second system disk partition is converted into the second virtual system partition, and the second data disk partition is converted into the second virtual data partition. Afterwards, the first virtual system partition is copied to virtual disk one as a system disk, the first virtual data partition is copied to virtual disk two as a data disk, and the system disk and the data disk are integrated to generate a virtual disk file in the first target format; the second virtual system partition is copied to virtual disk one as a system disk, the second virtual data partition is copied to virtual disk two as a data disk, and the system disk and the data disk are integrated to generate a virtual disk file in the second target format. The first target format and the second target format can be determined according to user needs.

[0162] The following takes the first system disk partition and the first data disk partition included in the first operating system as / dev / sda and / dev / sdb partitions respectively, the first virtual system partition as / dev / vda virtual partition, and the first virtual disk partition as / dev / vdb virtual partition as an example to illustrate the working principle of the data conversion program.

[0163] The working principle of the data conversion program is introduced. The program mainly realizes the technology of converting physical disk files into virtual disk files. The present invention mainly uses the dd method. If the user performs the first operating system data conversion, the main steps are as follows:

[0164] 1) The user logs in to the first operating system using the root account. First, use the fdisk-l command to query the system to find out that there are two partitions, / dev / sda and / dev / sdb. sda is the system disk partition and sdb is the data disk partition.

[0165] 2) The user needs to perform data conversion on both / dev / sda and / dev / sdb partitions. The data conversion program performs partition conversion: the dd command parameter if= represents the source disk, and of= represents the target disk.

[0166] a) Perform / dev / sda partition conversion and use the command: dd if= / dev / sda of= / dev / vda to generate / dev / vda virtual partition;

[0167] b) Perform / dev / sda partition conversion and use the command: dd if= / dev / sdb of= / dev / vdb to generate / dev / vdb virtual partition;

[0168] c) Perform data integrity check. Use the command: cmp / dev / sda / dev / vda to perform data consistency check. If there is no output, the data is consistent. If there is inconsistent data output, data synchronization is required.

[0169] d) If data inconsistency occurs after executing the command in step c), use the command: dd if= / dev / sda of= / dev / vda bs=4M conv=sync to synchronize the data.

[0170] 3) Create a virtual disk image and use the dd command to create an image file of the / dev / vda and / dev / vdb virtual disks. Copy the contents of the virtual partition to the file:

[0171] Run the command: dd if= / dev / vda of=v_disk1.img bs=4M status=progress to copy the data of the / dev / vda partition to a file named v_disk1.img. The data block size for each read and write operation is 4 MB, and the conversion progress can be displayed.

[0172] 4) Use multiple dd commands and seek parameters to merge the v_disk1.img disk image file and the v_disk2.img disk image file to generate a virtual disk file in qcow2 format:

[0173] dd if= v_disk1.img of=vm_disk bs=4M;

[0174] dd if= v_disk2.img of=vm_disk bs=4M seek=1.

[0175] Execute the above two commands to merge the data of v_disk1.img and v_disk2.img into vm_disk, and generate a virtual disk file named vm_disk, such as in the qcow2 format.

[0176] The above steps complete the conversion of the physical disk file into a virtual disk file. After obtaining the virtual disk file, the virtual disk file can be mounted on the virtual machine on the cloud computing platform. There are many mainstream cloud computing technologies at present, and each cloud computing technology has an adapted virtual disk format. Different virtual disk formats cannot be used universally under different cloud computing architectures. For example: the virtual disk format of the first virtualization is qcow2 and raw, and the virtual disk format of the second virtualization is vmdk format. The virtual disk in the vmdk format cannot be directly used on the first virtualization platform, resulting in the inability to flexibly use virtual disks between cloud computing platforms. In order to ensure that the obtained virtual disk file can be supported by the virtual machine, in implementation, after merging multiple virtual disk image files to generate a virtual disk file in the first target virtual disk format, and storing the virtual disk file in the first target virtual disk format according to the storage path, before mounting the virtual disk file to the blank virtual machine preset by the cloud computing platform, it also includes:

[0177] Get the virtual disk format supported by the virtual machine;

[0178] Determine whether the first target virtual disk format is a virtual disk format supported by the blank virtual machine;

[0179] If yes, the process proceeds to the step of mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform;

[0180] If not, prompt the user to select a virtual disk format from the virtual disk formats supported by the blank virtual machine as the second target virtual disk format; receive the second target virtual disk format input by the user; perform a virtual disk format conversion operation to convert the virtual disk file in the first target virtual disk format into a virtual disk file in the second target virtual disk format.

[0181] Mounting a virtual disk file to a blank virtual machine preset on a cloud computing platform includes:

[0182] The virtual disk file in the second target virtual disk format is uploaded to a blank virtual machine preset on the cloud computing platform.

[0183] The virtual disk format conversion operation includes:

[0184] Parsing the virtual disk file to be converted and obtaining metadata of the virtual disk file to be converted;

[0185] Create an empty target image file based on the converted virtual disk format and metadata;

[0186] The data of the virtual disk file to be converted that is read is written into the target image file according to the converted virtual disk format to perform the virtual disk format conversion operation.

[0187] In order to ensure data consistency between the file before and after the virtual disk format conversion, after the virtual disk format conversion operation is performed and before the virtual disk file is mounted on a blank virtual machine preset on the cloud computing platform, the following steps are also included:

[0188] Performing a data consistency check on the virtual disk file to be converted and the converted virtual disk file; wherein the converted virtual disk file is a virtual disk file obtained after performing a virtual disk format conversion operation on the virtual disk file to be converted;

[0189] If the data is verified to be consistent, the step of mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform is entered;

[0190] If the data is inconsistent, the data in the virtual disk file to be converted is used to synchronize the data in the converted virtual disk file, and the process returns to the step of performing data consistency check on the virtual disk file to be converted and the converted virtual disk file.

[0191] There is no limitation on the format of the second target virtual disk, which is determined according to the actual situation. The above process can be considered as a scenario in which the format of the virtual disk file is further converted after the physical disk file is converted into the virtual disk file. In order to enable those skilled in the art to better understand the virtual disk format conversion process of the present invention, it is described below in conjunction with the accompanying drawings and specific embodiments.

[0192] Since different virtual disk formats are not universal under different cloud computing architectures, in the embodiment of the present invention, the cloud computing platform replacement uses a virtual disk format conversion tool to perform disk conversion to adapt to the target cloud computing platform, thereby achieving cloud computing platform replacement.

[0193] The disk conversion tool is designed with a virtual disk conversion module, which can convert the format of virtual machine disk files. When users submit virtual disk format conversion tasks, they only need to enter the virtual machine ID. The disk format conversion tool will automatically identify the virtual machine disk and snapshots, and the virtual disk collector will first start the virtual machine snapshot check program. If the virtual machine has snapshots, start the disk consolidation program, merge the virtual disk file and the snapshot chain file, generate a new disk, submit the information to the virtual disk collector, and use the merged disk to perform the virtual machine disk file format conversion task. Figure 8 A schematic diagram of a virtual machine disk format conversion provided by an embodiment of the present invention, such as Figure 8 As shown, the disk format recognition program confirms that the collected virtual disk is in the first format (such as vmdk format), and passes the disk information to the virtual disk format converter. At the same time, the disk format converter obtains the merged complete disk file from the disk collector, and combines the target disk format set by the user to be the target disk format (such as qcow2 format), and the disk format converter starts the disk format conversion task. According to the storage path selected by the user, the disk format converter generates a virtual machine disk file in the target disk format (such as qcow2 format). The user creates a virtual machine on the cloud computing platform and mounts the converted virtual disk file to generate a new virtual machine to provide application services to the outside world.

[0194] Fig. 9 A flowchart of a virtual disk converter provided by an embodiment of the present invention is shown in FIG. Fig. 9 As shown, the built-in intelligent format identifier of the virtual disk converter obtains the virtual disk file information, and compares and confirms that the virtual disk file to be converted is a first format disk (such as a vmdk format disk) and a second format disk (such as a vhd format disk) according to the format dictionary (such as vmdk, qcow2, raw, vhdx and vhdx formats, etc.). The virtual disk format converter executes the format conversion program. The user inputs the target virtual disk format as: target format one (such as qcow2 format), target format two (such as raw format), target format three (such as vhdx format). It can also be set at the task start node. The disk conversion program calls the format dictionary to obtain the target format, starts to execute the disk format conversion task, and outputs the target as: virtual disk file one of target format one, virtual disk file two of target format two, and virtual disk file three of target format three. It enables users to specify any format of virtual disk files and convert them into any format of virtual disk files, and one source virtual disk file can generate multiple target virtual disk files. Users can use these virtual disk files to generate virtual machines for use on virtualization platforms under various architectures.

[0195] The working principle of the format conversion of virtual disk files mainly involves virtual disk file metadata analysis and data conversion.

[0196] 1. Virtual disk file analysis.

[0197] a. Open disk file: First, according to the virtual disk file path provided by the user, open the source virtual disk file to read the disk data.

[0198] b. Read metadata: Read the metadata of the source virtual disk file, including key information such as file size, cluster size, disk format, etc. This information will be used for the properties of the target virtual file.

[0199] c. Create a target virtual disk file: Create an empty target image file based on the target virtual disk format and metadata information specified by the user. The size and attributes of the target image file are determined based on the metadata of the source file.

[0200] 2. Data conversion.

[0201] Read the data of the source virtual disk file sector by sector and write it to the target virtual disk file according to the specified output format. For example, the command is to convert the vmdk format disk file to qcow2 format:

[0202] qemu-img convert -f vmdk -O qcow2 v_disk1.vmdk vm_disk.qcow2;

[0203] All data is successfully converted and written to the target virtual disk file, the source and target files are closed, and the entire conversion process is completed.

[0204] In the above process, the physical disk is converted into a virtual disk file, and the virtual disk file is converted into a final virtual disk file. In order to mount the final virtual disk file on the virtual machine, data migration is achieved. The method of mounting the virtual disk file on the blank virtual machine preset by the cloud computing platform includes at least one of the following:

[0205] Method 1: Upload the virtual disk file to a blank virtual machine preset on the cloud computing platform through the network;

[0206] Method 2: Store the virtual disk file on a mobile storage device;

[0207] Mount the mobile storage device containing the virtual disk file on the blank virtual machine preset on the cloud computing platform.

[0208] The mobile storage device can be a USB flash drive or other mobile storage device. After the user completes the physical disk conversion, the virtual disk file can be directly obtained. The user can upload it to the target virtualization platform from the local computer. The network fluctuation in the middle has little impact and the upload can be continued. The user can also place the virtual image file on a USB flash drive or other mobile storage device, mount it directly to the virtualization platform server, and copy it to the storage path of the virtualization platform through the physical interface of the server, achieving the requirements of high transmission efficiency, fast speed and high stability.

[0209] In order to ensure that the virtual machine can provide services externally, after mounting the virtual disk file to the blank virtual machine preset by the cloud computing platform, it also includes:

[0210] Responding to the user's operation of starting the virtual machine;

[0211] Checking the information of the virtual machine; wherein the information of the virtual machine includes at least system configuration, application program and business data;

[0212] If the verification is passed, the virtual machine is controlled to switch to the target network, and business applications are provided through the target network; wherein the target network is the network used by the virtual machine to provide business applications.

[0213] In order to enable those skilled in the art to better understand the above-mentioned processing of the virtual machine, it is described below with reference to the accompanying drawings and specific embodiments. Fig.10 A schematic diagram of a process of processing a virtual machine during a data migration process provided by an embodiment of the present invention, such as Fig.10 As shown, a virtual machine is created and configured in the computing platform. The virtual disk file is mounted on the virtual machine, the virtual machine is started, the application configuration and data integrity are checked, and finally the application service is provided. Specifically, the user first creates a blank virtual machine on the cloud computing platform, configures the virtual machine (central processing unit (CPU), memory and network), selects to mount the converted virtual disk file in the disk configuration, and selects to mount the system disk file and the data disk file in turn through the disk file identifier to complete the creation of the virtual machine. The user starts the virtual machine on the cloud computing platform, waits for the operating system to start, checks the system configuration, application program, and business data in the operating system, and after confirming that the relevant information is correct, switches the formal network of the virtual machine, provides business applications to the outside world, completes the conversion from the server physical disk to the virtual machine disk, and achieves the purpose of data migration.

[0214] It is worth noting that the above processes all involve verification of data consistency. The data consistency verification method includes at least one of the following:

[0215] Method 1 (i.e. disk bitmap comparison): obtain the bitmap information of the same data block on the disk where the source data is located and the disk where the destination data is located;

[0216] If it is detected that the bitmap information of the same data block is inconsistent, it is determined that the data is inconsistent;

[0217] If the bitmap information of the same data block is detected to be consistent, it is determined that the verified data is consistent.

[0218] Method 2 (i.e. disk file traversal): use the preset checksum algorithm to obtain the first checksum of the source data;

[0219] Obtain a second checksum of the target data using a preset checksum algorithm;

[0220] In the case where it is detected that the first checksum is different from the second checksum, determining that the checked data is inconsistent;

[0221] When it is detected that the first checksum is identical to the second checksum, it is determined that the checked data are consistent.

[0222] Method three (i.e. disk data volume comparison): obtain the first data volume of the source data and the second data volume of the destination data;

[0223] In the case where it is detected that the first data amount is different from the second data amount, determining that the data is inconsistent;

[0224] When it is detected that the first data amount is the same as the second data amount, determining that the data are verified to be consistent;

[0225] Method 4 (i.e. data file data comparison): obtaining the number of first files corresponding to the source data and the number of second files corresponding to the target data;

[0226] When it is detected that the number of the first file is different from the number of the second file, determining that the data is inconsistent;

[0227] When it is detected that the number of the first file is the same as the number of the second file, it is determined that the verified data is consistent.

[0228] In the process of converting data on a physical disk into a physical disk file, the source data refers to the data on the physical disk, and the destination data refers to the data on the physical disk file; in the process of converting a physical disk file into a virtual disk file, the source data refers to the data on the physical disk file, and the destination data refers to the data on the virtual disk file; in the process of converting the format of a virtual disk file, the source data refers to the data on the virtual disk file before the conversion, and the destination data refers to the data on the virtual disk file after the conversion. Fig.11 A schematic diagram of a disk data integrity check and synchronization provided by an embodiment of the present invention, such as Fig.11 As shown, the source disk and the target disk file can check data consistency by disk bitmap comparison, disk file traversal, disk data volume comparison and data file data comparison. If the data is inconsistent, the data of the source disk is synchronized to the target disk file.

[0229] The above describes the processing of the physical disk conversion task. This embodiment further describes the processing of the virtual disk conversion task. In the case of determining the virtual disk data conversion to be performed in the disk conversion task according to the hard disk information, the data migration method further includes:

[0230] Obtaining a current virtual disk format corresponding to the virtual disk file to be converted and a third target virtual disk format input by a user; wherein the third target virtual disk format includes at least one virtual disk format, and the third target virtual disk format is a virtual disk format supported by the blank virtual machine;

[0231] When it is detected that the current virtual disk format is different from the third target virtual disk format, a virtual disk format conversion operation is performed to convert the to-be-converted virtual disk file in the current virtual disk format into a virtual disk file in the third target virtual disk format;

[0232] The virtual disk file in the third target virtual disk format is mounted to a blank virtual machine preset on the cloud computing platform.

[0233] It is worth noting that the process of converting the virtual disk file to be converted in the current virtual disk format into the virtual disk file in the third target virtual disk format is the same as the method of converting the virtual disk format in the process of processing the physical disk conversion task described above, and will not be repeated here. Similarly, data consistency verification can also be performed after the virtual disk format conversion, and the method of data consistency verification is also the same as the above method, and will not be repeated here.

[0234] The above describes the process of processing a physical disk conversion task and the process of processing a virtual disk conversion task. Fig.12 The overall flow chart of a disk conversion task processing provided by an embodiment of the present invention is as follows: Fig.12 As shown, the method includes:

[0235] S14: Start the task;

[0236] S15: Get disk conversion task;

[0237] S16: Determine whether the disk is a physical disk; if so, proceed to step S17; if not, proceed to step S31;

[0238] S17: confirm that it is a physical disk conversion;

[0239] S18: Disk data integration;

[0240] S19: Get physical disk file;

[0241] S20: disk conversion processing;

[0242] S21: Obtain the converted virtual disk file;

[0243] S22: after obtaining the virtual disk file, determine whether the data is consistent; if not, proceed to step S23; if yes, proceed to step S24;

[0244] S23: Synchronizing data of the virtual disk file using the physical disk file;

[0245] S24: disk format conversion processing;

[0246] S25: Generate target disk file;

[0247] S26: after generating the target disk file, determine whether the data is consistent; if not, proceed to step S27; if yes, proceed to step S28;

[0248] S27: Synchronizing data of the target disk file using the virtual disk file;

[0249] S28: The virtual machine mounts the first target disk file;

[0250] S29: Start the virtual machine;

[0251] S30: Complete the task;

[0252] S31: Determine whether it is a virtual disk conversion;

[0253] S32: disk format identification;

[0254] S33: disk format conversion;

[0255] S34: Generate a second target disk file;

[0256] S35: after generating the second target disk file, determine whether the data is consistent; if not, proceed to step S36; if yes, proceed to step S37;

[0257] S36: Synchronizing data of the second target disk file using the virtual disk file before conversion;

[0258] S37: The virtual machine mounts the second target disk file; and returns to step S29.

[0259] In the method provided in the embodiment of the present invention, the server physical disk is converted into a virtual disk, and at the same time, the shortcomings of low data transmission efficiency, easy failure and poor stability in the process of data migration through the network in the related technology are made up. The physical disk conversion technology of the present invention is mainly executed locally, avoiding the limitations of network fluctuations and low bandwidth during network transmission. After the user completes the physical disk conversion, the virtual disk file can be directly obtained, and the user can upload it to the target virtualization platform on the local computer. The intermediate network fluctuation has little impact and can be continued. The user can also place the virtual image file on a USB flash drive or a mobile storage device, mount it directly on the virtualization platform server, and copy it to the storage path of the virtualization platform through the physical interface of the server, so as to achieve the requirements of high transmission efficiency, high speed and high stability. The present invention also designs data integrity checks for multiple nodes, ensures the data consistency of the source disk file and the target disk file, greatly improves the success rate of data migration, and realizes the lossless, safe and efficient migration of physical machine business applications and business data to the cloud computing platform. Avoid the human investment in business impact redeployment and reduce the time investment and integrity issues of manual copying of business data. Disk data integration technology can be used to integrate data in multiple scenarios. In physical machines, data files can be integrated into disk files. Combined with data identification programs, operating system files and business data files can be integrated into disk files respectively. In cloud computing scenarios, virtual disks and snapshot chains can be integrated. Data integration technology can be used in physical disk merging, virtual disk backup and other scenarios. The full automation of disk conversion reduces the probability of manual intervention errors, realizes safe and efficient data migration, concurrent task execution, speeds up the business migration cycle, and reduces labor cost investment. Virtual disk format conversion realizes mutual conversion between multiple formats, improves the cloud computing adaptation of virtual disks under multiple architectures, and reduces the time investment of virtual disk data migration back and forth. Through disk data consistency verification, data synchronization problems in the disk conversion process are solved. The verification program will detect the target disk data in real time and compare the integrity with the source disk. If there is data increment, the data synchronization program will be started to synchronize data, improve data integrity and ensure data security, reduce repeated migration work caused by incomplete data, shorten the project implementation cycle, and reduce labor cost investment.

[0260] In the above embodiments, the data migration method is described in detail, and the present invention also provides corresponding embodiments of the data migration device and the data migration equipment. It should be noted that the present invention describes the embodiments of the device part from two perspectives, one is based on the functional module perspective, and the other is based on the hardware perspective.

[0261] An embodiment of the present invention provides a data migration device, which, based on the perspective of functional modules, includes:

[0262] A first acquisition module, used for acquiring a physical disk file generated by the data to be migrated;

[0263] A generation module, used for generating a virtual partition according to the physical disk partition information to which the physical disk file belongs;

[0264] A copy module, used for copying the content of the virtual partition into a virtual disk image file to convert the physical disk file into a virtual disk file;

[0265] The mounting module is used to mount the virtual disk file to the blank virtual machine preset on the cloud computing platform.

[0266] In some embodiments, the data migration device further includes:

[0267] An identification and marking module, used to identify data on the physical disk and mark the data type; wherein the data type includes an operating system data type and a business application data type;

[0268] a transmission module for transmitting the identification of the data type to the data collection tool;

[0269] The acquisition module is used to acquire data on the physical disk according to the data type identifier in the data acquisition tool, and use the acquired data on the physical disk as data to be migrated.

[0270] In some embodiments, the data migration device further includes:

[0271] A first verification module performs data consistency verification on the data on the physical disk and the physical disk file;

[0272] A first trigger module is used to trigger the generation module if the data is verified to be consistent;

[0273] The marking and transmission module is used to mark the data type of the new data if data inconsistency is detected and the physical disk generates new data; collect the new data according to the data type of the new data in the data collection tool, and transmit the new data to the data integration tool; integrate the new data into an incremental data file in the data integration tool; convert the incremental data file into a physical disk file corresponding to the incremental data, and return to trigger the first verification module.

[0274] In some embodiments, the data migration device further includes:

[0275] The second acquisition module is used to acquire the source physical disk file corresponding to the virtual disk file;

[0276] The second verification module is used to perform data consistency verification on the virtual disk file and the source physical disk file;

[0277] The second trigger module is used to trigger the mounting module if the data is verified to be consistent;

[0278] The first data synchronization module is used to synchronize the data in the virtual disk file with the data in the source physical disk file if the data is inconsistent; and return to trigger the second verification module.

[0279] In some embodiments, the data migration device further includes:

[0280] A third acquisition module is used to acquire the virtual disk format supported by the virtual machine;

[0281] A judgment module, used to judge whether the format of the first target virtual disk is a virtual disk format supported by the blank virtual machine; if so, trigger the mounting module, if not, trigger the prompt module;

[0282] The prompt module is used to prompt the user to select a virtual disk format from the virtual disk formats supported by the virtual machine as the second target virtual disk format; receive the second target virtual disk format input by the user; and perform a virtual disk format conversion operation to convert the virtual disk file in the first target virtual disk format into a virtual disk file in the second target virtual disk format.

[0283] In some embodiments, the data migration device further includes:

[0284] A receiving module, used for receiving a disk conversion task;

[0285] The fourth acquisition module is used to acquire the hard disk information of the operating system corresponding to the disk conversion task;

[0286] The third triggering module is used to trigger the first acquiring module when it is determined according to the hard disk information that physical disk data conversion is to be performed in the disk conversion task.

[0287] In some embodiments, the data migration device further includes:

[0288] A fifth acquisition module, used to acquire the current virtual disk format corresponding to the virtual disk file to be converted and a third target virtual disk format input by the user; wherein the third target virtual disk format includes at least one virtual disk format, and the third target virtual disk format is a virtual disk format supported by the blank virtual machine;

[0289] a conversion module, configured to, when detecting that the current virtual disk format is different from the third target virtual disk format, perform a virtual disk format conversion operation to convert the to-be-converted virtual disk file in the current virtual disk format into a virtual disk file in the third target virtual disk format;

[0290] The mounting submodule is used to mount the virtual disk file in the third target virtual disk format to a blank virtual machine preset on the cloud computing platform.

[0291] In some embodiments, the data migration device further includes:

[0292] A third verification module is used to perform data consistency verification on the virtual disk file to be converted and the converted virtual disk file; wherein the converted virtual disk file is a virtual disk file obtained after performing a virtual disk format conversion operation on the virtual disk file to be converted;

[0293] The fourth trigger module is used to trigger the mounting module if the data is verified to be consistent;

[0294] The second data synchronization module is used to synchronize the data in the converted virtual disk file with the data in the virtual disk file to be converted if the data is inconsistent, and return to trigger the third verification module.

[0295] In some embodiments, the data migration device further includes:

[0296] A response module, used for responding to a user's operation of starting a virtual machine;

[0297] A verification module, used to verify the information of the virtual machine; wherein the information of the virtual machine includes at least system configuration, application program and business data;

[0298] The switching module is used to control the virtual machine to switch to the target network and provide business applications through the target network when the verification is passed; wherein the target network is the network used by the virtual machine to provide business applications.

[0299] Since the embodiments of the apparatus part correspond to the embodiments of the method part, please refer to the description of the embodiments of the method part for the embodiments of the apparatus part, which will not be repeated here.

[0300] Fig.13 This is a structural diagram of a data migration device provided by another embodiment of the present invention. This embodiment is based on the hardware perspective, such as Fig.13 As shown, the data migration device includes:

[0301] A memory 20, for storing computer programs;

[0302] The processor 21 is used to implement the steps of the data migration method mentioned in the above embodiment when executing the computer program.

[0303] Among them, the processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 21 can be implemented in at least one hardware form of a digital signal processor (DSP), a field-programmable gate array (FPGA), and a programmable logic array. The processor 21 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU; the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 21 may be integrated with a graphics processing unit (GPU), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 21 may also include an artificial intelligence (AI) processor, which is used to process computing operations related to machine learning.

[0304] The memory 20 may include one or more computer-readable storage media, which may be non-transitory. The memory 20 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory 20 is at least used to store the following computer program 201, wherein, after the computer program is loaded and executed by the processor 21, it can implement the relevant steps of the data migration method disclosed in any of the aforementioned embodiments. In addition, the resources stored in the memory 20 may also include an operating system 202 and data 203, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 202 may include Windows, Unix, Linux, etc. The data 203 may include, but is not limited to, the data involved in the above-mentioned data migration method, etc.

[0305] In some embodiments, the data migration device may further include a display screen 22 , an input / output interface 23 , a communication interface 24 , a power supply 25 , and a communication bus 26 .

[0306] Those skilled in the art will understand that Fig.13 The structure shown in the figure does not constitute a limitation on the data migration device, and may include more or fewer components than those shown in the figure.

[0307] The data migration device provided by the embodiment of the present invention includes a memory and a processor. When the processor executes the program stored in the memory, it can implement the following method: a data migration method, the effect is the same as above.

[0308] An embodiment of the present invention further provides a computer program product, including a computer program / instruction, which implements the steps of the above-mentioned data migration method when executed by a processor.

[0309] Finally, the present invention also provides an embodiment corresponding to a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps recorded in the above method embodiment are implemented.

[0310] It is understandable that if the method in the above embodiment is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc. Various media that can store program codes.

[0311] The computer-readable storage medium provided by the present invention includes the above-mentioned data migration method, and the effect is the same as above.

[0312] The above is a detailed introduction to a data migration method, device, product, equipment and medium provided by the present invention. The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the embodiments can be referenced to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description. It should be pointed out that for ordinary technicians in this technical field, without departing from the principle of the present invention, several improvements and modifications can be made to the present invention, and these improvements and modifications also fall within the scope of protection of the present invention.

[0313] It should also be noted that, in this specification, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

Claims

1. A data migration method, characterized in that: Applied to a physical machine, the method comprises: Acquire a physical disk file generated by the data to be migrated; wherein, the data to be migrated is integrated into a data file, and a physical disk file is generated according to the data file; the data type corresponding to the data on the physical disk is marked, and the data on the physical disk is collected as the data to be migrated according to the data type; and data consistency check is performed on the data on the physical disk and the physical disk file; Generate a virtual partition according to the physical disk partition information to which the physical disk file belongs; Copying the content of the virtual partition into a virtual disk image file to convert the physical disk file into a virtual disk file; performing a data consistency check on the virtual disk file and the source physical disk file; Mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform; Generating a virtual partition according to the physical disk partition information to which the physical disk file belongs includes: Using a disk file collector to obtain the physical disk file to be converted from all the physical disk files; Identify the disk information of the physical disk file to be converted by a disk type identifier, determine the physical disk partition to which the physical disk file to be converted belongs according to the disk information, and transmit the mark corresponding to the physical disk partition to which the physical disk file to be converted belongs to the disk format converter; In the disk format converter, data conversion is performed on the physical disk file to be converted according to the physical disk file to be converted and the physical disk partition to which the physical disk file to be converted belongs, so as to generate the virtual partition.

2. The data migration method according to claim 1, characterized in that: Before obtaining the physical disk file generated by the data to be migrated, the method further includes: Identify data on the physical disk and mark the data type; wherein the data type includes operating system data type and business application data type; transmitting an identification of the data type to the data collection tool; The data acquisition tool acquires the data on the physical disk according to the data type identifier, and uses the acquired data on the physical disk as the data to be migrated.

3. The data migration method according to claim 2, characterized in that: The obtaining of the physical disk file generated by the data to be migrated includes: Get the data type corresponding to the data to be migrated; Integrating the data to be migrated that are of the same data type into a data file in a data integration tool according to the data types corresponding to the data to be migrated; The data file is converted into a disk file to obtain the physical disk file.

4. The data migration method according to claim 3, characterized in that: After obtaining the physical disk file generated by the data to be migrated and before generating the virtual partition according to the physical disk partition information to which the physical disk file belongs, the method further includes: Performing a data consistency check on the data on the physical disk and the physical disk file; If the data is verified to be consistent, the step of generating a virtual partition according to the physical disk partition information to which the physical disk file belongs is entered; If data inconsistency is detected and the physical disk generates new data, the data type of the new data is marked; the new data is collected in the data collection tool according to the data type of the new data, and the new data is transmitted to the data integration tool; the new data is integrated into an incremental data file in the data integration tool; the incremental data file is converted into a physical disk file corresponding to the incremental data, and the step of performing data consistency check on the data on the physical disk and the physical disk file is returned.

5. The data migration method according to claim 1, characterized in that: Copying the content of the virtual partition into a virtual disk image file to convert the physical disk file into a virtual disk file includes: Obtaining a preset first target virtual disk format and a storage path corresponding to the virtual disk file; Copying the contents of the plurality of virtual partitions to corresponding virtual disk image files respectively; The plurality of virtual disk image files are merged to generate the virtual disk file in the first target virtual disk format, and the virtual disk file in the first target virtual disk format is stored according to the storage path to convert the physical disk file into the virtual disk file stored according to the storage path.

6. The data migration method according to claim 1, characterized in that: Generating a virtual partition according to the physical disk partition information to which the physical disk file belongs includes: Get the preset disk conversion rate; The virtual partition is generated according to the physical disk partition information to which the physical disk file belongs and according to the disk conversion rate.

7. The data migration method according to claim 5, characterized in that: After the content of the virtual partition is copied into the virtual disk image file to convert the physical disk file into the virtual disk file, and before the virtual disk file is mounted on the blank virtual machine preset by the cloud computing platform, the method further includes: Obtaining a source physical disk file corresponding to the virtual disk file; Performing a data consistency check on the virtual disk file and the source physical disk file; If the data is verified to be consistent, the step of mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform is entered; If the data is inconsistent, the data in the virtual disk file is synchronized with the data in the source physical disk file; and the process returns to the step of performing data consistency check on the virtual disk file and the source physical disk file.

8. The data migration method according to claim 5, characterized in that: After merging the plurality of virtual disk image files to generate the virtual disk file in the first target virtual disk format, and storing the virtual disk file in the first target virtual disk format according to the storage path, and before mounting the virtual disk file to a blank virtual machine preset on a cloud computing platform, the method further includes: Obtaining a virtual disk format supported by the blank virtual machine; Determine whether the first target virtual disk format is a virtual disk format supported by the blank virtual machine; If yes, then proceed to the step of mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform; If not, prompting the user to select a virtual disk format from the virtual disk formats supported by the blank virtual machine as the second target virtual disk format; receiving the second target virtual disk format input by the user; performing a virtual disk format conversion operation to convert the virtual disk file in the first target virtual disk format into the virtual disk file in the second target virtual disk format; The step of mounting the virtual disk file to a blank virtual machine preset on a cloud computing platform includes: The virtual disk file in the second target virtual disk format is mounted on a blank virtual machine preset on the cloud computing platform.

9. The data migration method according to claim 1, characterized in that: Before obtaining the physical disk file generated by the data to be migrated, the method further includes: Receive disk conversion tasks; Obtaining hard disk information of the operating system corresponding to the disk conversion task; When it is determined according to the hard disk information that the physical disk data conversion to be performed in the disk conversion task is to be performed, the step of obtaining the physical disk file generated by the data to be migrated is entered.

10. The data migration method according to claim 9, characterized in that: In the case where the virtual disk data conversion to be performed in the disk conversion task is determined according to the hard disk information, the method further includes: Obtaining a current virtual disk format corresponding to the virtual disk file to be converted and a third target virtual disk format input by a user; wherein the third target virtual disk format includes at least one virtual disk format, and the third target virtual disk format is a virtual disk format supported by the blank virtual machine; In the case where it is detected that the current virtual disk format is different from the third target virtual disk format, performing a virtual disk format conversion operation to convert the to-be-converted virtual disk file in the current virtual disk format into the virtual disk file in the third target virtual disk format; The virtual disk file in the third target virtual disk format is mounted on a blank virtual machine preset on a cloud computing platform.

11. The data migration method according to claim 10, characterized in that: The performing of the virtual disk format conversion operation includes: Parsing the virtual disk file to be converted and obtaining metadata of the virtual disk file to be converted; Creating an empty target image file according to the converted virtual disk format and the metadata; The read data of the to-be-converted virtual disk file is written into the target image file according to the converted virtual disk format to perform a virtual disk format conversion operation.

12. The data migration method according to claim 11, characterized in that: After performing the virtual disk format conversion operation and before mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform, the method further includes: Performing a data consistency check on the virtual disk file to be converted and the converted virtual disk file; wherein the converted virtual disk file is a virtual disk file obtained after performing a virtual disk format conversion operation on the virtual disk file to be converted; If the data is verified to be consistent, the step of mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform is entered; If the data is inconsistent, the data in the virtual disk file to be converted is used to synchronize the data in the converted virtual disk file, and the process returns to the step of checking the data consistency between the virtual disk file to be converted and the converted virtual disk file.

13. The data migration method according to any one of claims 4, 7 or 12, characterized in that: The data consistency verification method includes at least one of the following: Method 1: Obtain the bitmap information of the same data block on the disk where the source data is located and the disk where the destination data is located; If it is detected that the bitmap information of the same data block is inconsistent, it is determined that the data is inconsistent; If the bitmap information of the same data block is detected to be consistent, it is determined that the data is consistent; Method 2: using a preset checksum algorithm to obtain a first checksum of the source data; Using the preset checksum algorithm to obtain a second checksum of the destination data; In the case where it is detected that the first checksum is different from the second checksum, determining that the checked data is inconsistent; When detecting that the first checksum is the same as the second checksum, determining that the checked data are consistent; Method three: obtaining a first data volume of the source data and a second data volume of the destination data; In the case where it is detected that the first data amount is different from the second data amount, determining that the data is inconsistent; In the case where it is detected that the first data amount is the same as the second data amount, determining that the data are verified to be consistent; Method 4: Obtaining the number of first files corresponding to the source data and the number of second files corresponding to the target data; In the case where it is detected that the number of the first files is different from the number of the second files, determining that the verified data is inconsistent; When it is detected that the number of the first files is the same as the number of the second files, it is determined that the verified data is consistent.

14. The data migration method according to claim 1, characterized in that: The method of mounting the virtual disk file to a blank virtual machine preset on the cloud computing platform includes at least one of the following: Method 1: Upload the virtual disk file to a blank virtual machine preset on a cloud computing platform via the network; Method 2: storing the virtual disk file on a mobile storage device; The mobile storage device containing the virtual disk file is mounted on a blank virtual machine preset on a cloud computing platform.

15. The data migration method according to claim 1, characterized in that: After mounting the virtual disk file to a blank virtual machine preset on a cloud computing platform, the method further includes: Responding to the user's operation of starting the virtual machine; Checking the information of the virtual machine; wherein the information of the virtual machine includes at least system configuration, application program and business data; If the verification is passed, the virtual machine is controlled to switch to the target network, and business applications are provided through the target network; wherein the target network is a network used by the virtual machine to provide business applications.

16. A data migration device, characterized in that: Applied to a physical machine, the device comprises: A first acquisition module is used to acquire a physical disk file generated by the data to be migrated; wherein the data to be migrated is integrated into a data file, and a physical disk file is generated according to the data file; Marking the data type corresponding to the data on the physical disk, collecting the data on the physical disk as the data to be migrated according to the data type; performing data consistency check on the data on the physical disk and the physical disk file; A generating module, used for generating a virtual partition according to the physical disk partition information to which the physical disk file belongs; A copy module, used for copying the content of the virtual partition into a virtual disk image file to convert the physical disk file into a virtual disk file; Perform data consistency check on the virtual disk file and the source physical disk file; A mounting module, used to mount the virtual disk file to a blank virtual machine preset on the cloud computing platform; The generation module is specifically used for: Using a disk file collector to obtain the physical disk file to be converted from all the physical disk files; Identify the disk information of the physical disk file to be converted by a disk type identifier, determine the physical disk partition to which the physical disk file to be converted belongs according to the disk information, and transmit the mark corresponding to the physical disk partition to which the physical disk file to be converted belongs to the disk format converter; In the disk format converter, data conversion is performed on the physical disk file to be converted according to the physical disk file to be converted and the physical disk partition to which the physical disk file to be converted belongs, so as to generate the virtual partition.

17. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the data migration method described in any one of claims 1 to 15 are implemented.

18. A data migration device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the data migration method as described in any one of claims 1 to 15 when executing the computer program.

19. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the data migration method according to any one of claims 1 to 15 are implemented.

Images