Avamar: Log Gap Errors Occur with Sqlmeta.xml Entry Deletion Due to Policy Driven Incremental Backups

Summary: SQL Plugin deleted valid entries from sqlmeta.xml after reporting log gap errors

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Log gap errors are reported on Avamar SQL Plugin 7.5.x, 18.x and 19.x hosted on Windows SQL servers.

The SQL Plugin deletes valid database entries from sqlmeta.xml file when reporting log gap errors. In one case, the log gap error on the Database showed due to an earlier backup taken using native backup or restore tool. This deletion is only seen for policy driven incremental backups; and manual incremental backup preserves the entries on the sqlmeta.xml file.

Cause

As per design , avsql removeing sqlmeta.xml entries when reporting a log gap error  is an expected behavior.

There is no data loss since the metadata of the current backup is preserved in the local copy of sqlmeta.xml. Also the metadata of the current backup is preserved in the Avamar server.
For older backups, the metadata is preserved in the Avamar server.

This behavior is fixed after a full backup runs to clear the log gap condition. The entire backup history is intact on the Avamar server, and the behavior will not impact restores or future incremental backups. 

Resolution

This behavior is expected, and by design,policy driven incremental backups

Affected Products

Avamar
Article Properties
Article Number: 000066625
Article Type: Solution
Last Modified: 16 Sept 2025
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.