On 9/14/22 05:12, Guilherme Santos wrote:
Hey guys, could anyone give me a hand?

This is my scenario... I have a client that, some times, loses the connectivity 
with the storage1 but it has with storage2.
Could I let configured storage2 as a "backup" using only one job?

Thanks!

Hello Guilherme,

There is a new feature called "Storage Groups"

In your Job, or Pool you can set more than one Storage:

Storage = Storage1, Storage2, [...]


Then set the policy for how Bacula will choose the Storage:

StorageGroupPolicy = LeastUsed


Currently supported policies are:

ListedOrder - This is the default policy, which uses first available storage 
from
the list provided

LeastUsed - This policy scans all storage daemons from the list and chooses the
one with the least number of jobs being currently run


Keep in mind that if connectivity to a Storage is broken during a Job, the job 
will still just fail. This new Storage Group
feature is only for ch
oosing the Storage to use at Job start.

Regardless of Policy chosen, if a Storage cannot be connected to, another will 
be chosen until all options are exhausted.


Hope this helps,
Bill

--
Bill Arlofski
w...@protonmail.com

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to