Don’t guess. Confirm overflow by reading the logs.
Look for lines like:
ERR | Overflow: Arithmetic operation resulted in an overflow.
ERR | Stack: at Veeam.Backup.Core.CHnagingBlockProcessor.ProcessBlock(Int64 offset, Int32 length)
If you see Int32 in the stack trace next to a file size or offset value, you’ve confirmed the 32-bit boundary issue. veeam backup and replication overflow error
When Veeam interacts with storage arrays (Pure, NetApp, HPE Nimble), it uses snapshot identifiers or transfer offsets. An overflow can happen if the array API returns a 64-bit value but Veeam’s internal handler uses a 32-bit variable. Don’t guess
Run this SQL query on Veeam’s configuration database: Look for lines like: ERR | Overflow: Arithmetic
SELECT name, system_type_name, max_length
FROM sys.dm_exec_describe_first_result_set(
'SELECT TOP 1 backup_size, data_size, total_size FROM dbo.Backup.ModelSections', NULL, 1
);
Look for columns defined as int (max 2,147,483,647 bytes ~2GB) when your actual values exceed that. bigint supports up to 9 exabytes.