Avamar: Linux/UNIX backup errors "Unable to Open or Inconsistent with original data size"

Avamar Backup Errors

Avamar backup completes with exceptions. Reviewing the logs shows messages similar to the following:

• Avamar backup fails with file read errors
• Errors indicate "unable to Open" or "Inconsistent with original data size"
• Files may be reported as not found or in use during backup

Example error messages include:

avtar Error <16507>: Path "/logs/tools/verbose.log": Total processed bytes 49347 is inconsistent with original data size 70715
avtar Error <5137>: Unable to open "/logs/tools/verbose.logbk" for backup (code 2: No such file or directory)

Root Cause of the Issue

The Avamar UNIX/Linux clients do not create a snapshot of the disk to backup from. Instead, the Avamar client scans the disk and creates a list of files to backup. During the backup, the file found is compared to the file originally found. If the file's information differs, an error is logged.

• The file size may have changed between the time it was initially found and the time it was backed up.
• A file may have been removed after it was initially found, but before it was backed up.
• A file may be in use when Avamar tries to back it up, preventing the backup from occurring.

These discrepancies can lead to errors being logged during the backup process, even if the backup is completed and usable for restore purposes.

Resolving Avamar Linux/UNIX Backup Errors

To resolve the Avamar Linux/UNIX backup errors, follow these steps:

• Stop all applications running during the backup.
• Exclude the offending file or path to the file.

These methods can help prevent backup errors and ensure a successful backup process.