PlateSpin Protect 11.2 SP1 Resolved Issues

Issue: Because of changes in the Windows cluster support in version 11.2, PlateSpin Protect requires full DNS resolution for forward lookup and reverse lookup of the IP addresses for the cluster and its nodes. (Bug 947072)

Fix: Ensure that the PlateSpin Server can resolve DNS forward lookup and reverse lookup for the IP addresses of the cluster and its cluster nodes. You can update the DNS server or update the local hosts file (%systemroot%\system32\drivers\etc\hosts) on the PlateSpin Server host.

Issue: The PlateSpin.VMwareRoleTool.exe utility reported exceptions for some permissions that were missing for the PlateSpin Virtual Machine Manager in the PlateSpinRole.xml file. (Bugs 969197, 962265, 958576)

Fix: The PlateSpinRole.xml file now includes all required minimum permissions.

Issue: Previously, the email notifications and reports were not available after you upgraded to 11.2. Your settings for these features were reset during the upgrade. (Bug 947597)

Fix: PlateSpin honors your SMTP settings, email notification settings, and replication reports.

Issue: After an upgrade to version 11.2, the vSphere Client might not properly report the CPU cores and cores per sockets settings for previously configured target VMs on ESXi 5.5 and later. (Bug 947170)

Fix: The VM CPU and Sockets settings are reported properly in the vSphere Client.

Issue: After an upgrade to version 11.2, an insufficient licenses error can occur for a Linux or Windows workload that was configured to change CPU settings for sockets and cores per socket. (Bug 946562)

Fix: No improper errors occur when you modify CPU settings for sockets and cores per sockets.

Issue: The PlateSpin Configuration page does not display descriptions for TakeControlSockets and TakeControlCoresPerSocket parameters. (Bug 946558)

Fix: Descriptions are available for the TakeControlSockets and TakeControlCoresPerSocket parameters on the PlateSpin Configuration page.

Issue: Previously, the default Cluster IP Address names on the PlateSpin Configuration page did not match the default names in the Windows cluster in the Chinese Simplified and Chinese Traditional languages. The PlateSpin Server was unable discover the cluster workload, and the add workload action failed. (Bug 945124)

Fix: The default Cluster IP Address names now match the default names in the Windows cluster in the Chinese Simplified and Chinese Traditional languages.

Issue: When protecting a Windows Server 2008 R2 workload to VMware 5.5 or 6.0, a non-critical error occurs for installing tools when Install VMware Tools is enabled. However, the VMware tools are properly installed. (Bug 992705)

Fix: The installation of VMware Tools on a Windows Server 2008 R2 workload completes without errors.

Issue: When you use the Web Interface to discover workloads and targets, the discovery might fail with a warning message. (Bugs 978308, 975092, 946132)

Fix: To avoid discovery failures caused by timing issues, a default heartbeat startup delay of 15 seconds (15000 ms) is set on the OFX Controller. The setting is configurable by adding the HeartbeatStartupDelayInMS registry key on the source workload. This registry key is not configured by default. See Modifying the OFX Controller Heartbeat Startup Delay in the PlateSpin Protect User Guide.

Issue: Previously, Windows Sever 2003 workloads might hang during discovery. (Bug 951595)

Fix: Discovery no longer hangs for Windows Server 2003 workloads.

Issue: An error occurred for workloads with GPT partitions larger than 2.2 TB for target workloads on VM containers using ESXi 6.0. (Bug 935511)

Fix: This release supports workloads with GPT partitions larger than 2.2 TB for target workloads on VM containers using supported versions of VMware ESXi and vCenter 5.5 and higher.

Issue: The first full replication for a RHEL 6.7 workload on a VMware 6.0 container fails because of an Out of Memory condition during replication. (Bugs 988814, 980995, 970315)

Fix: In the PlateSpin Configuration settings, the default value for the TakeControlMemorySizeInMB parameter has been increased from 512 MB to 768 MB. See Take Control Memory SizeTake Control Memory Size in the PlateSpin Protect 11.2 SP1 Release Notes.

Issue: After a full replication for a workload running Microsoft SQL Server 2012, the SQL Server’s differential backup fails until a full backup with Microsoft tools runs again. This issue might occur if Microsoft VSS Writer for SQL Server (SqlServerWriter) is running during the replication. (Bug 983567)

Fix: The issue with SqlServerWriter has been resolved. SQL server differential backups are not broken.

Issue: Replication fails because of an unauthorized access exception. (Bug 965606)

Fix: Protect catches and handles the exception.

Issue: At replication time, a controller connection could not be established with a source workload if it was a gateway, proxy, or remote access server. A restart of the Routing and Remote Access Windows Service was needed on the source workload to clear the IP interface and allow the replication process to connect. (Bug 966024 and 951535)

Fix: At replication time, the controller can connect to source workloads that act as a gateway, proxy, or remote access server without requiring a restart of the Routing and Remote Access Windows Service.

Issue: A source workload in a NAT environment was added using its NAT public IP address; however, the workload’s NICs were mapped only to private IP addresses. At replication time, its NAT public IP address was unknown to the source operating system. (Bug 970430 and 961985)

Fix: When a source workload is in a NAT environment, you can configure the target workload to use the source workload’s NAT public IP address as the first address to try in a NAT IP-pinning scenario when connecting to the source machine for replication.

Issue: Because Protect pads the volume size when it creates the target disk, large volumes approaching 2 TB in size that use MBR partitioning might exceed 2TB in the target volume and need to use GPT partitioning for the target disk. (Bug 960139)

Fix: Protect allows the source disk with MBR partitioning to use GPT partitioning on the target disk to support this condition.

Issue: An interim patch failed in some instances for workloads with GPT partitions larger than 2.2 TB for target workloads. (Bug 953696)

Fix: GPT partitions work as expected.

Issue: A Waiting for Controller to Start recoverable error occurred after the replication of a workload with multiple NICs because of differences in the order of multiple NICs presented and the expected order. (Bug 953069)

Fix: The NIC configuration handles the order as presented.

Issue: A first replication failed for a workload with multiple NICs because the NICs had the same MAC address in their bonded configuration. (Bug 950716)

Fix: The NIC configuration properly resolves the network mappings.

Issue: In some conditions, Prepare for Sync honored the total number of CPUs set for the target VM, but it incorrectly modified the settings for cores and sockets on the target VM. It set the cores per socket to 1, and the number of sockets to the total number of CPUs. (Bug 949765)

Fix: Prepare for Sync honors the cores and sockets settings on the target VM.

Issue: Replication jobs for Linux workloads left ofx.xxxxxxxxxxxx files in the source workload’s /tmp directory. (Bug 949397)

Fix: This release adds a clean-up step to remove the temporary files after a replication job runs. You can manually remove the existing ofx.xxxxxxxxxxxx files in the /tmp directory.

Issue: After you upgraded to version 11.2, subsequent full replications failed for file-based replications if the workload had extended partitions with logical drives. The first full replication after the upgrade and incremental replications were not affected. It did not occur for new contracts. (Bug 948855)

Fix: For file-based replications, subsequent full replications now work as expected for workloads that have extended partitions with logical drives.

Issue: For some configurations of the Cores per Socket setting for workloads, PlateSpin did not properly load the floppy image, so the target VM was not configured correctly. (Bug 942967)

Fix: After the successful first full replication, the VM boots as expected.

Issue: Cluster node names were case sensitive and did not support mixed case names. (SR 10975270421)

Fix: This release allows cluster node names in mixed case. It treats all node names as case insensitive.

Issue: During a failover job, the target VM fails to boot. The failover process stalls at configuring the services with a Configuration Service Not Started error. (Bugs 994314, 991089, 991068, 988132, 987156, 986629, 984153, 982362)

Fix: Failover jobs perform as expected for most workloads. If you encounter the error, See Troubleshooting the Configuration Servicein the PlateSpin Protect User Guide.

Issue: For target Linux workloads on VMware containers, after the data copy completes and the configuration service begins, the cutover hangs because the vCDROM lock was not properly released. (Bugs 988839, 975853)

Fix: The vCDROM lock is properly released after installing VMware tools in Linux.

Issue: After a test failover, the target VM came up with no NICs for a workload with teamed NICs. (Bug 957484)

Fix: The NICs are available on the target VM following a test failover.

Issue: For a Windows Server Cluster workload, it was possible for a hard drive to not come online correctly on Failover or Test Failover, and the drive had to be brought online manually. (Bug 956559)

Fix: The hard drives are brought online automatically after a failover or test failover.

Issue: A test failover for a workload with teamed NICs failed while configuring the NIC because of differences in the order of multiple NICs presented in VMware and the expected order. (Bug 952233)

Fix: The NIC configuration handles the order as presented.

Issue: A test failover for a workload with teamed NICs assigned default names to NICs because the teamed interface with the adapter name was persisting through the failover. (Bug 951610)

Fix: The NIC configuration can now resolve the network mappings.

Issue: Previously, when you initiated the Save and Failback option for a source workload that uses UEFI boot mode, the failback failed if the physical target workload used the BIOS boot mode. This issue occurred because of the mismatch in boot modes for the source and target. (Bug 949579)

Fix: The failback validator allows the condition where the boot modes do not match on the source and target workloads.

Issue: Previously, for workloads with multiple NICs, the DNS settings were not automatically configured during the failback. (Bug 945090)

Fix: DNS settings are sticky for failback to physical targets with multiple NICs.