VMware

vSphere Data Protection 5.1.10 Release Notes

vSphere Data Protection 5.1.10 | 25 APR 2013

These release notes include the following topics:

Benefits and Features

Read about the benefits and features of this product at the following links:

Supported Environments

For information on supported environments, see the VMware Compatibility Guide.

Upgrading to vSphere Data Protection 5.1.10

The upgrade process is documented in the vSphere Data Protection Administration Guide

Enhancements in vSphere Data Protection

vSphere Data Protection 5.1.10 includes the following enhancements:

  • In the vSphere Data Protection user interface, the Configure tab now includes a Log tab, which is used to view detailed log information (this tab also includes an export to file option)
  • Integration with vCenter alarms and alerts notification system
  • Ability to clone backup jobs
  • New filters for Restore tab
  • Added restore rehearsal (launched from the Action menu)
  • Added more post-restore options (for example, automatically power on, NIC reconnect)

Known Issues

The following known issues have been discovered through rigorous testing. The list of issues below pertains to this release of vSphere Data Protection only.

  • "Loading backup job data" error message appears for a long time (up to five minutes) when a large number of VMs (~100 VMs) are selected for a single backup job. This issue can also occur when creating a new backup job, lock or unlock, refresh, delete, or delete actions for large jobs.

    This is expected behavior when very large jobs are selected. This message will resolve itself when the action is completed, which can take up to five minutes. This is a known issue and will be fixed in a future release

  • If a virtual machine is deleted during a VDP restore operation, the virtual machine is not properly removed from the VDP inventory. This causes an error when editing the backup jobs that included the deleted virtual machine as source. Additionally, if a virtual machine is created with the same name, attempts to add the virtual machine to a backup job will fail.

    Avoid deleting virtual machines during restore operations. If this error does occur, create the virtual machine with a new name and add it to a new backup job.

  • When a large backup job (more than 100 virtual machines) is created, the recent tasks pane does not always show the correct percentage completed.

    This is a known issue and will be fixed in a future release.

  • The following message might be displayed during the first login to the VDP appliance: "An unexpected error occurred and the cause could not be determined. Please check your VDP configuration screen to troubleshoot, or contact an administrator."

    If you encounter this error, retry the login. If the problem persists, try the following troubleshooting steps:

    • Confirm that the user name or password that is used to validate the VDP Appliance to the vCenter Server is correct. Only one user account and password are used for VDP validation. This is configured through the VDP Configure utility. See the vSphere Data Protection Administration Guide for more information.
    • Confirm that the network settings for IP and DNS configuration for the VDP Appliance are correct. See the vSphere Data Protection Administration Guide for more information.
  • The vCenter domain account password (used to connect to the VDP Appliance) cannot contain blank spaces. The VDP Appliance will initially run with this setting using a 30-day evaluation license, but if the VDP Appliance is rebooted after 30 days, the VDP Appliance will fail to restart.

    As a standard practice, provide a valid vCenter Server password that contains no spaces. Ping the VDP Appliance to make sure it restarts successfully.

  • When a larger size VM (with discrete hard disks) is restored over an existing smaller size VM (with one disk), the restore job completes but only one disk is actually restored. The VDP Appliance does not display this activity with an error message (for example: "not enough destination disks"). As a result, there is a possibility of data loss if all the disks are not restored and the user is not aware of it because no VDP event is generated.

    This is a known issue and will be addressed in a future release.

  • When logging into the File Level Recovery (FLR) utility using the Advanced Login option, only the credentials used during VDP vCenter registration are supported. No other administrative credentials are allowed.

    When logging into the FLR utility using the Advanced Login option, enter the same login credentials you used for vCenter registration.

  • As part of the base web service when building backup jobs from a group, the cache is flushed. If the cache flush occurs immediately prior to the backup job running, the backup job may fail.

    This appears to be a timing issue. Therefore, the workaround is to simply repeat the same action a second time.

  • An event should display the error code along with the error message. Execution error codes do not display in the Events console for errors generated on the VDP appliance.

    This is a known issue and will be addressed in a future release.

  • The proxy fails to unregister during the vCenter switch. The reboot still occurs on the VDP Appliance and upon completion of the reboot, the newer vCenter does not have a proxy and, therefore, backup jobs fail due to a 'No Proxy' error.

    Contact Technical Support.

  • When the user disconnects the VDP Appliance, locates the backed-up VM inventory, right-clicks the VM in the vCenter inventory list, and selects the Restore Rehearsal option, the Select Backup page is designed to display a list of backups. However, the list of accessible datastores is blank (NULL).

    Click the down arrow that corresponds to the combo box and select a backup from the list.

  • When a VM backup occurs under a cluster (for example: ESX1 and ESX2) and the ESX2 is in a Disconnected, Not Responding, or Standby state, attempts to trigger a restore-as-new operation for the VMs under the local datastore fail for the local/shared datastore target.
    The probable cause is the datastore for the VM is not accessible. The issue is specific to the "restore-as-new fails" case when a backed-up VM resides inside a cluster and on the local datastore. When the backed-up VM resides inside a cluster and on a shared datastore, the issue does not occur.

    When triggering a restore-as-new operation for VMs in a cluster environment, ensure the VM resides inside the cluster and on a shared datastore rather than on the local datastore. Manually power on the ESX server in question and it will operate as expected.

  • Using the backup wizard for SQL clients, backups do not occur at the local instance level but rather at the database level. Though the backup of this database completed successfully, subsequent database backups fail. The user might not notice that the new database attempt failed until they attempt to restore the database.

  • If a large backup job is created (~100 VMs), the backup job can take up to ten minutes to create.

    This is a known issue and will be addressed in a future release.

  • The File Level Restore (FLR) user interface does not display an error message when the user browses partitions that are either invalid or not supported.

    This is a known issue and will be addressed in a future release.

  • The message "Reinitializing VDP appliance. Estimated time to complete: x minutes" displays multiple times on the console during VDP setup. While this is not harmful, the message is misleading.

    This is a known issue and will be addressed in a future release.

  • Although a backup job has been canceled and deleted, it resumes and continues to run to 92% completion, and then stops.

    To prevent this from happening, take the following steps:

    1. Wait for a backup job task to complete running and then perform a delete operation.
    2. If a running task is cancelled, wait for the cancel task to complete. When the task is canceled in the server, a Cancel event is posted. It is safe to delete the group after this event posts to the canceled task.
  • If a thin provisioned VDP reaches datastore capacity, then even after freeing up the datastore and creating more space, integrity check errors occur on the VDP.

    This is a known issue and will be addressed in a future release.

  • Random characters appear in the EULA text during OVA deployment on the thick client. This issue occurs when single- or double-inverted commas or apostrophe characters are used on Firefox or Internet Explorer web browsers.

    There is no workaround or resolution.

  • When a user migrates VDP to a different vCenter and port which are not the default, file level restore (FLR) and restore rehearsal options fail to work as expected.

    This is a known issue that will be fixed in a future release. The file level restore (FLR) application and the restore rehearsal feature do not work in a non-default vCenter.

Resolved Issues

The following issues have been resolved:

  • Windows 2008 R2 backups fail with VixDiskLib_Open error stating no access rights to the VMDK file.

    Manually set the vmx configuration parameter disk.EnableUUID to 'false'. Once updated, all subsequent backups will work.

  • If a VM is deployed from an OVA or OVF in a protected container, depending on timing, it may not be automatically added to any backup jobs.

    Confirm that the VM is added to the protected container after it is deployed.

  • If an upgrade is performed while backup jobs are active, the upgrade will fail.

    Revert back to the snapshot that was taken prior to the upgrade.

  • Windows 2008 R2 backups can fail if the VM is configured with disk.EnableUUID with the true value.

    Manually update the vmx configuration parameter disk.EnableUUID to 'false'. Once updated, all subsequent backups will work.

  • Displayed restore points should be listed alphabetically. If a VM is renamed, it does not update the sort and is displayed in the same order as the original VM name.
  • If the vCenter is restarted, VDP Monitoring Events may not be displayed properly.

    To fix this issue, type the following command on the VDP Appliance: emwebapp.sh --restart

  • If backed up VMs are on a cluster and the primary host fails, jobs cannot be restored to the failover node.
  • The VDP-Configure utility on the vCenter registration page should list vCenter IP as an option, in addition to the host name.
  • In Email configuration, the Email Configuration page does not load the new settings when the user switches to the email sub-tab.

    The current behavior is to pull this information from the vCenter Client, which could take up to 12 seconds. The expected behavior is this page should be refreshed when it is opened.

  • If a VDP Appliance is removed, it might not be refreshed in the vSphere Web Client. If a user attempts to access the deleted VDP Appliance, an appropriate error message needs to be displayed.
  • Sometimes the Restore tab takes too long to load and the cached data becomes out of date.

    Use the Refresh button.

  • The VDR migration might fail with large VDR to VDP conversions.
  • If the UI or VDP Configure use localization, information is not always properly displayed.
  • If VMs in a cluster with HA enabled are migrated over due to a host failure, backup/restore of VMs that were migrated over will fail.

    A workaround is to power back on the host that lost power.

  • vCenter events sometimes show an excessive number of login and logout activities.

  • When you create a new backup job and use the same name as an existing backup job, there is no error message within the Backup wizard. After the wizard is complete, an error message is displayed that the new backup job was not created.
  • The framework to support localized error messages is not available.

  • VMs that exist in the vCenter inventory under a Resource Pool or a vApp successfully back up on a VDP Appliance. However, when you create a new VM during restoration on the vCenter, the restore might fail.
  • If you restore a VM that has a higher-level hardware version to an ESX host that does not support the hardware version of the VM, the restore will fail to create the VM with a vague error message.
  • Sometimes during a restore operation, the VDP Appliance generates an exception message that indicates the restore initiation for the VM has failed.

    This is misleading since the restore job is getting initiated successfully and completes successfully.