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

Microsoft Hyper-V VSS plug-in known issues

The following table lists the Microsoft Hyper-V VSS plug-in known issues in this release:

Table 1. Microsoft Hyper-V VSS plug-in known issues
Issue ID Subject/Functional area Description Workaround/Resolution
Data Domain token authentication issue with clients earlier than Avamar release 7.5 Avamar release 7.5 introduced Data Domain token authentication for the Microsoft application plug-ins. Data Domain token-based authentication is not supported for clients before release 7.5. The interim solution to this problem is to upgrade the clients to release 7.5, or to disable token-based authentication on the Avamar server. NA
274173 Command-line interface restores from backups on Cloud fail for Microsoft application plug-ins Restore operations from the command-line interface do not work for Microsoft application plug-ins (SQL, SharePoint, Exchange, Hyper-V) when the backup resides in the Cloud.

For these restore operations, use the Avamar Management Console's Avamar Administrator window.

NA
290914 Logfile option cannot be used for Hyper-V, SharePoint, and Exchange backups to specify an alternate path for log file generation When performing backups for Microsoft application plug-ins including Hyper-V, SharePoint, and Exchange, you cannot use the logfile option to specify an alternate file path location for the generated log files. Logs can only be generated in the default path, C:\Program Files\avs\var\. NA
313896 [Windows 2019]For SMB VMs RCT Incremental backup fails for vms hosted on remote nodes(passive nodes) Whenever we have VMs hosted on secondary nodes or remote nodes(passive nodes) other than the primary node the incremental backups fail with unable to get the RCT extents error. NA
322762 esc 38247 Avamar Config checker is unable to get the integration services version for Hyper-V VM in Hyper-V 2016/2019 environment. Avamar Config Checker fails to get the version of Integration Services for VMs hosted on Hyper-V 2016/2019 nodes. NA
323821 [Windows 2019]AV-Hyper-V VSS Synthetic full restores fail with an error: Hyper-V VSS Writer failed in Post-Restore event on Windows 2019 S2D and on Windows 2019 VSS synthetic full original location restores and redirected-restores fail with error: Hyper-V VSS Writer failed in Post-Restore event on Windows 2019 S2D and on Windows 2019. For Windows 2019, RCT workflow is recommended. NA
324145 [Windows 2019] AV-Hyper-V VSS redirected restores fail with an error: Hyper-V VSS Writer failed in Post-Restore event on Windows 2019 S2D and on Windows 2019 VSS redirected restores fail with error: Hyper-V VSS Writer failed in Post-Restore event on Windows 2019 S2D and on Windows 2019. For Windows 2019, RCT workflow is recommended. 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: <>()\