vSphere Data Protection 6.1.1 Release Notes

|
vSphere Data Protection 6.1.1 Release Notes | 10 November, 2015

These release notes include the following topics:

Benefits and Features

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

vSphere Data Protection 6.1.1 supports in-place upgrade, that is, upgrade from 6.1 to 6.1.1.

Note: In-place upgrade is supported from vSphere Data Protection 6.1 onwards.

Supported Environments

For information on supported environments, see the VMware Interoperability Matrix.

Known Problems and Limitations

The following are the known problems and limitations in this release of vSphere Data Protection.

VMware Issues

  • Support for routed / NAT / Firewall / IDS / TSNR between the vSphere Data Protection appliance and vCenter Server (1292848)

    When configuring the network for the vSphere Data Protection appliance and vCenter Server, modifying network address information using NAT or other configuration methods (for example: firewall, IDS, or TSNR) is not supported. When those tools are deployed as part of the virtual network, some vSphere Data Protection functionality may not work as designed.

  • Powering On of VM fails when backed up VM was connected to DVS and restored to other ESX (222475)

    When powering on a VM after you restore it, vCenter Server returns a PowerOnFailure error similar to the following:

    DRS cannot find a host to power on or migrate the virtual machine. Network interface 'Network adapter 1' uses network '77 d3 02 50 5f 76 ca d7-db f9 42 6c 0f 6f 87 1f', which is not accessible

    This error message occurs when the environment where you restore the VM does not have the network connection that was present when you backed up the VM. For instance, a user backs up a VM that is connected to a distributed vSwitch. Then the user restores the VM to an ESX host that is part of a Distributed Resource Scheduler (DRS) cluster. The vSwitch does not exist in the DRS cluster. Powering on the VM, therefore, fails.

    Workaround

     Edit the VM settings, set the network connection to the network adaptor, and then power on the VM.

Interoperability Issues

  • In a Virtual SAN environment, the image-level restore to original location operation is allowed, but the disk-level restore to original location operation is grayed out, after migrating the entire virtual machine to another datastore (58839)

    Workaround

    Either restore the entire VM with an image-level backup or restore the disk level backup as a new disk on the original VM.

Upgrade Issues

  • ISO detection fails during upgrade from vSphere Data Protection 6.1 to 6.1.1 (244505)

    Workaround

    Before you upgrade the vSphere Data Protection appliance, perform the following steps:

    1. From the vSphere Data Protection 6.1.1 installation package on the vSphere Data Protection appliance that you want to upgrade, copy the VDP61_Iso_Hotfix.tar.gz file to any directory, for example, /root on the same vSphere Data Protection appliance.
    2. Extract the VDP61_Iso_Hotfix.tar.gz file by running the following command:

      tar -zxvf VDP61_Iso_Hotfix.tar.gz

    3. Go to the VDP61_Iso_Hotfix directory.
    4. Add the execute permissions to the VDP61_Iso_Hotfix.sh file by running the following command:

      chmod a+x VDP61_Iso_Hotfix.sh

    5. Run the VDP61_Iso_Hotfix.sh file:

      ./VDP61_Iso_Hotfix.sh

    The hotfix checks whether it is running on vSphere Data Protection 6.1. If the hotfix cannot detect vSphere Data Protection 6.1, it exits without applying any changes.

    The hotfix backs up the vdr-configure.war file of vSphere Data Protection 6.1 to the /VDP_Files directory. You require the vdr-configure.war file if you want to revert vSphere Data Protection to the state, in which it was before running the hotfix.

VMDK Issues

  • Incorrect behavior of the vSphere Data Protection appliance when more disks are added to the same SCSI slots (59774)

    The vSphere Data Protection appliance initiates a restore operation with the same SCSI IDs on the same existing VM assigned to two different restore points. In addition, the Summary page incorrectly indicates that two new virtual disks will be added. The Restore operation completes successfully without informing the user that only the first single disk was added, and the second disk simply replaced the first disk.

vSphere Data Protection Issues

  • A password change on a configured vCenter Server instance is not allowed on the vSphere Data Protection appliance, even after the vCenter Server password has expired (59497)

    The vSphere Data Protection-Configure application does not allow a password change for the configured vCenter Server instance if backups are in a Running state on the server. If the user password on the configured vCenter Server instance has already expired, no tasks are posted on the task console, and, consequently, the tasks cannot be canceled.

    Workaround

    Perform the following steps:

    1. Wait until all the backups and tasks finish in the vSphere Data Protection appliance and then change the password.
    2. Restart the vSphere Data Protection appliance in the maintenance window, and then log into the vSphere Data Protection-Configure user interface and change the vCenter Server password from the vSphere Data Protection-Configure user interface.

  • The Performance Assessment Test (PAT) result changes to Never Run when the datastore name is changed (59784)

    In this scenario, the user opens the vSphere Data Protection-Configure user interface, clicks the Storage tab, selects a datastore, and clicks the Run performance analysis on storage configuration checkbox. The performance analysis test completes successfully and the results of the performance analysis are displayed correctly. If the user changes the name of the datastore, however, the performance analysis results erroneously indicate the status as Never Run.

  • The vSphere Data Protection GUI displays an error message in the Firefox browser when you edit a Data Domain device (231126)

    If you edit a Data Domain device by using the vSphere Data Protection GUI or the vSphere Data Protection configuration utility in the Firefox browser, an error message, which states that editing the Data Domain device has failed, appears even though the configuration is correct.

    Workaround

    Use either the Chrome browser or the Internet Explorer browser.

  • The Configuration tab page displays the services are not running messages after either restarting vSphere Data Protection or initial configuration (235086)

    After either restarting vSphere Data Protection or initial configuration, the Configuration tab page of the vSphere Data Protection configuration utility displays the following messages, and the proxies status in red.

    • Backup and recovery services are not running.
    • File Level Restore service is not running.

    The messages disappear after 20 minutes.

    Workaround

    To make the messages immediately disappear, click the refresh button beside Proxies.

  • The status of the Data Domain devices on the Storage tab page appears wrong after either changing the vSphere Data Protection password or restarting the management service (237934)

    After either changing the vSphere Data Protection password or restarting the management service, the following message appears on the Storage tab page for the Data Domain devices:

    Data Domain storage status not available. Unable to retrieve ssh key file pair.

    However, after approximately 20 minutes, the Data Domain devices appear online.

  • The vCenter Server certificate does not appear in the vCenter Registration window though the certificate is uploaded during the initial configuration of vCenter Server (238242)

    Though the vCenter Server certificate is uploaded during the initial configuration of vCenter Server, the certificate does not appear in the vCenter Registration window of the vSphere Data Protection configuration utility. Also, the user selection does not persist.

    You must upload the vCenter Server certificate whenever you register vCenter Server.

  • If a vCenter Server instance has vSphere Data Protection appliances of multiple versions, the UI of any vSphere Data Protection version displays the features of the latest version (235357)

Backup Issues

  • Loading clients takes a significant amount of time when editing or cloning a backup job (50334)

    The edit or clone action of a backup job for a SharePoint server (upgraded plug-in) takes 5 to 10 minutes to load clients. In addition, some delay occurs when loading clients for Microsoft Exchange and SQL servers that were created before an upgrade.

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

Migration Issues

  • A backup verification job does not migrate the verification script parameters (238608)

    After migrating a backup verification job that contains the verification script parameters to an Avamar server, clicking More Options on the Avamar Administrator > Policy Management > Edit VM Backup Validation Group > Overview page does not display the verification script parameters of the migrated job.

  • After migrating to vSphere Data Protection 6.1, you cannot restore the application data to the original location by clicking Reset (240401)
  • The backup jobs that do not have active clients do not migrate to vSphere Data Protection 6.1.1 (244970)

    Migrating a backup job that has all MC_Retired clients (VMs) from vSphere Data Protection 6.1 or earlier to 6.1.1 fails because the clients are not active, that is, they are retired (deleted).

Restore Issues

  • If a virtual machine is deleted during a vSphere Data Protection restore operation, the virtual machine is not properly removed from the vSphere Data Protection 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. (35110)

    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.

  • File Level Restore (FLR): "Error 10007: Miscellaneous error" is displayed for most of the FLR failures (45699)

    The "Error 10007: Miscellaneous error" message is displayed for most of the FLR failures. In addition, FLR does not display any error message in cases where there is a restore failure due to the disk being full or a long file path. Therefore, it is impossible to determine the root cause of the FLR failure.

  • Deleted disks are skipped when restoring to original location (53004)

    If the target VM no longer has the same disk footprint as the original VM that was backed up (if the disks have been removed or deleted from the VM), performing a "Restore to original location" operation, after selecting a restore point timestamp in the Restore pane, will silently fail to restore the missing disk of the VM.

    Workaround

    Restore the disk to its original location after manually adding the missing disk to the VM. Ensure the disk is the same size as it was when the VM was backed up. If this workaround fails, restore the disk to a new location to create a new VM. When the restore task completes, detach the restored disks from the new VM and attach them to the required VM using the information in "Detaching and Reattaching Storage" of the vSphere Data Protection Administration Guide.

  • Canceling a restore operation does not delete the restored data on a VM (237125)

    While performing a restore to a different VM that is not the source VM, if you cancel the operation, the cancelation succeeds, but the already restored data that is part of the canceled restore is not deleted from the VM.

  • Restoring to the same source location on a VM by selecting the Restore along with configuration option fails (237015)

    If the source virtual disks are removed on a VM, and you restore the same virtual disks to the same source location on the VM by selecting the Restore along with configuration option, the operation fails.

    Workaround

    Perform the restore to an alternate location.

Replication Issues

  • Replication of replicated clients under a particular tenant on the target server fails (194669)

    The replication of replicated clients from a source to a target server under a particular tenant account fails with the following error message:

    Specified account ( ) does not fall within the current authorization domain.

    In addition, the failure occurs with the following source/target combinations:

    • Source server: vSphere Data Protection Advanced and Target Server: vSphere Data Protection Advanced/Replication Target Identity (RTI)
    • Source server: RTI and Target Server: RTI/vSphere Data Protection Advanced

  • Replication Recovery: Replication logs are filling up the root partition - need to create a symlink to another partition (195196)

    The replication logs are currently going to the /space partition and not to the root partition.

    Workaround

    Manage the replication logs in the /usr/local/Avamar/var/client directory (the space partition).

Microsoft Application Issues

  • On Microsoft Exchange clients, there are many warning messages in the avagent log that print frequently and fill up the logs (56723)

    The Microsoft Exchange client is left registered with two vSphere Data Protection Advanced appliances on vCenter Server, which is causing this issue.

  • You cannot back up the SharePoint Server databases if the database names contain unicode characters (192449)
  • You cannot perform a Granular Level Recovery (GLR) on an Exchange client (238439)

    You cannot perform a GLR on an Exchange client if the GLR plug-in is not installed. Even if you install the GLR plug-in by using the repair option of the Exchange client installer, you cannot perform the GLR.

    Workaround

    1. Uninstall the Exchange client.
    2. Run the Exchange client installer.
    3. On the Feature selection page, select the GLR feature.
    4. Complete the installation.

Automatic Backup Verification (ABV) Issues

  • ABV: Verification job fails after renaming the datastore (55790)

    This error can occur if you rename or move the destination datastore outside of vSphere Data Protection.

    Workaround

    Edit the verification job and select the renamed or moved destination datastore as the new destination. For instructions, refer to "Editing a Backup Verification Job" in the vSphere Data Protection Administration Guide.

  • Improper error messages are reported if the Verification job failed because of connection issues due to Data Domain (56619)

    The backup cannot be restored and the Verification job fails because the vSphere Data Protection appliance cannot talk to the Data Domain. It is expected for the Verification job to fail; however, the proper error message does not display and the user does not know the root of the failure.

  • ABV does not start if the last backup completed with an exception (206091)

Fixed Problems

The following table lists the problems that have been fixed in this release of vSphere Data Protection:

Defect Number Description

243524

The following problems have been fixed as part of this defect:

  • Java vulnerabilities (Upgrade to JRE 8u60)

    • Oracle Java SE Multiple Vulnerabilities (April 2014 CPU) (Unix)
    • Critical (10.0) 76533 Oracle Java SE Multiple Vulnerabilities (July 2014 CPU) (Unix)
    • Critical (10.0) 78482 Oracle Java SE Multiple Vulnerabilities (October 2014 CPU) (Unix)
    • Critical (10.0) 80907 Oracle Java SE Multiple Vulnerabilities (January 2015 CPU) (POODLE) (Unix)
    • Critical (10.0) 82821 Oracle Java SE Multiple Vulnerabilities (April 2015 CPU) (FREAK) (Unix)
    • Critical (10.0) 84825 Oracle Java SE Multiple Vulnerabilities (July 2015 CPU) (Unix)
  • SUSE vulnerabilities

    • High (7.8) 83705 SUSE SLES11 Security Update : glibc (SUSE-SU-2015:0551-1)
    • High (7.8) 83708 SUSE SLES11 Security Update : kernel (SUSE-SU-2015:0652-1)
    • High (7.8) 85151 SUSE SLES11 Security Update : bind (SUSE-SU-2015:1316-1)
  • Enable TLS 1.2 and disable TLS 1.0 for external port access

  • Support for in-place upgrade from vSphere Data Protection 6.1 to vSphere Data Protection 6.1.1

241895 The vSphere Data Protection migration hangs at 42% on IPv6 setup during disk attachment