Version 9.1 provides several new features, enhancements, and bug fixes.
For Release Notes documents that accompanied previous 9.x.x releases, visit the PlateSpin Migrate 9 Documentation Web Site and go to Previous Releases at the bottom of the main page.
New Source Workload Types: This release supports the following new workload types:
SUSE Linux Enterprise Server (SLES) 9
Open Enterprise Server (OES) 2
Oracle Enterprise Linux (OEL) 5.3, 5.4
Support for Paravirtualized Targets: You can now migrate Linux workloads to XEN-on-SLES (version 10) as paravirtualized VMs.
Bandwidth Throttling: This release provides greater control over the amount of network resources used by PlateSpin Migrate.
See Bandwidth Throttling
.
Compression: This release provides ways to reduce your networking costs by enabling you to have volume data compressed on the source workload as it is replicated to the target.
See Data Compression
.
Support for Network Address Translation (NAT): This release provides support for network configurations that use Network Address Translation (NAT).
See Migrations Across Public and Private Networks Through NAT
.
Improved X2P Migration Experience: The X2P migration mechanism has undergone several improvements and now provides a much broader support for vendor-specific driver management. In addition, the PlateSpin boot ISO image includes new tools, including a Windows driver injection utility for more robust driver management.
Support for GPT: This version provides support for source workloads (Windows Server 2008 and later) that use the GUID Partition Table (GPT) disk partition layout standard. Supported only for peer-to-peer migrations; not supported for workload imaging.
Support for Thin Disks: This release supports thin (thin-provisioned) virtual disks that appear to the VM to have a set size but only consume the amount of disk space that is required by that disk.
Enhanced support for VMware networking: This release supports:
Up to 10 virtual NICs per VM (ESX 4.x only)
VMXNET 2 and VMXNET 3 virtual network adapters
International Language Support: This release provides international language support (French, German, and Japanese) for the product interface and the documentation. 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.
Discontinued Support: Support for some older sources and targets has been discontinued.
VMware ESX 3.0.x is no longer supported as a migration target.
Red Hat Linux 7.3, Red Hat Enterprise Linux (RHEL) 2.1, and SUSE Linux Enterprise Server (SLES) 8 are no longer supported as migration sources.
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. The issue has been fixed.
Requirement to open port 3725 on target: The requirement to have port 3725 open on the target for block-level data replication caused migrations to fail when a target was located behind a NAT device. Port 3725 no longer needs to be open on the target (it must still be open on the source).
677413 Target VM blue screens with ‘Stop 7B’ error: A target VM might blue screen with a Stop 7B error after doing a server sync of a Windows 2008 x64 and a Windows 2008 R2 workload. The issue has been fixed.
Workloads cannot be migrated to Extensible Firmware Interface (EFI)-enabled hardware: This issue is currently under investigation.
595490 Preserving boot partition causing 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.
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.
698884: You cannot use a virtual CD-ROM drive when performing an ESXi to ESXi V2V migration if the version of the VMware Tools software is the same on the source and the target VM.
See KB Article 7008774.
666602: You might not be able to run a Windows NT4 migration from a PlateSpin Migrate Server installed on Windows 2008 and Windows 2008 R2. This issue is currently under investigation.
698721 Missing pre-installation requirement (documentation): Installation instructions require that IIS on 64-bit versions of Windows Server 2003 be configured to run in 32-bit mode. This requirement applies to the 64-bit versions of all supported operating systems, including Windows Server 2008 (64-bit) and Windows Server 2008 R2 (not stated in non-English documentation).
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.
506154 Special character in datastore name causing migration problems: Migration operations might fail when they are attempted on ESX datastores that have the + special character in the datastore name.
See KB Article 7008750.
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.
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.
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...).
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 Guidelines for Discovery Parameters
in your User Guide.
No software RAID support for Linux workloads: PlateSpin Migrate does not support Linux workloads with volumes on software RAID.
493589 (Windows sources) Non-default per-volume VSS settings are not preserved after migration: This issue is under consideration for an upcoming fix.
548208 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. This issue is under consideration for an upcoming fix.
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.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2011 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.