VMware

vSphere Data Protection 5.1.20 Release Notes

vSphere Data Protection 5.1.20 | 14 MAR 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.20

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

Enhancements in vSphere Data Protection 5.1.20

vSphere Data Protection 5.1.20 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)
  • Expands capacity up to 8 TB per appliance
  • Supports the ability to expand existing datastores
  • Supports guest-level backups of Microsoft SQL Servers
  • Supports guest-level backups of Microsoft Exchange Servers

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.

  • In the event that there is a host failure in a high availability cluster, the next backup job might be processed as a full backup rather than an incremental backup.

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

  • The FLR Advanced Login Mode is case-sensitve for the user name.

    Use the same case sensitivity for the user-defined name in vSphere. This is a known issue and should not be case-sensitive. This will be addressed in a future release.

  • VDP FLR fails to mount supported disks if any of the disks selected are unsupported.

    The expected behavior is to mount the supported disks and provide an error message for unsupported disks. This will be addressed 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 Select Restore Options page has a field called 'Location path' with an optional field to restore to an alternate location. If the user specifies an alternate location path, the db files path of the target db on the target SQL client system remains the same as the source db in the source SQL client system; the user is not able to specify an alternate path for the db files.

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

  • The user is not notified when a backup job of a client becomes disabled for any reason. No tasks are generated and no error message is displayed.

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

  • When a user cancels and deletes backup jobs, the expected behavior is the backup job should end and not resume. For Microsoft Exchange clients, the deleted backup jobs resume and continually run.

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

  • The VDP appliance does not properly validate authentication, even if the user provides an invalid or incomplete IP address or an invalid fully-qualified domain name (FQDN). Although the client plug-in installation process completes without an error message, the client does not activate.

    Reinstall the client software with a valid IP address, hostname, or fully-qualified domain name. As a standard practice, follow the typical method of providing valid VDP Advanced server credentials. After you have reinstalled the client software, ping the appliance.

  • Scheduled image backup jobs do not trigger at the beginning of the backup start window after a time zone change. After changing the time zone, the scheduled backup is delayed by one hour.

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

  • The SQL Server does not allow differential or incremental backups on the master database. If a user backs up the master database and selects incremental or differential as the backup type, VDP Advanced automatically converts this to a full backup.

    On SQL servers, perform a full backup type when backing up the master database.

  • The vSphere Data Protection Advanced appliance name does not appear consistently in the user interface. For example, the VDP configure pages still refer to the product as vSphere Data Protection.

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

  • On backup jobs performed on Microsoft Exchange 2010 clients, the backup job detail sources display the dismounted databases, but when the user is editing the client, the dismounted databases do not return information.

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

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

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

  • Details of selected application options do not display on the 'Ready to Complete' page of the backup wizard. Details would provide the user the option to confirm that the selected options are configured correctly.

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

  • When a backup job is deleted and the user attempts to verify the deletion from the Edit Backup Jobs wizard, there is no indication that the database for the selected SQL client no longer exists.

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

  • If a VDP Advanced Appliance is deployed on an ESX host with vSphere version 4.1 (update 1, 2, or 3), the capacity expansion user interface generates an error message and the vSphere Web Client hangs.

    This is a known issue. A workaround is to deploy the VDP Advanced appliance on other supported vSphere versions. See the section about software requirements in the vSphere Data Protection Administration Guide.

  • When a user clicks the log bundler in the VDR-Configure user interface, the Client activity log reports no activity, even when backup and restore operations fail.

    This issue is not consistently reproducible; however, if it occurs restart the Apache Tomcat server using the emwebapp.sh --restart command.

  • VDP uses HTTP access to access vmx and nvram content. If datastore access over HTTP is disabled in the vpxd.cfg file or the vCenter Server, the VDP backup fails and displays a "Miscellaneous Errors" message.

    For VDP backups to work, the user must enable HTTP access of the datastore in the vpxd.cfg file of the vCenter Server.