Sorry, I thought one thing and wrote another. It's not
InnoDB - it's MyISAM. It's the adequate storage engine
for Bacula. Regards,
Georger
--- Georger Araujo <[EMAIL PROTECTED]> escreveu:
> Russel,
> Supporting proprietary DBs would be nice, but you're
> given THREE free choices for storing your catalog -
> SQLite, Postgres, and MySQL - and two are mature,
> capable DBs. I personally use MySQL and it works
> very
> well. I don't speak on Kern's behalf, but it would
> take more work (and testing and documentation and
> upgrade migration scripts... it goes on) to support
> relatively few users.
> How big is your catalog? Take in consideration
> Bacula's typical workload on the DB: lots of
> inserts,
> no concurrency, no transactions. MySQL w/ InnoDB
> does
> the job nicely, and you can run it on the same
> server
> as Bacula.
> Of course, you can fetch the sources, implement your
> desired DB back end, and then submit patches. But if
> your catalog size doesn't justify the extra work, go
> for MySQL w/ InnoDB. Regards,
>
> Georger
_______________________________________________________
Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular.
Registre seu aparelho agora!
http://br.mobile.yahoo.com/mailalertas/
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
