|vSphere Data Protection (VDP) 6.1 Release Notes | 10 SEP 2015|
These release notes include the following topics:
Benefits and Features
Read about the benefits and features of this product at the following links:
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 VDP.
- Support for routed / NAT / Firewall / IDS / TSNR between the VDP Appliance and the vCenter (1292848)
When configuring the network for the VDP Appliance and the vCenter, 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 VDP functionality may not work as designed.
- The SQL Server 2005 section in the "VDP Application Support" chapter of the vSphere Data Protection Guide (versions 5.8 and 6.0) erroneously claims "x64" support
The text currently reads as follows:
SQL Server 2005 SP3 x64 on:
- Windows Server 2003 SP1 or later, x86/x64
- Windows Server 2003 R2, SP2 or later, x86/x64
- Windows Server 2008 SP1 or later, x86/x64
- Windows Server 2008 R2, x64
Note the SQL Server should read: "SQL Server 2005 SP3" (remove "x64"). The bullet points are correct.
- 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 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.
Edit the VM settings, set the network connection to the network adaptor, and then power on the VM.
- Add documentation to the admin guide to indicate that VDP 6.0 will not support VVOL (223246)
VDP 6.0 does not support backups and restores of VMs on Virtual Volumes (VVOLs).
- Customer Experience Improvement Program (PhoneHome) is not supported in a pure IPv6 vSphere Data Protection environment (225343)
- In a VSAN 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)
Either restore the entire VM with an image-level backup or restore the disk level backup as a new disk on the original VM.
- Incorrect behavior of the VDP Appliance when more disks are added to the same SCSI slots (59774)
The VDP 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.
- A password change on a configured vCenter Server is not allowed on the VDP Appliance, even after the vCenter Server password has expired (59497)
The VDP-Configure application does not allow a password change for the configured vCenter if backups are in a Running state on the server. If the user password on the configured vCenter has already expired, no tasks are posted on the task console, and, consequently, the tasks cannot be canceled.
Perform the following steps:
- Wait until all the backups and tasks finish in the VDP Appliance and then change the password.
- Restart the VDP Appliance in the maintenance window, and then log into the VDP-Configure user interface and change the vCenter password from the VDP-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 VDP-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.
- VDP 6.1 does not support the traditional Chinese locale (235157)
- VDP 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 VDP GUI or the VDP 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.
Use either the Chrome browser or the Internet Explorer browser.
- The Configuration tab page displays the services are not running messages after either restarting VDP or initial configuration (235086)
After either restarting VDP or initial configuration, the Configuration tab page of the VDP 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.
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 VDP password or restarting the management service (237934)
After either changing the VDP 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.
- vCenter certificate does not appear in the vCenter Registration window though the certificate is uploaded during the initial configuration of vCenter (238242)
Though the vCenter certificate is uploaded during the initial configuration of vCenter, the certificate does not appear in the vCenter Registration window of the VDP configuration utility. Also, the user selection does not persist.
You must upload the vCenter certificate whenever you register vCenter.
- If a vCenter Server has VDP appliances of multiple versions, the UI of any VDP version displays the features of the latest version (235357)
- Loading clients takes a significant amount of time when editing or cloning a backup job (60249)
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.
- 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 VDP 6.1, you cannot perform a restore to the original location (240401)
- 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. (35110)
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.
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.
- Restore of a secondary replica fails or halts prematurely with a log gap error (197437)
When you restore an incremental backup of a secondary replica, the operation returns either a status indicating that the restore operation failed or halted prematurely and the log indicates the log gap error though the database has no log gap. The issue does not occur when you restore a primary replica.
The issue relates to the synchronization of the AlwaysOn nodes, and occurs during the creation of SQL metadata file in the backup workflow, in cases where you back up a secondary AlwaysOn replica.
The issue results in backups with a corrupted metadata file. So, you cannot either perform a log tail recovery or link differential or incremental backups to this backup chain. However, there is no data loss.
Perform a full backup. Ensure that the Force incremental backup after full backup option is not selected.
- 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.
Perform the restore to an alternate location.
- 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: VDP Advanced and Target Server: VDP Advanced / Replication Target Identity (RTI)
- Source server: RTI and Target Server: RTI / VDP 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
/spacepartition and not to the
Manage the replication logs in the
/usr/local/Avamar/var/clientdirectory (the space partition).
- Replication succeeds when there are no restore points (196573)
Replication jobs run and complete successfully, even after the restore points have been deleted. The replication job, however, does not replicate the backups. The expected behavior is the job should fail as there are no restore points to replicate.
This is a known issue that will be fixed in a future release.
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 VDP Advanced Appliances in the vCenter, which is causing this issue.
- Upgrade 2014: The Backup Agent user is reset to Local System after upgrading the Microsoft Exchange client plug-in (191795)
When upgrading the Microsoft Exchange client plug-in from the previous version of the VDP Advanced Appliance to the current VDP Advanced Appliance, the backup agent service logon user is reset to Local System, rather than Backup User.
From VDP version 5.5.6 to 5.8, the system resets the credentials to local system credentials without asking for permission, causing the backup job to fail
To edit the Microsoft Exchange backup job or to create a new Microsoft Exchange backup job, the user must manually configure the backup agent service. To do this, the user must enter the username and password using the Backup User Configuration Utility.
- VDP 6.1 does not support the skip log gap detection feature of SQL Server (196513)
- 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.
- Uninstall the Exchange client.
- Run the Exchange client installer.
- On the Feature selection page, select the GLR feature.
- 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 VDP.
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 VDP 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)
The following table lists the problems that have been fixed in this release of VDP:
|222603||The delete and edit operations on a VDP appliance that has more than 15 backup jobs take more than 10 minutes each to complete.|
|225694||CPU consumption does not decrease after an email schedule has been triggered for longevity scale setup.|
|225816||VDP takes a long time to open jobs such as, backup, automatic backup verification, and replication for editing.|
|229809||The browsers that end trust for SHA-1 SSL certificates for VDP require update.|
|230593||VDP crashes while creating or performing backup jobs.|
|233382||Restoring workorder id for vCenter tasks requires prefixing the client name.|
|235375||Opening a restore rehearsal or a backup now wizard from VC inventory throws a flex exception.|
|39456||Initial creation of large scale (100 VM) backup job takes a long time (10+ minutes).|
|194717||Accessing backups for multiple clients on the recover wizard is very slow.|
|207133||Replication default job duration requires modification.|
|222963||Selecting Distributed Virtual Port Group for network fails to deploy a proxy VM.|
|232550||Encrypted responses are displayed in the HTML format.|
|37897||If you concurrently select a large number, more than 100, of restore points, a few restore points are not locked, unlocked, or deleted.|
|197992||If you simultaneously run the Exchange backup jobs for DAG cluster and DAG passive member, the backup jobs fail.|
|223739||Exchange Server 2013 DAG federated GLR redirected recoveries to a mailbox server that is not part of the DAG fail.|
|230098||GLR restore error :avexchglr Error <13378>: Failed to find C:\Program Files\avp\var\avfscache\AVFSMOUNT\pchs-exch-pv02_00000000\F$\Program Files\Microsoft\Exchange Server\V15\Mailbox\StaffFaculty\*.edb|
|230752||You cannot restore a subset of databases if a backup contains the DAG databases that are active on another node.|
|60530||VDP restore fails if a backup contains special characters in the database names.|
|55338||An RDB restore of an entire backup must be allowed if the backup contains a single database.|
|223328||Completed Tail-Log backups of SQL Server are not available for restore.|
|238924||NGC error #1009 occurs if you restore a disk to a different location.|
|223855||Exchange Server 2013 DAG database recoveries do not validate the suspension of the DAG database replication.|
|230947||Exchange Server 2013 backup fails if the server hosts the suspended copy of a database.|
|223797||Simultaneous scheduled backups of two Availability Group clients to the same secondary replica fail and display lock error.|
|224298||You cannot edit a backed up job if the backed up VM exists in a datacenter that exists in a folder at the vCenter root level.|
|55795||Verification job does not start if the destination path for a host is changed.|
|231287||GLR-browsing two mail boxes on an Exchange Server results in the avmapi error 0x80005010.|
|234895||The admin user does not have the Read permission for the log files.|
|232552||Ciphers are not compliant with VMware's Product Security Requirements (PSR).|
|232335||The VDP console must display the thumbprint of the VDP server certificate.|
|232355||You do not require the current password to change the password in the VDP configuration utility.|
|232433||SSL/TLS certificate validation is disabled by default.|
|232434||VDP does not validate the certificate while either testing the connection or registering the vCenter server.|
|234979||The VDP configuration utility requires an option to enable or disable the vCenter certificate verification.|
|197873||A VDPA server is prone to the man-in-the-middle attacks.|
|207375||A VM backup fails if the ESX server is moved from one datacenter to another within the same vCenter inventory.|
|232352||The VDP configuration utility requires eliminating the session fixation vulnerability.|
|228510||The VPXD logs display the "SSL routines:SSL3_GET_CLIENT_HELLO:wrong version number" error.|
|230978||The VM image level backups require detecting the consistency level.|
|231064||The vSphere web client and the Email Summary report incorrectly display the VDP backup job status.|
|195497||Performing a restore to original does not revert the configuration changes.|
|224650||You cannot perform a File Level Restore from the MC_RETIRED and REPLICATE domains.|
|231693||Advanced login to perform an FLR fails if the user is a member of the AD Group.|
|233432||The VDP UI displays the ABV job details in the never under completion column though the ABV job succeeded.|
|235593||If you initiate an FLR, the restore job is initiated multiple times for the same FLR.|
|53520||An FLR client displays duplicate loading signs and restore points when backups are being mounted.|
|224256||The Outgoing mail server field does not accept an IPv6 address.|
|236692||The VDP Exchange client installation in Japanese fails and displays the Transforming Table Error message.|
|231891||The backup agent service for a SQL failover cluster instance is not created on the passive node.|
|232553||Configuring the network does not require a password.|
|236763||A VMDK backup job silently fails after migrating a disk to a different datastore.|