PlateSpin Migrate 2019.2 Release Notes

July 2019

PlateSpin Migrate 2019.2 includes new features and enhancements and resolves several previous known issues.

The documentation for this product is available in HTML and PDF formats on the PlateSpin Migrate 2019.2 Documentation website.

This product contains undocumented utilities that the Technical Support team might use to diagnose or correct problems.

1.0 Documentation Updates

The following changes have been made to this document since the release of PlateSpin Migrate 2019.2 in February 2019.

1.1 July 2019

Location

Change

What’s New for AWS Quick Start

NOTE:Effective July 31, 2019, PlateSpin Migrate updates the AWS Quick Start support to help you quickly and easily deploy PlateSpin Migrate 2019.5 server on the AWS Cloud. Refer to the PlateSpin Migrate 2019.5 Documentation website.

1.2 June 2019

Location

Change

Deprecated Functions

PlateSpin Migrate discontinues support for migrations of workloads with multipath I/O (MPIO) enabled. We recommend that you perform migration with a single path, and then enable MPIO on the cutover workload.

1.3 May 2019

Location

Change

What’s New for AWS Quick Start

This section is new.

1.4 April 2019

1.5 March 2019

Location

Change

What’s New for Migrate Server in Azure Cloud

This section is new.

PlateSpin Migration Factory

Table 1 identifies the compatibility of the current and prior releases of PlateSpin Migrate and PlateSpin Transformation Manager.

2.0 What’s New for AWS Quick Start

PlateSpin Migrate updates the AWS Quick Start support to help you quickly and easily deploy PlateSpin Migrate 2019.2 server on the AWS Cloud. For more information about the Quick Start, see Micro Focus PlateSpin Migrate on AWS.

NOTE:Effective July 31, 2019, PlateSpin Migrate updates the AWS Quick Start support to help you quickly and easily deploy PlateSpin Migrate 2019.5 server on the AWS Cloud. Refer to the PlateSpin Migrate 2019.5 Documentation website.

3.0 What’s New for Migrate Server in Azure Cloud

PlateSpin Migrate 2019.2 server image and replication environment are now available in Microsoft Azure Marketplace. In the Azure Marketplace, search for PlateSpin, then select the PlateSpin Migrate and PlateSpin Replication Environment images from Micro Focus.

4.0 What’s New

PlateSpin Migrate 2019.2 includes several new features and enhancements.

Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs.

4.1 PlateSpin Migration Factory

In a PlateSpin Migration Factory environment, PlateSpin Migrate 2019.2 supports PlateSpin Transformation Manager 2019.2 and PlateSpin Migrate Connector 2019.2 (a component of PTM). To install PTM in a PlateSpin Migration Factory deployment, see the PTM 2019.2 Appliance Guide.

Table 1 identifies the compatibility of the current and prior releases of PlateSpin Migrate and PlateSpin Transformation Manager.

Table 1 Compatibility Matrix for PlateSpin Migrate and PlateSpin Transformation Manager

  • PlateSpin Migrate
  • PlateSpin Transformation Manager
  • and PlateSpin Migrate Connector

Version (Release Date)

Version (Release Date)

2019.2 (Feb 2019)

2019.2 (Feb 2019)

2018.11 (Nov 2018)

2.0 (Nov 2018)

12.3 (Aug 2018)

Not tested with version 1.1.1

12.2.2 (Apr 2018)

Not tested with version 1.1.1

12.2.1 (Dec 2017)

1.1.1 (Dec 2017)

12.2 (Jan 2017)

1.1 (Dec 2016)

12.1 (May 2016)

1.0 (Apr 2016)

4.2 AWS Migration Enhancements

  • Support for New Target Platforms

    PlateSpin Migrate adds supports for AWS GovCloud.

  • Support for New AWS Instance Types

    PlateSpin Migrate adds support for the following new AWS instance types for x86 and x86_64 processor architectures offered by Amazon Web Services since the last Migrate release: r5, r5d, z1d, t3, m5a, c5n, r5a, p3dn, g3s.

    NOTE:The F1 instance types are supported only for Linux workloads.

4.3 Azure Cloud Migration Enhancements

  • Support for New Azure Instance Types

    PlateSpin Migrate supports new Azure instance types offered by Microsoft Azure since the last Migrate release.

  • Ability to Install Azure Agent on Target Windows Workloads

    PlateSpin Migrate can install the Windows Azure Agent on target Windows workloads at Cutover and Test Cutover. The Install Azure Agent option is available on the Workload Configuration page for Windows migrations to Azure.

4.4 VMware vCloud Director Migration Enhancements

  • SLES 12 PRE for Migrating BIOS Workloads to vCloud

    PlateSpin Migrate provides a SLES 12 PlateSpin Replication Environment that is used for migrating 64-bit BIOS workloads to target VMware vCloud platforms. For information about creating the virtual appliance for the SLES 12 PRE, see Understanding PlateSpin Replication Environment Used for Migration of Workloads to vCloud in the User Guide.

  • Support for BIOS Workloads with XFSv5 File Systems

    The SLES 12 PRE for BIOS workloads includes support for migration source Linux BIOS workloads with an XFS v5 file system to vCloud.

4.5 VMware and VMware Cloud on AWS Migration Enhancements

  • Ability to Add Multiple VMware DRS Clusters with the Same Cluster Name

    The Add Target dialog now allows you to add multiple DRS clusters with the same cluster name provided each cluster has a unique IP address/domain name.

4.6 Source Workload Support Enhancements

  • Supported Linux Workloads

    PlateSpin Migrate adds support for the following source Linux workloads. For information about precompiled blkwatch drivers, see List of Distributions in the User Guide.

    Platform

    Versions

    Remarks

    Red Hat Enterprise Linux (RHEL)

    • 6.10
    • 7.6

    The XFS version 5 (v5) file system is supported on RHEL 7.3 and later, and on distributions based on those versions.

    Migration of UEFI and BIOS workloads with XFS v5 file systems to vCloud requires the vCloud PRE (PlateSpin Replication Environment) based on SLES 12 SP3.

    Oracle Linux

    Distributions based on RHEL.

    Use precompiled blkwatch drivers for the Oracle Unbreakable Enterprise Kernel (UEK) and standard kernel.

    CentOS

    Distributions based on RHEL.

    Use RHEL precompiled blkwatch drivers.

    SUSE Linux Enterprise Server (SLES)

    12 SP2 without BTRFS

    Migrate does not support migration of workloads that use the BTRFS file system.

    For detailed information and caveats about supported source workloads, see Supported Configurations in the User Guide.

4.7 Target Platform Support Enhancements

  • Support for Target VMware 6.7 U1 Platforms

    • VMware vCenter 6.7 U1

    • VMware ESXi 6.7 U1

    • vSAN 6.7 U1

  • Support for Target VMware 6.5 U2 Platforms

    • VMware vCenter 6.5 U2

    • VMware ESXi 6.5 U2

    • vSAN 6.5 U2

For detailed information and caveats about supported target virtualization platforms, see Supported Target Virtualization Platforms in the User Guide.

4.8 Web Interface Enhancements

  • Incremental Replication option for Test Cutover is disabled by default

    Performing an incremental replication before a test cutover is optional. For Test Cutover, the Incremental Replication option is deselected by default.

5.0 Deprecated Configurations and Functions

PlateSpin Migrate 2019.2 discontinues support for the following configurations and functions.

IMPORTANT:Before you upgrade from PlateSpin Migrate 2018.11 to PlateSpin Migrate 2019.2, ensure that you complete planned migrations that involve configurations and functions that will be deprecated in version 2019.2.

5.1 Deprecated Support for Source Workloads

PlateSpin Migrate 2019.2 discontinues support for migration of the following source workloads to any target:

  • Microsoft Windows Server 2003 (all versions and service packs)

  • Microsoft Windows Server 2003 Clusters (all versions and service packs)

  • Microsoft Windows 7, 8, and 8.1 (no migration of Windows desktops)

5.2 Deprecated Support for Target Platforms

PlateSpin Migrate 2019.2 discontinues support for migration of source workloads to the following target platforms:

  • vCloud Director 5.5.x and 5.6.x

  • VMware vCenter and ESXi 5.1 (all updates)

  • VMware vCenter and ESXi 5.0 (all updates)

  • VMware vCenter and ESXi/ESX 4.1 (all updates)

  • Citrix XenServer (all versions/service packs)

  • SUSE Linux Enterprise Server with Xen (all versions/service packs)

5.3 Deprecated Functions

PlateSpin Migrate 2019.2 discontinues support for the following functions:

  • Portability and migration to images

  • Offline migration

  • VLAN tagging support for target workloads for X2P migrations

    For X2P migrations, PlateSpin Migrate supports only untagged network packets on any network interface that is used during the migration process. However, VLAN IDs continue to be supported for migrations to Microsoft Hyper-V.

  • Exclude File List and Include File List options for block-based data transfer

    The following parameters are no longer available in PlateSpin Configuration:

    • BlockBasedTransferExcludeFileList

    • BlockBasedTransferIncludeFileList

  • Configuring the AWS Instance Type that is used for the AWS Replication Environment Virtual Machine. The AwsInstanceTypeForReplicationEnvironment parameter is no longer available in PlateSpin Configuration.

  • Multipath I/O (MPIO) support

    PlateSpin Migrate discontinues support for migrations of workloads with multipath I/O (MPIO) enabled. We recommend that you perform migration with a single path, and then enable MPIO on the cutover workload.

5.4 Deprecated National Language Support

PlateSpin Migrate 2019.2 discontinues support for the following national languages:

  • French

  • German

  • Chinese Simplified

  • Chinese Traditional

In addition to these languages, documentation discontinues support for Spanish and Brazilian Portuguese.

6.0 Known Issues

Micro Focus strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Micro Focus Support and Services.

For information about known issues in previous releases, see Previous Releases.

6.1 Known Issues for Upgrade

After Upgrade, Migrations Fail for Deprecated Source Workloads and Target Platforms

Issue: After you upgrade to PlateSpin Migrate 2019.2, existing migrations might fail if they have been configured for deprecated source workloads and target platforms. See Deprecated Support for Source Workloads and Deprecated Support for Target Platforms.

Workaround: Before you upgrade your Migrate Server to version 2019.2, ensure that you complete planned migrations for source workloads and target platforms that are not supported for 2019.2.

After Upgrade, Import Fails for Workloads That Were Registered Using Migrate Agent in 2018.11

Issue: After you upgrade to PlateSpin Migrate 2019.2, workloads that were registered by using Migrate Agent in PlateSpin Migrate 2018.11 are not imported even though Preserve Data was selected during the upgrade. The export mechanism in version 2018.11 does not export the registered workloads. This issue does not affect workloads discovered through the Migrate Web interface or Migrate Client. (Bug 1126341)

Workaround: Before you upgrade your Migrate Server to version 2019.2, ensure that you complete all planned migrations for workloads that were registered with the Migrate Agent in PlateSpin Migrate 2018.11.

After Upgrade, the PlateSpinVAppTemplateList Does Not Contain an Entry for Migration of 64-Bit BIOS Workloads to vCloud

Issue: When you upgrade to PlateSpin Migrate 2019.2, the list of PlateSpin Replication Environment templates for VMware vCloud has not been updated to include the following entry to support migration of 64-bit BIOS workloads:

RepEnvImage64BitBIOS="PlateSpin Replication Environment - BIOS"

This entry is added automatically for new installations of PlateSpin Migrate. (Bug 1128244)

Workaround: Before you can migrate 64-bit BIOS workloads to vCloud, you must add an entry for the 64-bit BIOS Replication Environment Image to the PlateSpinVAppTemplateList parameter in the PlateSpin Server Configuration Settings.

To add an entry for 64-bit BIOS PRE for vCloud:

  1. Log in to the PlateSpin Migrate server, then go to the PlateSpin Server Configuration Settings page:

    https://<platespin-server-IP-address>/platespinconfiguration

  2. Search for vcloud to locate the PlateSpinVAppTemplateList parameter.

  3. Click Edit in the Value column for the parameter.

  4. On a new line below the current entries, add the following line:

    RepEnvImage64BitBIOS="PlateSpin Replication Environment - BIOS"

  5. Save the change.

6.2 Known Issues for Migration to AWS

Unable to Configure the DNS Servers on the Cutover AWS Target VM for a Linux 7.x Workload

Issue: When you perform a cutover or test cutover of a supported Linux 7.x BIOS workload to AWS, the cutover is successful. The static IP address that you configured in the migration job is correctly set on the cutover target VM, but the configured DNS servers are not set on the cutover target VM. (Bug 1124880)

Workaround: Manually configure the DNS servers on the cutover target VM.

Disks on a Successfully Migrated AWS Target Instance Might Fail to Come Online

Issue: When you migrate a source workload that has multiple disks to AWS, one or more disks that are backed by low-cost EBS volume types such as Cold HDD or Throughput Optimized HDD on the migrated target instance might fail to come online after a successful migration. (Bug 1127249)

Workaround: Manually bring the offline disk drives online and assign drive letters to them.

Copy Target Workload Settings Might Not Copy the Host Setting For Dedicated Hosts in AWS GovCloud

Issue: Consider that you want to migrate a workload to a dedicated host on AWS GovCloud and you configure the target workload settings to launch the target instance on the dedicated host with the Host option set to Use auto-placement. Subsequently, if you use the Copy Target Workload Settings option to automatically copy the same settings to Target Workload Test Settings section, the value of the Host option in the Target Workload Test Settings section might not set to Use auto-placement. (Bug 1127351)

Workaround: In the Target Workload Test Settings section, manually set the Host option to Use auto-placement.

6.3 Known Issues for Migration to VMware vCloud Director

After Upgrade, the PlateSpinVAppTemplateList Does Not Contain an Entry for Migration of 64-Bit BIOS Workloads to vCloud

Issue: When you upgrade to PlateSpin Migrate 2019.2, the list of PlateSpin Replication Environment templates for VMware vCloud has not been updated to include the following entry to support migration of 64-bit BIOS workloads:

RepEnvImage64BitBIOS="PlateSpin Replication Environment - BIOS"

This entry is added automatically for new installations of PlateSpin Migrate. (Bug 1128244)

Workaround: Before you can migrate 64-bit BIOS workloads to vCloud, you must add an entry for the 64-bit BIOS Replication Environment Image to the PlateSpinVAppTemplateList parameter in the PlateSpin Server Configuration Settings.

To add an entry for 64-bit BIOS PRE for vCloud:

  1. Log in to the PlateSpin Migrate server, then go to the PlateSpin Server Configuration Settings page:

    https://<platespin-server-IP-address>/platespinconfiguration

  2. Search for vcloud to locate the PlateSpinVAppTemplateList parameter.

  3. Click Edit in the Value column for the parameter.

  4. On a new line below the current entries, add the following line:

    RepEnvImage64BitBIOS="PlateSpin Replication Environment - BIOS"

  5. Save the change.

Unable to Configure Static IP Address and DNS Servers on the Cutover vCloud Target VM for a Linux 7.x Workload

Issue: When you perform cutover of a supported Linux 7.x BIOS workload to vCloud, the cutover is successful and the static IP address that you configured in the migration job correctly displays in the vCloud Director. However, the configured static IP address and DNS servers are not set on the cutover target VM and the VM uses a DHCP address instead. This issue is not seen when you perform a test cutover of the Linux workload. (Bug 1124879)

Workaround: Manually configure the static IP address and DNS servers on the cutover target VM.

Replication Fails in a FIPS-Enabled Environment for vCloud and AWS Targets

Issue: In a FIPS-enabled environment, FIPS is enabled for the PlateSpin Migrate Server and source workloads. Replication of a FIPS-enabled workload to a target vCloud or target AWS platform fails with the following error:

Exception has been thrown by the target of an invocation.
This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

This error is not observed for migration of FIPS-enabled source workloads to other target platforms. (Bugs 1125662, 1125663)

Workaround: You can enable PlateSpin Migrate to suppress errors for non-compliant FIPS algorithms.

  1. In a text editor, open the ofxcontrollerexecution.exe.config file found in this folder:

    <install folder>\PlateSpin Migrate Server\Controller\Packages\0\C863075B-8130-4d29-893B-70FF2AD9308C\1

  2. Add the following element to the runtime section of the file:

    <configuration>
        <runtime>
             ...
            <enforceFIPSPolicy enabled="false"/>
        </runtime>
    </configuration>
  3. Save your changes.

6.4 General Issue

RHEL 6.10 Source Workloads Crash During Incremental Replication

Issue: During incremental replications, a system crash occurs for source Red Hat Enterprise Linux (RHEL) 6.10 workloads running Linux kernel 2.6.32-754.6.3.el6.x86_64. (Bug 1119323)

Workaround: The system crash is a Red Hat known issue for RHEL 6.10 running Linux kernel version 2.6.32-754.6.3.el6.x86_64. See the following Red Hat Knowledgebase Articles:

To avoid this issue, do either of the following:

  • Follow the Red Hat Bug Advisory RHBA-2018:3763, which will apply Linux kernel 2.6.32-754.9.1.el6.x86_64 to the source workload.

    -OR-

  • Use Linux kernel version 2.6.32-754.3.5.el6.x86_64 or earlier on the source workload.

After the crash occurs, the blkwatch driver might cause a failure in the normal boot process on the source workload. Remove the blkwatch driver until you have resolved the Red Hat issue. See How to Disable the blkwatch Kernel Module on Source Linux Workloads (KB 7006279).

7.0 Resolved Issues

PlateSpin Migrate 2019.2 resolves the following previously known issues.

7.1 Before Upgrade: Invalid URL for KB Article 7921083 How to Export and Import PlateSpin Database Data

Issue: During an upgrade from PlateSpin Migrate 12.3 to PlateSpin Migrate 2018.11, the Export the Data documentation link to KB Article 7921083 How to Export and Import PlateSpin Database Data goes to the location, but receives an error message: Document is not available. (Bug 1116641)

Fix: The upgrade now links to How to Export and Import PlateSpin Database Data (KB Article 7013175) at https://support.microfocus.com/kb/doc.php?id=7023175.

7.2 After VMware Maintenance or Update, VMware Target No Longer Appears in the Web Interface and Its Associated Workloads Go into an Unsupported State

Issue: If PlateSpin Migrate 12.3 refreshes a VMware target’s information during a VMware maintenance window or update, the VMware target can disappear from the Migrate Web Interface and its associated workloads go into an unsupported state. (Bug 1117364)

Fix: PlateSpin Migrate ensures that the VMware target does not get removed if a target refresh occurs during VMware maintenance or update. After the maintenance or update completes, you must refresh the target in Migrate before you resume migrations. See Best Practices for Maintaining or Updating VMware Environments That Are Configured as Migration Targets in the User Guide.

7.3 Deleting a Workload from the PlateSpin Migrate Client Does Not Remove the Workload from the Web Interface

Issue: When you use the Migrate Client to delete a workload, the workload is deleted from the Migrate Client but is not automatically removed from the Web Interface. Consequently, rediscovering the same workload fails. (Bug 1061693)

7.4 Discovering a Workload in the PlateSpin Migrate Client Fails When a Migration License Is Not Available

Issue: If you choose to discover a workload in the PlateSpin Migrate Client when there are no remaining migrations available for the license, the workload discovery job in the Migrate Client fails to initiate and no message is displayed. However, the workload is added in the Web Interface, which prevents rediscovery. (Bug 1061694)

7.5 Unable to Configure X2P Migration in PlateSpin Migrate Client for a Workload Discovered Using Migrate Agent

Issue: When you use PlateSpin Migrate Client to perform X2P Sync migration of a workload that is discovered using Migrate Agent, the PlateSpin Migrate Client interface displays an error and does not allow the migration to proceed. (Bug 1103168)

7.6 Configure AWS Migrations: Placement Group Validation Error Message Does Not List All the Unsupported Instance Types

Issue: When you configure migrations to AWS target, If you select an instance type that AWS does not support launching in a placement group, then PlateSpin Migrate displays a error message when you select a placement group. However, this error message might not list all the unsupported instance types. (Bug 1116718)

Fix: The message is generalized and does not list any of the unsupported instance types. Placement Group configuration in Migrate is limited to cloud instance types supported by Amazon EC2. Refer to AWS EC2 Documentation for the latest information about placement groups and AWS rules and limitations for using them:

7.7 PlateSpin Migrate Might Recommend an Unsupported EC2 Instance (A1) Powered by ARM-Based AWS Graviton Processors When You Configure Migration to AWS

Issue: When you configure migration of a workload to AWS, PlateSpin Migrate might recommend an EC2 Instance (such as A1) that is powered by ARM-Based AWS Graviton Processors if it matches the source workload's settings for cores, memory, volumes, and NICs. However, PlateSpin Migrate does not support the instance types that are powered by ARM-Based AWS Graviton Processor. (Bug 1122166)

Fix: PlateSpin Migrate now recommends only a supported instance type based on x86 and x64 processor architectures.

7.8 For Linux Migration to Azure, the Ethernet Interfaces Have Different Names on the Target VM

Issue: Because the MAC addresses for NICs on a target Linux VM in Azure are different than the MAC addresses on the source Linux workload, Linux assigns different names to them. For example, the eth0 and eth1 Ethernet interfaces on a source Linux workload become eth2 and eth3 on the target Linux VM in Azure. (Bug 967468)

Fix: The NIC names are properly assigned in the target VM after cutover.

7.9 VMware Tools Not Installed on Target Workload When You Use the X2P Workflow for Migrating a Workload to VMware

Issue: When you use the X2P workflow to migrate a workload to VMware, you are required to set up the VMware Tools for the target workload before you perform the conversion so that the configuration service can install the tools on the target VM when the target VM contacts the PlateSpin Server. See Setting Up VMware Tools for the Target Workload in the User Guide.

However, the VMware tools does not automatically install on the target workload if the target workload already has some version of VMware tools installed. (Bug 1117874)

7.10 Duplicate Validation Messages Are Displayed When Using the Copy Target Workload Settings Button

Issue: When you configure a workload for migration to AWS, if validation messages are being displayed in the Target Workload Settings panel when you click Copy Target Workload Settings, the same validator messages are triggered in the Target Workload Test Settings panel, but they are displayed in duplicate. (Bug 1118536)

Fix: Validation messages are no longer displayed in duplicate.

7.11 Cloud Charges Continue to Incur for a Target Azure VM That Is Shut Down After Cutover to Azure

Issue: When you migrate a workload to Microsoft Azure with a configuration set to shut down the target workload after cutover, PlateSpin Migrate shuts down the guest operating system after a successful cutover. The migrated workload is in a Stopped (Allocated) status in Azure. Although the workload guest operating system is powered off, the Azure VM continues to incur Azure charges for the allocated VM resources. (Bug 977144)

Fix: Migrate shuts down the VM gracefully and deallocates the VM resources. The VM is in a Stopped (Deallocated) state, which incurs no charges from Azure.

7.12 Restore Paging File Assignments Failed on Target at Test Cutover

Issue: During Test Cutover for a physical to vCloud migration where the source machine boots from SAN, the following error occurs during configuration of the target VM:

Restore paging file assignments Failed: Non-critical Error

After Test Cutover, no page file has been set for the target VM. This issue does not occur at Cutover. (Bug 1063327)

Fix: After Test Cutover, the page file is set for the target VM.

7.13 Preparing Test Cutover of a Windows Domain Controller Workload to AWS Stalls

Issue: The test cutover of a Windows Domain Controller workload to AWS stalls with the following recoverable error if you use an AWS Xen-based instance type: (Bug 1099182)

The Configuration service in the target machine does not seem to have started.

Fix: To migrate a Windows Domain Controller Workload to AWS, use a Nitro-based instance type such as c5, m5, r5, t3, c5d, m5d, or z1d.

7.14 Migration of a CentOS Workload to AWS Stalls

Issue: The migration of a CentOS 7 or 7.1 workload to AWS target stalls with a recoverable error. This is because the NVMe driver causes a kernel panic due to the reboot of the workload. (Bugs 1112284, 1113304)

Fix: You must not use a Nitro-based instance type such as c5, m5, r5, t3, c5d, m5d, or z1d for migrating a CentOS workload with version lower than 7.4. This is because migration of RHEL, CentOS, and Oracle Linux workloads using Nitro-based instance types is supported for versions 7.4 and later.

7.15 Migration of a Windows Server 2008 R2 Workload to AWS Gets Stuck During Cutover If the Cloud Instance Size is Configured as i3.16xlarge

Issue: If you choose to migrate a Windows Server 2008 R2 workload to an AWS target and configure the migration job to use the i3.16xlarge cloud instance size, the migration job gets stuck at AWS(PV)tools Installation step (Bug 1095580)

Fix: The i3.16xlarge cloud instance size is not supported for migration of Windows Server 2008 R2 Workload to AWS. Configure the migration job to use a supported cloud instance size other than i3.16xlarge.

7.16 Migration of an OEL or CentOS 6.x Source Workload on a VMware Host Fails

Issue: .When you migrate an OEL or a CentOS 6.x source workload that is on a VMware host, the migration fails if the SCSI adapter type is not Paravirtual and the network adapter is not VMXNET3.(Bug 1060573)

7.17 Prompted to Specify Domain Credentials During Incremental Replication Even If You Chose to Preserve the Source Domain Registration During Full Replication

Issue: Consider that you enable the Preserve Source Server’s Domain Registration option to preserve the source domain registration while using the PlateSpin Migrate Client to configure the migration of a source workload that is in a domain and then perform a full migration of the workload. Subsequently, if you use the Web Interface to perform an incremental replication, you are prompted to specify the domain credentials even though you chose to preserve the domain registration during the full migration.(Bug 1115649)

Fix: PlateSpin Migrate Web Interface no longer prompts you to specify the domain credentials during incremental replication if you have already preserved the domain registration during full replication using the PlateSpin Migrate Client.

7.18 Discovery of Source Linux Workloads Fails If the Workload Credentials Include Special Characters

Issue: When you discover a source Linux workload whose credentials include special characters, the discovery fails. (Bug 1119032)

Fix: PlateSpin Migrate now supports discovery of source Linux workloads having special characters in its credentials. However, combination of some special characters (such as &#, <A through <Z (upper and lower case), <!, </, <?) that are not allowed in ASP.NET web forms are not supported.

7.19 Replication Fails If the Cloud Account Credentials Include Special Characters

Issue: If the password for a cloud account includes special characters or is blank, replications to that account fail with the following error:

Failed to Authenticate user root. 
Permission denied (password).

Migrate is unable to take control of the replication environment because authentication fails. (Bugs 1128247, 1127892)

Fix: PlateSpin Migrate now supports using special characters in the credentials you provide for cloud accounts. Ensure that characters you use in credentials for cloud accounts comply with vendor requirements and limitations.

7.20 Prompted to Specify Domain Credentials While Editing the Test Cutover Settings Even Though the Test Cutover Target workload is in the Same Domain As Source Workload

Issue: Consider that you prepare migration for a workload that is configured such that the target workload joins a different domain during run cutover, but joins the same source domain during test cutover. On re-configuring the migration settings for this prepared workload, you are prompted to specify the domain credentials for the test cutover workload even though the workload is configured to retain the same domain as the source workload.(Bug 1110794)

Fix: PlateSpin Migrate Web Interface no longer prompts you to specify the domain credentials for the test cutover workload if the workload is configured to retain the same domain as the source workload during the test cutover.

8.0 Installing or Updating PlateSpin Migrate

PlateSpin Migrate 2019.2 provides the Install PlateSpin Migrate Prerequisites PowerShell script to check for and install prerequisite software and apply the appropriate configuration: ASP.NET, IIS, and .NET Framework. See Installing Prerequisite Software in the Installation and Upgrade Guide.

To install PlateSpin Migrate 2019.2, see Installing PlateSpin Migrate in the Installation and Upgrade Guide.

To apply PlateSpin Migrate 2019.2 to your PlateSpin Server, you must have an existing installation of PlateSpin Migrate 2018.11 on a supported Windows platform, with or without interim patches and hotfixes applied. See Upgrading Migrate in the Installation and Upgrade Guide.

NOTE:To upgrade from an existing installation of PlateSpin Migrate 2019.2 Server to a supported new host platform, see Upgrading Migrate to a New Host Platform in the Installation and Upgrade Guide.

9.0 Licensing Information

For information about activating a new license, see PlateSpin Migrate Product Licensing in the User Guide.

10.0 Previous Releases

For documentation that accompanied earlier releases, visit the PlateSpin Documentation website and scroll to the release that you are looking for.

11.0 Contacting Micro Focus

For specific product issues, contact Micro Focus Support at https://support.microfocus.com/contact/.

Additional technical information or advice is available from several sources:

12.0 Legal Notice

For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.microfocus.com/about/legal/.

© Copyright 2007 – 2019 Micro Focus or one of its affiliates.