21.11.2020 · By default Veeam’s block size is set to Local Target, which is 1 MB before compression. Since compression ratio is very often around 2x, with this block size Veeam will write around 512 KB or less to the repository per Veeam block.
The Veeam block size of 512KB is going to be written in the underlying filesytem, which has a block size of 64k. It means that one block will consume 8 blocks ...
Feb 17, 2015 · More than Veeam block size, it’s useless to create a stripe size bigger than the filesystem you are going to use on top of it. For example,with NTFS the maximum block size is 64k, so any windows repository will use at most this value. Same goes for XFS on linux, but for example ZFS uses a variable block size, with default at 128k.
The Veeam block size (after compression) of 512KB is going to be written in the underlying filesytem, which has a block size of 64k. It means that one block ...
10.02.2021 · 1 — Veeam Agent for Microsoft Windows uses data block size of 512 KB. This block size is recommended for onsite backup to NAS over 1 GB Ethernet. 3 — Veeam Agent for Microsoft Windows uses data block size of 1024 KB. This block size is recommended for backup to SAN, DAS or local storage. 5 — Veeam Agent for Microsoft Windows uses data block size of 4 MB. …
25.07.2012 · So, as I said, Veeam requests blocks at 32k. If the storage reads blocks at 32k, it's the same size, and there's no read amplification. The 1MB block size of Local Target option is the size of the block used in Veeam to do deduplication and compression, but it happens after it's retrieved from the production storage.