On Sat, 27 Feb 2010 14:46:40 +0100
Stan Meier <stan.me...@billigmail.org> wrote:
> Hello world,
[...]
> Furthermore, most of those servers will need a default job performed
> (/etc, /root, /opt and so on). While it's easy to reuse a "JobDefs"
> stanza to actually define all those jobs, isn't there any way to
> "group" those servers? Do we really have to define more than 120 jobs,
> one for each server?
there's been plenty of very good advice given on bacula... thanks everyone!
so, on a slightly different slant...
I don't know how your servers are used/managed... fwiw, I've been trying to
move towards segregating configuration (/etc , crontabs,etc) from software (rpm
-qa as someone suggested), from data (ie, user generated files, DBs,etc).
If you think of it this way, configuration is managed via Puppet (and you only
need to backup Puppet), software is managed via, say, Kickstart (and you only
backup your kickstart data), and then you worry about your 'non-manageable
data'.
just my $0.02 :)
B
_________________________
{Beto|Norberto|Numard} Meijome
There are no stupid questions, but there are a LOT of inquisitive idiots.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
