2009/4/23 Attila Fülöp <lichtscheu AT gesindel DOT org>:
> Ever thought of using multiple catalogs, eg one catalog for each
> client or client group? This should mitigate most of the catalog issues
> you have.

Yes, we've thought about it. That has it's own set of problem though.
One is obviously the trouble of keeping multiple catalog db's around
and assigning clients to them, this isn't a big problem but it does
add complexity.
The other is the extra bconsole overhead of having to know what
catalog a client is in to perform certain operations. 'query' is a
prime example, or restore, a catalog must be selected before any
query/restore commands can be performed. This means you need to check
what catalog a client is assigned to for every bconsole command that
requires use of the catalog, which feels like it would get old fairly
quickly.

If anyone has any suggestions for using multiple catalogs in as
transparent a manner as possible I'd be very happy to hear them.

-- 
Simon Ekstrand

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users