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.

This article contains information about customer replaceable unit (CRU) videos for Dell Technologies VNX and VNXe products.

Root to root migration (R2R) or standard replication jobs fails when a domain user has a mismatched or missing password.

This article describes a packet loss issue observed when Avamar Data Store nodes configured with Linux active-backup network bonding are connected to Cisco Catalyst switches. The behavior may also occur with other switch models. The issue is caused by the switch’s MAC address learning behavior most likely related to the control‑packet learning feature not correctly handling the MAC address assignment used by Linux bonding, resulting in intermittent traffic loss.

This article addresses the problem of Avamar replication failures due to "SSL certificate/key not found or invalid" errors.

This article provides the instructions to perform after changing the GSAN root password if axionfs reports errors.

VMware backup failed when there is a manual snapshot. The Virtual Machine (VM) shows that it needs consolidation but failed.

This article describes why it is not possible to list clients in the Avamar User Interface (AUI).

Avamar replication runs on retired clients with 0 progress bytes.

This article describes an issue during VMware image client import where the virtual machine is not added due to an inconsistency between GSAN and MCDB.

This article addresses an Avamar 19.8 in Data Protection Central (DPC) activation issue.

Avamar image backup fails with error “Insufficient permissions in the host operating system” (error 3014) because VMware vCenter Server cannot authenticate the backup account.

This knowledge article provides solutions for resolving Hyper-V checkpoint creation errors for virtual machine (VM) backup failures.

Avamar backups to Data Domain fail with error 5005, DDR result code: 1, desc: no room left. The issue occurs when the Data Domain disk staging area is not configured or is disabled, causing Avamar to fail while creating the required staging directory.

Avamar Windows Client (WC) and Non‑Windows Client (NC) backups fail when connecting to Data Domain systems running DD OS 7.2.0.40-664052 or later. The issue affects Avamar 19.3.100-149 clients and results in connection failures either at backup start or during backup execution.

An Avamar backend capacity report takes a long time (hours to several days) to complete.

Booting from the Avamar Bare Metal Recovery (BMR) ISO stops responding at the Windows logo. This issue has been observed on servers with AMD processors.

On-demand replication job is stuck at a waiting-queue when an on-demand replication job is in progress.

An Avamar system may experience authentication issues using the admin or root account, and the error "su: Permission denied" is returned. This issue can be resolved by removing "~" from /etc/pam.d/common-auth-pc file.

Avamar Data Migration Enabler (ADMe) job fails during the Staging Phase when ADMe attempts to recapture the stat file (avtarres1.stat) after a restore operation. ADMe cannot parse or access the stat file, causing the migration workflow to stop.

PDM fails to create recommendation after installing OSRollup.

This article describes an issue that occurs when restoring a Virtual Machine (VM) to a different vCenter (VC) using Instant Access (IA).

This article explains the functionality of the proactive health check (PHC) script and provides a comprehensive guide on its execution.

This article provides the steps to remove a Data Domain System from an Avamar grid.

This Resolution Path article can be used as a starting point for all Avamar Capacity issues.

This article addresses high capacity on Data Domain in an Avamar Integrated environment.

The Avamar Management Console Server (MCS) fails with the message "Failed to connect to Administrator Server. Connection refused to host" due to the MCS service being down.

In an Avamar environment integrated with Data Domain, replication is completing with exceptions due to an "Out of streams" error.

This KB article provides access to Avamar 19.1 guides.

This article explains how an incorrect command in avsetup_snmpv3_user.sh prevents SNMPv3 user creation in Avamar and how stopping snmpd before running the script resolves it.