Bacula-users

Re: [Bacula-users] is 7.2 ready for prime time?

2015-09-25 11:53:01
Subject: Re: [Bacula-users] is 7.2 ready for prime time?
From: "Raymond Burns Jr." <rburnsj AT gmail DOT com>
To: Stephen Thompson <stephen AT seismo.berkeley DOT edu>, bacula-users AT lists.sourceforge DOT net
Date: Fri, 25 Sep 2015 15:50:04 +0000
Did you run a backup of the database?
If not, I bet you were terrified with all the errors :)
Same thing happened to me going to 7.0.5, and it sent me for a frenzy. I didn't run a backup of the database because of all the great responses from people.

When is the 7.2.0 rpm expected? Not running update until the rpm is there.

On Fri, Sep 25, 2015 at 10:43 AM Stephen Thompson <stephen AT seismo.berkeley DOT edu> wrote:


Spoke too soon, I see what's going on, I was running update script from
new location (7.2.0) and it's referencing old location (7.0.5) and
running the wrong mysql script.



On 09/25/2015 08:34 AM, Stephen Thompson wrote:
>
> Help?
>
> Well, the compile and install went fine, but the update tables script is
> having issue.
>
> I was running 7.0.5 before.  Not sure what database version, but likely
> whatever was appropriate to 7.0.5.
>
>
> First time I ran script as su'ed user which caused this...
> ----------
> Altering mysql tables
>
> This script will update a Bacula MySQL database from version 12 to 14
>    which is needed to convert from Bacula Community version 5.0.x to 5.2.x
>
> ERROR 1045 (28000): Access denied for user 'stephen'@'localhost' (using
> password: YES)
> /home/bacula/conf/update_mysql_tables: line 31: [: !=: unary operator
> expected
> ERROR 1045 (28000): Access denied for user 'stephen'@'localhost' (using
> password: YES)
> Update of Bacula MySQL tables failed.
> ----------
>
> I assumed because access denied, that the script failed entirely, but
> then running it again as proper user...
>
> Second time...
> -----------
> ./update_bacula_tables
> Altering mysql tables
>
> This script will update a Bacula MySQL database from version 12 to 14
>    which is needed to convert from Bacula Community version 5.0.x to 5.2.x
>
> /home/bacula/conf/update_mysql_tables: line 31: [: too many arguments
> ERROR 1050 (42S01) at line 1: Table 'RestoreObject' already exists
> ERROR 1061 (42000) at line 17: Duplicate key name 'jobhisto_jobid_idx'
> ERROR 1060 (42S21) at line 19: Duplicate column name 'DeltaSeq'
> Update of Bacula MySQL tables succeeded.
> ----------
>
> Seems like it either partially ran before or I had changes already
> present from 7.0.5 update.
>
> However, my Director will not start due to database version number not
> being 15, and if I run the script any more times...
> ----------
> Altering mysql tables
>
> This script will update a Bacula MySQL database from version 12 to 14
>    which is needed to convert from Bacula Community version 5.0.x to 5.2.x
>
>
> The existing database is version 14 !!
> This script can only update an existing version 12 database to version 14.
> Error. Cannot upgrade this database.
> ----------
>
>
> If it updatad the database to 14, why is it not able to update to 15 if
> that's what the Director requires?
>
>
> thanks!
> Stephen
>
>
>
>
>
> On 09/24/2015 11:21 AM, Kern Sibbald wrote:
>> Hello,
>>
>> We put a caution message in every release, particularly for new features
>> which are generally tested but not always tested in production. Normally
>> most of the issues turn up for non-Linux distributions where we either
>> have not tested or have tested less than Linux.
>>
>> Version 7.2.0 is as stable or more so than any prior major release. That
>> said, there are always a few minor problems for each release and this
>> one is no different.  All the important problems (build issues on
>> Solaris and FreeBSD) have been corrected in the public git repository.
>>
>> Best regards,
>> Kern
>>
>> On 15-09-24 11:40 AM, Stephen Thompson wrote:
>>> All,
>>>
>>> I typically patch bacula pretty frequently, but I saw the somewhat
>>> unusual notice on the latest release notes that warns it may not be
>>> ready for use in production.  How stable is it?  I don't really have the
>>> resources to test this out, but rather would have to go straight to
>>> production with it.  I could always roll back, but that might entail the
>>> recovery from dump of a 900GB database.  Opinions?
>>>
>>> thanks,
>>> Stephen
>

--
Stephen Thompson               Berkeley Seismological Laboratory
stephen AT seismo.berkeley DOT edu    215 McCone Hall # 4760
Office: 510.664.9177           University of California, Berkeley
Remote: 510.214.6506 (Tue,Wed) Berkeley, CA 94720-4760

------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users