Dear All,
Today we are going to learn about Rainbow Server Migration Working Principle.
File-Level Migration
Application scenarios of file-level migration:
Expand or reduce the capacity of the planned destination VM disk space based on the source host capacity.
Migrate only some data files and exclude the data files that do not need to be migrated.
If the disk partition size of the source host is 200 GB and the actual file size is 10 GB, you are advised to use the file-level migration.
When migrating data in 32-bit Windows, you are advised to use the Windows file-level migration.
If the disk size of the source host is 100 GB (only 10 GB is used) and the disk size of the destination VM is 150 GB (capacity expansion) or 15 GB (capacity reduction) after the migration, the file-level migration is required.
Block-Level Migration
Application scenarios of block-level migration:
The host that contains a large number of small files.
The host with high disk space usage.
The partition structure must be consistent with the source host.
If the disk partition size of the source host is 200 GB and about 150 GB is used, you are advised to use the block-level migration.
If the average file size of the source host is less than 100 KB, you are advised to use the block-level migration.
If the disk size of the source host is 100 GB (only 10 GB is used) and the disk size of the destination VM is 150 GB (capacity expansion) or 15 GB (capacity reduction) after the migration, the file-level migration is required.
Migration Process
Information Collection
· Source host name
· Source host name
· OS
· Source host virtualization platform
· Network bandwidth
· Source host specifications (disks, CPUs, and memory)
· Boot mode (UEFI or BIOS)
· OEMed or self-developed
· Service description
Migration Assessment
· OSs that are not in the FusionCompute compatibility matrix
· OSs that are not in the Rainbow compatibility matrix
· UEFI + GPT (some systems)
· OEM
· FAT partition format
· Paravirtualization VM with Xen 6.0 or later
· Windows system partition and boot partition in the extended partition
Migration Plan
regards,
Kashif Ali
