Re: [Bacula-users] 2.0 server with 2.2 clients: stepwise upgrade possible?

[John D. <dre...@gm...>]

> Hi.  I've got 2.2.6 built on a system that will be my new director &
> main sd.
>
> I've run backups with the 2.0 server and sd and a 2.2 (windows) client,
> and it seems to work.  I haven't tried a restore yet, but I will.
>
> My questions are these:
> - Is this intended to work?
> - Is it reasonable to assume I can upgrade all my clients first and then
> move them to the new server?
>
This has not been tested as much as having the server at a higher
version than the clients. In the 4+ years I have used bacula I have
mostly had the server versions ahead of the clients.

>
> I'd move them one at a time but I only have one tape drive.  It'll get
> temporarily moved to the new server for testing and then move back until
> the cutover date.
>

I have bacula 2.36 SVN code as my bacula servers (director and
multiple bacula-sds) and a mix of 1.38 to 2.26 as my clients. The
reason for using 2.36 was there is a fix in there for a problem I was
having with a 2 drive autochanger. I have been using this for over a
month  now  and I have not seen any trace of the problem I was having.
I generally do not recommend moving to a svn version unless you have a
problem that the svn fix. However it is generally safe to upgrade to a
released version. And in your case I would upgrade to 2.2.6 as soon as
I can if you do any concurrent restores because there is a bug with
older versions of bacula where some of your files may not be restored
(although they are on the tape) when concurrent operations are in
progress. This bug does not happen very frequently but it can happen.

John