On 26.01.2022 18:42, dmitri maziuk wrote:
On 2022-01-26 11:06 AM, Peter Milesson via Bacula-users wrote:
...
Your way of explaining the reasoning of why to use smaller file
volumes, is very appreciated.
...
The only thing I haven't found out is how to preallocate the number
of volumes needed. Maybe there is no need, if the volumes are created
automagically. Most of the RAID array will be used by Bacula, just
leaving a couple of percent as free space.
If you use actual disks as "magazines" with vchanger, you need to
pre-label the volumes. If you use just one big filesystem, you can let
bacula do it for you (last I looked that functionality didn't work w/
autochangers).
If you use disk "magazines" you also need to consider the whole-disk
failure. If you use one big filesystem, use RAID (of course) to guard
against those. But then you should look at the number of file volumes:
some filesystems handle large numbers of directory entries better than
others and you may want to balance the volume file size vs the number
of directory entries.
For single filesystem, I suggest using ZFS instead of a traditional
RAID if you can: you can later grow it on-line by replacing disks w/
bigger ones when (not if) you need to.
Dima
Thanks for your input Dima.
I'm having a RAID5 array of about 40TB in size. A separate RAID
controller card handles the disks. I'm planning to use the normal ext4
file system. It's standard and well known, most probably not the fastest
though. That will not have any great impact, as there is a 4TB NVMe SSD
drive, which takes the odd of the slow physical disk performance.
Best regards,
Peter
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
