VMware

VMware Data Recovery 1.2.1 Release Notes

Features | Documentation | Knowledge Base | Communities

Data Recovery | 18 MAR 2011 | Build 369570

Last Document Update: 15 MAR 2011

Check frequently for additions and updates to these release notes.

This document contains the following sections:

Benefits and Features

Read about the benefits and features of this product at VMware Data Recovery Overview - VMware. For additional information about known issues and resolved issues, see:

Supported Environments

VMware Data Recovery 1.2.1 can be used with:

  • VMware vSphere 4.1 Update 1
  • VMware vSphere 4.0 Update 2

Upgrading to Data Recovery 1.2.1

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 VMware 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 or RDMs

  1. IMPORTANT: Before upgrading to VMware Data Recovery 1.2.1, make sure all operations in your current environment have completed before shutting down and performing the upgrade. If an integrity check or reclaim operation is running, allow the operation to complete. Do not CANCEL these operations.
  2. When no operations are running, unmount the destination disk and shut down the Data Recovery appliance.
  3. 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.
  4. Deploy the new appliance.
  5. Use the datastore browser to move the disk containing the deduplication store to the same location as the new appliance.
  6. 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.
  7. Power on the new appliance.
  8. 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.
  9. Configure networking on the new appliance.
  10. Use the Data Recovery vSphere plug-in to connect to the backup appliance.
  11. 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.
  12. 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.
  13. The client disconnects from the appliance after the configuration is restored and then reestablishes the connection. This may take several minutes.
  14. Once the client reconnects, check to see if a Reclaim or Integrity check operation has started. If so, STOP the operation.
  15. Immediately click Configure > Destinations and perform an integrity check on all mounted destinations.
  16. Verify the backup job configuration.
  17. Remove the older VMware Data Recovery appliance from the inventory.

Note that damaged 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 damaged 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

  1. IMPORTANT: Before upgrading to VMware Data Recovery 1.2.1, make sure all operations in your current environment have completed before shutting down and performing the upgrade. If an integrity check or reclaim operation is running, allow the operation to complete. Do not CANCEL these operations.
  2. When no operations are running, unmount the destination disk and shut down the Data Recovery appliance.
  3. 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.
  4. Delete the older Data Recovery appliance.
  5. Deploy the new appliance.
  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. On the Backup Destination page, click the Add Network Share link and enter the appropriate information for your particular CIFS share.
  10. 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.
  11. The client disconnects from the appliance after the configuration is restored and then reestablishes the connection. This may take several minutes.
  12. Once the client reconnects, check to see if a Reclaim or Integrity check operation has started. If so, STOP the operation.
  13. Immediately click Configure > Destinations and perform an integrity check on all mounted destinations.
  14. Verify the backup job configuration.
  15. Remove the older VMware Data Recovery appliance from the inventory.

Note that damaged 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 damaged 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. The list of resolved issues below pertains to this release of Data Recovery only.

  • Backup Appliance Security And Stability Enhanced

    Several changes have been made to enhance backup appliance security and stability.

    • The backup appliance's drivers have been updated to improve compatibility and performance.
    • The version of OpenSSL used by the backup appliance has been updated.
    • Nonrequired services have been disabled to reduce opportunities for exploits.

  • Deduplication Store Stability Enhanced

    The processes Data Recovery uses to complete integrity checks have been improved. Certain previously problematic cases are now handled more efficiently and unexpected cases are handled more smoothly.

  • Various Enhancements Made To Improve Data Recovery Functionality

    • Data Recovery did not apply the settings for IntegrityCheckInterval and BackupRetryInterval as specified in the datarecovery.ini file. These settings are now properly applied.
    • Logging has been modified to provide additional information.
    • In the past, FLR misidentified some acceptable IP addresses as problematic. These errors would result in the failure to mount valid restore points. FLR now evaluates addresses properly.