2009/4/13 Jeff Dickens <j...@m2.seamanpaper.com>: > >From the 2.4.0 release notes: > (http://sourceforge.net/project/shownotes.php?release_id=604636&group_id=50727) > > This Director and Storage daemon must be upgraded at the same time, > but they should be compatible with all 2.0.x File daemons, unless you > use some of the new features that affect the FD. In other words, you should > not have to upgrade all your File daemons when you upgrade. There is > no database upgrade needed from version 2.0.x to 2.2.0 nor from version > 2.2.x to version 2.4.0 > > > So, I would take this, in conjunction with this from the 3.0 release notes: > > This Director and Storage daemon must be upgraded at the same time, > but they should be compatible with all 2.4.x File daemons, unless you > use some of the new features that affect the FD. In other words, you should > not have to upgrade all your File daemons when you upgrade. However, any > release of version 2.5.40 or greater requires a database upgrade. > > to mean that my 2.2.8 Windows FDs will work with 3.0, and that there is only > one database upgrade involved. > Older clients should be fine. This is by design. > > Is anyone else in the same boat as me? > Not me. I run bacula-2.4.4 servers at work and I have been doing this for several months. At home I upgraded from 2.5.X beta to 3.0. I believe I did run a database update script but I am not 100% sure.
John ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
