Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell EMC Avamar 19.7 Release Notes

PDF

VMware known issues

The following table lists the VMware known issues in this release:

Table 1. VMware known issues
Issue ID Subject/Functional area Description Workaround/Resolution
esc 34477 Domain user not supported for file-level restore of virtual machine backup For non-Windows platforms, you cannot perform file-level restore of a virtual machine backup as a Domain user. The user can be part of the Standard or Administrators group. NA
- Exclude the proxy from the virtual machine backup if performing the backup with other VMware software Including the Avamar proxy in a backup consumes a large amount of space. When using other VMware software instead of the Avamar software to perform the virtual machine backup, it is recommended that you exclude the proxy virtual machine from the backup. NA
- Adding vCenter as IPv6 address is not supported, use FQDN instead When you register or add a VMware vCenter client to Avamar, ensure that you specify the fully qualified domain name (FQDN) of the vCenter. Using the IPv6 address is not supported NA
- HotAdd mode does not work with a VSAN disk Due to a known limitation with VMware, documented in the VDDK 6.0.1 release notes regarding vSAN 6.1, ESXi hosts do not allow HotAdd of a vSAN disk on a proxy virtual machine with datastore types other than vSAN. As a result, in a vSAN 6.1 environment, attempts to hotadd a VMDK vSAN datastore by a proxy residing outside vSAN fails. If hotadd mode is desired, host the proxy on the vSAN datastore. NA
248502 Support for validation of VMware image backup in MCCLI is limited When using the mccli backup validate, validation is scheduled but the activity is in waiting-client state. The --dest-client-name and --dest-client-domain options are not currently supported when validating a non /REPLICATE client backup. NA
248775 Proxy running on non PDL datastore is getting powered off during a PDL of virtual machine datastore The virtual machine proxy can get abruptly powered off if the proxy is engaged in a hotadd backup of a VMCP-enabled virtual machine, in the event of a permanent device loss of the virtual machine datastore. This problem might occur due to HA attempting to restart the proxy virtual machine, as it would have mounted the VMDK of the virtual machine.

The interim solution to this problem is to ensure that the next schedule starts correctly, which manually removes all the hotadd disks from the Avamar proxy, and power it back on. A snapshot consolidation may also be required for the virtual machine.

NA
263450 File-level restore not supported for GPT/EFI drives on Windows 2012 when drive has been edited by third party disk tool Avamar does not support the use of GPT/EFI drives on Windows 2012 for file-level restore operations when the drive has been edited by a disk tool from a third party software vendor. Before mounting the drive for file-level restore, verify that all the disks on the virtual machine have valid/supported partitions. NA
278280 Instant Access that is not supported with cloud tiering Instant Access restores are not supported for data that is migrated to the cloud using the cloud tiering feature. NA
282640 Restoring a remote backup fails when the restore is to a specific ESXi that is different from the original ESXi server Restoring a remote backup fails when the restore is to a specific ESXi that is different from the original ESXi server. The interim solutions to this problem are:
  • If a local backup exists, restore the local backup to the specific ESXi.
  • If a local backup does not exist, and the original ESXi is running, restore the remote backup to original ESXi and then restore the remote backup to the specific ESXi.
Use the avrepl command to replicate the remote backup to the source Avamar when the following occurs:
  • A local backup does not exist.
  • The original ESXi is not running.
Restore the local backup to the specific ESXi: 
avrepl --[replscript]restore=true --operation=replicate --[replscript]dstaddr=SRC_ADDR 
--[replscript]dstid=repluser --dstpassword=Chang3M3Now. --ap=Chang3M3Now. --[replscript]dpnname=SRC_ADDR
 --[replscript]dstencrypt=tls /REPLICATE/CLIENTPATH

Where SRC_ADDR is the IP address of the source Avamar server and CLIENTPATH is the client path. If CLIENTPATH is a domain, instead of a path, it moves all the clients' backups under the domain.

NA
290464 esc 29814 BMR fails When performing bare metal recovery (BMR) to a virtual machine with VMware hardware version 11, the following problems might occur:
  • WinPE cannot find a virtual disk.
  • The restored virtual machine will not boot.
The following workarounds apply:
  • Restore the system backup to a virtual machine with VMware hardware version 8 or 9.
  • Ensure the hardware configuration of the target host is the same as the hardware configuration of the source host.
291803 When logged in as Local user with administrator role, Advanced Policy Builder fails to install/upgrade/register client agents on SQL Virtual machines Due to the introduction of User Account Control (UAC) in Microsoft Windows 7 and later versions, when logged in as a Local user with the administrator role, the Advanced Policy Builder fails to install/upgrade/register client agents on SQL virtual machines. On the guest operating system, turn off Admin Approval Mode in the UAC settings for the admin group.
292446 During a restore, the virtual machine Generation ID might not increment which might cause data loss If a virtual machine with the Active Directory role is restored by using the Avamar backup data loss might occur as a result of a USN rollback. In this scenario, the restored virtual machine retains the same virtual GenerationID as the source virtual machine. Perform the following workaround:
  1. Restore the virtual machine from the backup.
  2. Do not start the virtual machine.
  3. Take a snapshot of the virtual machine by using VMware.
  4. Revert the virtual machine to the snapshot.
  5. Start the virtual machine.
293950 Virtual machine client jobs in waiting, failed or canceled state might not get restarted after fail-over After a vCenter high availability fail-over, virtual machine client jobs that were in a waiting, failed or canceled state before the fail-over might not be restarted by the Avamar Management Console. If this issue occurs, restart the Avamar Management Console services.
300223 If a rule is not created to exclude proxy VMs when rule-based protection is used, PDM registration fails PDM registration fails and the following error message appears if a rule is not created to exclude proxy VMs when rule-based protection is used: Could not register proxy: invalid domain When using rule-based protection, create a rule to exclude proxy VMs.
307561 Image-level virtual machine restore for a very large (1400+) number of virtual machines simultaneously is not supported Performance issues are observed when performing 1400 or more image-level virtual machine restores simultaneously. NA
309541 Limitations to vCenter High Availability Note the following limitations that are related to support for vCenter High Availability (VCHA):
  • If the proxy is not available after the VCHA event, a restart order gets issues for all failed/restarted jobs, which will not complete because the proxy is not available.
  • If Hot Add transport mode is used for the virtual disks and the proxy fails, all the associated clients with Hot Add disks in the proxy fail, and a new backup cannot be performed.
Perform the following workaround
  1. Bring the proxy back online, and then perform an on-demand backup with the same proxy. Disks are consolidated and the backups proceed.
  2. Manually remove all Hot Add disks from the proxy.
309934 Jetty service continues to run in proxy virtual machine after stop command When you run the service jetty stop command to stop the jetty service in the proxy virtual machine, the back-end process continues to run. Stop the back-end jetty process manually.
319308 Backup failed in Avamar 19.3 with VMC 1.10 In Avamar release 19.3, Virtual Machine backup is not supported with VMware VMC 1.10 release. NA
319375 Backup failed in Avamar 19.3 with VMC 1.9 In Avamar release 19.3, Virtual Machine backup is not supported with VMware VMC 1.9 release. NA
319482 Virtual Machine image restore to a different existing VM is not supported. Virtual Machine image restore to a different existing VM is not supported. NA
320131 vddk errors are seen for successful VM Image backup and restores vddk error during VM Image backup and restore "Error while loading feature config file: /etc/vmware/vsphereFeatures/vsphereFeatures.cfg, using default feature state values". This is treated as warning message from proxy perspective and safe to ignore. NA

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\