While planning the lift and shift migration, take these key points into consideration.
Lift and Shift Duration
The lift and shift process requires the shutdown of the source guest domain during the archive creation which can take a few hours to complete.
The duration of the lift and shift process varies based on many factors, with these factors having a significant impact on the overall duration:
Size of the guest domain’s storage – All the virtual disks are copied and compressed into an archive file. The larger the storage, the longer the compression takes to complete.
Compute resources of the source control domain – The ovmtcreate command that creates the archive file, runs in the source control domain.
Compute resources of the target control domain – The ovmtdeploy command that creates the guest domain, runs in the target control domain.
The lift and shift example described in this guide, based on a guest domain consisting of 1.4 TB of storage, took several hours to complete.
Optionally, the lift and shift process can be accelerated by temporarily shifting some CPU and memory resources on the source system to the control domain during the creation of the archive. These resources can be borrowed from other guest domains that can afford to be shut down for a period of time. When the archive is complete, the resources are returned to the guest domains. This guide describes how to do this.
Network Configuration Differences
The network topology (IP addresses, DNS configuration, and so on) is copied from the Oracle Solaris 10 source machine, but can be changed if required, to suit the network topology of the target system.