Graham,
I would be most interested to know if you have a "non-personal" reason
for
moving from Mysql to Postgres - do you know something I don't(?) :) probably :)
but you know what I mean
I guess its a matter of politics & opinions, but I always thought Mysql was a
generation ahead of postgres.
Please enlighten me.
Andrew R Paterson
Systems Engineer
DS Ltd
-----Original Message-----
From: Graham David Purcocks M.A.(Oxon.) [mailto:[EMAIL PROTECTED]
Sent: 13 May 2005 3:43PM
Cc: bacula-users; Andrew Paterson
Subject: Re: [Bacula-users] Upgrading live system from Bacula 1.34.6
tocurrent stable release
Just to be doubly awkward. I want to switch from MySql to Postgres, so
at which database version number should I do the switch? Actually
looking at the scripts I guess the answer to the former is Version 7.
Is there a Mysql->Postgres conversion script anywhere? Is is possible?
Thanks
Graham
On Fri, 2005-05-13 at 15:24, Kern Sibbald wrote:
> See <bacula-source>/updatedb
>
> On Friday 13 May 2005 11:01, Graham David Purcocks M.A.(Oxon.) wrote:
> > Well I'm on 1.32d so I'm further back and thinking the same thing.
> >
> > The basic question, which I haven't seen a response for, is are there a
> > set of database update scripts included with each release. So you run
> > each one to get from your version to the latest. Or do you have to dig
> > out each release where an update was made?
> >
> > Thanks
> > Graham
> >
> > On Wed, 2005-05-11 at 12:47, Andrew Paterson wrote:
> > > Hi,
> > > I have been running Bacula 1.34.6 on WIN-XP, Solaris 2.6/7/8/9/10
> > > (client only on XP & 2.6) for approximately a year now. What can I say
> > > ... I'm very fond of it :)
> > >
> > > However, I have a feeling I should upgrade to a newer version now - why?
> > > - (ummm! just a feeling in the ol' bones y'know!) primarily to catch up
> > > with bug-fixes/improvements.
> > >
> > > I currently use mysql V4.0.21 for the catalogue.
> > >
> > > What I am concerned about is that if I upgrade, am I going to find my
> > > existing catalogue incompatible with the new version of bacula (i.e. the
> > > DB schema may have changed).
> > >
> > > Therefore, is there an approved procedure for migrating my catalogue to
> > > the latest (stable) version of bacula?
> > >
> > > Are there any compatibility problems with the data held on my current
> > > backup media and the new version of bacula?
> > >
> > > In addition, does anyone have any idea if it's worth upgrading to a newer
> > > version of Mysql (although I don't anticipate that as much of a problem).
> > >
> > > Finally is the latest stable version compatible with webacula (probably a
> > > naff question - but I'd like to make sure).
> > >
> > > I am sure others have gone through the upgrade procedure - so please tell
> > > me how you fared.
> > >
> > > TIA
> > >
> > >
> > > Andrew R Paterson
> > > Systems Engineer
> > > DS Ltd
> > >
> > >
> > > -------------------------------------------------------
> > > 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_ids93&alloc_id281&op=click
> > > _______________________________________________
> > > Bacula-users mailing list
> > > Bacula-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/bacula-users
--
-------------------------------------------------------
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_ids93&alloc_id281&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
