These two chapters from the docs are helpful to understand concurrent jobs:
- https://docs.bareos.org/Appendix/Troubleshooting.html#concurrentjobs - https://docs.bareos.org/TasksAndConcepts/VolumeManagement.html#concurrentdiskjobs Your problem is that the storage list in the pool is possible but not really usable. In doc details you can see that only the first storage of the list is ever used: https://docs.bareos.org/Configuration/Director.html#config-Dir_Pool_Storage > Be aware that you theoretically can give a list of storages here but only the first item from the list is actually used for backup and restore jobs. you will have to define in each job which storage the job should use to spread the jobs to the multiple storages [email protected] schrieb am Dienstag, 30. März 2021 um 15:14:27 UTC+2: > Hi, > > I have one director (running bareos-dir + postgres) and multiple storage > servers (each running 1 bareos-sd instance). > > The storage servers are basically boxes with a lot of diskapace > available locally (/backup/). The plan is to use 50GB virtual (file) tapes. > > So far, pretty straightforward. > > > The challenge I'm facing: I would like my bareos-filedaemons to write > backups to any available tape, on any of the available storages. > > > So I went "well, I'll just create a single pool with multiple storages", > like shown below. > > The problem is: only the first defined storage (bareos-sd01) is ever > used, although the reference states that a list of storages can be > definded. > > Any ideas on how to fix this? > > Can I use multiple pools with one storage each? > > Regards, > > > > ++++++++++ > on the director: > > Pool { > Name = bareos-dir-pool > Pool Type = Backup > Storage = bareos-sd01 > Storage = bareos-sd02 > Recycle=yes > AutoPrune = yes > Volume Retention = 17 days > Maximum Volume Bytes = 50G > Label Format = "tape-" > Volume Use Duration = 23h > Action On Purge = Truncate > Maximum Volumes = 50 > } > Storage { > Name = bareos-sd01 > Address = 10.0.100.133 > Device = bareos-sd01-device > Media Type = file01 > Password = blah > Maximum Concurrent Jobs = 4 > } > > Storage { > Name = bareos-sd02 > Address = 10.0.100.132 > Device = bareos-sd02-device > Media Type = file02 > Password = blah > Maximum Concurrent Jobs = 4 > } > > ++++++++++ > on storage01: > > Device { > Name = bareos-sd01-device > Archive Device = /backup/bareos-sd01-device > Media Type = file01 > Device Type = File > Random Access = Yes > LabelMedia = yes > AutomaticMount = yes > Requires Mount = no > RemovableMedia = no > AlwaysOpen = no > Maximum Concurrent Jobs = 4 > } > > on storage01: > > Device { > Name = bareos-sd02-device > Archive Device = /backup/bareos-sd02-device > Media Type = file02 > Device Type = File > Random Access = Yes > LabelMedia = yes > AutomaticMount = yes > Requires Mount = no > RemovableMedia = no > AlwaysOpen = no > Maximum Concurrent Jobs = 4 > } > ++++++++++ > > -- > Florian Panzer > > ----------------------------------- > PLUSTECH GmbH > Jäckstraße 35 > 96052 Bamberg > Telefon: +49 951 299 09 716 <+49%20951%2029909716> > https://plustech.de/ > Geschäftsführung: Florian Panzer > Amtsgericht Bamberg - HRB 9680 > ----------------------------------- > AWS Certified Solution Architect - Associate > AWS APN Consulting Partner > Mitglied in der Allianz für Cybersicherheit > des Bundesamtes für Sicherheit in der Informationstechnik > Mitglied im IT-Cluster Oberfranken > -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/72b4b190-3c8e-4c8e-8ed0-ede801f41bc2n%40googlegroups.com.
