PlateSpin Protect version 11.0 provides new features and enhancements.
For Release Notes documents that accompanied previous 10.x releases, visit the PlateSpin Protect 11 Documentation Web Site and go to Previous Releases in the Table of Contents at the bottom of the main page.
Feature parity with Protect 10.3; upgradeability from Protect 10.3 and Protect 10.4
Support for vSphere 5.0 Update 2, vSphere 5.1 Update 1 and vSphere 4.1 Update 3
Full UEFI and GPT support for all Windows workloads
Support for workloads on the following platforms:
Windows 8, 8.1
Windows 2012, 2012 R2
SUSE Linux Enterprise Server (SLES) 11 SP2, SP3
A new REST-based API.
VMware Site Recovery Manager (SRM) integration
Localized for installation and use on machines configured for the German, French, Japanese, Chinese Traditional, and Chinese Simplified languages
PlateSpin Protect 11.0 does not support Microsoft Windows clustering configuration.
The following bugs, discovered in prior releases, have been fixed in PlateSpin Protect version 11.0 (reference includes Bugzilla bug number and summary):
No software RAID support for Linux workloads: PlateSpin Protect does not support Linux workloads with volumes on software RAID.
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 “Protection Tiers” in your User Guide).
590635 Inconsistent failover results after upgrading: Following an upgrade to PlateSpin Protect, 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, run a replication.
595490 Preserving boot partition on failback causes failback to stall: In some failback scenarios, the system improperly allows you to preserve an active (or boot) partition on the target, preventing the target from booting properly. This issue is under investigation.
Workaround: In Failback Details, do not opt to preserve any boot partitions on the target.
638392 ESX 4.1: Direct host discovery results in missing VM port groups if dvSwitch port groups share the same name.
Workaround: Ensure that port group names are unique.
702152 Protection over a WAN takes a long time if VM container has a large number of datastores: Under some circumstances the process of locating the appropriate ISO image required for booting the target might take longer than expected. This might happen when your PlateSpin Server is connected to the VM container over a WAN and your VM container has a large number of datastores. This issue is under investigation.
737715 Unable to relocate failover VM using Storage vMotion: In some circumstances, where your protection container is a VMware DRS Cluster in vSphere 5 and the initial replica of the workload is created incrementally, Storage vMotion might be unable to relocate the failover VM’s disk files across shared storage locations.
For workarounds, see KB Article 7008494.
781217 (SLES 9) Issue with volumes mounted using UUIDs: An issue with how mount points on SLES 9 workloads are looked up and how PlateSpin Protect handles Linux volumes might negatively impact the protection of SLES 9 workloads with volumes that are mounted by UUIDs. This issue is being investigated.
Workaround: Modify the workload’s /etc/fstab configuration file to use device names instead of UUIDs for storage devices and partitions. See KB Article 7010812.
860917 Cannot prepare OES workload for incremental replication: If you create a VM or modify an existing VM in the VMware Virtual Infrastructure Client (VIC) and select as the Guest Operating System, the VM appears in the PlateSpin Browser (as an unknown OS type), but it is not listed at all in the drop down list in the Prepare for Incremental Replication page of the Protect Web UI.
Workaround: To make this VM available as a target for X2V replication, in the VIC, change the operating system type to and refresh the container. The VM is then listed in the Protect UI.
862269 Full replication of a Windows 2012 R2 block-based disk with complex partitioning might fail: Testing has shown that a full replication of a Windows 2012 64-bit workload with complex disks (that is, more than 57 partitions) fails in PlateSpin Protect. Make sure the workload you attempt to replicate has no more than 57 partitions or volumes.
863173 The X2P failback of Linux workloads causes failure of the X Server graphical interface: A protected Linux workload replicated to a target, failed over, and then failed back to a physical target loses functionality of its X Server interface.
Workaround: The issue is caused by a reconfiguration of the failed-over VM when VMware tools are installed. To correct this, use the following command to find the files with the string BeforeVMwareToolsInstall in the filename:
find / -iname '*BeforeVMwareToolsInstall'
After you identify all such files, move them back to their original locations, then reboot the workload to fix the workload's X Server interface.
864326 Conversion fails while downgrading from UEFI to BIOS firmware: The conversion of a protected UEFI workload (Windows 6.2 and above kernel versions) to fail back 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.
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information Web site.
For general corporate and product information, see the NetIQ Corporate Web site.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
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.
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.
© 2014 NetIQ Corporation and its affiliates. All Rights Reserved.
If this product claims FIPS compliance, it is compliant by use of one or more of the Microsoft cryptographic components listed below. These components were certified by Microsoft and obtained FIPS certificates via the CMVP.
893 Windows Vista Enhanced Cryptographic Provider (RSAENH)
894 Windows Vista Enhanced DSS and Diffie-Hellman Cryptographic Provider (DSSENH)
989 Windows XP Enhanced Cryptographic Provider (RSAENH)
990 Windows XP Enhanced DSS and Diffie-Hellman Cryptographic Provider (DSSENH)
997 Microsoft Windows XP Kernel Mode Cryptographic Module (FIPS.SYS)
1000 Microsoft Windows Vista Kernel Mode Security Support Provider Interface (ksecdd.sys)
1001 Microsoft Windows Vista Cryptographic Primitives Library (bcrypt.dll)
1002 Windows Vista Enhanced Cryptographic Provider (RSAENH)
1003 Windows Vista Enhanced DSS and Diffie-Hellman Cryptographic Provider (DSSENH)
1006 Windows Server 2008 Code Integrity (ci.dll)
1007 Microsoft Windows Server 2008 Kernel Mode Security Support Provider Interface (ksecdd.sys)
1008 Microsoft Windows Server 2008
1009 Windows Server 2008 Enhanced DSS and Diffie-Hellman Cryptographic Provider (DSSENH)
1010 Windows Server 2008 Enhanced Cryptographic Provider
1012 Windows Server 2003 Enhanced Cryptographic Provider (RSAENH)
This product may also claim FIPS compliance by use of one or more of the Open SSL cryptographic components listed below. These components were certified by the Open Source Software Institute and obtained the FIPS certificates as indicated.
918 - OpenSSL FIPS Object Module v1.1.2 - 02/29/2008 140-2 L1
1051 - OpenSSL FIPS Object Module v 1.2 - 11/17/2008 140-2 L1
1111 - OpenSSL FIPS Runtime Module v 1.2 - 4/03/2009 140-2 L1
Note: Windows FIPS algorithms used in this product may have only been tested when the FIPS mode bit was set. While the modules have valid certificates at the time of this product release, it is the user's responsibility to validate the current module status.
EXCEPT AS MAY BE EXPLICITLY SET FORTH IN THE APPLICABLE END USER LICENSE AGREEMENT, NOTHING HEREIN SHALL CONSTITUTE A WARRANTY AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, AND WARRANTIES INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OR CONDITION OF FITNESS FOR A PARTICULAR PURPOSE ARE HEREBY EXCLUDED TO THE EXTENT ALLOWED BY APPLICABLE LAW AND ARE EXPRESSLY DISCLAIMED BY NETIQ, ITS SUPPLIERS AND LICENSORS.