VMware

VMware Data Recovery 1.0.2 Release Notes

Features | Documentation | Knowledge Base | Communities

Data Recovery | 8 September 2009 | Build 188925

Last Document Update: 8 September 2009

Check frequently for additions and updates to these release notes.

Benefits and Features

Read about the benefits and features of this product at VMware Data Recovery Overview - VMware.

Upgrading to Data Recovery 1.0.2

Previous Data Recovery installations are likely to have existing restore points that should be preserved. To ensure these restore points are preserved, it is important to use the following processes described in this section.

Begin the upgrade process by installing the latest Data Recovery plug-in for the vSphere client.

To install the latest Data Recovery plug-in

  1. Close the vSphere Client.
  2. Use the Add or Remove Programs item in the Control Panel to uninstall any previous versions of the Data Recovery plug-in.
  3. Start the latest Data Recovery plug-in Windows Installer File (.msi) to install the Data Recovery plug-in.

Next you must deploy the new Data Recovery appliance without deleting existing restore points. If the destination volume for the deduplication store is a virtual disk, do not to delete the appliance. Deleting the appliance deletes the disks connected to the appliance. This would cause the backup data stored in the deduplication store to be deleted. To avoid such an issue, complete the following procedure:

To upgrade Data Recovery appliances with virtual disks

  1. Check if any backup jobs are currently running. When no jobs are running, power off the Data Recovery appliance.
  2. If you want to save the original Data Recovery appliance, rename it in some way. For example, you might rename an appliance called VMware Data Recovery to VMware Data Recovery - OLD.
  3. Deploy the new appliance.
  4. Use the datastore browser to move the disk containing the deduplication store to the same location as the new appliance.
  5. Edit the settings of the new appliance:
    1. Choose a Add > Hard Disk.
    2. Choose Use an Existing Virtual Disk
    3. Browse to the data store and select the virtual disk which is connected to the older appliance as destination.
    4. Choose the SCSI address.
    5. Choose Finish.
  6. Power on the new appliance.
  7. Edit the settings of the older appliance:
    1. Choose the hard disk which is used to store deduplication store.
    2. Select Remove, leave default option for remove from virtual machine. DO NOT select remove from virtual machine and delete files from the disk.
    3. Click OK.
  8. Configure networking on the new appliance.
  9. Use the Data Recovery vSphere plug-in to connect to the backup appliance.
  10. Complete the getting started wizard. Note that you should mount the desired disk, but do not format it. Formatting the disk will erase all deduplication store data. The disk to be used may not display the expected name, but the proper name will be displayed after the wizard is completed.
  11. You are prompted to restore the configuration from the deduplication store. Select Yes if you want to restore the jobs and backup events and history.
  12. The client disconnects from the appliance after the configuration is restored and then reestablishes the connection. This may take several minutes.
  13. Verify the backup job configuration.
  14. Remove the older VMware Data Recovery appliance from the inventory.

Note that corrupt restore points may cause the upgrade to fail. If you receive the message "Could not restore the Data Recovery appliance configuration" re-add the destination to the original Data Recovery appliance and then run an integrity check to clean up any corrupt restore points. After the integrity check completes successfully, repeat the upgrade process.

If the destination volumes for the deduplication store is a CIFS share or an RDM, complete the following procedure:

To upgrade Data Recovery appliances with CIFS shares or RDMs

  1. Check if any backup jobs are currently running. When no jobs are running, power off the Data Recovery appliance.
  2. If you want to save the original Data Recovery appliance, rename it in some way. For example, you might rename an appliance called VMware Data Recovery to VMware Data Recovery - OLD.
  3. Delete the older Data Recovery appliance.
  4. Deploy the new appliance.
  5. Edit the settings of the new appliance:
    1. Choose a Add > Hard Disk.
    2. Choose the option to add a RDM and then select the LUN that contains the deduplication store.
    3. Browse to the data store and select the virtual disk which is connected to the older appliance as destination.
    4. Choose the SCSI address.
    5. Choose Finish.
  6. Power on the new appliance.
  7. Configure networking on the new appliance.
  8. Use the Data Recovery vSphere plug-in to connect to the backup appliance.
  9. Complete the getting started wizard. Note that you should mount the desired disk, but do not format it. Formatting the disk will erase all deduplication store data. The disk to be used may not display the expected name, but the proper name will be displayed after the wizard is completed.
  10. Mount the CIFS share in the appliance.
  11. You are prompted to restore the configuration from the deduplication store. Select Yes if you want to restore the jobs and backup events and history.
  12. The client disconnects from the appliance after the configuration is restored and then reestablishes the connection. This may take several minutes.
  13. Verify the backup job configuration.
  14. Remove the older VMware Data Recovery appliance from the inventory.

Note that corrupt restore points may cause the upgrade to fail. If you receive the message "Could not restore the Data Recovery appliance configuration" re-add the destination to the original Data Recovery appliance and then run an integrity check to clean up any corrupt restore points. After the integrity check completes successfully, repeat the upgrade process.

Resolved Issues

The following issues have been resolved since the last release of Data Recovery. For additional issues that were resolved in Data Recovery 1.0.1, see VMware Data Recovery 1.0.1 Release Notes. For a full list of known existing issues, see VMware Data Recovery 1.0 Release Notes. The list of resolved issues below pertains to this release of Data Recovery only.

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

Known Issue

The following known issue has been discovered through rigorous testing. The list of issues below pertains to this release of Data Recovery only.

  • Termination of Incomplete Backup Jobs Produce Errors

    Backup jobs are only permitted to run during the backup window. If a backup job is in progress when the time period for the backup window ends, the backup job is terminated. When such jobs end, the following error is logged: Script execution terminated at specified stop time. If a backup job only partially completes, the resulting incomplete restore point may produce the following integrity check error: Backup Set format inconsistency (10 at n), where n is a variable number. The error can be ignored and the error condition is automatically resolved.