Despite Maximum Part Size now being 1G and Maximum File Size using the default
of 1G, the part files in the volumes are of size 10G. Since the pool is defined
to have Maximum Volume Bytes 10G, there are just 2 parts per volume, part 1
contains the volume metadata and part 2 contains the backup d
I am using 9.6.7-7 (adapted from the Debian 12 distributed version) on both
Debian 12/ARM64 (Raspberry Pi 5) and Debian 12/AMD64 (a VPS), with a max part
size of 1G and a max vol size of 5G. This works well for me.
It would not supprize me if the Amazon S3 API has some upper limit on file
size.
MinIO has a part limit of 5G, but a part in MinIO lingo is very likely not the
same as a part in Bacula lingo. Apart from that the limits are crazy high
considering this will be transferred over the public Internet.
I now have set Max Part Size to 1G and Max Volume Bytes to 10G and will see how
Hi there, I am struggling with the Amazon cloud driver. I have defined the Max
vol. bytes as 350G and not defined Max Part Size, but due to volume size of
350G, no part will be bigger than 350G, I suppose. Whether this makes sense
when transferring over the Internet is another story… what would
