VMware just released a brand new version of VMware Data Recovery.
Build Number 188925
Release Date 2009/09/09
This releases fixes a couple of known issues:
- Various Integrity Check Issues
Under certain circumstances, integrity checks reported damaged restore points and cannot load session errors. For example, such problems might be reported if:
- A combination of simultaneous overlapping backups and integrity checks are started.
- A backup is stopped before completion because the backup window closes. In such a case, the deduplication store records transactions, but the closing of the backup window prevents recording the transaction to the catalog.
When integrity checks failed in such cases, Data Recovery would mark restore points as damaged or report that the backup session could not be found. Data Recovery integrity check now handles these conditions properly, so these problems no longer occur.
- Connections Using Alternate Ports not Supported
By default, connections to vCenter Server use port 443. If vCenter Server is configured to use an alternate port, Data Recovery continued to attempt to connect using the default port. This caused the Data Recovery plug-in to report authentication failures when attempting to connect to the Data Recovery appliance. Alternate vCenter Server port configurations are now supported.
- Multiple VMDKs with the Same Name not Handled Properly
A virtual machine can have multiple VMDK files with the same name that are stored on different LUNs. In such a case, Data Recovery would only restore one of the disks. Data Recovery now restores all disks.
You can find the full release notes here.