2.1 Supported Configurations

2.1.1 Supported Source Workloads For Migration to Non-Cloud Platforms

PlateSpin Migrate supports the migration of the following Windows and Linux workloads to non-cloud platforms, such as physical machines and virtual machines on supported hypervisors. See Supported Target Virtualization Platforms.

The following migration features are supported for migration to non-cloud platforms:

  • Peer-to-peer migrations (P2V, V2V, V2P, P2P).

  • Peer-to-peer workload synchronization (P2V, V2V, P2P, V2P).

NOTE:Not all workloads are supported on all target virtualization platforms. Migration of workloads to a target virtualization platform is subject to the support of the guest operating system on the target host by the host vendor.

Review the following sections:

Supported Microsoft Windows Workloads For Migration to Non-Cloud Platforms

PlateSpin Migrate supports the following Microsoft Windows platforms for migration to virtual machines on virtualization hosts or to physical machines, except as noted in Table 2-1. See also Supported Workload Storage and Supported Workload Architectures.

Table 2-1 Non-Cloud Platforms: Supported Windows Workloads

Operating System

Remarks

Servers

Windows Server 2016

Migration to a VMware VM requires VMware vCenter 6.0 or later.

  • Windows Server 2012 R2
  • Windows Server 2012

  • Windows Server 2008 R2
  • Windows Server 2008

Includes domain controller (DC) systems and Small Business Server (SBS) editions.

Does not support migration of Windows Server 2008 R2 SP0 to Hyper-V because Microsoft no longer supports it. See Microsoft TechNet Website.

  • Windows Server 2003 R2
  • Windows Server 2003 SP 1 and later

 

Clusters

Windows Server 2016 Cluster

Supports quorum models:

  • Node and Disk Majority

  • No Majority: Disk Only

Both Migrate Client and Web Interface support automated migration of Windows Clusters to VMware vCenter containers. Migrate Client also supports semi-automated migration of Windows Clusters to physical machines by using the X2P workflow. See Section 24.0, Preparing for Migration of Windows Clusters.

Migration of Windows Server 2016 Clusters to VMware requires VMware 6.0 or later.

PlateSpin Migrate does not support migration of Windows Server clusters to the following target infrastructures:

  • Images

  • Cloud

  • Virtualization hypervisors other than VMware

PlateSpin Migrate supports only block-level replication for clusters. File-level replication is not supported.

Support includes block-based data transfer with a driver (Fibre Channel SANs only) or without a driver for incremental replications for clusters.

WARNING:Do not attempt to use the block-based driver on clusters with shared iSCSI drives. It renders the cluster unusable.

  • Windows Server 2012 R2 Cluster
  • Windows Server 2012 Cluster

Supports quorum models:

  • Node and Disk Majority

  • No Majority: Disk Only

  • Windows Server 2008 R2 Cluster
  • Windows Server 2008 Cluster

Supports quorum models:

  • Node and Disk Majority

  • No Majority: Disk Only

  • Windows Server 2003 R2 Cluster
  • Windows Server 2003 Cluster

Supports quorum model:

  • Single-Quorum Device Cluster

Desktops

Windows 8 and 8.1

Requires the High Performance Power Plan.

Windows 7

Supports only Professional, Enterprise, and Ultimate.

Supported Linux Workloads For Migration to Non-Cloud Platforms

PlateSpin Migrate supports the following Linux platforms for migration to virtual machines on virtualization hosts or to physical machines, except as noted in Table 2-2. See also Supported Workload Storage and Supported Workload Architectures.

Table 2-2 Non-Cloud Platforms: Supported Linux Workloads

Linux Distribution

Versions

Remarks

Red Hat Enterprise Linux (RHEL)

AS/ES/WS 4.x, 5.0 to 5.11, 6.0 to 6.9, and 7.0 to 7.4

For Red Hat Enterprise Linux 6.7, Oracle Linux 6.7, and CentOS 6.7 workloads with LVM volumes, PlateSpin Migrate supports incremental replication only for the latest available kernel (version 2.6.32-642.13.1.el6) for the 6.7 distribution.

For Red Hat Enterprise Linux 6.8, Oracle Linux 6.8, and CentOS 6.8 workloads with LVM volumes, PlateSpin Migrate supports incremental replication only for the latest available kernel (version 2.6.32-696.20.1.el6.x86_64) for the 6.8 distribution.

Migration of a paravirtualized source workload to a target platform as a fully virtualized workload is supported for RHEL 5. See Paravirtualized Source Workloads.

SUSE Linux Enterprise Server (SLES)

9, 10, 11 (SP1, SP2, SP3, and SP4)

The SLES 11 SP2 (32-bit) with kernel 3.0.13-0.27-pae is not supported. The kernel for this version of SLES must be upgraded to 3.0.51-0.7.9-pae so that the conversion works.

Migration of a paravirtualized source workload to a target platform as a fully virtualized workload is supported for SLES 10 and 11. See Paravirtualized Source Workloads.

CentOS

See Red Hat Enterprise Linux.

Same level of support as that for workloads running RHEL except that CentOS 4.x is not supported for Hyper-V.

Migration of CentOS 7.x to VMware requires VMware vCenter 5.5 or later.

Oracle Linux (OL) (formerly Oracle Enterprise Linux)

See Red Hat Enterprise Linux.

Same level of support for standard kernels as that for workloads running RHEL except that OEL 4.x is not supported for Hyper-V.

Same level of support for Unbreakable Enterprise Kernel (UEK) kernels on supported RHEL distributions for OL 6.7 and later.

NOTE:The following guidelines apply to Linux migrations to non-cloud target platforms:

  • Workload imaging is not supported in Linux workloads.

  • Conversion of BIOS based Linux system to UEFI based is not supported.

2.1.2 Supported Workloads for Migration to the Cloud

To migrate the workloads to Microsoft Azure and VMware vCloud Director, use the PlateSpin Migrate Web Interface. To migrate the workloads to Amazon Web Services, use the PlateSpin Migrate Client.

Only P2C and V2C migrations are supported.

NOTE:

  • Not all workloads are supported on all target cloud platforms. Migration of workloads to a cloud container is subject to the support of the guest operating system on the target cloud platform by the cloud provider.

  • Windows and Linux UEFI workloads are migrated as BIOS workloads to the target cloud platform.

  • Before you migrate a paravirtualized Linux source workload running on Citrix XenServer or KVM to a target platform as fully virtualized guest, see Paravirtualized Source Workloads.

Review the following sections:

Supported Workloads For Migration to Microsoft Azure

PlateSpin Migrate supports the following platforms for migration to Microsoft Azure Cloud for the global environment and the sovereign Azure China environment. See also Supported Workload Storage and Supported Workload Architectures.

For information about migrating workloads to Microsoft Azure, see Prerequisites for Migration to Microsoft Azure and Migration to Microsoft Azure.

Table 2-3 Azure: Supported Windows Platforms

Operating System

Remarks

Microsoft Windows Server 2016

 

Microsoft Windows Server 2012 R2

 

Microsoft Windows Server 2012

 

Microsoft Windows Server 2008 R2

 

Table 2-4 Azure: Supported Linux Platforms

Linux Distribution

Versions

Remarks

Red Hat Enterprise Linux (RHEL)

6.7 to 6.9 and 7.1 to 7.4

For Red Hat Enterprise Linux 6.7, Oracle Linux 6.7, and CentOS 6.7 workloads with LVM volumes, incremental replication is supported only for the latest available kernel (version 2.6.32-642.13.1.el6) for the 6.7 distribution.

For Red Hat Enterprise Linux 6.8, Oracle Linux 6.8, and CentOS 6.8 workloads with LVM volumes, PlateSpin Migrate supports incremental replication only for the latest available kernel (version 2.6.32-696.20.1.el6.x86_64) for the 6.8 distribution.

SUSE Linux Enterprise Server (SLES)

11 (SP3 and SP4)

Migration of a paravirtualized source workload to a target platform as a fully virtualized workload is supported for SLES 11. See Paravirtualized Source Workloads.

CentOS

See Red Hat Enterprise Linux.

Same level of support as that for workloads running RHEL.

Oracle Linux (OL) (formerly Oracle Enterprise Linux)

See Red Hat Enterprise Linux.

Same level of support for standard kernels as that for workloads running RHEL.

Same level of support for Unbreakable Enterprise Kernel (UEK) kernels on supported RHEL distributions for OL 6.7 and later.

NOTE:PlateSpin Migrate does not support migration for source Linux workloads to Azure if the boot (/boot) partition is on a different disk than the root (/) partition.

Supported Workloads For Migration to VMware vCloud Director

PlateSpin Migrate supports the following platforms for migration to VMware vCloud Director. See also Section 2.1.3, Supported Workload Storage and Section 2.1.4, Supported Workload Architectures.

For information about migrating workloads to Microsoft VMware Cloud Director, see Section 11.0, Prerequisites for Migration to VMware vCloud Director and Section 30.0, Migration to VMware vCloud Director.

Table 2-5 vCloud: Supported Windows Platforms

Operating System

Remarks

Microsoft Windows Server 2012 R2

 

Microsoft Windows Server 2012

 

Microsoft Windows Server 2008 R2

 

Microsoft Windows Server 2008

 

Microsoft Windows Server 2003 R2

DoNotReplaceSysFiles must be set to True.

Microsoft Windows Server 2003 with Service Pack 1 (SP1) or later

DoNotReplaceSysFiles must be set to True.

Table 2-6 vCloud: Supported Linux Platforms

Linux Distribution

Versions

Remarks

Red Hat Enterprise Linux (RHEL)

4.x, 5.0 to 5.11, 6.0 to 6.9, and 7.0 to 7.4

For target vCloud containers, PlateSpin Migrate does not support the XFS version 5 (v5) file system. RHEL 7.3 and 7.4 (and distributions based on them) are not supported for workloads with XFS v5 file systems.

For Red Hat Enterprise Linux 6.7, Oracle Linux 6.7, and CentOS 6.7 workloads with LVM volumes, incremental replication is supported only for the latest available kernel (version 2.6.32-642.13.1.el6) for the 6.7 distribution.

For Red Hat Enterprise Linux 6.8, Oracle Linux 6.8, and CentOS 6.8 workloads with LVM volumes, PlateSpin Migrate supports incremental replication only for the latest available kernel (version 2.6.32-696.20.1.el6.x86_64) for the 6.8 distribution.

Migration of a paravirtualized source workload to a target platform as a fully virtualized workload is supported for RHEL 5. See Paravirtualized Source Workloads.

SUSE Linux Enterprise Server (SLES)

10 and 11 (SP1, SP2, SP3, and SP4)

Migration of a paravirtualized source workload to a target platform as a fully virtualized workload is supported for SLES 10 and 11. See Paravirtualized Source Workloads.

CentOS

See Red Hat Enterprise Linux.

Same level of support as that for workloads running RHEL.

Oracle Linux (OL) (formerly Oracle Enterprise Linux)

See Red Hat Enterprise Linux.

Same level of support for standard kernels as that for workloads running RHEL.

Same level of support for Unbreakable Enterprise Kernel (UEK) kernels on supported RHEL distributions for OL 6.7 and later.

Supported Workloads For Migration to Amazon Web Services

PlateSpin Migrate supports the following platforms for migration to Amazon Web Services. See also Section 2.1.3, Supported Workload Storage and Section 2.1.4, Supported Workload Architectures.

For information about migrating workloads to Microsoft Amazon Web Services, see Section 8.0, Prerequisites for Migration to Amazon Web Services and Section 28.0, Migration to Amazon Web Services.

Table 2-7 AWS: Supported Windows Platforms

Operating System

Remarks

Microsoft Windows Server 2016

 

Microsoft Windows Server 2012 R2

 

Microsoft Windows Server 2012

 

Microsoft Windows Server 2008 R2

 

Microsoft Windows Server 2008

 

Microsoft Windows Server 2003 R2

 

Microsoft Windows Server 2003 with Service Pack 1 (SP1) or later

 

Table 2-8 AWS: Supported Linux Platforms

Linux Distribution

Versions

Remarks

Red Hat Enterprise Linux (RHEL)

5.1 to 5.11, 6.1 to 6.9, and 7.0 to 7.4

For Red Hat Enterprise Linux 6.7, Oracle Linux 6.7, and CentOS 6.7 workloads with LVM volumes, incremental replication is supported only for the latest available kernel (version 2.6.32-642.13.1.el6) for the 6.7 distribution.

For Red Hat Enterprise Linux 6.8, Oracle Linux 6.8, and CentOS 6.8 workloads with LVM volumes, PlateSpin Migrate supports incremental replication only for the latest available kernel (version 2.6.32-696.20.1.el6.x86_64) for the 6.8 distribution.

Migration of a paravirtualized source workload to a target platform as a fully virtualized workload is supported for RHEL 5. See Paravirtualized Source Workloads.

SUSE Linux Enterprise Server (SLES)

11 (SP2 and SP3)

Migration of a paravirtualized source workload to a target platform as a fully virtualized workload is supported for SLES 11. See Paravirtualized Source Workloads.

CentOS

See Red Hat Enterprise Linux.

Same level of support as that for workloads running RHEL.

Oracle Linux (OL) (formerly Oracle Enterprise Linux)

See Red Hat Enterprise Linux.

Same level of support for standard kernels as that for workloads running RHEL.

Same level of support for Unbreakable Enterprise Kernel (UEK) kernels on supported RHEL distributions for OL 6.7 and later.

2.1.3 Supported Workload Storage

The following workload storage guidelines apply to all migrations:

Partitioning Schemes

PlateSpin Migrate supports MBR (Master Boot Record) and GPT (GUID Partition Table) partitioning schemes for Windows and Linux workloads. Workloads and storage for migration must be configured on disks partitioned with the MBR or GPT. Although GPT allows up to 128 partitions per single disk, PlateSpin Migrate supports only 57 or fewer GPT partitions per disk.

Windows File Systems

PlateSpin Migrate supports only the NTFS file system on any supported Windows system. It does not support Windows FAT or ReFS file systems for migration.

NOTE:If the volumes are encrypted with the BitLocker disk encryption feature, they must be unlocked (decrypted) for the migration.

Linux File Systems

PlateSpin Migrate supports EXT2, EXT3, EXT4, REISERFS, and XFS file systems.

NOTE:

  • PlateSpin Migrate supports the XFS version 5 (v5) file system on RHEL 7.3 and later, and on distributions based on those versions. However, XFS v5 support does not apply for workloads on target VMware vCloud containers.

  • Migration of encrypted volumes is not supported. If the volumes are encrypted, they must be unlocked (decrypted) for the migration.

Disks

PlateSpin Migrate supports several types of storage disks, including basic disks, source Windows dynamic disks, LVM2, hardware RAID, NAS, and SAN.

NOTE:The following caveats apply for storage disks:

  • Windows Dynamic Disks: PlateSpin Migrate does not support Windows dynamic disks at the target.

    For dynamic disks, the storage does not follow the Same as Source mapping strategy. Both Simple Dynamic Volumes and Spanned Dynamic Volumes will reside on the target workload as Simple Basic Volume disks. The target disk is partitioned as GPT if the total combined size of the dynamic volume’s member disks exceeds MBR partition size limits. For more information, see Microsoft TechNet: Understanding the 2 TB limit in Windows Storage.

  • Software RAID: PlateSpin Migrate supports hardware RAID; however, PlateSpin Migrate does not support software RAID. This is applicable for both Windows and Linux workloads.

Linux Disks, Partitions, and Volumes

  • Migrate supports GRUB and GRUB 2 boot loaders for Linux workloads.

  • Migrate supports Linux workloads with /boot on the first disk (sda).

  • The boot partition of a source Linux workload must have a minimum of 100 MB free space. During the migration process, PlateSpin Migrate uses the free space to create a new initrd image with all the required drivers to make the machine ready for the initial boot process.

  • Non-volume storage, such as a swap partition that is associated with the source workload, is recreated in the migrated workload.

  • The layout of volume groups and logical volumes for LVM2 is preserved in the Same as Source mapping strategy so that you can re-create it during migration.

  • LVM raw disk volumes are supported in the Same as Source configurations on Linux workloads.

Linux Live Data Transfer

  • For Linux workloads, Migrate supports only block-based live data transfer with a blkwatch driver. For a list of pre-compiled blkwatch drivers, see Section D.2.2, List of Distributions.

  • Some of the supported Linux versions require that you compile the PlateSpin blkwatch module for your specific kernel. Those workloads are called out explicitly.

    Precompiled blkwatch drivers are available for the standard kernel and Unbreakable Enterprise Kernel (UEK) as noted in the Section D.2.2, List of Distributions. For other Oracle Linux distributions, precompiled drivers are available only for the corresponding Red Hat Compatible Kernel (RHCK).

FC SANs

PlateSpin Migrate supports the Fibre Channel (FC) SAN communications protocol.

FCoE SANs

Fibre Channel over Ethernet (FCoE) is supported for P2P and P2V migrations for workloads listed in Table 2-9. Migration has been tested using FCoE devices from Qlogic.

Table 2-9 Supported Source Workloads for FCoE

Source Workloads with FCoE

Version

Remarks

  • Windows Server
  • 2012 R2
  • 2008 R2

Standalone servers only; no clusters.

SUSE Linux Enterprise Server

11 SP4

 

FCoE drivers and support functionality are available in the PlateSpin ISO image. See Downloading the PlateSpin ISO Images.

Multipath I/O

PlateSpin Migrate supports migration of a source workload configured for multipath I/O (MPIO) in a Fibre Channel (FC) SAN environment. The target workload can be in the same or different SAN environment. The source workload and target workload must have all SAN disks.

NOTE:The workload must boot from a SAN disk. Workloads with mixed local and SAN disks are not supported, except as otherwise noted in Table 2-10.

MPIO support functionality is available in the PlateSpin ISO image. See Downloading the PlateSpin ISO Images.

See Table 2-10 for a list of platforms that have been tested for migrations in MPIO environments.

Table 2-10 Supported Source Workloads for MPIO

Platform

Versions

Remarks

Microsoft Windows Server

  • 2012 R2
  • 2008 R2

 

Microsoft Windows Server in a Failover Cluster

2012 R2

The cluster migration has also been tested using a local system disk with all data disks in a FC SAN.

Red Hat Enterprise Linux (RHEL)

  • 7.2
  • 6.8

For Red Hat Enterprise Linux 6.8, Oracle Linux 6.8, and CentOS 6.8 workloads with LVM volumes, PlateSpin Migrate supports incremental replication only for the latest available kernel (version 2.6.32-696.20.1.el6.x86_64) for the 6.8 distribution.

MPIO requires additional multipath software to be installed in the operating system, in the form of a Windows Feature or a Linux package or module. You use MPIO management tools to enable MPIO and configure MPIO policies for SAN devices with multiple paths. Refer to vendor documentation for information about setting up hardware to provide multiple paths to a storage device and about installing and configuring MPIO.

See Table 2-11 for information about supported MPIO migration scenarios and target workload expectations.

Table 2-11 Supported MPIO Migration Scenarios

Source Workload

Target Workload

MPIO Software

Multiple Storage Paths Available

Single Storage Path Available

MPIO software is installed. MPIO is enabled and configured.

MPIO software is automatically reconfigured on the target workload for the target MPIO environment.

To disable MPIO, you must manually reconfigure MPIO on the workload.

MPIO software remains, and MPIO is reconfigured for a single path. You can leave the software or remove it manually, as appropriate for your planned network.

If you add MPIO hardware after migration is completed, you must manually reconfigure MPIO on the workload.

MPIO software is installed. MPIO is disabled.

MPIO software remains installed but disabled.

To enable MPIO, you must manually configure MPIO on the workload.

MPIO software remains installed but disabled. You can leave the software or remove it manually, as appropriate for your planned network.

If you add MPIO hardware after migration is completed, you must manually configure MPIO on the workload.

MPIO software is not installed.

MPIO software is not installed.

To enable MPIO, you must manually install and configure MPIO on the workload.

No MPIO-related changes are made for the workload.

2.1.4 Supported Workload Architectures

The following workload architecture guidelines apply to all migrations:

Protocols

  • Linux source workloads must be running a Secure Shell (SSH) server.

Processors

PlateSpin Migrate supports migration of x86-based physical and virtual workloads in your data center:

  • 64-bit

  • 32-bit

Cores and Sockets for Target VMs

For VM containers using VMware 5.1, 5.5, and 6.0 with a minimum VM hardware Level 8, PlateSpin Migrate enables you to specify the number of sockets and the number of cores per socket for the target workload. It automatically calculates the total cores. This parameter applies on the initial setup of a workload with an initial replication setting of Full Replication.

NOTE:The maximum number of cores the workload can use is subject to external factors such as the guest operating system, the VM hardware version, VMware licensing for the ESXi host, and ESXi host compute maximums for vSphere (see ESXi/ESX Configuration Maximums (VMware KB 1003497)).

Some distributions of a guest OS might not honor the cores and cores per socket configuration. For example, guest OSes using SLES 10 SP4 retain their original cores and sockets settings as installed, whereas other SLES and RHEL distributions honor the configuration.

Virtual CPUs for Target VMs

For VM containers using VMware 4.1, PlateSpin Migrate enables you to specify the required number of vCPUs (virtual CPUs) to assign to the target workload. This parameter applies on the initial setup of a workload with an initial replication setting of Full Replication. Each vCPU is presented to the guest OS on the VM container as a single core, single socket.

UEFI and BIOS Firmware

Migration of UEFI-based Windows and Linux source workloads is supported for all target platforms. The target workload is converted from UEFI to BIOS for target cloud platforms: Amazon Web Services, Microsoft Azure, and VMware vCloud Director. For other platforms, the target workload is configured as UEFI or BIOS, as supported by the target platform vendor.

Migrate transfers workloads from source to target while enforcing the supported firmware for the respective source and target operating systems. When any migration between UEFI and BIOS systems are initiated, Migrate analyzes the transition and alerts you about its validity.

NOTE:If you are migrating UEFI-based workload onto vSphere target container and you want to continue using the same firmware boot mode, you must target a vSphere 5.0 container or newer.

The following are examples of Migrate behavior when doing conversion between UEFI and BIOS-based systems:

  • When you migrate a UEFI-based workload to a VMware vSphere 4.x or Cloud container (which does not support UEFI), Migrate transitions the workload’s UEFI firmware to BIOS firmware.

  • When you migrate a UEFI-based source to a BIOS-based target, Migrate converts the UEFI system’s boot disks, which were GPT, to MBR disks.

  • (For Windows Workloads) When you migrate a BIOS workload to a UEFI-based target, Migrate converts the BIOS system's boot disks, which are MBR, to GPT disks.

Paravirtualized Source Workloads

Paravirtualized to fully virtualized conversion is supported for the following source workloads running on a Citrix XenServer or KVM virtual host:

  • Red Hat Enterprise Linux (RHEL) 6.0 and Linux distributions based on RHEL 6.0

  • Red Hat Enterprise Linux (RHEL) 5.x and Linux distributions based on RHEL 5.x

  • SUSE Linux Enterprise Server 10 and 11

Only block-based conversions are supported.

Before you migrate a paravirtualized Linux source workload running on Citrix XenServer or KVM to a target platform as fully virtualized guest, do the following:

  • Ensure that both the paravirtual and standard kernel are installed on the paravirtualized source workload.

  • Manually compile the block-based drivers for Xen kernel.

2.1.5 Supported Target Virtualization Platforms

PlateSpin Migrate supports the following target virtualization platforms.

NOTE:

  • Migration of workloads to a target virtualization platform is subject to the support of the guest operating system on the target host by the host vendor.

  • You need an OS license for the migrated target workload.

Table 2-12 Supported Target VMware Platforms for the Migrate Web Interface and Migrate Client

Platform

Versions

Remarks

VMware vCenter

  • 6.5 (U1 with latest patches)
  • 6.0 (U1, U2, and U3)
  • 5.5 (U1, U2, and U3)
  • 5.1 (U1, U2, and U3)
  • 5.0 (U1, U2, and U3)
  • 4.1 (U1, U2, and U3)

VMware Virtual SAN (vSAN) storage is supported on vCenter target containers as follows:

  • vSAN 6.6 on vCenter 6.5 containers

  • vSAN 6.2 on vCenter 6.0 containers

  • vSAN 5.5 on vCenter 5.5 containers

Raw Device Mapping (RDM) for target VMs is supported using the X2P workflow.

See also Table 2-13, Supported VMware Datastores.

VMware ESXi

  • 6.5 (U1 with latest patches)
  • 6.0 (U1, U2, and U3)
  • 5.5 (U1, U2, and U3)
  • 5.1 (U1, U2, and U3)
  • 5.0 (U1, U2, and U3)
  • 4.1 (U1, U2, and U3)

All ESXi versions must have a paid license; migration is unsupported with these systems if they are operating with a free license.

Raw Device Mapping (RDM) for target VMs is supported using the X2P workflow.

See also Table 2-13, Supported VMware Datastores.

VMware ESX

  • 4.1 (U1, U2, and U3)

Raw Device Mapping (RDM) for target VMs is supported using the X2P workflow.

See also Table 2-13, Supported VMware Datastores.

Table 2-13 Supported VMware Datastores

Datastore Type

Supported Configurations

VMFS

Supported for all supported versions of VMware vCenter, ESXi, and ESX platforms.

NFS v3

Supported only for supported versions of VMware vCenter 5.5 and ESXi 5.5 platforms.

Other

Other datastore types are not supported, such as Virtual Volumes, NFS v4.1, and vFlash.

Table 2-14 Supported Target Virtualization Platforms for the Migrate Client Only

Platform

Versions

Remarks

Microsoft Hyper-V Server

  • Microsoft Hyper-V Server 2016

Supported for automated workflow or the X2P workflow. See

See also Prerequisites for Migration to Microsoft Hyper-V.

Microsoft Windows Server with Hyper-V

  • Windows Server 2016 (GUI and Core mode)
  • Windows Server 2012 R2
  • Windows Server 2012

Supported for automated workflow or the X2P workflow. See

See also Prerequisites for Migration to Microsoft Hyper-V.

Citrix XenServer

  • 7.3

Fully virtualized guests are supported.

Supported through the X2P workflow. See Migration to Virtual Machines on Citrix XenServer.

See also Prerequisites for Migration to VMs on Citrix XenServer.

SUSE Linux Enterprise Server with Xen

11 SP3 and 11 SP4

Fully virtualized guests are supported.

Supported through the X2P workflow. See Migration to Virtual Machines on Xen.

See also Prerequisites for Migration to VMs on Xen.

SUSE Linux Enterprise Server (SLES) with KVM

11 SP4 and 12 SP1

Fully virtualized guests are supported.

Virtio devices are supported.

Supported through the X2P workflow. See Migration to Virtual Machines on KVM.

See also Prerequisites for Migration to VMs on KVM.

Red Hat Enterprise Linux (RHEL) with KVM

7.4

Fully virtualized guests are supported.

Virtio devices are supported.

Supported through the X2P workflow. See Migration to Virtual Machines on KVM.

See also Prerequisites for Migration to VMs on KVM.

2.1.6 Supported Target Cloud Platforms

PlateSpin Migrate supports migration of workloads to target cloud platforms. Microsoft Azure and VMware vCloud Director are supported in the Migrate Web Interface. Amazon Web Services is supported in the Migrate Client. See Table 2-15 and Table 2-16.

Table 2-15 Supported Target Cloud Platforms for the Migrate Web Interface

Platform

Versions

Remarks

Microsoft Azure

  • Azure Cloud global environment
  • Sovereign Azure China environment

Each PlateSpin Server can support only one of the supported Azure environments at a time. See Section 9.9, Configuring the Target IaaS Environment for Azure Cloud.

NOTE:Contact Micro Focus Support and Services for assistance if you want to migrate workloads to other sovereign Azure environments.

See also Prerequisites for Migration to Microsoft Azure.

VMware vCloud Director

  • 9.1
  • 8.20
  • 5.5.x and 5.6.x

See also Prerequisites for Migration to VMware vCloud Director.

Table 2-16 Supported Target Cloud Platform for the Migrate Client

Platform

Versions

Remarks

Amazon Web Services (AWS)

Amazon EC2 environment

See also Prerequisites for Migration to Amazon Web Services.

2.1.7 Supported International Languages

In addition to English, PlateSpin Migrate provides National Language Support (NLS) for Chinese Simplified (ZH-CN), Chinese Traditional (ZH-TW), French (FR-FR), German (DE-DE), and Japanese (JA-JP).

Localized online documentation is available in these languages, as well as in Spanish (ES-ES) and Brazilian Portuguese (PT-BR).

2.1.8 Supported Web Browsers

The PlateSpin Migrate Web Interface, PlateSpin Configuration options, and Help files are available from a supported web browser:

  • Google Chrome, version 34.0 and later

  • Microsoft Internet Explorer, version 11.0 and later

  • Mozilla Firefox, version 29.0 and later

NOTE:JavaScript (Active Scripting) must be enabled in your browser.

To use the Web Interface in one of the supported international languages, see Configuring Language Settings for International Versions.