PlateSpin Protect 11.0.1 Hotfix 1 Release Notes

February 2015

PlateSpin Protect 11.0.1 Hotfix 1 resolves specific previous issues as well as important performance and reliability issues. NetIQ Corporation strongly recommends that you apply Hotfix 1 immediately. This document outlines why you should install this hotfix.

Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the PlateSpin Protect Forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.

Release Notes documents for PlateSpin Protect 11.0.1 and its hotfixes are available on the PlateSpin Protect 11.0.1 Documentation website.

For Release Notes documents that accompanied previous PlateSpin Protect releases, see Previous Releases at the bottom of the Table of Contents on the PlateSpin Protect 11.0.1 Documentation website.

1.0 What’s New?

PlateSpin Protect 11.0.1 Hotfix 1 includes software fixes that resolve the following issues:

  • 902259 - Replication statistics report that the same data is being transferred repeatedly on subsequent incremental replications. Formerly, bitmap history files were not being deleted, which caused incremental transfers to include previously transferred data. After you apply PlateSpin Protect 11.0.1 Hotfix 1 to a PlateSpin Protect Server, the duplicate data will be transferred one additional time during the next incremental replication. This behavior occurs because the bitmap history file(s) that need to be deleted on the source, which cause the issue, are not deleted until after the next incremental replication occurs.

    The workaround to prevent the duplicate data transfer from occurring is to manually delete the bitmap history files from the source after Hotfix 1 is applied to the PlateSpin Protect Server and prior to the next incremental replication. The bitmap history files are hidden files that reside on the root of each protected volume with the file naming format of platespin.bitmap.bbvt.pr.%date%. You can manually delete the bitmap history files if the last incremental replication was successful. However, if there is uncertainty that the last incremental replication was successful, then you should leave the bitmap history files on the source for the next incremental replication.

  • 901292 - Adding HostNamesForRegCleanup property, Registry file will be updated to only those workloads that are mentioned in this property

  • 897361 - Windows 2003 The Target VM does not Boot “Volume with serial number 00000000 does not exist among these known serial numbers”

  • 896499 - Forge Upgrade Utility fails with VMs residing on external NFS datastore

  • 894992 - WorkloadTargetUpgrader was not correctly filtering out WorkloadTarget objects that were not imported from the list of targets to be refreshed

  • 894926 - Modified regular expression to detect filenames that begin with a number

  • 701400 - When protecting onto cluster with NFS datastores, local datastores are exposed in Protect UI

2.0 System Requirements

PlateSpin Protect 11.0.1 Hotfix 1 can be applied to a base installation of PlateSpin Protect 11.0.1.

For more information about PlateSpin Protect 11.0.1, see the PlateSpin Protect 11.0.1 Release Notes on the PlateSpin Protect 11.0.1 Documentation website.

3.0 Applying the Hotfix

Before you apply PlateSpin Protect 11.0.1 Hotfix 1, you must plan downtime for the following:

  • Ongoing Replications: For a problem-free process, apply the hotfix while the system is quiet (all replications are paused and no jobs are running).

  • Affected Windows Workloads: A reboot is required for changes to be applied to Windows workloads that are protected through block-level replications. After you apply the hotfix and resume replication, a new task and an associated action (Upgrade Tools) is generated for all affected Windows workloads. Executing the Upgrade Tools action upgrades the Block-Based Component on the Windows source workloads and reboots them.

The continuity of Linux workloads is not affected, and the Block-based Transfer Components are upgraded without requiring a reboot.

To apply the hotfix:

  1. Save the PlateSpinProtectHotFix_11.0.1.HF1.exe file on your PlateSpin Protect Server computer.

  2. In the PlateSpin Protect Web Client, pause all replications. Allow incomplete jobs to finish, then ensure that no jobs are running.

  3. Run the downloaded hotfix executable. Follow the instructions in the wizard until you have finished installing the hotfix.

  4. Resume replications paused in Step 2.

  5. Repeat Step 1 through Step 4 on each PlateSpin Protect Server computer.

4.0 Known Issues

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. There are no known issues for PlateSpin Protect 11.0.1 Hotfix 1.

For information about known issues for PlateSpin Protect 11.0.1, see the PlateSpin Protect 11.0.1 Release Notes on the PlateSpin Protect Documentation website.

For Release Notes documents that accompanied previous PlateSpin Protect releases, see Previous Releases at the bottom of the Table of Contents on the PlateSpin Protect 11.0.1 Documentation website.

5.0 Contact Information

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 website.

For general corporate and product information, see the NetIQ Corporate website.

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.