Avamar

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.

A procedure to manually remove Data Domain Cloud Disaster Recovery (DDCDR) components from Amazon Web Services (AWS) if the Cloud Disaster Recovery Server (CDRS) cloud deployment fails. (A cleanup procedure after a failed CDRA/CDRS installation or upgrade.)

This Resolution Path for the Avamar Plugin aims to guide the Avamar backup administrators, or support engineers, through the initial steps of troubleshooting "ItemPoint with the Avamar Plugins"

This article explains how to verify the Avamar DB2 plugin archivelog configuration to ensure that DB2 databases are correctly set up for archive log backups.

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

The purpose of this KB is to give instructions to collect logs and environment information for troubleshooting Avamar Exchange VSS plugin issues.

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.

Avamar image backups to Data Domain (DD) fail with avtar errors 10542, 10509, 10630, 894.

This article discusses how to configure Avamar 'REST-API backups' to store on Data Domain, with the following 'REST-API examples in swagger-UI page.

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 provides the instructions to disable the "Back Up" and "Back Up Now" options and only allow restores from the avamar client agent.

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

Avamar Structured Query Language (SQL) backups fail with an error indicating that the server principal NT AUTHORITY\SYSTEM cannot access a SQL Server database under the current security context. This issue occurs when the Local System account permissions are removed from the SQL Server instance, which are required for SQL Writer and VDI‑based backup operations.

Avamar replication runs on retired clients with 0 progress bytes.

The Avamar Bare Metal Recovery (BMR) Wizard stalls at retrieving critical volumes in backup on Windows servers that have many attached disks. The wizard appears unresponsive during volume discovery.

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 KB article describes an issue where SharePoint backups fail. All Volume Snapshot Service (VSS) writers are in a Stable state.

Proxy Deployment Manager fails in registration with error 'could not register proxy: invalid domain'

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.

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.

Avamar Client Manager does not support push upgrade for Hyper-V, SharePoint, SQL Server, and Exchange after ItemPoint integration starting with Avamar version 7.4.

PDM fails to create recommendation after installing OSRollup.