vSphere Data Protection 5.1.11 Release Notes

vSphere Data Protection 5.1.11 | 6 JUN 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.

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

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

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

  • The VDP Appliance displays backup jobs in the Recent Tasks panel for groups that have been deleted and no longer exist.

    This is a known issue and will be fixed in a future release. The workaround is, when a task is hung and there is no associated job running, cancel the task to remove it from the Recent Tasks panel.

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

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

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.

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