Hello Crystian, > Good morning > How are you?
> On it [ https://blog.bacula.org/whitepapers/CloudBackup.pdf | > https://blog.bacula.org/whitepapers/CloudBackup.pdf ] > In the section: > MaximumPartSizeThis directive specifies the maximum size for each CloudVolume > part. Smaller part sizes will reduce restore costs, but may require asmall > additional overhead to handle multiple parts. The maximum numberof parts > permitted in a Cloud Volume is 524,288. The maximum size of anygiven part is > approximately 17.5TB > I'm using 256MB, but, my doubt are: > If there is a recommended size for this? > The smaller the better? > Is 256 MB a good size? The parts are the chunk of data that Bacula will be uploading during backup and downloading during restore. Object storage transactions are atomic. You can only transfer the entire object or nothing. Smaller parts mean less downloaded data (e.g.) if you only need to restore a small file. They are also easier to transfer, since a faulty transmission will require retransmiting all the chunk. However, I personally think very small part size is hard to manage because it will generate thousands of them. Also, I "guess" it might generate some performance overhead. That said, there is no magic number. It depends on your Internet link, object storage provider cost metrics, usability etc. > Thanks Regards, -- MSc Heitor Faria CEO Bacula LATAM mobile1: + 1 909 655-8971 mobile2: + 55 61 98268-4220 [ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] [ http://www.bacula.com.br/ ] América Latina [ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | bacula.com.br ]
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
