Steen wrote: > On Tuesday 13 June 2006 17:22, Jeff Dickens wrote: > >> It would be nice if there were ClientDefs, StorageDefs, PoolDefs, >> analagous to the JobDefs which creates sets of defaults for Jobs, >> >> I'm setting up Bacula to do disk-based backups for 20-30 Windows >> Clients, and this requires adding something on the order of 100 lines to >> bacula-dir.conf for each client, with Client, Job, Storage and three >> Pool definitions (full, diff, incr). Some clients will have custom >> filesets. Also, a Device definition has to be added to bacula-sd.conf >> for each client. >> > I don't understand why you think so? > Do you need to have separate volumes for each client? > Normally on network-based backup you have rather few types of client, grouped > on the basis of the retention times for the data that the clients hold, and > all clients in one group backup to the same pool, same device and same > storage > I'm using the information in the "Basic Volume Management" chapter of the manual as my guide. Since I do need to do concurrent disk jobs, and since I want to keep one client per volume, I end up with a device per client in bacula-sd.conf, and storage, job and three pool resources per client in bacula-dir.conf. It all seems to be working great so far, it's just that the config could be a little more concise.
>> I'm able to use the "@" directive to include a per-client file in >> bacula-dir.conf. To add a client I can just take a copy of this file >> and do a global search & replace. But if there were "ClientDefs" etc al >> that would be a neater solution. >> >> >> _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
