PlateSpin Migrate 2019.11 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.11 Documentation website.
This product contains undocumented utilities that the Technical Support team might use to diagnose or correct problems.
The following changes have been made to this document since the release of PlateSpin Migrate 2019.11.
|
Location |
Update |
|---|---|
|
This section is new. |
|
|
This section is new. |
PlateSpin Migrate 2019.11 server image and replication environment for Azure Global and Azure China are 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.
PlateSpin Migrate updates the AWS Quick Start support to help you quickly and easily deploy PlateSpin Migrate 2019.11 server on the AWS Cloud in addition to the existing support for deploying PlateSpin Migrate 2019.8 server on the AWS Cloud. For more information about the Quick Start, see Micro Focus PlateSpin Migrate on AWS.
PlateSpin Migrate 2019.11 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.
Support for New AWS Metal Instance Types
PlateSpin Migrate adds support for the following new AWS EC2 Bare Metal instances offered by Amazon Web Services since the Migrate 2019.8 release:
c5n.metal, c5.metal, i3en.metal
NOTE:These metal instances are supported on Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and all supported Linux workloads for migration to AWS.
Support for Using Same AWS Regions with Different AWS Accounts
PlateSpin Migrate supports the creation and use of multiple AWS target platforms with the same AWS region in different AWS accounts.
Support for Using Multiple vCloud Target Platforms with the Same Organization Name
PlateSpin Migrate supports the creation and use of multiple vCloud target platforms with the same Organization name.
Support for Migration to VMware vCloud Director Versions 9.7 and 9.5
PlateSpin Migrate adds support for migration to VMware vCloud Director versions 9.7 and 9.5.
PlateSpin Migrate adds support for the following source Linux workloads:
|
Platform |
Version |
Remarks |
|---|---|---|
|
Red Hat Enterprise Linux (RHEL) Oracle Linux Cent OS |
7.7 |
Precompiled blkwatch drivers for these workloads are not included in the PlateSpin Migrate software. Before you migrate these workloads, you must do one of the following to include the blkwatch drivers applicable for your Linux source workload:
|
|
SUSE Linux Enterprise Server (SLES) |
12 SP4 without BTRFS |
|
Support for Target VMware 6.7 U2 Platforms
VMware vCenter 6.7 U2
VMware ESXi 6.7 U2
Support for Target VMware 6.5 U3 Platforms
VMware vCenter 6.5 U3
VMware ESXi 6.5 U3
For detailed information and caveats about supported target virtualization platforms, see Supported Target Virtualization Platforms
in the User Guide.
Ability to configure the Single disk storage layout to assign all the data volumes or LVM volume groups to a single disk on the target workload. See Storage Disks and Volumes Using Migrate Web Interface
in the User Guide.
The Migrate Agent Utility driver-install command is enhanced to automatically compile blkwatch drivers and install them on the source Linux workload when none of the precompiled drivers exactly match the kernel running on your Linux workload. The compiled drivers are then automatically uploaded to the precompiled drivers folder in the PlateSpin Server library. See Migrate Agent Commands for Linux
in the User Guide.
Ability to Configure the Type of SCSI Adapter and VMware Tools for Installing on the Target Workload
By default, PlateSpin Migrate configures the SCSI adapter and VMware tools that are the best choice for the OS on the target workload. PlateSpin Migrate controls this behavior by using the UseSameAsSourceVMwareSCSIAdapterType parameter that is set to False by default. To enable PlateSpin Migrate to configure the same SCSI adapter as on the source workload and retain the source workload VMware tools on the target workload, set the value of UseSameAsSourceVMwareSCSIAdapterType parameter to True. See Configuring the SCSI Adapter and VMware Tools for the Target Workload
in the User Guide.
Ability to Configure the Azure Instance Type Used For the Azure Replication Environment Virtual Machine
For the Azure Replication Environment VM, PlateSpin Migrate Server by default uses the smallest instance size that is required for the workload migration based on the number of disk drives you configure for the target workload. To change the Azure instance type used during replication, set the value of the AzureInstanceSizeForReplicationEnvironment parameter to the Azure instance type you want to use for the Replication Environment Virtual Machine. See Configuring the Azure Instance Type Used For the Azure Replication Environment Virtual Machine
in the User Guide.
Modified the Default Replication Port Direction for Migrations to Non-Cloud Platforms from Source to Target
For migration to non-cloud platforms, the target workload used to contact the source workload to initiate the replication data transfer. PlateSpin Migrate 2019.11 now enables the source workload to contact the target workload (by default) for initiating the replication data transfer irrespective of the target platform. This is controlled at the server level by setting the default value of the SourceListensForConnection parameter to False. See Configuring the Contact Direction for the Replication Port
in the User Guide.
PlateSpin Migrate 2019.11 discontinues support for the migration of the SLES 11 SP3 source workloads to Azure cloud.
IMPORTANT:Before you upgrade from PlateSpin Migrate 2019.8 to PlateSpin Migrate 2019.11, ensure that you complete planned migrations that involve configurations and functions that will be deprecated in version 2019.11.
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.
This document lists the known issues specific to PlateSpin Migrate 2019.11 release. For information about previous releases known issues, which might continue to apply for this release unless they are marked as resolved in the subsequent releases, see the Previous Releases Release Notes.
Issue: The PlateSpin Migrate Web Interface displays an asterisk symbol for all unsupported AWS instances to indicate experimental support for such instances that are not tested for the release. PlateSpin Migrate 2019.8 did not include support for AWS instance types such as c5.metal, c5n.metal, i3en.metal and the PlateSpin Migrate Web Interface displayed the asterisk symbol for all such unsupported AWS instances.
After an upgrade, the Web Interface continues to display the asterisk symbol for such instances when you edit a migration job that is previously configured with an AWS instance type unsupported in PlateSpin Migrate 2019.8 even though the instance type is now supported in PlateSpin Migrate 2019.11. (Bug 1156296)
Workaround: The c5.metal, c5n.metal, i3en.metal instances are supported in PlateSpin Migrate 2019.11. Do one of the following:
Ignore the asterisk symbol for these instances and configure the migration job using these instances.
In the Migrate Web Interface, refresh the AWS target to remove the asterisk symbol for the supported instances.
Issue: In PlateSpin Migrate 2019.8, the Migrate Web Interface displayed an error message when you attempted to add the same cloud target more than once because adding the same cloud target multiple times was not supported.
After an upgrade, the Web Interface continues to display this error message when you add the same cloud target again even though PlateSpin Migrate 2019.11 supports multiple discovery of the following targets: (Bug 1156291)
AWS target platform with the same AWS region in different AWS accounts
vCloud target platform with the same Organization name
Azure target platform with the same Azure Location in different Azure subscriptions
Workaround: In the Migrate Web Interface, refresh the existing cloud (AWS, Azure, or vCloud) target before you add another one. For example:
If an AWS target with US West (Oregon) region is already added and you want to add another AWS US West (Oregon) target in a different AWS account, then click the refresh icon for the already added AWS US West (Oregon) target on the Targets page before you add a new AWS target with the same region.
If an Azure target with Central US location is already added and you want to add another Azure Central US target in a different Azure Subscription, then click the refresh icon for the already added Azure Central US target on the Targets page before you add a new Azure target with the same location.
Issue: An on-premise source workload cannot contact a target workload in Oracle Cloud to initiate replication because PlateSpin Migrate cannot discover the public IP of the target workload in Oracle Cloud. So, the target workload must contact the source workload to initiate replication. (Bug 1152580)
Workaround: Ensure that the source workload is reachable and set the SourceListensForConnection parameter to True to reconfigure the replication port direction on the Migrate Server for enabling the target workload to contact the source workload. See Configuring the Contact Direction for the Replication Port.
PlateSpin Migrate 2019.11 resolves the following previously known issues.
Issue: When you use PlateSpin Migrate Web Interface for semi-automated migrations to physical targets or for migrations to VMware, the migration fails if the target disk or datastore does not have enough space. The Web Interface does not prevent the configuration if the size difference is small. However, the migration fails if there is insufficient space available on the target at cutover or test cutover.
For X2P migrations, the migration fails with the following error: There is not enough space on target disk.
For VMware migrations, the migration fails with the following error: The ReConfigVM_task submitted to the VMware ESX server failed. Insufficient disk space on datastore.
(Bug 1136920)
Fix: PlateSpin Migrate Web Interface prevents the configuration and displays an error message if the target disk or datastore does not have the same or more storage space than the workload you want to migrate.
Issue: When you use the PlateSpin Migrate Installation Launcher to install PlateSpin Migrate Client on a computer that is not a PlateSpin Migrate Server host, the Install PlateSpin Client option is disabled (grayed out). (Bug 1148654)
Fix: The PlateSpin Migrate Installation launcher now lets you install PlateSpin Migrate Client on a computer that is not a PlateSpin server host.
Issue: For migrations to Hyper-V, you get a warning message for the Hyper-V target if the workload’s storage requirements will result in insufficient free space to be available on the specified Hyper-V server to meet its current storage allocations. (Bug 1144075)
Adding this disk to the selected datastore may exceed the amount of free space required for recovery points for other workloads
In addition, warning messages might be displayed for the workload volumes:
Insufficient disk space <volname>: is under allocated by xx GB
Fix: PlateSpin Migrate Web Interface now provides an appropriate error message for the Hyper-V target when the workload’s storage requirements will result in insufficient free space to be available on the specified Hyper-V server to meet its current storage allocations.
Issue: For migrations to Azure, a Managed Disk Name error might occur for Windows workloads that have multiple types of dynamic disk volumes (Spanned, Striped, Mirror, and RAID-5). The error message states the following naming requirements for Azure Managed Disks: (Bug 1146900)
Azure Managed disk names may be up to 80 characters long. They must begin with an alphanumeric character then may include alphanumeric, underscore, period, or hyphen characters.
Fix: If the displayed Managed Disk Name is valid, PlateSpin Migrate no longer displays the incorrect error message and the migration completes successfully.
PlateSpin Migrate 2019.11 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.11, see Installing PlateSpin Migrate
in the Installation and Upgrade Guide.
To apply PlateSpin Migrate 2019.11 to your PlateSpin Server, you must have an existing installation of PlateSpin Migrate 2019.8 on a supported Windows platform. See Upgrading Migrate
in the Installation and Upgrade Guide.
NOTE:To upgrade from an existing installation of PlateSpin Migrate 2019.8 Server to a supported new host platform, see Upgrading Migrate to a New Host Platform
in the Installation and Upgrade Guide.
For information about activating a new license, see PlateSpin Migrate Product Licensing
in the User Guide.
For documentation that accompanied earlier releases, visit the PlateSpin Documentation website and scroll to the release that you are looking for.
For specific product issues, contact Micro Focus Support at https://support.microfocus.com/contact/.
Additional technical information or advice is available from several sources:
Product information and resources: https://www.microfocus.com/products/platespin-migrate/
Micro Focus Customer Center: https://www.microfocus.com/customercenter/
Product knowledge base and videos: https://www.microfocus.com/support-and-services/
Micro Focus Communities for PlateSpin: https://community.microfocus.com/t5/PlateSpin/ct-p/PlateSpin/
PlateSpin Idea Exchange: https://community.microfocus.com/t5/PlateSpin-Idea-Exchange/idb-p/PlateSpin_Ideas/tab/most-recent/
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.
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.