VMware

vSphere Data Protection 5.1.21 Release Notes

vSphere Data Protection 5.1.21 | 8 OCT 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.

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.

  • 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 fixed in a future release.

  • 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 there is no workaround.

  • 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 fixed 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 selected options are configured correctly.

    This is a known issue and will be fixed 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 fixed in a future release.

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

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

  • During a series of create, clone, and edit backup job operations, the backup job randomly fails.

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

  • Manual integrity checks fail at validation and returns the following error: "An integrity check could not be performed at this time. Please try again at a later time."

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

  • A cancelled restore task continues to process the work order. The restore completes as if it were not cancelled.

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

  • Users are allowed to enter text characters in the date range field.

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

  • The new destination path is listed, even after cancelling the selection while restoring a virtual machine as new.

    In this scenario, a user selects a VM for restore, selects a different destination than the original location, and then clicks Cancel. The new destination path is pre-populated, even though the operation was cancelled. This is a known issue and will be fixed in a future release.

  • Disk add and disk grow operations do not work with an ESX 4.x host, unless the user manually sets the minimum required RAM.

    The workaround is to manually adjust the memory as required for the target capacity:

    • Capacity: 2 TB, Required Memory: 6 GB
    • Capacity: 4 TB, Required Memory: 8 GB
    • Capacity: 6 TB, Required Memory: 10 GB
    • Capacity: 8 TB, Required Memory: 12 GB

    The steps are documented in the "Disk Expansion with Essentials Plus" section of the vSphere Data Protection Administration Guide.

  • The first differential/incremental backup is forced to full when the differential option is specified.

    When the user runs a database backup as a differential backup and the option is selected to run differential with force full (an option that is enabled by default), and the backup is promoted to a full backup, then the next differential backup ends up running as a full backup as well.

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

Resolved Issues

The following issues have been resolved:

  • Failing to unregister the proxy during vCenter switch should not reboot the appliance.

    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.

    This issue is resolved in this SP release.

  • VDP is not able to connect to the vCenter of a non-default port when updates occur.

    The VDP Appliance code has a default port (443) specified in the vCenter client data structure. When a reboot occurs, the client resets to use port 443, which blocks communication between the vCenter and VDP.

    With a change made to the VDP Appliance code, a custom port value (9876) in the database now persists during a server reboot.

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

  • VDP UI: No event or error messages display when a user attempts to back up virtual machines on a shut down ESX Host.

    This issue is resolved. Now, the following event message displays: VDP: Failed to initiate a backup or restore for a virtual machine. Probable cause is the datastore for the virtual machine is not accessible.

  • Creating backup jobs without selecting a retention policy should not be allowed.

    The VDP Appliance allowed users to create an image backup job without specifying a retention policy. Though the Create a new backup job wizard shows the Retention Policy option as enabled, no retention policy displays on the Ready to complete page and an error message displays, indicating the wizard was unable to create a backup.

    This issue is resolved and the wizard no longer allows users to create a backup job without selecting a retention policy.

  • The vdp-configure UI incorrectly displays the management service as stopped during the first 5 minutes after core services are stopped.

    This issue is resolved in this SP release.

  • Cannot connect to the VDP Appliance when the http header size is larger than 8 KB.

    This issue was resolved by increasing the server's maximum http header size to 32 KB.

  • The default vCenter port number is 443. If the default port number is changed to a non-default port, the VDP plug-in is not visible.

    This issue is resolved in this SP release. When run on Windows or Linux platforms, the VDP plug-in is now visible when a non-default vCenter port is used.

  • Capacity manager page freezes the vSphere Web Client

    This issue is resolved in this release. The Capacity Manager UI page loads successfully.

  • The backup schedule exists on the VDP Appliance after deleting the backup job.

    This issue is resolved in this SP release.

  • /var/log/ messages not included in the Log Bundle

    This issue is resolved in this SP release. Adding /var/log messages to the log bundle greatly helps Support personnel when troubleshooting.

  • The backup fails when the VMX file is suspiciously small.

    VDP is unable to back up virtual machines under datacenters with special characters in the name. When the backup is performed outside of VDP using a browser, however, the backup executes as expected. VDP creates the backup job by taking the folder directly from vCenter and setting it on the client to be backed up.

    This issue is resolved in this SP release.

  • Email reports run for days of the week that are not selected. This can result in emails being generated on multiple days of the week when only a single day of the week is requested.

    This issue is resolved in this SP release.

  • The vCenter switch failed while changing the IP address in the vCenter to the FQDN in the same vCenter.

    When a user modifies a vCenter configuration in the vdp-configure UI, a pop-up warning displays the following message: You are attempting to change the vCenter configuration. If you choose to continue with this operation, your existing VDP configuration will be reset, existing backup jobs will be deleted, and clients will be retired. While backups of existing clients will be accessible, you will need to rebuild your VDP configuration.

    This issue is resolved in this SP release.

  • The VDP plug-in fails to register on the vCenter; a version error displays.

    This issue is resolved in this SP release.

  • Update the VDDK for VDP 5.1.11 and VDP 5.1.20 releases

    Successful bug-fix update to the Virtual Disk Development Kit (VDDK) to align with VDP release 5.1.11 and 5.1.20 releases. For detailed download instructions, refer to vsphere-early-access.vmdev.net or consult your VMware Ecosystem Engineering team representative.

  • Virtual Center authentication errors cause vCenter connections to drop and not be re-established.

    Do not refresh the vCenter's cache data when you experience retrieval issues between the vCenter and MCS. In addition, if there are vCenter connection issues, do not initiate VMwareEventsMonitor.

  • The disk virtual machine restores a thick disk in the vCenter.

    This issue is resolved in this release. When restored as a new VM, the VM now restores as a thin disk in the vCenter.

  • The versioning check in the VDP Upgrade UI assumes a two-digit minor version in the format <release>.<major>.<minor>.<build_number>. The versioning check fails if the <minor> version is one-digit (for example: 5.5.1.x.

    The version comparison algorithm was moved from the UI to the server, which fragments each version individually.

  • SQL incremental backups failing intermittently after upgrading to version 6.1. The SQL incremental backups are working as expected in version 5.x.

    This issue is resolved in this release.

  • Restoring a SQL Server Database with the tail log file backup enabled completed, but the tail log backup is not available for restore.

    This issue is resolved in this release.

  • Backups fail when the host is put into standby mode or maintenance mode.

    This issue is no longer reproducible.

  • VDP posts inaccurate backup and restore tasks erratically, even when the backup and replication jobs are not executed.

    Inaccurate backup and restore tasks were removed from the event console and log viewer.

  • Defining SCSI controller for disk will fail with non-English vCenters.

    During disk expansion or diskless OVA deployment, the string "SCSI Controller" is used to identify the controller, but this string does not translate across all languages and virtual machines.

    The logic was modified to identify SCSI controllers across all languages and VMs.

  • When VDP Advanced is deployed on vCenter version 5.5, the Configuration tab does not load properly.

    This issue is resolved in this SP release.