Dave wrote:
> Hi,
> Can you tell me more about your config? It sounds like what i'm
> trying to do. I've got multiple machines, some local, one not, that i
> want to back up to disk. I want to use the same information you did,
> but it seems as if i need a separate set of three pool definitions and
> three separate storage definitions to pull this off. I've tried
> looking at other solutions, but they haven't worked. I don't want to
> massively overbloat my configuration, but i think that's what is going
> to happen.
> Any help appreciated.
> Thanks.
> Dave.
>
> ----- Original Message ----- From: "Jeff Dickens" <[EMAIL PROTECTED]>
> To: <bacula-users@lists.sourceforge.net>
> Sent: Wednesday, June 14, 2006 8:14 AM
> Subject: Re: [Bacula-users] Idea: ClientDefs, StorageDefs, PoolDefs, etc.
>
>
>> 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.
>>>>
>>>>
Here are the some files I've created to use as defaults files for new
clients:
For the sd, I make a copy of this name <newclientname>-sd.conf, and edit
it to replace "xyzzy" with the new client name:
Device {
Name = xyzzy-filedev
Media Type = xyzzy-file
Archive Device = /bacula/xyzzy
LabelMedia = yes;
Random Access = yes;
AutomaticMount = yes;
RemovableMedia = no;
AlwaysOpen = no;
}
Then I create the new client's directory: /bacula/<newclientname>,
include the above config file in bacula-sd.conf using the "@" directive
and restart the sd.
For the directory I do the same search & replace on this file, called
simply xyzzy.conf: I actually keep the client config files in a
subdirectory of /etc/bacula called /etc/bacula/clients just to keep
things neat.
# xyzzy
Client {
Name = xyzzy-fd
Address = xyzzy
FDPort = 9102
Catalog = MyCatalog
Password = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
File Retention = 3 months
Job Retention = 6 months
AutoPrune = yes # Prune expired Jobs/Files
}
Job {
Name = xyzzy
JobDefs = XP_WS_Defs
Client = xyzzy-fd
Write Bootstrap = "/var/bacula/xyzzy.bsr"
Storage = xyzzy-filestore
Pool = xyzzy-pool-incr
Full Backup Pool = xyzzy-pool-full
Incremental Backup Pool = xyzzy-pool-incr
Differential Backup Pool = xyzzy-pool-diff
}
Storage {
Name = xyzzy-filestore
Address = otter
SDPort = 9103
Password = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
Device = xyzzy-filedev
Media Type = xyzzy-file
}
Pool {
Name = xyzzy-pool-full
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 65 days
Use Volume Once = yes
LabelFormat = "xyzzy-full-"
}
Pool {
Name = xyzzy-pool-incr
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 4 days
Use Volume Once = yes
LabelFormat = "xyzzy-incr-"
}
Pool {
Name = xyzzy-pool-diff
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 15 days
Use Volume Once = yes
LabelFormat = "xyzzy-diff-"
}
Then of course one must fill in the passwords for the sd and the
director, include the above file in bacula-dir.conf and restart the
director. Note that *I AM NEW AT THIS*. Please don't take any of this
as authoritative. I may well find numerous screw-ups in my setup before
I have a stable config.
The JobDefs "XP_WS_Defs" referenced above includes the FileSet and
schedule used by all my XP workstations.
Regarding my original point, you can see from the above that it sure
would be nice if there were a "PoolDefs". It would save about 15 lines
of config per client, which can add up fast.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
