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

[Michael Schwager]

Innobackupex is excellent- we use it- but it's not as trivial as a tar copy
of the mysql directory (shut the database down first). For example, you may
end up using the database username/password on the command line in your
scripts (which you should probably avoid). Also, according to the man page,
"After  creating  a  backup,  the  data  is  not  ready to be restored."
...Ehm, in a word: YIKES! RTFM for sure! At least they tell you what you
need to do, and it's not hard, but if you miss it...

Anyway, here's a bash example of how we back up our production database.
Details such as defining LOG_DIR and BACKUP_DIR left as an exercise for the
reader:

cleanup () {
status=$?
rm -f $TMPFILE
exit $status
}

trap cleanup EXIT SIGQUIT SIGHUP SIGINT SIGTERM

TMPFILE=$(mktemp /tmp/dbbkpX)

suffix=$(date +%w)
cp /etc/my.cnf $TMPFILE
cat /var/lib/mysql/defaults.cnf >> $TMPFILE

mkdir -p $LOG_DIR $BACKUP_DIR

innobackupex --defaults-file $TMPFILE $FULL_BACKUP_DIR > $LOG_DIR/$suffix
2>&1
innobackupex --defaults-file $TMPFILE --apply-log $FULL_BACKUP_DIR >>
$LOG_DIR/$suffix 2>&1




*- Mike Schwager*

*  Linux Network Engineer, Mocho Trading LLC*
*  312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax*


On Mon, Sep 28, 2015 at 2:49 AM, Uwe Schuerkamp 
wrote:

> On Fri, Sep 25, 2015 at 09:01:29AM -0700, Stephen Thompson wrote:
> >
> >
> >
> > I run daily backups of my database and had finished my monthly full run
> > for September, so I was technically covered.  However I was not looking
> > forward to restoring a 900+Gb mysql database from a text dump which on
> > my system would take days, if not an entire week.  The last time I had
> > to restore database from backup it was 4 or so years ago and my database
> > was only 300-400Gb back then.
> >
> > Stephen
> >
> >
>
> One word: innobackupex. You'll be up running in a few minutes again as
> opposed to a week when using a text file created by mysqldump (which,
> much like MyISAM tables, should be taken round the back and taken out
> of its misery once and for all ;))
>
> All the best,
>
> Uwe
>
>
>
>
>
>
>
>
>
> --
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>

-- 
This message is for the named person(s) use only. It may contain 
confidential proprietary or legally privileged information. No 
confidentiality or privilege is waived or lost by any mistransmission. If 
you receive this message in error, please immediately delete it and all 
copies of it from your system, destroy any hard copies of it and notify the 
sender. You must not, directly or indirectly use, disclose, distribute, 
print, or copy any part of this message if you are not the intended 
recipient. Mocho Trading LLC reserves the right to monitor all e-mail 
communications through its networks. Any views expressed in this message 
are those of the individual sender, except where the message states 
otherwise and the sender is authorized to state them to be the views of any 
such entity.
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[Michael Schwager]

On Fri, Sep 25, 2015 at 10:50 AM, Raymond Burns Jr. 
wrote:

> I didn't run a backup of the database because of all the great responses
> from people.


​Oh dear Lord man! If running mysql, shut the database down and tar up the​
/var/lib/mysql directory (or whatever you have in /etc/my.cnf). It's so
trivial, yet such a tremendous heart attack prevention technique!


*- Mike Schwager*

*  Linux Network Engineer, Mocho Trading LLC*
*  312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax*

-- 
This message is for the named person(s) use only. It may contain 
confidential proprietary or legally privileged information. No 
confidentiality or privilege is waived or lost by any mistransmission. If 
you receive this message in error, please immediately delete it and all 
copies of it from your system, destroy any hard copies of it and notify the 
sender. You must not, directly or indirectly use, disclose, distribute, 
print, or copy any part of this message if you are not the intended 
recipient. Mocho Trading LLC reserves the right to monitor all e-mail 
communications through its networks. Any views expressed in this message 
are those of the individual sender, except where the message states 
otherwise and the sender is authorized to state them to be the views of any 
such entity.
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[Uwe Schuerkamp]

On Fri, Sep 25, 2015 at 09:01:29AM -0700, Stephen Thompson wrote:
> 
> 
> 
> I run daily backups of my database and had finished my monthly full run 
> for September, so I was technically covered.  However I was not looking 
> forward to restoring a 900+Gb mysql database from a text dump which on 
> my system would take days, if not an entire week.  The last time I had 
> to restore database from backup it was 4 or so years ago and my database 
> was only 300-400Gb back then.
> 
> Stephen
> 
> 

One word: innobackupex. You'll be up running in a few minutes again as
opposed to a week when using a text file created by mysqldump (which,
much like MyISAM tables, should be taken round the back and taken out
of its misery once and for all ;))

All the best,

Uwe








--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[Kern Sibbald]

Good luck.

Kern

On 15-09-25 12:02 PM, Stephen Thompson wrote:
>
> So far so good.  Minor snafu on my part when updating database, but I'm
> running 7.2 now.  Looking good so far.  Will find out more when hundreds
> of jobs run tonight.
>
> Stephen
>
>
>
> On 09/24/2015 08: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
>>


--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[Stephen Thompson]

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
step...@seismo.berkeley.edu215 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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[Stephen Thompson]

I run daily backups of my database and had finished my monthly full run 
for September, so I was technically covered.  However I was not looking 
forward to restoring a 900+Gb mysql database from a text dump which on 
my system would take days, if not an entire week.  The last time I had 
to restore database from backup it was 4 or so years ago and my database 
was only 300-400Gb back then.

Stephen



On 09/25/2015 08:50 AM, Raymond Burns Jr. wrote:
> 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
> > 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 

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

[Stephen Thompson]

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
step...@seismo.berkeley.edu215 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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[Raymond Burns Jr.]

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 <
step...@seismo.berkeley.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
> step...@seismo.berkeley.edu215 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@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net

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

[Stephen Thompson]

So far so good.  Minor snafu on my part when updating database, but I'm 
running 7.2 now.  Looking good so far.  Will find out more when hundreds 
of jobs run tonight.

Stephen



On 09/24/2015 08: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
step...@seismo.berkeley.edu215 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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[Stephen Thompson]

Thanks, I'll be upgrading soon.

What known bugs are in the update_bacula_tables scripts?

thanks,
Stephen


On 9/24/15 10:51 PM, Uwe Schuerkamp wrote:
> On Thu, Sep 24, 2015 at 08:40:05AM -0700, 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?
>>
>
> I upgraded five bacula instances of varying size over the last four
> weeks or so, starting with the smallest (all were on 7.0.5 compiled
> from source on CentOS), no issues so far apart from the little bugs in
> the update_bacula_tables script.
>
> Cheers, Uwe
>

-- 
Stephen Thompson   Berkeley Seismological Laboratory
step...@seismo.berkeley.edu215 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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[Uwe Schuerkamp]

On Fri, Sep 25, 2015 at 06:43:57AM -0700, Stephen Thompson wrote:
> 
> Thanks, I'll be upgrading soon.
> 
> What known bugs are in the update_bacula_tables scripts?
> 
> thanks,
> Stephen
> 

Hi Stephen,

not real "bugs", but rather some weird messages about the EOT tag not
being found and other stuff when you run them, the scripts seem to
have worked fine on my catalogs though.

All the best,

Uwe


--
arvato Systems S4M GmbH | Sitz Köln | Amtsgericht Köln HRB 27038








--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[Stephen Thompson]

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
step...@seismo.berkeley.edu215 McCone Hall # 4760
Office: 510.664.9177   University of California, Berkeley
Remote: 510.214.6506 (Tue,Wed) Berkeley, CA 94720-4760

--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[Kern Sibbald]

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


--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[Uwe Schuerkamp]

On Thu, Sep 24, 2015 at 08:40:05AM -0700, 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?
> 

I upgraded five bacula instances of varying size over the last four
weeks or so, starting with the smallest (all were on 7.0.5 compiled
from source on CentOS), no issues so far apart from the little bugs in
the update_bacula_tables script.

Cheers, Uwe

-- 
arvato Systems S4M GmbH | Sitz Köln | Amtsgericht Köln HRB 27038








--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users