* Shared objects
* Virtual backups
* Duplicate Job Control
* TLS Authentication
* Exclude Dir Containing = <filename-string>
* Plugins including Exchange 2003/2007 Plugin
* libdbi backend abstraction
* Bat enhancements
Upgrading from 2.4.4 to 3.0.2 requires updating the database using
/usr/local/libexec/bacula/update_bacula_database. Database upgrades
from older databases can be done with other scripts in
/usr/local/libexec/bacula/updatedb. You can determine your database
version in mysql and postgresql with 'select * from version'.
As sthen@ reminded me and the documentation points out, when upgrading
between major versions (2.x.x -> 3.x.x), you should upgrade all of your
components at the same time due to protocol changes.
a *lot* of help from and ok sthen@
Bacula changelog:
http://bacula.svn.sourceforge.net/viewvc/bacula/branches/Branch-2.2/bacula/ChangeLog?revision=6309&view=markup
Major port change in this version:
-main subpackage is now bacula-client
-server subpackage remains bacula-server
-bat subpackage is new bacula admin tool
-client subpackage goes away.
If the old -main subpackage was installed, the upgrade path is to
install both bacula-client and bacula-server.
Lots of input and assistance from sthen and okan.
ok okan; "if it works for you, go for it" sthen
