Avamar Plug-in for SQL

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.

This article addresses an issue where the number of sparse files differs between the data partitions causing the grid to enter admin mode.

Avamar Garbage Collection completes, but the following is observed in the ddrmaint.log: 'Operation time limit reached. gc did not complete'.

The "space.log" can get too large causing Simple Network Management Protocol (SNMP) issues between Avamar and Data Domain.

A Data Domain was removed without removing associated backups from Avamar, causing hfscheck to fail with MSG_ERR_DDR_ERROR due to the nonexistent ddrindex.

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

Instant Access (IA) restore fails with "Reached the maximum number of instant access sessions that are allowed on the Data Domain system."

SQL Incremental backup fails with avsql Error <40258>: XXXXXX - Could not allocate space for object 'dbo.backupset'.'XXXXXXXXXX' in database 'XXXX' because the 'PRIMARY' filegroup is full.

Avamar Administrator dashboard shows erratic capacity forecast for Data Domain.

Unable to open Avamar Administration UI - Connection refused to host.

This article explains the behavior observed when checkpoints are not removed from Avamar, even after successful checkpoint validation.

This article describes how to use common Microsoft SQL Server T‑SQL scripts to assist with troubleshooting Avamar SQL Plug‑in backup issues. These scripts help identify backup history, validate log sequence number (LSN) continuity, and investigate log gap errors.

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.

This article describes how to verify SQL Server permissions required by Dell Avamar to perform backup and restore operations.

Avamar SQL backups for SQL Server Availability Groups (Always On AG) fail to recognize the --sqlserver flag during UI‑initiated browse or dataset operations. Command‑line backups work as expected, but UI browse operations fail because the SQL Server name is not correctly resolved when passed in lowercase.

Avamar 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: SQL Incremental backups intermittently leave a frozen avtar.exe session. "avsql error: lock error - process already running or error creating local lock file"

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.

The plugin installation wizard reports the agent as already installed and shows the previous version because registry entries from the previous Avamar Plugin remain on the client after removal.

The Avamar server may generate event code 22602 due to a database error caused by a subquery returning multiple rows. This issue appears in the Management Console Server (MCS) logs and is likely related to an incorrect MCS restore.

This article explains the change of status starting from OS Security Rollup 2024-R2.

This article provides a way of restoring database from a primary or a secondary Data Domain using product such as Oracle Recovery Manager (RMAN) Agent and DDBEA.

The Data Protection Engine (DPE) plugin cannot operate on vCloud Director (vCD) 10.4.1, causing URLServiceException 02105 and 403 with NullPointerException logs; cause is vCD 10.4.1 unsupported.

This article outlines a known issue that occurs in Avamar Administrator (JNLP) following an update to Java version 1.8.0_481.

In Avamar versions prior to 19.8 SQL clients deployed in Microsoft Azure using Data Domain Virtual Edition (DDVE), backups may fail randomly with session security enabled. The failures occur due to SSL certificate and private key validation errors caused by incorrect IP address selection when the client resolves to the IPv6 loopback address instead of IPv4.

Avamar Hyper‑V backups fail or complete with exceptions when multiple virtual machines (VMs) from specific Hyper‑V nodes are selected in the backup dataset. The backups fail with error 43426, indicating that checkpoint creation failed and the affected VMs were skipped.

Avamar SQL restore log still shows a time-out after extending the waiting time.

How to reset or regenerate certificates due to expiration (or misconfiguration).

Uploading an Avamar Workflow Package (AVP) into the repository fails with "Can not check the readiness status of the file, ignoring: <package_name>.avp" (The error is in the avinstaller.log.0 log which can be accessed from the UI or command line.)