Using VAL to backup file directory with frequent deletes, how to avoid "Failed to backup file123" warnings?

[cerberus]

Hello,

Using VBR v13.0.1.2067 to backup a RedHat Linux VM via VAL v13.0.1.404.

Job is configured in "Managed by backup server" mode, and it backs up directly from the live system.

The issue I am running into is, one of the directories is massive (millions of files), and there are frequent updates to the directory, including deletes.

When the backup job starts, and it gets around to backing up the file it thinks is still there, that file may already be deleted, and as such the job has many similar warnings:

Code: Select all

6/1/2026 1:36:33 AM Warning : Failed to backup [/usr1/lobs/369/9215500]

In our case, this is expected and should not raise a warning. Is there anyway to configure the job or the agent on the host, to NOT raise a warning if a file is missing during backup?

[rovshan.pashayev]

Hi Mirza,

Try this on each machine:

1. Edit the configuration file: /etc/veeam/veeam.ini
2. Set the parameter:

Code: Select all

# Display warnings for skipped files backup process: 0 = Disable, 1 = Partial, 2 = Full
skippedFilesWarnings = 0

3. Restart the service:

Code: Select all

systemctl restart veeamservice.service