Den tis 25 apr. 2023 kl 15:02 skrev Boris Behrens <bb@kervyn.de>:
We have a customer that tries to use veeam with our rgw objectstorage and it seems to be blazingly slow. What also seems to be strange, that veeam sometimes show "bucket does not exist" or "permission denied". I've tested parallel and everything seems to work fine from the s3cmd/aws cli standpoint. Does anyone here ever experienced veeam problems with rgw?
Mostly the issue that if you do not set block sizes to a large value, it will create REALLY small files. If "problems" relates to "poor MB/s perf", then this could be it. TCP will not get up to any speed if you keep the S3 objects to very small sizes. Look at https://community.veeam.com/blogs-and-podcasts-57/sobr-veeam-capacity-tier-c... for "extra large blocks" to make them 8M at least. We had one Veeam installation vomit millions of files onto our rgw-S3 at an average size of 180k per object, and at those sizes, you will see very poor throughput and the many objs/MB will hurt all other kinds of performance like listing the bucket and so on. -- May the most significant bit of your life be positive.