VMware

VMware Data Recovery 1.0.1 Release Notes

Features | Documentation | Knowledge Base | Communities

Data Recovery | 07 JULY 2009 | Build 176771

Last Document Update: 15 JULY 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.1

Installations of Data Recovery 1.0 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 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.

  • Large Temporary Files Removed as Expected

    Data Recovery modifies virtual machines' vmdk files' settings so a snapshot can be created for backup purposes. In the past, after the backup has been created, the vmdk file's settings was sometimes left configured for snapshots even after the backup was complete. This led to these virtual machines being left in snapshot mode while accumulating snapshots that were undetected by vSphere Client. This process has been redesigned so that these temporary files are no longer be left behind. In previous versions of Data Recovery, this issue can be resolved by following the process described in the knowledge base article titled "Delete ddb.delete entries and snapshots left behind by Vmware Data Recovery".

  • Backups Can Be Completed While Integrity Checks Are Running

    Data Recovery can complete backup operations at the same time that an integrity check is running. In the past, when an integrity check was running, backups could not be completed.

  • Improved Integrity Check Backup Speed

    Integrity check has been optimized for faster performance. In the past, comparable integrity checks took longer to complete.

  • Improved VMotion Licensing Support

    Virtual machines can be moved between hosts using VMotion without producing licensing issues. In the past, if a virtual machine was moved between hosts using VMotion, licensing checks sometimes produced errors.

  • Reduced Data Recovery Backup Appliance Shutdown Time

    The Data Recovery Backup appliance now shuts down more quickly than it did before. In the past, the appliance often took 15 minutes to shutdown.

  • Improved Support for Different Time Zones

    In the past, Data Recovery did not consistently handle time zones with positive offsets relative to GMT. For example, Data Recovery could encounter issues with data associated with the Paris time zone, which has an offset of +1, whereas data associated with the New York time zone, which has an offset of -5 was handled as expected. These issues no longer occur.

  • Data Recovery Supported with Essentials Plus Licenses

    Data Recovery is included in Essentials Plus licenses. In the past, using Data Recovery with Essentials Plus licenses failed. Backup jobs created with Essentials Plus licenses failed with the error, License not available to perform operation. Feature hotplug not licensed....

  • Integrity Check Optimized to Run During Idle Times

    Before running regularly scheduled integrity checks, the Backup Appliance determines if the current time is during a backup window. If the current time is not during a backup window, the integrity check runs. If the current time is during a backup window, the backup appliance checks the backup schedule to determine if there will be a time in the next 24 hours that will not be during a backup window. If there is a time in the next 24 hours that is not during a backup window, the Backup Appliance waits for that time. If there is no time that is not during a backup window in the next 24 hours, the Backup Appliance completes the integrity check.