It means that one block will consume eight blocks at the filesytem level, but no block will be wasted, as the two are aligned. The Veeam block size (after compression) of 512KB is going to be written in the underlying filesytem, which has a block size of 64k. There are three layers where the block size can be configured: Veeam block size for the backup files, the filesystem and the storage volumes. This value can be used to better configure storage arrays especially low-end storage systems can greatly benefit from an optimized stripe size. Since compression ratio is very often around 2x, with this block size, Veeam will write around 512KB or less to the repository per Veeam block. You can customize the block size during the job configuration using the storage optimization setting of the backup job.īy default, Veeam’s block size is set to local target, which is 1MB before compression. However, it is highly recommended to test this prior to deployment whenever possible.ĭuring the backup process, data blocks are processed in chunks and stored inside backup files in the backup repository. Block sizesĪs can be seen from the field, optimal value for the stripe size is often between 128KB and 256KB. A block storage device can be a local disk ( Direct Attached Storage) or a LUN provided via a Storage Area Network like iSCSI or Fibre Channel. These kinds of repositories do provide a block storage device to a Windows or Linux repository server. This site uses Just the Docs, a documentation theme for Jekyll.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |