Skip to main content
Avamar image

Avamar

Avamar

Articles

Invalid entry. Please use only Letters, numbers and any special characters except <>)(%/;,=#-/*

30 out of 1425 shown
1425 out of 1425 shown

This document highlights minimum, recommended, and latest code versions for Dell Technologies Enterprise and Data Center Infrastructure products. Dell carefully evaluates and monitors code deployment data to ensure that product releases meet our stringent expectations to provide our customers with reliable products and solutions.
Updated:  September 10, 2026 ID: 000205512

This document highlights minimum, recommended, and latest code versions for Dell Technologies Enterprise and Data Center Infrastructure products. Dell carefully evaluates and monitors code deployment data to ensure that product releases meet our stringent expectations to provide our customers with reliable products and solutions.
Updated:  September 10, 2026 ID: 000502480

This article explains how to enable debug mode during a Windows client Bare Metal Restore (BMR) using the Avamar Bare Metal Recovery Wizard.
Updated:  September 11, 2026 ID: 000197689

This knowledge article provides instructions for upgrading the Embedded Service Enabler (ESE) service on Avamar.
Updated:  September 11, 2026 ID: 000467709

This article explains an issue where the Certificate Manager Service (acmservice) unexpectedly terminates the GSAN process during an MCS restart. This behavior is rare and occurs only under specific circumstances.
Updated:  September 10, 2026 ID: 000507469

Avamar SQL client restore fails with "avsql Error <14279>: Instance xxx wasn't found"
Updated:  September 10, 2026 ID: 000059022

During an Avamar file system restore with the --restore-acls-only option, some files receive no access control lists because inherited ACLs are not processed by default.
Updated:  September 10, 2026 ID: 000066187

Windows backups using Avamar Volume Shadow Copy Service report avvss Error 8784 because the Background Intelligent Transfer Service (BITS) writer is missing; backups appear failed but are restorable.However, the backup appears in the restore UI and can be restored. All Avamar versions are impacted.
Updated:  September 10, 2026 ID: 000082036

Learn how Avamar backs up and restores the Active Directory Lightweight Directory Services (AD LDS) formerly Active Directory Application Mode (ADAM) using VSS or file‑system backups, and restore steps.
Updated:  September 10, 2026 ID: 000158506

When browsing a backup job log in the Avamar UI, the request times out and shows the error “Client failed to respond to a request for its log.” The default 10‑second browse timeout is insufficient for large logs.
Updated:  September 10, 2026 ID: 000202240

This article explains how to use the 'goav client winlogs get-logs' command.
Updated:  September 10, 2026 ID: 000317368

During a Granular Level Recovery (GLR) of an Exchange database, Avamar sends an email alert and logs events, though the restore finishes successfully.
Updated:  September 10, 2026 ID: 000207309

This article describes what information is needed when troubleshooting Avamar capacity issues, and how to collect it.
Updated:  September 09, 2026 ID: 000040862

This article discusses aspects of Avamar's encryption-at-rest functionality including its purpose and caveats. The internal sections of this article, which is available to Dell staff and partners only, explain how to configure it.
Updated:  September 09, 2026 ID: 000046249

This knowledge base article shows how to upgrade avamar virtual machine proxy using proxy deployment manager (PDM).
Updated:  September 09, 2026 ID: 000020235

The SharePoint Volume Shadow Copy Service (VSS) plug-in installation fails with "EMC Avamar for Windows Setup Wizard ended prematurely"
Updated:  September 09, 2026 ID: 000041401

Microsoft Windows OS 2016 issue regarding Volume Shadow Copy Service (VSS) completing with Exceptions.
Updated:  September 09, 2026 ID: 000057085

Volume Shadow Copy Service (VSS) backup for Windows failing with error: ERROR: Win32 call L"GetVolumePathNameW" failed and avvss Error <12077>: VSS returned an error message exiting HR = 0x8007007b
Updated:  September 09, 2026 ID: 000063946

During Avamar backups, the process may halt unexpectedly, leaving avsql and avtar threads stuck. The issue is caused by a software glitch in the GetConfiguration function of the Microsoft SQL VDI API used by the Avamar plugin.
Updated:  September 09, 2026 ID: 000068644

Configuring multiple Avamar Network Data Management Protocol [NDMP] clients allows for more than 4 streams and enables concurrent backups of large volumes and independent backups of multiple business units on the same Network Attached Storage [NAS] device.
Updated:  September 09, 2026 ID: 000021990

Multistream backups of databases with thousands of file groups fail, returning error AV_WC_SQL_BU caused by a VDS configuration timeout. Single stream backup works
Updated:  September 09, 2026 ID: 000193595

The Windows Avamar client shows only the VSS plug‑in on the Backup/Restore tab because the file system plug‑in is missing after downgrading from 19.2 to 19.1, leaving a previous plug‑in installed.
Updated:  September 09, 2026 ID: 000201404

Using the --restore-acls-only flag leaves the root drive and some middle‑layer folder ACLs unrecovered because the restore relies on SetNamedSecurityInfoW and SetFileSecurity, which cannot fully apply those permissions.
Updated:  September 09, 2026 ID: 000080830

An Avamar Gen4T node reports the following: Symptom Code 52702 - HW_PWR_SPY_DISCONNECT_G4T
Updated:  September 09, 2026 ID: 000064029

An AlwaysON database backup reports “Error: A log gap was identified or a full backup was not found” for incremental after a full backup, caused by LSN values in SQL not matching backup metadata.
Updated:  September 08, 2026 ID: 000065986

Query regarding the use of 2FA (Two-Factor Authentication) to access an Avamar grid over SSH.
Updated:  September 08, 2026 ID: 000022842

This article provides estimates on scheduling lead time when booking Remote Proactive Services (RPS) upgrades.
Updated:  September 08, 2026 ID: 000021599

Avamar: The snmpwalk command failing to Avamar server.
Updated:  September 08, 2026 ID: 000025629

An Avamar Gen4T node reports the following: Symptom Code 52764 - HW_PHYS_DISK_BAD_BLOCK_G4T
Updated:  September 08, 2026 ID: 000051354

An Avamar Gen4T installation fails to validate the number of data nodes due to an incorrect bondconf.xml.
Updated:  September 08, 2026 ID: 000030962