Backup Central

On Tue, Jan 24, 2012 at 12:00 PM, Marcello Romani
<mromani < at > ottotecnica.com> wrote:
Il 24/01/2012 17:43, Xabier Elkano ha scritto:
El 24/01/12 17:02, Marcello Romani escribió:
Il 24/01/2012 12:21, Xabier Elkano ha scritto:

[snip]

I'm just thinking out loud, but I don't see how having a catalog for
each client can help you scale, since you can't put them on different db
servers. You'd probably have a higher ROI by upgrading the DBMS hardware
and/or migrating to postgres and/or throwing some (consultancy) money at
tuning.

Just my 2 cents.
Why not? If I want I can put each catalog on different db servers, each
catalog has its own db config. But this is not the idea, I want to put
all catalogs on the same db server but trying to keep tables as small as
possible to reduce IOs on db server, because is the server bottleneck
now. I can upgrade my server hardware, putting more memory or cpu, but
my problem is on disks handling these table sizes.

May be, I've not explained it very well

Now, I can't grow my bacula installation without installing another
director to distribute the clients, because using only one catalog, its
database is too big and restores are becoming impossibles to do.

So, I am currently testing two catalogs (with two databases) in same
director and it is working fine (but, yes implies more stuff to do).
For the record:

"Currently, Bacula can only handle a single database server"

I think that this sentence is only explaining that if you have compiled
bacula to use mysql, you can only use mysql as db server (and not
postgresql), but you can use as many mysql servers as you want to
storage your catalogs.


So what is the correct meaning of that sentence ? Only tests will tell


I believe it meant that with bacula prior to 5.2.X you had to compile
in your db choice (sqlite, postgresql,mysql) and could not change that
choice at runtime. Now with 5.2 You can mix and match and have more
than 1 catalog.

John

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

On 24/01/12 17:08, John Drescher wrote:

I believe it meant that with bacula prior to 5.2.X you had to compile
in your db choice (sqlite, postgresql,mysql) and could not change that
choice at runtime. Now with 5.2 You can mix and match and have more
than 1 catalog.

1: You can only define one database server in bacula-dir

2: You can have as many catalogs on that server as you want.

3: No matter which database engine you choose, as the table sizes
increase it will perform badly unless tuned properly.

Different engines suit different loads but until the size and load
factor of bacula's requirements gets _large_ the differences are largely
academic, so people should go with what they're comfortable with.

4: Changing between mysql/postgres is irritating but as long as dumps
are done in proper compatibility mode, relatively painless

(I have around 350 million files in my databases. Tuned Postgres vs
tuned Mysql has measurable performance/memory differences. With only 20
million files onboard the differences are negligable)

There are advantages and disadvantages to a monolithic catalog. This is
a matter of personal taste.

5: Splitting up a monolithic catalog set takes a fair amount of patience.

FWIW I have multiple catalog sets:

a: Servers and support gear (daily machine backups)
b: Fileserver cluster1 backups (100Tb or so)
c: Fileserver 2 backups (~200Tb)
d: Desktop hardware

This is mainly done for political and dump/restore size reasons. There's
very little performance/memory difference between running them all
monolithically or separate.)


6: Poolsets are per-catalog. 1 pool cannot service multiple catalogs.
(the data about what's on which tape is per-catalog)

7: Bacula scales to limits which would blow most people's minds - well
beyond most COTS (commercial off the shelf) software and past every
other OSS package I'm aware of.





------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users