VMware

vSphere Data Protection 5.5.1 Release Notes

vSphere Data Protection 5.5.1 | 22 SEP 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; this 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.

    Workaround: As a best practice, 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.

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

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

  • Expiration time for a backup is not consistent for a scheduled backup and an ad hoc backup.

    The expiration time for the same backup job is not always the same if the backup job with a custom retention policy executes on demand. This is a known issue.

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

  • Edit fails to locate a VM that has been migrated to a different host if the edit is performed before hourly synchronization.

    One or more VMs protected by the backup job may have been migrated to new hosts using vMotion.

    Workaround: Retry the edit after one hour; the wizard will successfully locate the VM.

  • The Restore pane reflects the timestamps as per the time zone of the client machine where the vSphere Web Client is launched.

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

  • Image backup and VMDK backup job of VM with SCSI bus-sharing enabled is allowed, but fails, and the job task does not appear in the vCenter.

    The following VMware knowledge base article clearly states that snapshots are not supported for SCSI bus sharing VMs:

    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006392

    Workaround: If you require bus-sharing, follow the instructions in the Resolution section of the knowledge base article.

  • When a user attempts to restore a regular retired VM or a replicated retired VM with an unregistered VM name, the VDP Appliance follows a different approach in validation.

    When a user restores a retired client using a previously-existing VM name, the restore should not trigger because the VM's configuration files still exist in the datastore. When the restore action is performed from a retired replicated restore point, however, the VDP Appliance does not inform the user that the existing VM configuration files for the original VM exist.

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

  • During VDP installation, if the user clicks Previous on the vCenter registration screen with no values being entered, the system fails to initialize the vCenter and the installation fails.

    Workaround: Log out from the VDP-Configure session, clear the browser cache, and log in again. The device allocation should now display the current free space.

  • Ad-hoc replication from the Reports tab replicates other VM backups.

    If an ad-hoc replication job is performed from the Reports tab, backups for other virtual machines that are present in the replication job are also replicated.

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

  • vCenter events do not generate during initial configuration if the user modifies the VDP hostname or IP address.

    Workaround: Monitor the reconfiguration events on the VDP Appliance console.

  • After an MCS restart, the Last Run Time and Duration values of a previously-executed Replication job changes to the default value.

    After restarting the management services for a 5.5 version of the VDP Appliance, the Last Run Time and Duration values on the Replication tab for a previously-executed replication job changes to the default value of Never.

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

  • vCenter registration for a VDP Appliance should not succeed when the vCenter user permissions are assigned on the ESX host level.

    The VDP Appliance allows the user to configure the appliance even if the vCenter user permissions are assigned at the ESX host level. The Web client, however, does not display the VDP plug-in when the user logs into it using the newly-configured vCenter.

    Workaround: As a best practice, explicitly assign users as Administrator on the vCenter root node. You can find these instructions in the User Account Configuration section of the vSphere Data Protection Administration Guide.

  • Replicated backups cannot be replicated again.

    The Replication wizard does not support replicating backups that have already been replicated from a different source server. Clients or restore points that have already been replicated from a different source server do not appear as available in the Create | Edit | Clone replication job wizard.

  • The VDP Appliance creates a restore point for VM clients on the Restore tab that are associated with cancelled backup tasks.

    Backup jobs that are cancelled on the VDP Appliance from the Web Client are not synchronous with reported cancel action results. As a result, the VDP Appliance erroneously creates a restore point for the canceled VM clients in the backup job.

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

  • Unable to replicate backups from imported disks.

    Imported backups (that is, backups that were created with a previous appliance from where disks were imported to a new appliance) cannot be replicated. You can only replicate VM clients that have a current VM client registration.

    This is a known limitation of storage import and will be fixed in a future release.

  • Image restore as new fails for disks larger than 2 TB.

    The restore image as new feature fails only in a thick disk configuration where the disk is backed up to a SAN datastore and then restored to the same datastore, which consumes too much disk space. This issue does not exist on thin disk clients.

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

  • Alarms are raised during second boot.

    After finishing the configuration and subsequently restarting the VDP appliance, intermittent alarms are raised during the second boot process. An example of this alarm is "VDP: [008] File level restore services are not running".

    If this occurs, please allow for the boot process to complete and then manually acknowledge and clear the alarm. While these alarms are valid at the time they are raised, the boot process resolves the situation.

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

  • Attach existing storage to VDP: If the integrity check takes a long time to run, the configure task gets stuck at 80 percent and does not mark the task as complete.

    The VDP Appliance will complete the configuration successfully, even in cases where the integrity check takes a very long time to run. This is a known issue and will be resolved in a future release.

  • Upon successful upgrade to VDP 5.5.1, the user will see two plug-ins listed on the left pane of the vCenter.

    When the upgrade installs successfully, two plug-ins appear on the left pane of the vSphere Web Client. VDP versions 5.1 and earlier are managed using the vSphere Data Protection plug-in. VDP version 5.5 is managed using the vSphere Data Protection 5.5 plug-in.

    NOTE: Two plug-ins also appear if a VDP Appliance version 5.5 is installed and a version earlier than 5.5 already exists.

    To remove the vSphere Data Protection plug-in, you must upgrade all VDP Appliances to VDP version 5.5 and use the plug-in manager to disable the VDP plug-in.

    Refer to the VMware vSphere Documentation Center web site for information about managing vCenter plug-ins.

  • vdp-configure: Invalid gateway and subnet mask values are accepted on the configuration tab.

    If you inadvertently enter invalid system settings in the VDP Appliance console, the system accepts the settings and then you are not able to open the VDP-Configure URL.

    Workaround: From the vSphere Web Client, open a console session into the VDP Appliance and change the gateway and subnet mask values. You can find instructions in the Configuring the VDP Appliance System Settings section of the vSphere Data Protection Administration Guide.

  • Scalability: Web Client UI loses connection with VDP timing out, while submitting more than 10 restores.

    If you restore more than ten backups in a single restore job, the UI times out and loses connectivity with the VDP Appliance.

    Workaround: Limit the number of backups you restore in a single restore job to fewer than ten.

  • Attach existing storage to VDP: Message when trying to import a non-data disk can be reworded.

    Attempting to import non-data disk of VDP currently shows the following error message: Selected disk is not a valid disk

    The message should be reworded to the following error message: Selected disk is not a valid data disk

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

  • Filtering option at Restore page filter fails if user wants to make multiple selections among several backups.

    When the user navigates to the Restore page and attempts to restore multiple virtual machines, the back arrow filter functionality fails. After the user clicks the first VM, he must manually navigate back to select subsequent VMs.

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

  • Rollback to a validated checkpoint for the VDP Appliance fails after vCenter change.

    When the user changes the hostname or the IP address of the vCenter server and then logs into VDP-Configure to perform a rollback on the VDP Appliance, the rollback fails.

    Workaround: As a best practice, after successful vCenter configuration when all the VDP services are up, manually run an integrity check, which creates a valid checkpoint. If required, you can then perform a rollback to that checkpoint.

  • Restore fails when attempted to restore as new VM using previous name of the renamed VM.

    When the user creates a backup job for a VM, selects the restore point, and enters the old name of the renamed VM in the Restore to New Location field, the restore fails with the following message: "Unable to restore VM for restore point. The datastore path already exists."

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

  • Attach existing storage to VDP: Restore pane shows multiple entries with the exact same name if import is done more than once against the same vCenter.

    When a user performs more than one import in a single vCenter, the exact same name appears in the Restore pane for both restore point entries.

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

  • Restore at the disk level is failing when the destination is selected as a vApp or a Resource Pool inside a 2-node cluster.

    The user is not able to restore a VMDK while choosing the destination as a vApp or a Resource Pool in a 2-node host cluster.

    Workaround: Rerun the restore job and choose a standalone ESXi Host or ESXi Host cluster as the destination. After the restore job completes, you can manually add the restored VM into the vApp or Resource Pool.

  • No proper error handling when running scheduled disk backup job of a VMDK which was migrated to another datastore.

    A scheduled backup job of a VMDK completes without any errors but when the datastore location is changed to another datastore, the error occurs.

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

  • During VDP installation, the Add Disk operation silently fails if the datastore is deleted or renamed before clicking Yes on the storage configuration confirmation dialog.

    Renaming or deleting the datastore which was selected to store the VDP data disks invalidates the Add Disk operation. Even though the Add Disk operation failed, the system falsely reports a successful operation. The disks do not attach to the VDP Appliance, yet the system prompts the user to reboot.

    By default, the option "Store With Appliance" is checked, which deploys the disks on the same datastore when deploying the VDP Appliance. This issue occurs only when the user clears the Store With Appliance option and selects a different datastore.

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

  • During VDP installation, in the Device Allocation screen: VDP allows the user to proceed with an unmounted datastore for storing new disks.

    The VDP Appliance allows a user to add new disks to an unmounted datastore. The system does not report an error and allows the user to proceed further. It is only when the user clicks Yes on the Ready to Complete page that the Add Disk operation fails with a fatal error message.

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

  • When the datacenter name is named using a non-Latin alphabet, VDP-initiated backups will fail.

    Workaround: Change the datacenter name to a name using the Latin alphabet.

  • "Set Restore Option" during restore rehearsal is blank if you are not connected to the VDP Appliance.

    On the Set Restore Options page of the Restore a backup wizard, you can specify to where you want the backup restored (Restore to Original Location or Restore to New Location). The Set Restore Options page is blank, however, if you are not connected to the VDP Appliance.

    Workaround: Connect to the VDP Appliance to use the Restore a backup wizard and its options.

Resolved Issues

The following issues have been resolved:

  • When a VM backup occurs under a cluster (for example: ESX1 and ESX2) and the ESX2 Host 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, this issue does not occur.

    This issue is resolved in this release.

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

    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.

    This issue is resolved in this release.