> yes, i am seeing that now. thank you for the tip. i was actually
> trying to setup volumes based on backup type (full, diff, inc) in
> combination with clients. so client1 wold have a volume client1_fulls,
> client1_diffs, and client1_incs, but i can't seem to get it working
> properly.  i was 'trying' to set it up that way so in the event that i
> run into this very same situation, then i would be able to purge
> backups of a specific type for only one client and backup type (eg.
> purge all of client1_incs) as not to affect the others.
>
> is this setup similar to what you are trying to convey?
>

I do not bother to separate the backups in this way but others have
reported success using this method. The real need is when doing a full
for a client you should always have the ability to recycle a volume
without being forced to recycle the one that contains all the fulls
for the client (or any other client). So basically you will always
have at least 1 entire full for each client at all times after the
first full is run.

John

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users