Hi Danie,
I'm upgrading bacula on Solaris so no RPM's.
I install the source (from the tar file) do a ./configure etc to build it.
But that's another story!
I probably can't help you much because I'm trying to be VERY careful since
I'm trying to upgrade a live network set-up.
Anyway what I am doing in *fanatically* simple steps is:
1. rename the current installation with a version number so that when I switch
to the new version of bacula I can still switch back if necessary
(but the DB changes will make that difficult).
So.... I renamed /etc/bacula to /etc/bacula_1.34.6.
2. rename the binaries in /sbin (bacula-dir, bacula-fd, bacula-sd, bconsole,
bcopy,
bextract, bls, bscan, bsmtp, btape, btraceback & dbcheck with a _1.34.6 suffix
as above.
3. Install the new version of bacula (in my case via make install)
you would I presume install from rpms.
I sincerely hope that the rpm would leave your existing catalog alone (a pretty
good assumption).
4. rename the new /etc/bacula to /etc/bacula_1.36.3 d.o. for the new binaries
in /sbin
(e.g. bacula-fd becomes bacula-fd_1.36.3)
5. Tediously making symbolic links to the current bacula in order for my
existing setup
to continue working:
ln -s /etc/bacula_1.34.6 /etc/bacula
cd /sbin
ln -s bacula-dir bacula-dir_1.34.6
...
ad nauseum.
Now, we have two parallel bacula configs - if you want to finish this bit write
a little
script to remove the existing symlinks and make new ones pointing at either
1.34.6 or 1.36.3 so that you can switch neatly & quickly.
6. I then at some point stop bacula (/etc/init.d/bacula stop) on all affected
systems.
On the server....
7. do a database dump :
<path to mysql bin>/mysqldump -u bacula -p<bacula password>
bacula>/var/bacula/working/MANUAL_CATALOG_SAVES/bacula.sql.`date`
Or something like that - examine /etc/bacula/make_catalog_backup
8. Upgrade the database schema:
src/cats/update_mysql_tables
in my build tree - dunno where you find that from your rpm install.
I guess I'm now committed (no going back) :(
V----------------Can someone confirm that I need to do this--------------V
9. reload the database:
mysql -u bacula -p<your pwd>
use bacula;
show tables; # should give a list including the new CDImages table I guess
source </var/bacula/working/MANUAL_CATALOG_SAVES/bacula.sql.[date]a>
# the sql dump produced in step 7.
^D
^----------------Can someone confirm that I need to do that--------------^
On all systems....
10. Make all new new symlinks to point everything at 1.36.3
11. say a prayer!
12. fire up bacula - /etc/init.d/bacula start
check that everything is running. particularly on the server.
13. run up bconsole & look at the catalog(!).
14. Don't blame me :) - this is a case of the blind leading the blind!
I believe that to undo the upgrade I need to:
o stop bacula
o remake my symlinks to point at 1.34.6
o DELETE the database
o recreate the database using the 1.34.6 creation script.
o reload the database dump
o restart (the old) bacula
I assume no responsibility whatsoever for anything in this (dumb) procedure,
If I've missed something please let me know.
Arno, have you got any advice here?
Just my 10cents
Andrew R Paterson
Systems Engineer
DS Ltd
-----Original Message-----
From: Danie Theron [mailto:[EMAIL PROTECTED]
Sent: 17 May 2005 10:02AM
To: Andrew Paterson
Cc: Bacula-Users (E-mail)
Subject: Re: [Bacula-users] Upgrading from 1.34.6 to 1.36.3
Andrew Paterson wrote:
>Hi,
> I am considering upgrading from 1.34.6 to 1.36.3 and am (double!)
> checking the required DB updates.
>It appears that the Database schema follows its own versioning independent of
>the bacula source code
>(seems sensible).
>I conclude that I am running a Version 7 database schema (select * from
>Version;).
>Bacula 1.36.3 requires me to upgrade to a Version 8 database schema.
>
>What I am a little uncertain about is as follows:
>
>There are two scripts for upgrading the schema from V7 to V8:
>updatedb/update_mysql_tables_7_to_8
>and
>src/cats/update_mysql_tables
>
>These scripts are similar, except that the one in src/cats has been "built" by
>configure and points to where my DB utils
>(mysql-4.0.21) reside and will therefore execute successfully - I would need
>to fix paths in the updatedb script.
>
>In addition, the src/cats script does not verify that the current DB version
>is V7 before continuing whereas the updatedb script does (i.e. the src/cats
>version just assumes this to be the case - rerunning it would I assume just
>result in a load of harmless sql errors).
>
>Most significantly, the src/cats script creates a new table (CDImages) whereas
>the updateeb script does not.
>
>I conclude that for my upgrade (1.34.6->1.36.3) (Mysql database V7->V8) I only
>need to run the src/cats/update_mysql_tables script. The script in updatedb
>being redundant in this case.
>
>Can some kind soul who has been through this upgrade already verify this for
>me?
>
>Andrew R Paterson
>Systems Engineer
>DS Ltd
>
>
>
>
>
Hi Andrew ,
I have also posted questions about upgrading to 1.36.3 , no answers yet.
Did you install bacula from the rpms (which I did) or from the .tar package?
I would really like to upgrade (having some restore issues with my
current version 1.36.2) , and I DON'T want to muck up my current
installation. Could you possibly (if you already have) explain to me how
you went about upgrading.
Thanks in advance!
D
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_idt12&alloc_id344&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
