Hello,
On 3/21/2006 6:13 PM, Bill Moran wrote:
Basically, I'm putting together a backup solution with Bacula, and I
want to get feedback on my organization to see if anyone can suggest
improvements. We aren't having any real _problems_, I'm just curious
as to if I can do it better.
Without much thought: Perhaps, at least you could do things different ;-)
Since we have a number of servers with duplicate setups, I organized
the fileSets by task. For example, I have a standard fileset, and
then specialized filesets for different types of systems (Note that
this is somewhat simplified):
Ok, simplification understood...
FileSet {
Name = "CFBSDStandard"
Include {
File = /etc
File = /usr/local/etc
File = /var
}
}
Then, each service type has a specific fileset. For example:
FileSet {
Name = "CFweb"
Include {
File = /usr/local/www
}
}
FileSet {
Name = "CFPostgreSQL"
Include {
File = /usr/local/pgsql
}
}
So, for an arbitrary server, there will be a Job (again, simplified):
Job {
Name = "Server1-std"
FileSet = "CFBSDStandard"
}
If Server1 has PostgreSQL running production, there will also be a job:
Job {
Name = "Server1-DB"
FileSet = "CFPostgreSQL"
}
The theory is that this will allow us to easily create a service
abstraction for how things are backed up. This organization results
in every server having at least 2 jobs associated with it. Busy
servers will have many.
Right... this can become a problem in the way Bacula presents the
restore possibilities, and it can make restores slower than necessary...
The only whine I have is that it would be nice if Server1-std and
Server1-DB could share the name. For example:
Job {
Name = "Server1"
FileSet = "CFBSDStandard"
FileSet = "CFPostgreSQL"
}
As the more seasoned Bacula users already know, this doesn't work.
Right, and this is something I'd like to see... or, even better, the
possibility to inherit filesets from filesets. Like
FileSet {
Name = CFWeb
Use = CFLinStandard # see, I'm a linux person
# (nothing against BSD, though ;-)
Include {
File = /usr/local/www
File = /var/log/apache2
}
}
which should add the fileset together.
Nor does it work to define two jobs with the same name.
Overall, this is a minor inconvenience, but I have difficulty believing
that I'm the first person to try this. Is there a better way to
organize things to accomplish what we want?
Yes, perhaps, at least a different one.
Use includes, either the @-variant or the <-variant to have a limited
list of file sets prepared in external files which you could use like this:
FileSet {
Name = CFWeb
Include {
File = "</etc/bacula/CFBSDBase.set"
File = "</etc/bacula/CFBSDWeb.set"
File = "</etc/bacula/whatever.set"
}
}
That's what I would do if I wanted to avoid having many Jobs an Client /
FileSet combinations.
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
