Prepare the Source System

Language:

Perform this procedure on the Oracle Solaris 10 system that is hosting the guest domain that you plan to migrate to another system.

(Recommended) Apply the latest Critical Patch Updates to the guest domain.
Refer to this Oracle website for further details:https://www.oracle.com/security-alerts/
Ensure that any long running transactions and connections are either left to complete or terminated based on business considerations.
Backup any critical data before the start of this process, so that you can fall back to this system if anything goes wrong.
Clean up and delete unwanted data on the source guest domain.
Install the Oracle VM Server for SPARC patch 151934-06 (or later) on the control domain of the source system.
Installation of the patch provides ovmtcreate and supporting utilities that are required for this lift and sift scenario.
1. Determine if the patch is already installed.
  Use the patchadd command. For example:
```
# patchadd -p | grep 151934
```
2. Log into My Oracle Support (https://support.oracle.com).
3. Search for the latest version of patch 151934 for the Oracle Solaris on SPARC (64-bit) platform.
  Tip – Use 151934- (number with a dash) as the search string so that all versions of the patch are displayed.
4. If the patch is not installed, or if there is a later version of the patch, download the latest version.
5. Use the patchadd command to install the patch.
  The patching process installs the ovmtcreate utility in the /opt/SUNWldm/lib/contrib directory.
Prepare a working directory for the lift.
The ovmtcreate command requires temporary space in a working directory to compress the guest domain's storage. As a conservative best practice, create a directory that has space equal to the guest domain's virtual disk storage, divided by 2. For the alternative method, you only need the half the space of the virtual disks you plan to include in the archive.

For best performance, create the working directory on a source system local disk. This avoids copying the disk images over the network. If local storage is not available, you can create a working directory on network storage.

These command line examples display the available space in the working directory called /WorkingDirectory.
```
root@SourceControlDomain# zfs list wpool
NAME    USED    AVAIL  REFER    MOUNTPOINT
wpool   1.63M   650G   39K      /WorkingDirectory

root@SourceControlDomain# df -h /WorkingDirectory
Filesystem       size   used  avail capacity   Mounted on
wpool            650G   39K   650G  1%         /WorkingDirectory
```
If the guest domain hasn't been rebooted recently, reboot it.
Rebooting a domain helps to ensure that it is in a healthy state. If there is a problem, it is easier to troubleshoot before the domain is moved to another system.
(Optional) Assign additional available virtual CPU and memory resources to the source system's control domain.
Ensuring that the control domain has the maximum amount of virtual CPU and memory resources improves the performance of the archive creation. After the archive is created, return the control domain's resources to their original values. As a general rule, the control domain should have a minimum of two CPU cores.

To perform this step, there must be available vCPUs and memory in the source system which are not used or can be borrowed from guest domains that can be shutdown for a temporary period of time.

Note - Performing this step might require a reboot of the source system which might increase down time.

For more information about CPU and memory allocation, refer to the Oracle VM Server for SPARC Administration Guide based on the version of the virtualization software that is running on the source system. The documentation libraries are available at: https://docs.oracle.com/en/virtualization/oracle-vm-server-sparc/

For example:
```
root@SourceControlDomain# ldm set-core 4 primary
root@SourceControlDomain# ldm set-mem 24G primary
```

Related Information

Lifting and Shifting the Virtual Disks Separately (Alternate Method)