Yes, I know that the Bacula Release Notes say "As always, both the Director
and Storage daemon must be upgraded at the same time."

Is this because of some shared library versions or something else "single
host environment"- related?

I'm migrating my old CentOS 5.x-32 system with Bacula 5.0.3, to CentOS
6.2-64, with Bacula 5.2.6.

I'm very tempted to have an intermediate step (for just a few days) with
the old storage (running in the old hw) and the new director (in the new
hw).

So both the director and storage would be of 5-generation with different
minor numbers, and everything running in any single host, would be of
exactly the same version.  Any chance this combination might work?

Of course, as long as I had that cocktail in use, I wouldn't touch the conf
files for no other reason but to edit machine names where necessary. So no
attempt to use any new features... if the communication protocols between
the daemons haven't changed, I guess there shouln't be anything
wrong -unless the daemons explicitly check the version info.


Regards,
Timo



------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users