Hi Valentin, After trying many options, my mistake was the number of "Maximum Concurrent Jobs" that I have configured different values between bareos-dir storage resource and bareos-sd storage resource. I followed the instructions in the comments of bareos-sd storage - (# It is usually best to make sure the value on the SD's Storage resource leaves a little room (if you set it to 40 on the director, try 50 on the SD).), - but I think that this comment is to set a greater "Maximum Concurrent Jobs" for the bareos-dir director resource and not for the bareos-dir storage resource.
Now, everything is working as expected. Thank you, Valentin. Best regards. On Friday, April 24, 2020 at 6:01:03 PM UTC-3, Valentin Dzhorov wrote: > > Hey Ricardo, > > I am sorry for the delayed response. I did find a solution to my issue, or > so I think. At least I have not experienced any of the issue after changing > the Maximum Connections in the storage resource on the storage server. The > default is 42, I have increased it to 100 and no longer get that error. > Here is the documentation for that var: > https://docs.bareos.org/Configuration/StorageDaemon.html#config-Sd_Storage_MaximumConnections. > > Please let us know how it goes for you if you decide to have a go at > increasing the value of this var. > -- 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/51e694e6-fddf-4a54-aaae-9ceee80bd7f8%40googlegroups.com.
