Ingo Hellmer
18 Posts
Quote from Ingo Hellmer on November 15, 2022, 8:37 am
Thank you for this response. What is the next best value for bluestore_block_db_size? 600GB converted to bytes
in Veeam you define the backup block size with the primary backup and the default is 1MB (local target). In version11 the max. block size is 4MB (local target - large blocks). These blocks are inside the veeam backup files and are sent to the object store. We use 4MB but nevertheless with about 50TB backup files there are a lot of objects. And when using immutability the metadata of lots of blocks changes. This is why I need metadata on SSD.
Thank you for this response. What is the next best value for bluestore_block_db_size? 600GB converted to bytes
in Veeam you define the backup block size with the primary backup and the default is 1MB (local target). In version11 the max. block size is 4MB (local target - large blocks). These blocks are inside the veeam backup files and are sent to the object store. We use 4MB but nevertheless with about 50TB backup files there are a lot of objects. And when using immutability the metadata of lots of blocks changes. This is why I need metadata on SSD.
admin
2,918 Posts
Quote from admin on November 16, 2022, 9:22 pm
It should be larger than 300 GB, this is the size of the cache level, plus you need to add some more space used during rocksdb compaction. Some users set at slightly above 300 GB, but safest is to double the size to 600 GB if you can.
It should be larger than 300 GB, this is the size of the cache level, plus you need to add some more space used during rocksdb compaction. Some users set at slightly above 300 GB, but safest is to double the size to 600 GB if you can.
