Migrating instances

The IBM® Cloud Pak System uses workload patterns to create consistent, validated, and repeatable applications within an environment. By using the workload mobility feature, you can migrate workloads that run across systems with minimal changes and minimal downtime.

Note: Virtual System Instance is the only supported workload type.

Important: This migration feature is applicable only if you are on 2.3.3.3 Interim Fix 1 or higher.

You can migrate a Virtual System Instance that runs on a source IBM Cloud Pak System (A) to target IBM Cloud Pak System (B). That is, migration from System A to System B that runs on Generation 3 or higher IBM Cloud Pak Systems. The 'source' system is the environment where the workload exists in its current format. The workload gets migrated to another 'target' system, the new host for the migrated workload.

For IBM Cloud Pak System migration, this feature supports the migration of multiple virtual machines within a Virtual System Instance. With successful migration, the attached resources of the source virtual machine, such as disks and NICs are also migrated to the target along with the workload.

You cannot migrate an unmanaged workload or single virtual machine without a Virtual system Instance.

For migration with VMware vMotion in environments without shared storage, see https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-561681D9-6511-44DF-B169-F20E6CA94944.html.