Avamar Server

This document highlights minimum, recommended, and latest code versions for Dell Technologies Enterprise and Datacenter Infrastructure products. We carefully evaluate and monitor code deployment data to ensure that product releases meet our stringent expectations to provide our customers with reliable products and solutions.

Data Domain Capacity Resolution Path.

Avamar VSS backup fails with "avvss Error <12077>: VSS returned an error message exiting HR = 0x8004231f" error due to insufficient storage on a volume being added to the shadow copy set.

Volume Shadow Copy Service (VSS) Plug-in Backup with Hot Fix (HF) 310901 applied is not completing with the error "avvss Error <8784>: BackupComplete(): Writer 'BITS Writer' instance '{..}' not found on system!"

This article describes how to modify the inactivity timeout on the Avamar Administrator Console.

Avamar Backup using SQL Plug-in completed with exceptions or errors. 995 the I/O operation has been aborted because of either a thread exit or an application request or operating system error 0x8007000e. (Not enough storage is available to complete this operation.)

Upgrading IDPA to 2.7.7 or Griffin (Avamar and Data Domain) causes random backup failures due to rejected connections in Data Domain from Object Existence Check (OEC).

This article addresses alerts seen on the newly deployed Avamar 19.12 server the "Event ConnectEMC notification failed" error during event notification setup.

RabbitMQ Resolution Guide

This article explains how to assign an Initial Company Administrator.

Knowledge base (KB) article that provides detailed instructions for applying Hyper-V hotfixes in the correct order.

RecoverPoint for Virtual Machines(VMs) 6.0.3.1 and later are qualified with VMware vStorage APIs for Data Protection(VADP) backup solutions. However, sometimes protected Virtual Machines may see Snapshot Consolidation errors or Virtual Machine restarts, during backup operations.

This article explains how to use the 'goav client hyperv' command set.

The article describes Structured Query Language (SQL) backup failures, where log‑gap errors and missing sqlmeta.xml entries occur because the parser’s buffer limit (32 MB) prevents Logical Sequence Number (LSN) validation.

With no changes or upgrades to Avamar or the Data Domain, the connection to the Data Domain fails to connect, and jobs timeout with no progress.

Client‑side log retention defaults clean logs every 5‑6 days; using only --loglifetime and --logsizecap (e.g., --loglifetime=60 --logsizecap=1024) does not extend retention. Add --logminlifetime equal to the desired days (e.g., --loglifetime=30 --logminlifetime=30 --logsizecap=1024) to keep logs for 30 days. See Dell Knowledge Base article 000060840 and JIRA AVAMARESC‑3266.

Dell Avamar Server and Dell Avamar Virtual Edition remediation is available for improper limitation of a pathname to a restricted directory ('path traversal') vulnerability that could be exploited by malicious users to compromise the affected system.

This article discusses several issues that can prevent a vCenter from being added to Avamar.

The article is provided to help assist with the adding Virtual Machine (VM) Clients to Avamar using the Management Console Command Line Interface (MCCLI).

This article explains how to promote Company Administrators.

This article provides a summary of the current supportability of the Avamar Administrator console.

This article explains Dell guidelines on company administrator assignment.

Dell Avamar Server and Dell Avamar Virtual Edition remediation is available for multiple security vulnerabilities that could be exploited by malicious users to compromise the affected system.

Avamar AlwaysOn backups for Structured Query Language (SQL) may time out, with logs showing status wrapup and remote client forwarding errors. Cause: secondary slow, breaking link; multistream load.

After upgrading Avamar from version 19.4 to 19.7, Hyper‑V Resilient Change Tracking (RCT) backups report Windows Management Instrumentation (WMI) query failures, checkpoint issues, and orphaned checkpoints.

This article addresses a failure scenario in Avamar Hyper-V cluster backups where communication delays between cluster nodes cause Volume Shadow Copy Service (VSS) snapshot synchronization timeouts. The issue is resolved by adjusting timeout parameters in the avhypervvss.cmd configuration file.

Avamar Hyper‑V backups show missing backup history file, cannot resolve the Data Domain (DD) server name and fail target validation; caused by an avtar.exe binary version incompatible with the DD version.

This article explains why the Avamar restore UI backup size shows a different value to the backend report value for the same client.

Avamar Downloader Service (LDLS) is not pushing downloaded files to an Avamar server which is correctly configured, authenticated, and is reachable.

An Avamar grid that was previously full is cleaned of data. After, after garbage collection has removed all eligible data, it continues to show ~30% usage.