The VMguy

The vSphere integrated backup product, Data Recovery, has been updated to 1.0.2.  No new features or functionality, just bug fixes according to the release notes.  You can download the release in the downloads section here. Here are the list of resolved issues in this release in case you have experienced any:

• Various Integrity Check IssuesUnder 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 SupportedBy 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 ProperlyA 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.