PlateSpin Protect version 11.0.1 provides minor enhancements and bug fixes to the product.
For Release Notes documents that accompany hotfix Protect releases, visit the PlateSpin Protect 11 Documentation Web Site.
For Release Notes documents that accompanied previous Protect 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.
This section includes cross references to content in this document that has been newly added, deleted, or modified. Changes are dated for convenience.
Added information about Release Notes for hotfix releases of PlateSpin Protect 11.0.1.
The following updates have been made to these Release Notes:
|
Update |
Description |
|---|---|
|
New bullet item included in Known Issues. |
Provided instructions for German, French, Japanese, Chinese Traditional, and Chinese Simplified users who unsuccessfully try to access product Help from the menubar. |
The following updates have been made to these Release Notes:
|
Update |
Description |
|---|---|
|
New bullet item included in What’s New in This Release. |
Updated the list to indicate actual supported platforms for PlateSpin Server installation as documented in System Requirements in the PlateSpin Protect 11.0.1 Installation and Upgrade Guide. |
The following updates have been made to these Release Notes:
|
Update |
Description |
|---|---|
|
Bug 892202 in Known Issues. |
Newly-identified Known Issue regarding a false validator warning displayed while protecting a Linux workload. |
Support for Microsoft Windows 2008 R2 clusters.
Support for ESXi 5.5 U1 as a supported VM container, which enables support for 2TB (or larger) disks for Windows UEFI workloads using GPT. It also enables support for protecting Windows 8/8.1 and Windows Server 2012 workloads.
Support removed for installing the Protect Server on Windows Server 2012, Windows Server 2008 SP2, Windows Server 2003, and Windows Server 2003 R2 (32-bit and 64-bit)
This release addresses the following bugs:
869036 - The PlateSpin Server fails to install on Windows 2008 R2. The product now uses the .NET 4 framework for installation launcher prerequisites. As a result, the server installation on Windows 2008 R2 is now successful.
881197 - Unable to manage target VM settings with VIC; target created as VM version 10. The version for the target VM for failover was being incorrectly set. We added a config setting to control the maximum allowed hardware version when creating the failover VM. It now defaults the created target VM as version vmx-09.
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.
698611 - Full cluster replication failure under certain circumstances: If a Windows 2008 R2 Cluster protection contract is set up through the sync to an existing VM method, and if the active cluster node “flips” prior to the full replication, the full replication job fails.
See KB Article 7008771.
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.
892202 - Validator warning on block-based kernel driver may not be always accurate. Currently, when you add a Linux workload for protection, the product interface might display a message informing you that the system is
Unable to find a compiled version of the block-based kernel driver to exactly match the kernel on this Linux workload....
The message advises further to build a block based driver upon the next replication.
This validator message is likely inaccurate, due to the addition of hundreds of newly- supported Linux distributions for which Protect has a pre-compiled version of the blkwatch driver (seeLinux Distributions Supported by Protect
in the PlateSpin Protect 11.0.1 User Guide). If your workload (that is, the Linux distribution) matches an entry on the list, you can ignore the message and continue.
892206 - Incorrect link to Knowledgebase article with information about compiling a custom block-based driver: When you add a Linux workload to Forge or Protect, the product might not be able to find a block-based kernel driver to match the kernel of that workload. When this happens, a warning message is displayed with a link to a Knowledgebase article explaining how you can build a new custom driver for the workload.
Currently, the message inaccurately provides a link to a Novell site, http://www.novell.com/support/viewContent.do?exteralId=7005873. Please use the following NetIQ URL to navigate to the correct KB article: https://www.netiq.com/support/kb/doc.php?id=7005873.
Localized Help from Menu “Not Found”: The launch of localized versions of help files (German: de, French: fr, Japanese: ja, Chinese Traditional: zh-CHT, and Chinese Simplified: zh-CHS) available from the Help menu fails because of an error in packaging those files for the installation of the shipping version of the product.
To remedy the error:
Navigate to the following location on the PlateSpin Server:
...\PlateSpin Protect Server\PlateSpin Forge\web\doc\<language>\Help\protect-Help
Inside this folder, you will find 158 separate .html files, along with two subfolders:
\images
\ui
Copy these 160 items (copy the subfolders “as-is”) to the following location:
...\PlateSpin Protect Server\PlateSpin Forge\web\doc\<language>\Help\
In effect, you are moving the files up one directory in the file structure where they can be correctly called by the help system.
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.
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.
© 2015 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.