PlateSpin Forge 3.0.2 HotFix 1 Release Notes

January 13, 2011

Version 3.0.2 HotFix 1 is the latest release of PlateSpin Forge.

For Release Notes documents that accompanied previous 3.x.x releases, visit the PlateSpin Forge 3 Documentation Web Site and check Previous Releases at the bottom of the main TOC page.

1.0 About This HotFix

HotFix 1 is a cumulative update, representing a number of bug fixes, distributed as a follow-on to the 3.0.2 release. You can apply HotFix 1 only to that version.

WARNING:If after the 3.0.2 release you have installed a custom patch that addressed an issue that is not in the list of bugs listed below, installing this hotfix might compromise the functionality of that custom patch; please contact Technical Support before attempting to install this hotfix.

To apply HotFix 1 to your product installation:

  1. Pause all replications.

    (Optional) Take a snapshot of the Forge Management VM in case the hotfix fails to install properly. See Managing Forge Snapshots.

  2. From the Forge 3 Download Page, download the PlateSpinForgeHotFix_3.0.2-HF1.exe file and save it on your Forge Management VM.

  3. Run the downloaded hotfix executable and follow the on-screen instructions.

  4. Resume replications paused in Step 1.

2.0 Bug Fixes Included in This HotFix

HotFix 1 addresses the following bugs:

  • 652783 Sluggish Performance of Web Client: In some circumstances, the PlateSpin Forge Web Client became very slow if the inventory of protected workloads was at or above 20. This issue has been resolved.

  • 653073 Change of DST Not Reflected in Protection Schedules: After a daylight saving time (DST) change, scheduled replications ran an hour early or late. This issue has been resolved.

  • 654000 Database Overgrowth Disrupting Protection Schedules: The internal cleanup process was not preventing the PlateSpin Forge Server database from reaching the maximum size limit. This issue has been resolved.

  • 645949 Failover Workload Failing to Join Domain: Upon attempting a Test Failover or a Failover operation, improper validation of workload credentials sometimes prevented the failover workload from automatically joining a domain. This issue has been resolved.

  • 650701 Partition Alignment Issue Resulting in Poor VM Disk Performance: Failure to enforce an optimal 64-kilobyte alignment for the first partition of each new virtual disk resulted in an increase of virtual machines’ disk I/O operations, degrading performance. This issue has been resolved.

  • 646327 Report Data Not Sorted Chronologically: Sorting report data by date did not properly rearrange data chronologically. This issue has been resolved.

  • 628747 Non-Default Location of pagefile.sys Not Properly Maintained: Upon startup, a failover workload was allowed to create its pagefile.sys file in its default location on drive c:\, which sometimes resulted in problems if the original workload’s pagefile was in a non-default location. This issue has been resolved.

  • 654356 No NIC Detected on Physical Target: In some scenarios, a driver installation problem resulted in a failure to detect a network interface card on a physical target. This issue has been resolved.

  • 655802 Unresponsive ‘Refresh Container’ Job Blocking Scheduled Incrementals: An internal state machine exception sometimes caused the removal of workload target records, resulting in the disruption of scheduled incrementals. This issue has been resolved.

3.0 Known Issues

The list of known issues is unchanged from version 3.0.2.

See the PlateSpin Forge 3.0.2 Release Notes.