PlateSpin Migrate 12.2.1 Release Notes

January 2018

PlateSpin Migrate 12.2.1 includes new features and enhancements and resolves several previous known issues. The service pack is cumulative and includes all patches and hotfixes released since the PlateSpin Migrate 12.2 release.

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

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

1.0 Documentation Updates

This section contains information on documentation content changes that were made in the Release Notes after the initial release of PlateSpin Migrate 12.2.1.

1.1 January 2018

Location

Change

Mouse Does Not Work in the VM Console Window for the Target VM

This topic addresses a VMware Tools issue.

2.0 What’s New

PlateSpin Migrate 12.2.1 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. You can post feedback in the PlateSpin Migrate forum on Micro Focus Forums, our online community that also includes product information, blogs, and links to helpful resources.

2.1 Rebranding

PlateSpin Migrate 12.2.1 has been rebranded as a Micro Focus product. The rebranding does not impact product features, installation paths, and file names. Your existing licenses remain valid.

2.2 Performance

PlateSpin Migrate 12.2.1 provides improved performance for the following components:

  • Data transfer: Optimized heartbeat and logging during transfers

  • Web Interface: Workload configuration tasks

2.3 Supported Configurations

PlateSpin Migrate 12.2.1 enhances support for source workloads and target containers.

Supported Windows Workloads

PlateSpin Migrate 12.2.1 adds support for the migration of the following Windows workloads, as supported by the target platform vendor:

Platform

Remarks

Microsoft Windows Server 2016

Migration to VMware containers requires VMware 6.0 or later.

Microsoft Windows Server 2016 Cluster

Supported only for migration to VMware containers running VMware 6.0 or later.

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

Supported Linux Workloads

PlateSpin Migrate 12.2.1 adds support for the following 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.9 and 7.3

PlateSpin Migrate does not support the XFS version 5 (v5) file system on Red Hat Enterprise Linux 7.3 and distributions based on RHEL 7.3.

Oracle Linux

Distributions based on RHEL.

Precompiled blkwatch drivers are available for the standard kernel and Unbreakable Enterprise Kernel (UEK) for RHEL 6.7 and later.

CentOS

Distributions based on RHEL.

Use RHEL precompiled blkwatch drivers.

  • Paravirtualized Linux source workload having both paravirtual and standard kernels and running on Citrix XenServer or KVM can now be migrated to a target platform as a fully virtualized guest. However, the block-based drivers for Xen kernel must be manually compiled.

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

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

Supported Target Platforms

PlateSpin Migrate 12.2.1 adds support for the following target platforms. For detailed support information, see the Supported Configurations section in the User Guide.

Target Virtualization Platforms

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

  • VMware

    • VMware vCenter and ESXi 6.5

    • VMware vCenter and ESXi 6.0 U3

    • VMware vSAN 6.2

    • Multiple NICs for target Linux workloads (previously supported for Windows)

    NOTE:The following VMware datastore types available in VMware 6.0 and later are not supported:

    • Virtual Volumes

    • NFS 4.1

    • vFlash

  • Microsoft Hyper-V

  • KVM

    • Virtio devices

  • Xen

    • SUSE Linux Enterprise Server 11 SP4

  • Citrix XenServer

    Use the PlateSpin ISO for SUSE Linux Enterprise Server 11 SP3 as the LRD to boot the virtual machine. Citrix XenServer 6.5 and earlier does not support SLES 11 SP4.

Target Cloud Platforms

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

  • Amazon Web Services

    • Windows License activation support

    • Three PlateSpin Replication Environments (PREs) in AWS

      • PlateSpin Replication Environment - Linux (bring your own license (BYOL))

      • PlateSpin Replication Environment - Windows

      • PlateSpin Replication Environment - Windows (BYOL)

  • Microsoft Azure

  • VMware vCloud Director

    • Version 5.6.x

Support of the BBT Driver for Windows Cluster Migration

PlateSpin Migrate 12.2.1 adds support for driver-based block-based transfer for incremental replications of the original active node. Using a BBT driver requires a node reboot during setup. Use the BBT driver only with shared storage in Fibre Channel SANs. See Block-Based Transfer for Clusters in the User Guide.

WARNING:Do not attempt to use SingleNodeBBT on clusters with shared iSCSI drives. It renders the cluster unusable.

Support for UEFI

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.

Support for MPIO

PlateSpin Migrate 12.2.1 supports Multipath I/O (MPIO) for Fibre Channel (FC) SANs on the following workloads with all SAN disks. Workloads must boot from SAN disk. Mixed local and SAN disks are not supported for MPIO.

  • Windows Server 2012 R2

  • Windows Server 2012 R2 Cluster

  • Windows Server 2008 R2

  • Red Hat Enterprise Linux 7.2

See Multipath I/O in the User Guide. See also PlateSpin ISO.

Support for FCoE

PlateSpin Migrate 12.2.1 supports Fibre Channel over Ethernet (FCoE) for P2P and P2V migrations of the following workloads:

  • Windows Server 2012 R2

  • Windows Server 2008 R2

  • SUSE Linux Enterprise Server 11 SP4

See FCoE SANs in the User Guide. See also PlateSpin ISO.

Enhanced VLAN Tagging

PlateSpin Migrate 12.2.1 Client enables you to specify the virtual network ID to be used on the target machine that is hosted on a Hyper-V server. This release adds support for VLAN tagging for the following:

You can also edit the VLAN tag during Replication and Prepare for Sync jobs.

2.4 Enhanced Configuration Options

PlateSpin Migrate 12.2.1 adds several configuration options for migration in the Migrate Web Interface and Migrate Client.

Migration to AWS

  • Number of NICs: Add or Remove NICs

  • Update Regions list

  • Specify target AWS instance name during Full Replication

See Configuring Full Migration of a Workload to Amazon Web Services in the User Guide.

Migration to Azure

  • Ability to configure a target workload VM in Azure using only private IP addresses in an Azure VPN deployment scenario.

  • Enhanced configuration options:

    • Azure Resource Group (new or existing)

    • Network Connections in Target Workload Settings (for Cutover):

      • Enable/disable NIC. You can disable all but one source NIC for migration.

      • (Optional) NIC Resource Group defaults to the Azure Resource Group. You can specify a separate resource group for each NIC.

      • Public IP (required for the Primary NIC in a non-VPN deployment scenario).

      • Primary NIC.

    • Network Connections in Target Workload Test Settings (for Test Cutover):

      • Available NICs are the same as those selected for Cutover.

      • (Optional) NIC Resource Group defaults to the Azure Resource Group. You can specify a separate resource group for each NIC.

      • Public IP (required for the Primary NIC in a non-VPN deployment scenario).

      • Primary NIC.

    • Cloud Instance Size menu clearly displays values for each VM instance: CPUs, Memory, Maximum NICs, Maximum Data Disks, and Supports Premium Storage.

    • Volumes enables you to deselect volumes to satisfy the maximum disk size allowed by the selected Cloud Instance Size in Azure.

    • Services (or Daemons) to stop for Cutover with Incremental Replication enables you to stop services on source workloads during cutover.

  • Suggested resource names use hyphens instead of underscores for new workload migration configuration.

See Migration to Microsoft Azure in the User Guide.

Migration to VMware vCloud

  • Ability to deselect all but one NIC for migration

See Migration to VMware vCloud Director in the User Guide.

Migration to VMware

  • Ability to deselect all but one NIC for migration

  • Ability to specify whether to Connect at Power On

  • Ability to install VMware tools on Windows target VMs on VMware in a semi-automated (X2P) migration

See Migration to VMware in the User Guide.

Migration to Any Target Platform

  • Ability to concurrently stop dependent and related kernel services is available for automatic and semi-automatic conversions. It is available for Migrate Client and Migrate Web Interface.

2.5 PlateSpin Migration Factory

PlateSpin Migrate 12.2.1 provides enhancements for event notifications and REST APIs to enable integration with PlateSpin Transformation Manager 1.1.1 and PlateSpin Migrate Connector 1.1.1 for PlateSpin Migration Factory:

  • Event messages for state change events for all migrations (Client and Web Interface) are published for subscribers.

  • On the Workloads list, the Web Interface provides read-only display of status for migration jobs configured and executed in the Migrate Client. See Status for Workloads Managed in Migrate Client in the User Guide.

  • Workload configuration data is accessible to PTM.

  • Discovery database is accessible to PTM.

Key enhancements made in Transformation Manager and Migrate Connector for PlateSpin Migrate 12.2.1 include:

  • Ability to track state change events for imported workloads with matching external migrations performed on PlateSpin Migrate servers

  • Ability to bookmark pages, including all the search, navigation, and state conditions.

  • Dashboard enhancements:

    • Dashboard statistics: The PTM dashboard statistics include imported workloads with matching external migrations performed on Migrate servers.

    • What’s Happening displays key events for the current date, or for a specified date. Users quickly know what workloads to work on today, and what workloads to prepare for an upcoming date.

    • Bookmarks displays the user’s personal bookmarks. Users can easily return to favorite pages or dialogs without performing repetitive and complex queries. Links honor the permissions of the logged-in user.

    • Recently Viewed displays links to pages and dialogs that the user recently accessed for view or edit actions. Users can quickly return to a location without repeating the navigation or complex search criteria. Links honor the permissions of the logged-in user.

See the PlateSpin Transformation Manager Documentation website.

2.6 Migrate Agent Utility

PlateSpin Migrate 12.2.1 provides the Migrate Agent Utility for Linux. Migrate Agent for Linux works with automated migrations performed in the Migrate Web Interface and the Migrate Client. It is not supported for semi-automated (X2P) migrations. See Migrate Agent Utility for Linux in the User Guide.

PlateSpin Migrate 12.2.1 enhances the Migrate Agent Utility for Windows to support automated migrations performed in the Migrate Client in addition to the Migrate Web Interface. It is not supported for semi-automated (X2P) migrations. See Migrate Agent Utility for Windows in the User Guide.

2.7 PlateSpin ISO

In this release, PlateSpin ISO uses SUSE Linux Enterprise Server 11 SP4 for the Linux RAMDisk (LRD).

  • The default file includes drivers and functionality to support Fibre Channel over Ethernet (FCoE) for semi-automated X2P migrations. For supported workloads, see Support for FCoE.

  • The MPIO file includes drivers and functionality to support Multipath I/O for semi-automated X2P migrations. For supported workloads, see Support for MPIO.

A PlateSpin ISO for SUSE Linux Enterprise Server 11 SP3 is available to use for target virtualization platforms that do not support SUSE Linux Enterprise Server 11 SP4. It does not support FCoE or MPIO.

See Downloading the PlateSpin ISO Images in the User Guide.

2.8 PlateSpin Configuration Parameters

PlateSpin Migrate 12.2.1 adds parameters in the PlateSpin Configuration tool:

  • Windows Cluster: The PlateSpin global configuration setting WindowsClusterMode determines the method of block-based data transfer for incremental replications as driverless (Default) or driver-based (SingleNodeBBT). See Support of the BBT Driver for Windows Cluster Migration.

  • Azure: The following Azure settings determine whether a PlateSpin Server supports target subscriptions in the Azure global environment or in the sovereign Azure China environment.

    • AzureAuthenticationAdddress

    • AzureCloudAddress

    • AzureStorageEndpointStorage

    See Configuring the Target IaaS Environment for Azure Cloud in the User Guide.

  • AWS: The following AWS settings lets you configure whether or not AWS should manage the Microsoft software licensing compliance on the target Windows workload.

    • AWSActivateWindows

    • AWSKMSServers

    • KMSClientSetupKeys

    See Configuring OS License Activation on Windows Targets Migrated to AWS in the User Guide.

  • Networking: The following networking settings lets you configure whether or not PlateSpin Migrate should install network drivers on the target workload.

    • EnableLightNetworking

    • HostNamesForLightNetworking

2.9 Install PlateSpin Migrate Prerequisites Script

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

3.0 Deprecated Functionality

PlateSpin Migrate 12.2.1 no longer supports the following:

  • Installation of PlateSpin Migrate Server on Windows Server 2012.

  • Migration for the following desktop workloads:

    • Windows Vista SP1 and later

    • Windows XP SP1 and later

  • Migration to target VMs or target containers on virtual hosts running Microsoft Windows Server 2008 and 2008 R2 with Hyper-V.

  • Migration to target VMs on Red Hat Enterprise Server 6.x with KVM.

  • Migration to target VMs on SUSE Linux Enterprise Server 11 SP3 with KVM.

4.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.

4.1 Known Issues for Upgrade

The following issues are being researched:

Web Interface Does Not List Resource Groups When You Configure a Workload for Migration to an Azure Target for the First Time Post Upgrade

Issue: After you upgrade the Migrate server to version 12.2.1, if you use the Web Interface to configure a workload and select an Azure target for the first time after the upgrade, the Azure Resource Group and Resource Group menus do not list any resource groups.

Workaround: In the Web Interface, go to Targets and refresh the target Azure containers to enable the listing of resource groups in the Configuration page for migration to Azure.

Target Cloud Containers and Associated Workloads Are Not Imported

Issue: If your user password for a target Cloud container changes or expires after you export the database and before you import the data after upgrade, the container is not imported and its associated workload configurations are corrupted in the imported database. The container and workloads are not displayed in the Web Interface. The workloads are visible in the Migrate Client, but cannot be managed. Manually re-adding the container and workloads in the Web Interface fails because their objects are already present in the database. (Bug 1033680)

Workaround: To use the same Migrate server for migrations to the target Cloud container, you must re-install PlateSpin Server, which resets the database. You must re-configure all target containers and workloads.

To avoid the issue, ensure that credentials in the Migrate database are valid and unchanged for target Cloud containers at export and import. See Ensuring Valid Credentials for Target Cloud Containers in the Installation and Upgrade Guide.

4.2 Known Issues For Migration to Azure

The following issues are being researched:

Some Cloud Instance Sizes Are Incorrectly Displayed as Not Supporting Premium Storage in the Web Interface

Issue: Some Cloud Instance Sizes that support Azure Premium Storage display incorrectly in the Migrate Web Interface as not supporting Premium Storage. The display error occurs because of a modified naming convention in Azure for newly introduced instance sizes. PlateSpin Migrate recognizes the instances properly as supporting Premium Storage; the product functionality is not affected. (Bug 1071399)

Workaround: Look at the name of the Cloud Instance Size to determine whether it supports Premium Storage. The second word contains an S or s if the instance supports Premium Storage. For example, Standard E64s v3 supports Premium Storage, but Standard E64 v3 does not.

OL 7.3 UEFI Running RHCK: Preparing Test Cutover Fails

Issue: For Oracle Linux 7.3 UEFI running RHCK kernel, Preparing Test Cutover fails as follows:

  • For Azure: Displays error: Configuration service in the target machine does not seem to have started.

  • For vCloud: The status displays as running but the target VM displays the grub> prompt.

This issue is not observed on OL 7.3 with RHCK for BIOS, nor for OL 7.3 with UEK for UEFI or BIOS. (Bug 1067023)

Workaround: None.

RHEL 7.3 UEFI to BIOS Migration Fails Incremental Replication at PrepOSToBoot; Cannot Determine the Location of grub.cfg

Issue: For RHEL 7.3 and distributions based on RHEL 7.3, incremental replications for UEFI to BIOS migrations fail during Preparing Target Machine.to Boot Operating System because it cannot determine the location of the grub.cfg configuration file. This error occurs in Azure and vCloud. (Bug 1066071)

Workaround: After the failure, repeat Run Migration (Incremental).

Linux Workloads: Boot and Root Partitions Must Be on the Same Disk

Issue: Microsoft Azure does not support Linux workloads that have the boot (/boot) partition on a different disk than the root (/) partition. (Bug 972062)

Workaround: 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.

PlateSpin OFX Controller Does Not Start on a Virtual Machine Source

Issue: If you configure Migrate to install the block-based component during the first replication, PlateSpin OFX Controller might not start on the source workload during the Install Block-Based Components step. The Service Manager reports this problem if the VM is running so slowly that the OFX Controller startup event times out. (Bug 1033673)

Workaround: Manually start PlateSpin OFX Controller on the source workload. To avoid the problem, you can configure the workload to install the block-based component during Prepare Workload instead of First Replication, or you can increase the Memory and CPU resources of the source VM to improve its startup performance.

4.3 Known Issues For Migration to Amazon Web Services

The following issues are being researched:

Migration of a RHEL 5.x Source Workload Installed With a Non-Default Disk Layout Fails

Issue: If you choose to migrate a RHEL 5.x source workload that is installed with a non-default disk layout, the migration fails. (Bug 1069738)

Workaround: None.

Migration of a RHEL 5.x Source Workload That is On a VMware Host Fails

Issue: If you choose to migrate a RHEL 5.x source workload that is on a VMware host, the migration fails if VMware tools are not installed on the source workload. (Bugs 1069538,1069540)

Workaround: Before you migrate a RHEL 5.x source workload, you must ensure that the VMware tools are installed on the source workload.

4.4 Known Issues For Migration to Hyper-V

The following issues are being researched:

Setting a MTU Value Less Than 1500 Is Not Honored For Migrations to Hyper-V Host With Synthetic Adapters

Issue: If the MTU value is set to less than 1500 when you migrate workloads to Hyper-V host having synthetic adapters, the set MTU value is not honored. (Bug 1062546)

Workaround: None. This is a limitation with Hyper-V host having synthetic adapters.

Error When Migrating a Windows Workload to a Hyper-V Target Using the X2P Workflow

Issue: When you use the X2P workflow to migrate a Windows 2003 or 2008 workload to a Microsoft Hyper-V host, the job stalls or goes into a recoverable error at the Uninstalling Controller step. This is because the integration services driver is not available on the Hyper-V host (Bug 1053168, 1062716)

Workaround: Manually add the integration services driver on the Hyper-V host. See KB Article .

4.5 Known Issues For Migration to KVM

The following issue is being researched:

Migration of a Workload to a KVM Virtual Machine Having Virtio Disk as the Boot Disk and IDE Disk as the Data Disk Fails

Issue: When you migrate a workload to a KVM virtual machine that has its Virtio disk configured as the boot disk when both IDE and Virtio disks are available on the VM, the migration of the workload fails at Creating and Partitioning Volumes step. (Bug 1063004)

Workaround: On the KVM VM, do one of the following and then migrate the workload:

  • Configure the IDE disk as the boot disk and the Virtio disk as the data disk.

  • Configure the Virtio disk as the boot disk and a non-IDE disk such as SATA or SCSI disk as the data disk.

4.6 Known Issues For Migration to vCloud

The following issues are being researched:

OL 7.3 UEFI Running RHCK: Preparing Test Cutover Fails

Issue: For Oracle Linux 7.3 UEFI running RHCK kernel, Preparing Test Cutover fails as follows:

  • For Azure: Displays error: Configuration service in the target machine does not seem to have started.

  • For vCloud: The status displays as running but the target VM displays the grub> prompt.

This issue is not observed on OL 7.3 with RHCK for BIOS, nor for OL 7.3 with UEK for UEFI or BIOS. (Bug 1067023)

Workaround: None.

RHEL 7.3 UEFI to BIOS Migration Fails Incremental Replication at PrepOSToBoot; Cannot Determine the Location of grub.cfg

Issue: For RHEL 7.3 and distributions based on RHEL 7.3, incremental replications fail for UEFI to BIOS migrations during Preparing Target Machine.to Boot Operating System because it cannot determine the location of the grub.cfg configuration file. This error occurs in Azure and vCloud. (Bug 1066071)

Workaround: After the failure, repeat Run Migration (Incremental).

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)

Workaround: None.

4.7 Known Issues For Migration to VMware

The following issues are being researched:

Mouse Does Not Work in the VM Console Window for the Target VM

Issue: Sometimes on Test Cutover or Cutover, the mouse does not work for the VM in the vSphere Web Client. That is, when you perform Actions > Open Console to open the VMware Web Console, the mouse pointer does not function properly within the virtual machine console window.

Workaround: Restart the VM to allow VMware Tools to recognize the USB Controller for the mouse. In vSphere, select Actions > Power > Restart Guest OS.

PlateSpin OFX Controller Does Not Start on a Virtual Machine Source

Issue: If you configure Migrate to install the block-based component during the first replication, PlateSpin OFX Controller might not start on the source workload during the Install Block-Based Components step. The Service Manager reports this problem if the VM is running so slowly that the OFX Controller startup event times out. (Bug 1033673)

Workaround: Manually start PlateSpin OFX Controller on the source workload. To avoid the problem, you can configure the workload to install the block-based component during Prepare Migration instead of First Replication, or you can increase the Memory and CPU resources of the source VM to improve its startup performance.

4.8 General Issues

The following issues are being researched:

Migrate Client: After Undiscover Server, the Jobs View Does Not Show the Undiscover Server Job Status

Issue: After performing an Undiscover Server action, the Jobs view does not display a job entry for the Undiscover Server job. The user cannot easily determine whether the job completed successfully. Undiscover Server jobs were available in the Jobs view in PlateSpin Migrate 12.2. (Bug 1071172)

Workaround: None.

Migration of a Windows Server 2003 Workload Might Get Stuck at Configuring Operating System Step

Issue: When you choose to migrate a Windows Server 2003 workload, the migration job might stall or go into a recoverable error at the at Configuring Operating System step. (Bug 1069833)

Workaround: To resume the conversion, restart the target workload.

Web Interface Does Not Display the Edited Host Name of a Discovered Workload

Issue: If you edit the host name of a discovered workload, the new host name displays in the Migrate Client, but not in the Web Interface. (Bug 1042869)

Workaround: After the host name of a discovered workload is changed, undiscover the workload and then rediscover it.

Undiscover Target Job Displays an Error in the Migrate Client Even When the Target is Successfully Undiscovered

Issue: When you use the Migrate Client to undiscover a target residing on an unreachable vCenter, the status of the undiscovery job in the Migrate Client displays as Failed. However, the target is successfully undiscovered from both the Migrate Client and the Web Interface. (Bug 1062786)

Workaround: Ignore the job status message.

X2P Migration of a Workload to a Hyper-V VM Having Dynamic Memory Enabled Fails

Issue: When you use the X2P workflow to migrate a source workload to a Hyper-V VM that has dynamic memory enabled, the migration fails at Sending and Receiving files step. (Bug 1064801).

Workaround: Before you perform the migration, disable the dynamic memory on the Hyper-V VM. You can enable the dynamic memory on the Hyper-V VM post the migration.

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)

Workaround: Manually remove the workload from the Web Interface before you rediscover the workload.

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 Client.

You can discover the workload in the client only after the migration license is available. Before you rediscover the same workload, you must ensure to remove the workload from the Web Interface. (Bug 1061694)

Workaround: None.

Discovering a Source Workload By Host Name Fails When a Discovered Under Control Target Has the Same Host Name As the Source

Issue: If you choose to discover a source workload by its host name when an already discovered under control target has a matching host name, the discovery fails (Bug 1061695).

Workaround: Use the IP Address of the source workload instead of the host name to discover it.

Email Notification for the Replication Report Is Missing Content

Issue: Email notifications for the Replication Report are sent to recipients as scheduled, but the expected replication statistics for the active migrations are missing. The message reads: No workloads available yet for this report. The Web Interface shows that migrations are configured and replications occurred during the reporting period. (Bug 1023917)

Workaround: None. View the replication statistics for workload migrations in the Web Interface.

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)

Workaround: Edit the SCSI adapter type to Paravirtual and the network adapter type to VMXNET3 and then perform the migration.

5.0 Resolved Issues

The following is a list of issues that were resolved for this release:

5.1 Unable to Migrate a RHEL 7.2 Source Workload Installed With a Non-Default Disk Layout

Issue: If you chose to migrate a RHEL 7.2 source workload that is installed with a non-default disk layout, the migration failed. (Bug 1032569)

Fix: You can now migrate a RHEL 7.2 source workload even if it is installed with a non-default disk layout.

5.2 The Web Interface Displayed More Than One Instance of the Same Discovered Object Post Upgrade

Issue: If you use the PlateSpin Migrate Client to discover workloads and targets and have discovered the same object in different networks of the Migrate Client, then only the object that you discovered in the default network displays on the PlateSpin Migrate Web Interface. However, on upgrading to Migrate 12.2, more than one instance of the discovered object displays on the Web Interface depending on the number of times it has been discovered in the various networks. (Bug 977577)

Fix: This issue is no longer applicable because the Web Interface and the Migrate Client interface are no longer synchronized during the upgrade process.

5.3 Configure Fails for Migration of Oracle Linux 5.x with Paravirtual Kernel to VMware

Issue: Configuration fails for migration of a Oracle Linux 5.x with a Paravirtual kernel under Citrix XenServer to a target VM under VMware. (Bugs 1001424, 1001433, and 1001436)

Fix: This release has a workaround in place to handle the VMware non-support for boot disks on guest operating systems running Red Hat Enterprise Linux 5.x (32-bit and 64-bit) and derivative distributions.

5.4 Silent Install Is Not Supported for Migrate Servers Used with PlateSpin Transformation Manager

Issue: Silent installation of PlateSpin Migrate did not properly install the Event Messaging feature used by PlateSpin Transformation Manager. (Bug 1020689)

Fix: Install Visual C++ 2013 on the planned Migrate server prior to performing the silent install. See Installing Visual C++ 2013 for Batch-File Installation of PlateSpin Migrate in the Installation and Upgrade Guide.

6.0 Installing or Updating PlateSpin Migrate

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

To apply the PlateSpin Migrate 12.2.1 service pack to your PlateSpin Server, you must have an existing installation of PlateSpin Migrate 12.2, with or without interim patches and hotfixes applied. See Upgrading PlateSpin Migrate in the Installation and Upgrade Guide.

7.0 Licensing Information

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

8.0 Previous Releases

For documentation that accompanied earlier releases, visit the PlateSpin Migrate 12.2.1 Documentation website and scroll to Previous Releases.

9.0 Contacting Micro Focus

If you have suggestions for documentation improvements, click comment on this topic at the bottom of any of its HTML pages, or email Documentation-Feedback@netiq.com.

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

Additional technical information or advice is available from several sources:

10.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 © 2017 NetIQ Corporation, a Micro Focus company. All rights reserved.