Veeam Backup – Snapshot Overflow / Error 28

Hello,

We are experiencing an issue with Veeam backups on our dedicated server running AlmaLinux 9.8.

The first two backups completed successfully (October 2 and 4), but all subsequent backups have failed with the following error:

Snapshot overflow – veeamblksnap error 28 (ENOSPC)

The server has over 2 TB of free disk space, and we have already tried different snapshot configurations without success.

Has anyone experienced something similar or found a solution?

Also, we opened support ticket CS16891637 on October 8 and have not received a technical response yet.

Is this waiting time normal for OVHcloud support? How long does it usually take to get a response?

Thank you

3 Answers

3

Hello @Bernard

The ENOSPC error means that that temporary snapshot space has filled up. By default, Veeam reserves a very low limit for this purpose; if during the backup there are many disk writes, that small space fills up in seconds and the backup fails.

I think the solution to this problem is to increase the snapshot size. Take a look at this doc:

https://docs.ovhcloud.com/en/guides/storage-and-backup/backup-agent/troubleshooting

No, 4 days without a technical response is not normal if you have a higher‑level support contract.

OVHcloud publishes its target response times according to the support level you have https://www.ovhcloud.com/en-sg/support-levels/plans/

In any case, resolving your issue does not depend on support taking action, but on you increasing that limit on your server.

Hope I have helped you,
Sergio Turpín

Hello,

The likely cause is that the snapshot storage does not grow fast enough: by default, it grows in portions of 1 GiB, and if the server writes data faster than new portions are added, the snapshot overflows (error 28). The size of these portions is set by diffStorageMinimum in the [blksnap] section of /etc/veeam/veeam.ini. Its value is in 512-byte sectors, and the default, 2097152, is 1 GiB. Could you please double it to reach 2 GiB?

[blksnap]
diffStorageMinimum = 4194304

The kernel module only reads this value when it is loaded, and it stays loaded between backups, so restarting veeamservice is not enough. While no backup is running, you can restart the service and unload the module:

systemctl restart veeamservice
/usr/sbin/blksnap-loader --unload

The next backup then loads the module with the new value. During a backup, you can check it with:

cat /sys/module/veeamblksnap/parameters/diff_storage_minimum

Doubling it should be enough in most cases. If the backup still overflows, you can raise it again (8388608 = 4 GiB): the right value depends on how much data is written on the server during the backup. See also:
https://docs.ovhcloud.com/en/guides/storage-and-backup/backup-agent/troubleshooting

If this does not help, could you please provide the output of:

dmesg -T | grep -iE "veeam|blksnap|bdevfilter"

Hello,

The diffStorageMinimum value was increased from 2097152 to 4194304 in /etc/veeam/veeam.ini, and the new setting was applied to the running kernel module.

After several days of snapshot overflow errors, the backup finally completed successfully without any issues.

Thanks for the support!