on VBR we can define which block will be used for a job ( in advanced settings per job, storage -> storage optimization ).
in standalone veeam agent ( not connected to VBR / VCC ) we can store backups direct on S3 storage.
our S3 storage solution vendor - cloudian - recomends that we should use 8MB block size or 4MB due to limits objects count on S3 storage , wehre too many object can impact performance of whole S3.
In veeam agent in settings ( veeam.ini or TUI ) I can't find that settings.
but - when I've deep dive to sqlite database , I've found that agent by default use 1MB block size : KbBlockSize1024.
which is reported by veeam job info :
Block size: 1024 KB
I've manualy changed entries in sqlite database to KbBlockSize8192 and restarted job.
On S3 level I've noticed reduction of objects created by veeam agent went from 11k ( on block size 1024kb ) to 2k ( block size 8192Kb).
overal object size increased from 0.5MB to 3 MB
this change has direct impact to our S3 srKbBlockSize1024torage performance.
and question to Veeam staff
Will you add feature to change block size to veeam agent settings in TUI ?
Or I can change it directly in database and this will not provide any impact to veeam agent itself ?
I'm asking because we have go we clients which use only standalone agents and the send backup direct to our S3 storage.
there are not so many but the are killing performance for whole S3.
on VBR we can change block size to 4 or even 8MB and we did that.
but on agents there no simple/official way
