A data migration system and method from a physical machine to a virtual machine

Abstract

The invention discloses a data migration system from a physical machine to a virtual machine, wherein both the physical machine and the virtual machine can be connected to a migration integrated machine through a migration server, and a method based on the system is also disclosed, wherein a proxy client is installed on the physical machine, and the physical machine is restarted; the proxy client is opened and connected to the migration server; the migration integrated machine is connected to the migration server, and the data content of the system disk is received through the migration server; after a virtual machine is created on the migration integrated machine, the virtual machine is started through the RecoveryCD optical disc system; after the relevant parameters of the virtual machine are configured, the virtual machine reads the recovery data content on the migration integrated machine; the migration integrated machine is restarted to complete the data migration; the recovery data content of the virtual machine is checked, and compared with the data content of the physical machine. When the physical machine fails, the physical machine can be restarted immediately so that the new virtual machine can be reactivated to ensure the continuity of the business, and at the same time, the integrity of the data in the virtual machine can be ensured.

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a data migration system from a physical machine to a virtual machine and a method thereof. Background Art

[0002] At present, there is a problem with the migration method from physical machine to virtual machine on the market. When the physical machine fails, the migrated virtual machine cannot be started and used. There are many modules that need to be considered in the migration from physical machine to virtual machine. After the migration is completed, it is necessary to ensure that the machine can run. Therefore, for a data migration system and method from physical machine to virtual machine, the problem that the virtual machine cannot be started and used when the physical machine fails is what we need to solve. Summary of the invention

[0003] In order to overcome the above shortcomings, the purpose of the present invention is to provide a data migration system and method from a physical machine to a virtual machine. When a physical machine fails, the physical machine can be restarted immediately so that a new virtual machine can be reactivated to ensure business continuity while ensuring the integrity of the data in the virtual machine.

[0004] In order to achieve the above objectives, the technical solution adopted by the present invention is: a data migration system from a physical machine to a virtual machine, including a physical machine, a migration machine and a virtual machine set on the migration machine, and both the physical machine and the virtual machine can be connected to the migration machine through a migration server.

[0005] The beneficial effect of the data migration system from a physical machine to a virtual machine of the present invention is that both the physical machine and the virtual machine can be connected to the migration integrated machine through the migration server. The physical machine is protected and the data is copied to ensure that there is a completely identical data content in the migration integrated machine, and the virtual machine reads the data content on the migration integrated machine. In this way, the physical machine that needs to be migrated can be reactivated in the virtual machine environment, while avoiding the compatibility problem and the driver version problem required by the physical machine, so that the new virtual machine can be reactivated.

[0006] As a further improvement of the present invention, it also includes a proxy client for communicating with the migration server, and the proxy client is installed on the physical machine. The iSCSI component is manually started on the physical machine, and after the proxy client is installed on the physical machine, the physical machine is restarted.

[0007] As a further improvement of the present invention, an iSCSI component is provided on the physical machine.

[0008] As a further improvement of the present invention, it also includes a RecoveryCD optical disc system for starting the virtual machine, and the RecoveryCD optical disc system is set on the migration machine. The virtual machine is started with the RecoveryCD optical disc system. After entering the virtual machine, the relevant parameters of the virtual machine are configured, including the startup item copy, address, etc. The recovery wizard of the RecoveryCD optical disc system is entered, and after reading the data content on the migration machine, the data content is recovered to obtain the recovery data content.

[0009] As a further improvement of the present invention, it also includes snapshot resources mounted on the migration machine. The migration machine is also mounted with snapshot resources to improve and ensure that the synchronized data can be used, and can also be allocated to other machines for use to ensure that the data content is not damaged.

[0010] The present invention also provides a method for data migration from a physical machine to a virtual machine, comprising the following steps:

[0011] Step 1: Install the proxy client on the physical machine, start the iSCSI component on the physical machine, and then restart the physical machine;

[0012] Step 2: Open the proxy client and connect it to the migration server, then select disk protection for the system disk of the physical machine;

[0013] Step 3: The migration machine is connected to the migration server and receives the data content of the system disk through the migration server;

[0014] Step 4: After creating a virtual machine on the migration machine, import the RecoveryCD system on the migration machine and start the virtual machine through the RecoveryCD system.

[0015] Step 5: After configuring the relevant parameters of the virtual machine, the RecoveryCD system first recovers the data content on the migration machine to obtain the recovery data content, and then connects the virtual machine to the migration server, and the virtual machine reads the recovery data content on the migration machine;

[0016] Step 6: Restart the migration machine to complete data migration.

[0017] Step 7: Check the restored data content of the virtual machine and compare it with the data content of the physical machine.

[0018] The present invention discloses a method for data migration from a physical machine to a virtual machine. The iSCSI component is manually enabled on the physical machine, and after the proxy client is installed on the physical machine, the physical machine is restarted. After the proxy client is enabled and connected to a migration server, disk protection is selected to protect the system disk of the physical machine. The migration integrated machine is connected to the migration server, and with the help of a guide frame, a disk with the same capacity as the system disk is allocated on the migration integrated machine, and the system disk of the physical machine is synchronized through the migration server. Wait for the system disk to transfer data to the migration integrated machine in a 1:1 ratio, and after the transfer is completed, the data content of the system disk can be viewed on the migration integrated machine.

[0019] Create a virtual machine on the migration machine, then import the RecoveryCD system, and use the RecoveryCD system to start the virtual machine. After entering the virtual machine, configure the relevant parameters of the virtual machine, including the boot item copy, address, etc. Enter the recovery wizard of the RecoveryCD system, and after reading the data content on the migration machine, perform recovery to obtain the recovery data content. The virtual machine is connected to the migration server, and the virtual machine reads the recovery data content on the migration machine. The RecoveryCD system will determine the specific data recovery speed based on the actual hard disk configuration of the migration machine.

[0020] The time required for data content transmission is determined based on the amount of data content on the physical machine. After waiting for the data content to be transmitted to the virtual machine, the migration machine is restarted to restart the virtual machine. After the restart is completed, the data content on the physical machine is completely migrated to the virtual machine.

[0021] Finally, check the data content of the virtual machine and compare it with the data content of the physical machine. After the check is completed, not only can the virtual machine run, but also ensure that the data content is not lost.

[0022] Breaking the existing conventional solution, the physical machine is protected and the data is copied without destroying the infrastructure of the physical machine to ensure that there is a completely identical copy of the data in the migration machine, so that the physical machine to be migrated can be reactivated in the virtual machine environment, avoiding the compatibility issues and driver version issues required by the physical machine, so that the new virtual machine can be reactivated. At the same time, the integrity of the data content is also determined.

[0023] As a further improvement of the present invention, step 3 includes the following steps: step 31, a disk with the same capacity as the system disk is allocated on the migration machine, and the proxy client synchronizes the data content of the system disk to the disk of the migration machine through the migration server; step 32, a snapshot resource is also mounted on the migration machine. With the help of the guide frame, a disk with the same capacity as the system disk is allocated on the migration machine to synchronize the system disk of the physical machine. The migration machine is also mounted with snapshot resources and the like for improvement to ensure that the synchronized data can be used, and can also be allocated to other machines for use to ensure that the data content is not damaged. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 This is a structural block diagram of the first embodiment.

[0025] In the figure:

[0026] 1-Physical machine; 2-Migration machine; 3-Virtual machine; 4-RecoveryCD system. DETAILED DESCRIPTION

[0027] The preferred embodiments of the present invention are described in detail below in conjunction with the accompanying drawings so that the advantages and features of the present invention can be more easily understood by those skilled in the art, thereby making a clearer and more definite definition of the protection scope of the present invention.

[0028] Example 1

[0029] See attached Figure 1 As shown, this embodiment 1 is a data migration system from a physical machine 1 to a virtual machine 3, including a physical machine 1, a migration machine 2 and a virtual machine 3 arranged on the migration machine 2. Both the physical machine 1 and the virtual machine 3 can be connected to the migration machine 2 through a migration server.

[0030] Both physical machine 1 and virtual machine 3 can be connected to migration machine 2 through the migration server. Physical machine 1 is protected and data is copied to ensure that a completely identical data content is in migration machine 2, and virtual machine 3 reads the data content on migration machine 2. In this way, the physical machine 1 to be migrated can be reactivated in the environment of virtual machine 3, avoiding the compatibility issues and driver version issues required by physical machine 1, so that the new virtual machine 3 can be reactivated.

[0031] This embodiment 1 also includes a proxy client for communicating with the migration server, and the proxy client is installed on the physical machine 1. The iSCSI component is manually enabled on the physical machine 1, and after the proxy client is installed on the physical machine 1, the physical machine 1 is restarted.

[0032] In this embodiment 1, the physical machine 1 is provided with an iSCSI component.

[0033] The present embodiment 1 further includes a RecoveryCD optical disc system 4 for starting the virtual machine 3, and the RecoveryCD optical disc system 4 is set on the migration machine 2. The virtual machine 3 is started with the RecoveryCD optical disc system 4. After entering the virtual machine 3, the relevant parameters of the virtual machine 3 are configured, including the boot item copy, address, etc. The recovery wizard of the RecoveryCD optical disc system 4 is entered, and after reading the data content on the migration machine 2, the data content is recovered to obtain the recovery data content.

[0034] This embodiment 1 also includes snapshot resources mounted on the migration machine 2. The migration machine 2 is also mounted with snapshot resources to improve and ensure that the synchronized data can be used, and can also be allocated to other machines for use to ensure that the data content is not damaged.

[0035] Example 2

[0036] A method for data migration from a physical machine 1 to a virtual machine 3 of the present invention comprises the following steps:

[0037] Step 1: Install the proxy client on physical machine 1, start the iSCSI component on physical machine 1, and then restart physical machine 1;

[0038] Step 2: Open the proxy client and connect it to the migration server, and then select disk protection for the system disk of physical machine 1;

[0039] Step 3: The migration machine 2 is connected to the migration server and receives the data content of the system disk through the migration server;

[0040] Step 4, after the virtual machine 3 is created on the migration machine 2, the RecoveryCD optical disc system 4 is imported into the migration machine 2, and the virtual machine 3 is started through the RecoveryCD optical disc system 4. Meanwhile, the RecoveryCD optical disc system 4 can restore the data content on the migration machine 2 to obtain the restored data content;

[0041] Step 5: After configuring the relevant parameters of the virtual machine 3, the virtual machine 3 is connected to the migration server, and the virtual machine 3 reads the recovery data content on the migration machine 2;

[0042] Step 6: Restart the migration machine 2 to complete the data migration.

[0043] Step 7: Check the restored data content of virtual machine 3 and compare it with the data content of physical machine 1.

[0044] Manually enable the iSCSI component on physical machine 1, install the proxy client on physical machine 1, and then restart physical machine 1. After opening the proxy client and connecting to the migration server, select disk protection to protect the system disk of physical machine 1. Migration machine 2 is connected to the migration server. With the help of the guide frame, allocate a disk with the same capacity as the system disk on migration machine 2, and synchronize the system disk of physical machine 1 through the migration server. Wait for the system disk to transfer the data to migration machine 2 in a 1:1 ratio. After the transfer is completed, the data content of the system disk can be seen on migration machine 2.

[0045] Create a virtual machine 3 on the migration machine 2, then import the RecoveryCD optical disc system 4, and use the RecoveryCD optical disc system 4 to start the virtual machine 3. After entering the virtual machine 3, configure the relevant parameters of the virtual machine 3, including the boot item copy, address, etc. Enter the recovery wizard of the RecoveryCD optical disc system 4, and after reading the data content on the migration machine 2, perform recovery to obtain the recovery data content. The virtual machine 3 is connected to the migration server, and the virtual machine 3 reads the recovery data content on the migration machine 2. The RecoveryCD optical disc system 4 will determine the specific data recovery speed according to the actual hard disk configuration of the migration machine 2.

[0046] The time required for data content transmission is determined according to the amount of data content in physical machine 1. After waiting for the data content to be transmitted to virtual machine 3, migration machine 2 is restarted to restart virtual machine 3. After the restart is completed, the data content in physical machine 1 is completely migrated to virtual machine 3.

[0047] Finally, the data content of virtual machine 3 is checked and compared with the data content of physical machine 1. After the check is completed, not only virtual machine 3 can be run, but also the data content is ensured to be not lost.

[0048] Breaking the existing conventional solution, without destroying the infrastructure of physical machine 1, physical machine 1 is protected and data is copied to ensure that there is a completely identical data in migration machine 2, so that the physical machine 1 to be migrated can be reactivated in the environment of virtual machine 3, avoiding the compatibility issues and driver version issues required by physical machine 1, so that the new virtual machine 3 can be reactivated. At the same time, the integrity of the data content is also determined.

[0049] Step 3 of this embodiment 2 includes the following steps: Step 31, a disk with the same capacity as the system disk is allocated on the migration machine 2, and the proxy client synchronizes the data content of the system disk to the disk of the migration machine 2 through the migration server; Step 32, a snapshot resource is also mounted on the migration machine 2. With the help of the guide frame, a disk with the same capacity as the system disk is allocated on the migration machine 2 to synchronize the system disk of the physical machine 1. The migration machine 2 is also equipped with snapshot resources and the like for improvement to ensure that the synchronized data can be used, and can also be allocated to other machines for use to ensure that the data content is not damaged.

[0050] The above implementation modes are only for illustrating the technical concept and features of the present invention, and their purpose is to enable people familiar with this technology to understand the content of the present invention and implement it, and they cannot be used to limit the protection scope of the present invention. Any equivalent changes or modifications made according to the spirit of the present invention should be included in the protection scope of the present invention.

Claims

1. A data migration system from a physical machine to a virtual machine, characterized in that: It includes a physical machine, a migration machine and a virtual machine set on the migration machine, and the physical machine and the virtual machine can be connected to the migration machine through a migration server; The data migration method of the data migration system from a physical machine to a virtual machine comprises the following steps: Step 1: Install the proxy client on the physical machine, start the iSCSI component on the physical machine, and then restart the physical machine; Step 2: Open the proxy client and connect it to the migration server, then select disk protection for the system disk of the physical machine; Step 3: The migration machine is connected to the migration server and receives the data content of the system disk through the migration server; Step 4: After creating a virtual machine on the migration machine, import the RecoveryCD system on the migration machine and start the virtual machine through the RecoveryCD system. At the same time, the RecoveryCD system can restore the data content on the migration machine to obtain the restored data content. Step 5: After configuring the relevant parameters of the virtual machine, the virtual machine is connected to the migration server, and the virtual machine reads the recovery data content on the migration machine; Step 6: Restart the migration machine to complete data migration. Step 7: Check the restored data content of the virtual machine and compare it with the data content of the physical machine; Wherein, the step 3 further comprises the following steps: Step 31: Allocate a disk with the same capacity as the system disk on the migration machine, and the proxy client synchronizes the data content of the system disk to the disk of the migration machine through the migration server; Step 32: Snapshot resources are also mounted on the migration machine.

2. The data migration system from a physical machine to a virtual machine according to claim 1, characterized in that: The system also includes a proxy client for communicating with the migration server, wherein the proxy client is installed on the physical machine.

3. The data migration system from a physical machine to a virtual machine according to claim 1, characterized in that: The physical machine is provided with an iSCSI component.

4. A data migration system from a physical machine to a virtual machine according to claim 1, characterized in that: It also includes a RecoveryCD optical disc system for starting the virtual machine, and the RecoveryCD optical disc system is arranged on the migration integrated machine.

5. A data migration system from a physical machine to a virtual machine according to claim 1, characterized in that: It also includes snapshot resources mounted on the migration machine.

Images