Version 10.0.2 is the follow-on release after the PlateSpin Protect version 10 (English only) and 10.0.1 (international) releases. It introduces a number of new features, enhancements, and bug fixes.
For Release Notes documents that accompanied previous 10.x.x releases, visit the PlateSpin Protect 10 Documentation Web Site and check Previous Releases at the bottom of the main page.
The following new features are introduced in PlateSpin Protect version 10:
Protection support for additional workload types: This release extends protection support to the following workload types:
Microsoft Windows Server 2008 R2
Microsoft Windows 7
Support for Additional Target VMware Containers: This release extends protection support to the following VMware containers:
VMware ESX Server 4.1
Capability to Add and Access VM Containers by Using Windows Domain Credentials: You can now add and access the following VM containers by using your Windows domain credentials:
VMware ESX 4.0, 4.1
Block-Based Live Transfer support for protecting Windows volumes without drive letters: In previous releases, Windows volumes that did not have drive letters assigned might fail protection jobs.
Support for Bonded Networks: This release supports Linux source workloads with bonded NICs (link aggregation).
622112 Unable to Failover a Microsoft SQL Server cluster: An issue with MAC address configuration resulted in problems when trying to run a Failover or Test Failover of a Microsoft SQL Server cluster. This issue has been fixed.
625710 Unable to Test Failover after a node flip: An issue with updating cluster failover settings prevented Test Failover operations from successful completion after flipping the active node and running an incremental. This issue has been fixed.
639829 Server with multiple IP addresses failing to register a Linux physical target: Registration of a physical target for a Linux failback operation did not work properly if the PlateSpin Protect Server was configured with multiple IP addresses. This issue has been fixed.
635954 More than 4 NICs on a workload causing replication problems: Attempting to protect a workload that had more than 4 NICs resulted in an Error Preparing Replication with the following information in the error details: Index was outside the bound of arrays. This issue has been fixed.
622460 Failure to display product activation codes: Accessing product activation codes was cumbersome. This issue has been fixed; you can now look up product activation codes in a dedicated column in the PlateSpin Protect Web Client by clicking .
582005 Heavy load on ESX resulting in Config Service startup problems: Under certain circumstances (with ESX under heavy load and slow disk I/O), the Config Service did not start within 30 seconds and was subsequently killed by the Windows Service Control Manager (SCM). This issue has been fixed.
596420 Machines prepared for Server Sync in a previous release were not recognized: Machines that were prepared for synchronization through a previous release of PlateSpin Protect (Portability Suite) were not inventoried as valid synchronization targets in PlateSpin Protect 10. This issue has been fixed.
609918 Problem with automatic VMware tools installation during test failover: During a test failover of a protected 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 has been fixed.
600984 Workload license designations not reflecting hostname changes: The workload license designations screen did not reflect modified hostnames after failover. This issue has been fixed.
637066 Invalid characters in a workload’s machine.xml file causing discovery disruption: Invalid XML characters, occasionally found among source workloads’ service descriptions, were improperly filtered out of a workload’s machine.xml file, resulting in discovery or refresh problems. This issue has been fixed.
640618 Problem with incremental Failback of Windows workloads with dynamic disks: An incremental Failback operation fails if the protected workload had dynamic discs with no drive letters assigned.
Workaround: Before carrying out an incremental Failback operation, assign drive letters to the workload replica’s volumes and the dynamic disks of the Failback target (the original workload).
No software RAID support for Linux workloads: PlateSpin Protect does not support Linux workloads with volumes on software RAID.
590635 Inconsistent failover results after upgrading: Following the upgrade to PlateSpin Protect10, a failover operation might fail to complete or might not apply the correct failover parameters, such as the proper hostname and workgroup settings.
Workaround: Before performing a failover, manually run an incremental.
581860 Browser exception in the Chinese edition of the product: Attempting to connect to the PlateSpin Protect Server with a browser that does not have a specific version of Chinese added might result in Web server errors. For correct operation, use your browser’s configuration settings to add a specific Chinese language (for example, Chinese [zh-cn] or Chinese [zh-tw]). Do not use the culture-neutral Chinese [zh] language.
590484 Ambiguous reminder message: Upon removal of a workload, a reminder message in the PlateSpin Protect Web Client prompts you to ...uninstall Block Based Tools from the workload at the next scheduled downtime. The message is applicable only to Windows workloads. Windows clusters are unaffected.
610918 Unresponsive Expand and Collapse icons in integrated help: On some systems with enhanced browser security settings (such as Internet Explorer 8 on Windows Server 2008), the Expand and Collapse icons (+ and -) in the Table of Contents might fail to work. To fix the issue, enable JavaScript in your browser:
Internet Explorer: Click tab > zone > , then select the option for the feature.
Firefox: Click tab, then select the option.
493589 Non-default per-volume VSS settings are not preserved: This issue is under consideration for an upcoming fix.
558937 Failure of block-level replications that use VSS (Windows): If you are using third-party VSS-based backup software, block-level replications might occasionally fail.
Workaround: Use blackout windows. See your Application Configuration Guide.
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 © 2010 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.