Version 4.0, a hardware and software release of Forge, provides new features, enhancements, and bug fixes.
For Release Notes documents that accompanied previous 3.x releases, visit the PlateSpin Forge 4 Documentation Web Site and go to Previous Releases in the Table of Contents at the bottom of the main page.
Feature parity with Forge 3.3 & upgrade from Forge 3.3 and 3.4
Support for UEFI Windows workloads if system volume is on a disk that is smaller than 2 TB.
Support for SLES 11 SP2 & 3, OES 11 SP1 workloads.
NOTE:Forge 4 does not support Windows 2012 or Windows 2012 R2 server class workloads.
This release addresses the following bugs:
672815 Unable to start initial full replication due to missing vNIC-to-vNetwork mapping: In some situations during the Prepare Replication operation, a container refresh might interfere with the collection of inventory information about a newly created failover VM, impacting its network mapping and impairing the replication.
697049 Protection contract broken after vNIC's MAC address change: After setting up a protection contract, changing the MAC address of the failover VM’s virtual network adapter (either manually or automatically by the hypervisor) impaired the contract.
722096 Failover VM info removed from inventory upon refreshing container: Occasionally, when the PlateSpin Server was unable to properly retrieve information from its container, a Refresh Container operation might result in the removal of information about the failover VM, negatively impacting the protection contract and failover functionality.
734525 (Linux) Unable to connect to port 3725: An issue with how communication with a Linux workload with two NICs was being managed might occasionally cause problems in connectivity.
736280 Erroneous localhost.localdomain hostname in Linux failback: On failback, if the target hostname was set to No Change, the workload was assigned a localhost.localdomain hostname.
744867 Problem inventorying NLB cluster hosts: In some cases an issue with the collection and processing of Windows Network Load Balancing (NLB) Cluster hosts might cause configuration problems on the VM replica.
753157 Replication reports by e-mail not functioning properly: In some situations the removal of an email account that was listed as a recipient for PlateSpin Forge e-mail notifications might cause erratic behavior, such as ‘flooding’.
753449 (Windows) Workload hostname failing to change as required: In some cases the system might fail to assign a new hostname to the failover VM of a protected Windows Server 2008 workload when it was configured to join a domain.
756871 (Linux) Incorrect sequence of 2 NICs on target after failover: In some cases an issue with target NIC mapping caused networking problems, such as the Novell eDirectory service binding to the wrong NIC.
762850 (Linux) Unable to use non-default shells: PlateSpin Forge failed to protect Linux workloads that had a command line interpreter other than the Bash shell, which PlateSpin Protect Server uses by default. You can now override the default shell used by PlateSpin Forge Server to execute commands on a Linux workload.See KB Article 7010676.
768137 (Windows) Registry hives not replicating correctly during incrementals: In some cases an issue with how Windows Registry changes are handled in Windows Server 2003 and Windows XP might result in a mismatch between the Registries of a protected workload and its VM replica.
770964 (Windows) Problem running custom configuration script: An issue with how the product handled batch files prevented certain custom configuration scripts from running properly.
770996 Wrong user in Events report: In Events reports, all jobs were erroneously shown as initiated by system, instead of the actual username.
773097 (Windows XP) Incorrect SCSI controller type on failover VM: VM replicas of Windows XP workloads were being assigned BusLogic SCSI controllers (instead of LSI SCSI controllers), which negatively impacted failover functionality.
No software RAID support for Linux workloads: PlateSpin Forge does not support Linux workloads with volumes on software RAID.
Support for the GUID Partition Table (GPT) standard: PlateSpin Forge supports the protection of workloads that use the GPT disk partition layout standard. However, targets are always configured to boot from BIOS using an MBR (Master Boot Record). This limitation has the following implications:
Max 2 TB per volume: The maximum size of a protected workload’s volumes is restricted to 2.19 terabytes, the maximum for a partition allowed by MBR.
Physical targets for failback must boot from BIOS: Most hardware vendors provide support for multiple disk partitioning standards; for information on how to configure a physical target to boot from BIOS, or to reconfigure GPT hardware to operate in “legacy mode” (with support for BIOS), see your hardware vendor documentation.
See also KB Article 7005452.
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).
581860 Browser exception in the Chinese edition of the product: Attempting to connect to the PlateSpin Forge 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.
590635 Inconsistent failover results after upgrading: Following an upgrade to PlateSpin Forge, 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.
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.
611105 Missing protection contracts after upgrade: After upgrading your Forge appliance to version 3, protection contracts with workloads in a or a state might be missing from the user interface. This issue is under consideration for an upcoming fix.
655828 Failure to mount NSS volumes: Upon failover or test failover, 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 details, see the VMware vSphere 4.1 Release Notes. Sscroll down to the bulleted item Poor TCP performance....
686911 Problems with file downloads from or uploads to datastore: Under certain conditions, where the protection target is a VMware DRS Cluster, the system might fail to upload or download a file, such as a boot ISO image. This negatively impacts a protection contract.
See KB Article 7008306.
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.
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 Forge 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.
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.