Hello all,

I've been having some trouble lately with the newer versions of Amanda - 
we had been running it for about five years and on the last upgrade we've 
found that it's not quite as robust as it used to be (at least in our 
environment).  When we originally settled on Amanda I did look at Bacula 
but the project was too young for us to consider.  It appears now that it 
is much more mature and going in a good direction, so we'll be giving it a 
shot.

I've got a somewhat short list of questions...

-I'm still digging through the docs, but it appears that scheduling is one 
of the main differences between amanda and bacula.  Amanda tries to spread 
full dumps out over time, but it appears bacula leaves this up to the 
operator.  Is that correct?

-Are there any issues running the current stable release on FreeBSD 4.11? 
We do need to upgrade to 6.2 and are doing it slowly, but for the time 
being we're stuck running 4.11 on the majority of our hosts.

-Amanda calls gtar or dump on the clients.  Does bacula use an external 
program like this or does the client daemon directly access files?  I'm 
also unclear on the "differential" backup scheme - in amanda I only have 
full or incremental...

-For now I'll be using the SQLite backend.  Is it simple to move to 
PostgreSQL at a later time?

Lastly, anyone here who has already made the switch, I'd love to hear 
about how that went and what prompted you to switch.

You'll probably here more from me over the next week as I try to get this 
up and running and taking over our archival backups...

Thanks,

Charles

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to