Hi Uwe,
>
> We recently switched to running multiple catalogs and have seen
> similar strange issues, however not while restoring but more often
> when running backups.
Could you give some more info about your problems ? I want to be
prepared before migrating everything to bacula :)
> I'm won
I am also interested in how large your catalog is. We all have very
different budgets and definitions when it comes to "large" MySQL
representations, and a few of us may be able to offer some tips if that's
your bottleneck.
-Melvin
On Fri, Mar 22, 2013 at 8:25 AM, Uwe Schuerkamp
wrote:
> On Fri,
On Fri, Mar 22, 2013 at 01:37:42PM +0200, Bugbear wrote:
> Hi Dimitrij,
>
> Well, for me using only one catalog isn't solution at all. With the
> number of clients and files I'm backing up, using one database
> (catalog) causes huge performance penalties, that's why I use multiple
> catalogs.
>
Hi Dimitrij,
Well, for me using only one catalog isn't solution at all. With the
number of clients and files I'm backing up, using one database
(catalog) causes huge performance penalties, that's why I use multiple
catalogs.
Also I found some thread explaining exactly the same problem as mine:
h
Hi Bugbear,
Am 22.03.2013 09:11, schrieb Bugbear:
[...]
> I suppose this is some kind of bug, because:
> - This strange behaviour happens only to a custom set of clients (not
> all of the clients using shared catalog)
> - This only happens after I add more than 1 catalog
Second option is right.
Hello,
This is my situation:
I have Bacula-dir (Bacula 5.2.6) with about 200 clients. Also the major
part of my clients are sharing same catalog (MyCatalog), and I have
added 2 more clients with dedicated catalogs.
All of my clients are using File as a media type, and also all of them
have de