John Drescher wrote:
> On Thu, Jan 29, 2009 at 5:19 AM, ToMasz <nunatars...@gmail.com> wrote:
>> I've been using bacula 1.38.11 for some time and recently upgraded
>> successfully one of my file daemons to ver. 2.4.4.
>> Now I'm thinking about complete upgrade on all machines including
>> director but am unsure about possible pitfalls.
>> Will my config files still work? Or maybe newer versions use other
>> database solutions (I'm using internal bacula base)?
>>
>
> Your config files will work on every machine except possibly the
> director. Its been a very long time (2 years?) since I have used 1.38
> so I am not very sure of the changes needed.
>
> John
>
I don't remember exactly which version of sqlite it used.
(Perharps it depend of the lib's version present on the os : you didn't specify
it)
For sure I would made a copy & a dump (bacula-catalog is your friends) in case
of.
After I would make a complete backup of /etc/bacula config's files.
And I would remove all 1.38 related files. This depend of how your version was
installed
rpm, sources, deb etc...
And make the new installation.
After in your config file double/triple check every path (there's some change
between /etc/bacula and /usr/lib/bacula)
for the script. Adjust what is needed, and for sure, re-read the manual for the
new version.
test configs for each daemon with the -t
make tests.
--
Bruno Friedmann
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
