Re: [Bacula-users] Each Client own Pool and own label

2015-08-30 Thread E.L.L. Assoua
The problem was already solved,but thanks for reacting on this thread! Best regards, Luc Assoua Radosław Korzeniewski Friday, August 28, 2015 4:06 PMvia Postbox Hello, Yo

Re: [Bacula-users] Each Client own Pool and own label

2015-08-28 Thread Radosław Korzeniewski
Hello, You can have a single pool with different volume labels based on job variable - $Client, as you have at your example. It is not required to force multiple pools. best regards 2015-07-31 13:59 GMT+02:00 Ana Emília M. Arruda : > Hello Luc, > > Yes, I think that to have all the backup jobs

Re: [Bacula-users] Each Client own Pool and own label

2015-07-31 Thread Ana Emília M . Arruda
Hello Luc, Yes, I think that to have all the backup jobs for a specific client in specific volumes, you will need to have one pool for each client. With regard to the Label Format, If you will have more than one job for the same client, I would suggest you to not have the ${JobName} present in the

[Bacula-users] Each Client own Pool and own label

2015-07-31 Thread Luc A
Dear reader, I'm configuring a Director with 50+ Clients. For each backup that will be made, i want the Volume Name to correspond the Client name: Client Name = sql01-fd Volume Name = sql01-fd Must I create a Pool for each Client and use the Label Format option in the Pool Resource of the Direct