PlateSpin Migrate 9 Release Notes

July 30, 2010

1.0 About this Release

PlateSpin Migrate 9 introduces a number of important changes, new features, enhancements, and bug fixes.

This release upgrades and replaces any PlateSpin Migrate edition of the PlateSpin Portability Suite, which has been discontinued. For information on PlateSpin Protect 10, which replaces the PlateSpin Protect editions of the Portability Suite, see the PlateSpin Protect 10 Documentation Web Site.

2.0 New Features in Version 9

This release introduces the following major new features and enhancements:

  • Live migration support for Linux workloads: This release supports live migrations of a number of Linux workloads. See Supported Linux Workloads.

  • Support for migrating Windows clusters: This release supports the migration of Windows clusters into a virtual machine. See Migrating Windows Clusters.

  • Enhanced support for ESX 4: This release provides support for distributed switches on a target VMware ESX 4 server.

  • International Language Support: This release provides international language support (French, German, and Japanese) for the product interface and the documentation. Note that the English version of the documentation at the PlateSpin Migrate 9 Documentation Web Site, which is updated on a regular basis, should be considered as the most up-to-date version at all times.

    International versions will include a cumulative update at the time of the next major release.

3.0 Important Changes in Version 9

Note the following important changes in version 9:

  • Discontinued third-party block-based component (Windows): The third-party (SteelEye) block-based component has been discontinued. Block-level migrations of Windows workloads can be carried out using PlateSpin’s custom block-based component that leverages the Microsoft Volume Snapshot Service (VSS). Consequently, support for block-level migrations of Windows Server 2000 workloads has been discontinued and can be done only at the file level. This also applies to Windows Server 2003 workloads that do not have Service Pack 1 (or later) installed.

  • Discontinued target VM platforms: Some obsolete virtualization platforms have been discontinued. For a list of the currently supported VM platforms, see Supported Target Virtualization Platforms.

  • Discontinued support for PlateSpin Migrate and PlateSpin Protect collocation: PlateSpin Migrate and PlateSpin Protect, formerly part of the PlateSpin Portability Suite, are separate products with separate installers, and cannot be installed on the same host. If you have an existing Portability Suite license that covers both products, upgrade to either Migrate 9 or Protect 10, and contact PlateSpin Support for splitting your license.

4.0 Known Issues in Version 9

  • 493589 (Windows sources) Non-default per-volume VSS settings are not preserved after migration: The issue is under investigation.

  • 548208 (vCenter) Discovery failure if vCenter has an ESX server with no datastore: VMware vCenter discovery fails if an individual ESX server managed by vCenter has no datastore configured.

    Workaround: add a datastore to the ESX server and try again.

  • 505426 (ESX4) No warning or error on wrong vCPU selection: If the number of the requested vCPUs exceeds the number of physical CPUs on the ESX 4 host, the requested number is ignored and the target VM is created with a single vCPU without a warning. The issue is under investigation.

  • 604320 (Linux to ESX 4) Problem completing migration if the source OS has autologin or CD automount features enabled: The migration is also affected if you log in to the target during the job’s Configuration step.

    Workaround: Disable the autologin and CD automount features on the source; avoid logging in to the target workload prior to the completion of the migration.

  • 609918 Problem with automatic VMware tools installation during P2V: During a P2V migration of a SUSE Linux Enterprise Server (SLES) 11 SP1 workload, the virtual CD-ROM device might fail to mount on the recovery workload, impacting the installation of the VMware Tools software and causing warnings. This issue is being investigated.

  • 609885 (ESX 4) Non-ASCII characters in the Migrate Server hostname preventing workload migrations: Migrations to a VMware ESX 4 system fail if your PlateSpin Migrate Server has non-ASCII characters in its hostname.

    Workaround: Change the name of the Migrate Server host to contain ASCII-only characters.

  • 619942 Failure to execute a post-migration script with Unicode characters in the filename: If you use Unicode characters in the filename of your post-migration script, the script fails to execute.

    Workaround: Use only ASCII characters when naming a post-migration action.

  • 597846 (NT 4 to ESX 4) No post-migration networking: Upon migrating a Windows NT 4 workload to a VMware ESX 4 system, the target VM might have no networking.

    Workaround: 1. Remove any Ethernet adapters and restart the workload, 2. Add an Ethernet adapter by using the Have Disk... option and pointing the system to the vmxnet folder of VMware Tools installation directory (the default path is C:\Program Files\VMWARE\VMware Tools\DRIVERS\vmxnet). Select the VMware Virtual Ethernet Adapter option and ignore any warnings, 3. Configure the Ethernet adapter as required and restart the workload.