On 4/29/07, Jakob Praher <[EMAIL PROTECTED]> wrote:
> hi all,
>
> first of all this is my 3rd day with bacula. I think it is a nice backup
> software, though some stuff is really hard to get right at first. (I
> used to do ssh + rsync backups).
>
> i have different nodes:
> node1,
> node2,
> ..
>
> i am using bacula 1.38 (binary dist)
>
> All of those should get backed to a file
> - daily
> - weekly
> - monthly
>
> so actually i have a "logical" job, which says backup all the nodes. (I
> use jobdefs for the defaults, and for every client a single job). the
> scheduler overwrites the pool then.
>
> in order to change as little as possible when i add another machine, i
> simply want everything to go into 3 pools (daily, weekly, monthly). I
> have auto labeling and recyling enabled.
>
> using "use volume once" does not work since every client is done by a
> single job (am i right?). so i use the following construct
>
> Maximum Use Duration = 23 h.
>
This is fine. However are you saying that you are using 1 single job
for everything? I would say it is much better to have 1 job per client
and that way the different backup levels make sense (Full,
Incremental, Differential). As if you do a Full backup with the first
client how can you do an incremental with a second client since the
incremental will be based on the last full job ran?

John

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to