(summary here still shows VM size as 1.9TB though)
It’s a known bug that is going to be fixed in the next release.
As to exclusion issue, please be aware that this setting has to do with Veeam backup/replication processing only, meanwhile, VMware snapshot is operation that happens on all disks at once regardless of the options set in VB&R. As a result, you get a typical VMware failure that occurs when the snapshot file at its maximum size is unable to fit into a datastore.
As a potential workaround, you might want to set unrequired disks as independent ones via vSphere client, and also exclude them in VB&R console.
Hope this helps.