PlateSpin Migrate version 11.0 provides a number of new features, enhancements, and bug fixes.
For documentation that accompanied earlier 9.x releases, visit the PlateSpin Migrate 11 Documentation Web Site.
This section records the additions or deletions to these Release Notes. All changes are pertinent for the Migrate 11.0 release and were implemented as a result of customer feedback or related testing.
The following updates were made:
|
Update |
Description |
|---|---|
|
Newly supported:section of What’s New in This Release. |
Added: Semi-Automatic conversion onto RHEL 6.4 KVM container. Added: Note to clarify the extent of testing on KVM platform. |
The following updates were made:
|
Update |
Description |
|---|---|
|
Newly supported:section of What’s New in This Release. |
Added: Semi-Automatic conversion onto SLES 11 SP3 Xen container for fully-virtualized guests |
Feature parity with PlateSpin Migrate 9.2: Because of the change to a new preboot environment based on Linux RAM disk, some features had been temporarily discontinued in the past release (9.3). The following features are restored in version 11 of the product:
Support for Imaging: I2I and I2X
Windows file-based conversions
Newly supported: This release introduces workload support for the following platforms:
Microsoft Windows Server 2012 R2
Windows 8.1
SUSE Linux Enterprise Server (SLES) 11 SP1, SP2, and SP3
Novell Open Enterprise Server (OES) 11 SP1
Red Hat Enterprise Linux (RHEL)/Oracle Enterprise Linux (OEL) 5.9, 5.10, 6.4, 6.5
The following are also now supported:
vSphere 5.0 Update 2, 5.1 Update 1, and vSphere 5.5 workload containers
Windows workloads with UEFI/GPT
Semi-automatic conversion to Windows 2012 R2 Hyper-V Generation 1
Semi-Automatic conversion onto SLES 11 SP3 Xen container for fully-virtualized guests
Semi-Automatic conversion onto RHEL 6.4 KVM container
NOTE:Although PlateSpin Migrate can technically accomplish migrations onto any fully-virtualized hypervisor, we have performed only limited migration testing onto the KVM platform.
Miscellaneous: The following features are also new with this release:
A thoroughly tested SLES 11 SP3-based Linux RAM Disk (the temporary pre-execution environment for the migration of all workload types) with added tools.
Ability to upgrade from PlateSpin Migrate 9.2 and 9.3
The product has been localized for installation and use on machines configured for the German, French, and Japanese languages.
Installation of the PlateSpin Migrate 11.0 server on a Microsoft Windows 2008 64-bit host is currently not supported.
PlateSpin Migrate 11.0 does not support offline migration for Windows workloads.
The following is a list of bugs that were fixed for this release:
699774 - Linux BBT Driver package is not picked up by the server. The Migrate installation program now uses a package installer to deploy BBT driver packages.The Migrate Server now picks up 2.package.
790944 - Following a serial number change, resetting volume devices leaves all volumes unmounted and partitioning fails. This issue is resolved when mounting volumes with the new PlateSpin Linux RAM disk.
834553 - A migration (V2P) of a Windows 2008 R2 workload to a Dell R720 results in some NICs not working. Code changes have corrected the problem.
835805 - Target VM retaining registry entries for Source NIC. Code changes have corrected the problem.
843800 - Migration fails because disk inventory orders disks in order of discovery rather than disk type. The issue caused migration to fail when the inventory discovered HP Smart Array disks with a cciss driver before SCSI disks. Code changes have corrected the problem.
844431 - Migration fails if a physical machine with UEFI-based firmware is converted to a virtual machine. Code changes have corrected the problem.
844486 - Replication cannot find boot.ini file on source. A code change to return the actual boot.ini filename prior to replication has corrected the problem.
856929 - P2V migration fails with error: Argument cannot be null. Parameter name: path1. Code changes have corrected the problem.
861474 - P2P migration fails with error: The drive name does not exist. Parameter name: driveName. Code changes have corrected the problem.
864484 - Job wizard does not start. Error: System not referenced exception, object reference not set to an instance of an object. Code changes have corrected the problem.
865272 - Creating a VM fails on vCenter Server that has a distributed switch. Code changes have corrected the problem.
No software RAID support for Linux workloads: PlateSpin Migrate does not support Linux workloads with volumes on software RAID.
Requirements for VMware DRS Cluster support: PlateSpin Migrate supports VMware Clusters with and without DRS enabled, and with any level of DRS (Manual, Partially Automated, or Fully Automated). However, to be a valid migration target, your VMware Cluster must be discovered via vCenter and not by directly inventorying individual ESX servers.
See “Discovery Guidelines for Machine Types and Credentials” in your User Guide.
493589 (Windows sources) Non-default per-volume VSS settings are not preserved after migration: This issue is under consideration for an upcoming fix.
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. This issue is under consideration for an upcoming fix.
506154 Special character in datastore name causing migration problems: Migration operations might fail when they are attempted on ESX datastores that have the “+” or other special characters in the datastore name.
See KB Article 7009373.
595490 Preserving boot partition causes migration problems: In some migration scenarios, the system improperly allows you to preserve your boot partition on the target, preventing the proper workload from booting. This issue is under investigation.
Workaround: Do not opt to preserve your boot partition on the target.
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.
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.
655828 Failure to mount NSS volumes: After a migration is completed, NSS volumes with snapshots enabled are not automatically mounted as expected.
See KB Article 7008773.
680259 (VMware 4.1) Poor networking performance by traffic-forwarding VMs: In some scenarios, the replica of a workload that is forwarding network traffic (for example, if the workload’s purpose is to serve as a network bridge for NAT, VPN, or a firewall) might show significant network performance degradation. This is related to a problem with VMXNET 2 and VMXNET 3 adapters that have LRO (large receive offload) enabled.
Workaround: Disable LRO on the virtual network adapter. For guidance, see the VMware vSphere 4.1 Release Notes (scroll down to the bulleted item Poor TCP performance...).
685509 Failure with Access Denied error during replication to an image stored on a network share: The Controller service on Image servers that use network shares for storage does not preserve the service Log On As credentials after an upgrade. Image operations fail with an Access Denied message until the controller service is updated with the correct Log On As credentials.
See KB Article 7008772.
692680 VSS snapshots are not preserved: VSS snapshots taken by third-party applications on the source workload are not replicated to the target upon migration.
702152 Migration over WAN taking a long time if target VM host has a high number of datastores: Under some circumstances, when your Migrate server is connected to the VM host over WAN, and if your VM host has a high number of datastores, the process of locating the appropriate ISO image required for booting the target might take longer than expected. This issue is under investigation.
779194 Unmapped /home directory is disabled and unmounted after one time server sync: If you perform a server sync and then unman the /home partition to none, the partition /home directory should be mounted and enabled on the target server, instead it is disabled and unmounted.
Workaround: Following the Server Sync, uncomment the appropriate line in the target server’s /etc/fstab file.
See KB Article 7014638.
810460 VMware tools are not installed during a conversion of a Windows 20212 server core: VMware tools are not installed during a conversion of a Windows 2012 server core.
Workaround: Install the VMware tools manually after the conversion.
822601 Network card is not initialized on SLES 11 target VM hosted on Windows 2008 Hyper-V host: If you perform a SLES 11 workload (cloned VM) migration using the semi-automated method to a target VM (faked physical) on a Windows 2008 Hyper-V host, the process freezes at the "Configuring OS" step.
Workaround: For information about working around this issue, see KB 7012911.
824724 Target VM does not boot after migration from VMware ESX to Citrix Xen if boot files are located in second disk: When a VM is converted from VMware ESX to Citrix Xen and its boot files are allocated in second disk, the VM does not boot and manual intervention is requested. This is because Citrix XEN VM tries to boot with disk 0 rather than with the bootfiles allocated to disk 2.
Workaround: To resolve this problem, rearrange the virtual-disk position in XenCenter so that the virtual machine boots from the virtual disk containing the operating system. The knowledge article at the Citrix Web site includes information about how to change the position of the virtual disk containing the operating system.
See also KB Article 7012906.
825016 XenServer tools are not being removed after conversion: XenServer tools on a Windows VM in a Citrix XenServer hypervisor environment are not removed when the VM is converted to a VMware container or a physical container.
Workaround: The user must manually uninstall the XenServer tools after conversion.
825434 After migration, the primary partition (C:\) is converted to a logical partition on the target: Scenario: Moving or copying a Windows OS machine with more than three primary partitions to a physical machine where a Windows OS has been installed with minimum 3 primary partitions. At least one primary partition is preserved in the target machine.
Effect: After the migration, the Windows OS machine is unable to boot.
Example: The following error occurs when Windows 2003 machine is converted to Physical machine:
Windows could not start because the following file is missing or corrupt: <Windows root>\system32\ntoskrnl.exe.Please re-install a copy of the above file.
Workaround: For information about working around this issue, see KB Article 7012913.
826545 When Migrate undiscovers a machine, the machine node shown on the ESX host is not undiscovered: When you undiscover a workload, it displays as such in the Migrate client, but the ESX host shows that the node is not undiscovered.
Workaround: Undiscover the workload on the ESX host, then refresh the ESX host.
839329 - Attempt to retrieve data from VMware vCenter Server failed with the following exception: Permission to perform this operation was denied.
This problem can be corrected by following the procedures to define VMware Roles with tools as described in Using Tools to Define VMware Roles
in the PlateSpin Migrate 11.0 User Guide.
843431 - Attempting to boot from Hard Drive (C:) - Error loading operating System. MBR is corrupted. This problem can be corrected by running the ./BcdEditor /fixboot command in the LRD.
See also KB Article 7014709.
859440 V2P conversion hangs at the configuringoperating system step. When there are multiple boot options in the firmware and the hard disk is not the first boot device in the boot options list, the target machine does not boot from hard disk and conversion hangs.
Workaround: In the boot options of the physical machine, change the boot order so that is the first option, then restart the machine.
See also KB Article 7014623.
864325 Windows 8.1 workloads converting UEFI to BIOS fail to convert at the “sending files” step. The default OEM installation of Windows 8.1 (UEFI) creates a recovery partition with insufficient free space, making it impossible to create a Volume Shadow Copy (VSS) for the partition.
Workaround: Remove or expand the recovery partition. For more information, see KB Article 7014696.
864326 Conversion fails while downgrading from UEFI to BIOS firmware: The conversion of a UEFI workload (Windows 6.2 and above kernel versions) to BIOS-based machine fails at the Preparing OS step because the active partition cannot be found to update boot parameters.
Workaround: To work around this problem, update the partition type of where the system volume is present in either the source workload or the image. Use Export and Import of UI options or OFX Browser to edit the XML. For a complete list of steps, see KB Article 7014637.
865570 File-based transfer breaks for Windows 2012 R2 UEFI workload: X2P File-based transfer of Windows 6.2 and above kernel versions fails during the sending and receiving files stage.
Workaround: To force file transfer to work in this X2P scenario, you need to disable the CPU advanced flags in the firmware: VT-d, VT-s, Execute Disable Bit. For more information, see KB Article 7014698.
866467 Image capture of a Windows 32-bit OS fails: Migrate expects a folder named C:\Windows\Boot\EFI to be present in the source server for exporting content for future use. The folder is not present in Windows 32-bit operating systems earlier than Windows 2008/Vista, so when Migrate exports BCD information to the folder, the operation fails with the error:
Error message: Failed: C:\Windows\Boot\EFI
Workaround: To work around this issue, you need to create the C:\Windows\Boot\EFI folder, then create a Directory Junction under C:\Windows for C:\Windows\System32. For more information, see KB Article 7014710.
THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.
For purposes of clarity, any module, adapter or other similar material (“Module”) is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.
This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.
This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.
U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.
© 2014 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.