[Bacula-users] Doc/Faq for mysql

[Jan Walzer]

Hello List.

We're using bacula quite for a while here now and are really
satisfied.

But when it came to setup this thing, we had some minor problems.
One, I could solve last week, was that often enough MySQL-connection
decided to go byebye.
It only happend, when the backup wasn't monitored every day (Mostly
over weekends).

It was due to the fact, that a standard MySQL-Install has a timeout
set to 8h. So, if you only run a backup every 24h the db will disconnect
and fail to insert into the catalog.
Also bacula doesn't give a 2nd try, but it reinstantiates the connection.

Could someone, who cares for the docs please make an entry, that you
need to set the MySQL-Variable "wait_timeout" to an apropriate value?


Bye, and thanx for the nice work, Jan.

PS: please CC me

[Kern Sibbald]

Post by Jan Walzer
Hello List.
We're using bacula quite for a while here now and are really
satisfied.
But when it came to setup this thing, we had some minor problems.
One, I could solve last week, was that often enough MySQL-connection
decided to go byebye.
It only happend, when the backup wasn't monitored every day (Mostly
over weekends).
It was due to the fact, that a standard MySQL-Install has a timeout
set to 8h. So, if you only run a backup every 24h the db will disconnect
and fail to insert into the catalog.
Also bacula doesn't give a 2nd try, but it reinstantiates the connection.
Could someone, who cares for the docs please make an entry, that you
need to set the MySQL-Variable "wait_timeout" to an apropriate value?

I don't really understand why you are having problems. Between
jobs, Bacula closes the database. When a job starts, it re-opens
it. The connection will be closed as soon as no jobs are running.
So, I don't see why a timeout would matter. In addition, I use
MySQL here (3.23.57), and when Bacula waits on me to change
the tape, it is often far more than 8 hours, yet, I never
experience any database disconnects.

If Bacula has a database that is open and it gets
a serious error, Bacula will cancel the
current job.

When Bacula is opening a connection to the database
at the beginning of a job, if it fails, Bacula will
retry a second time. Thereafter it expects the database
to always be connected.

Are you interfacing to MySQL via TCP/IP or are
you using the default Unix socket?

I'll be happy to experiment with setting a different
wait time, but you'll need to be very explicit in
how to do it, because my MySQL documentation mentions
nothing about a wait_timeout variable (maybe the
the feature was added after the book was printed).

Best regards,

Kern

Post by Jan Walzer
Bye, and thanx for the nice work, Jan.
PS: please CC me
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bacula-users mailing list
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Volker Sauer]

Hi,

the MySQL-Variable "wait_timeout" can be set by adding

set-variable = wait_timeout= <n>

(where n ist the time in seconds) to my.cnf (e.g. /etc/my.cnf).
But I don't know if it is necessary.

Regards
Volker

Post by Kern Sibbald

Post by Jan Walzer
Hello List.
We're using bacula quite for a while here now and are really
satisfied.
But when it came to setup this thing, we had some minor problems.
One, I could solve last week, was that often enough MySQL-connection
decided to go byebye.
It only happend, when the backup wasn't monitored every day (Mostly
over weekends).
It was due to the fact, that a standard MySQL-Install has a timeout
set to 8h. So, if you only run a backup every 24h the db will disconnect
and fail to insert into the catalog.
Also bacula doesn't give a 2nd try, but it reinstantiates the connection.
Could someone, who cares for the docs please make an entry, that you
need to set the MySQL-Variable "wait_timeout" to an apropriate value?

I don't really understand why you are having problems. Between
jobs, Bacula closes the database. When a job starts, it re-opens
it. The connection will be closed as soon as no jobs are running.
So, I don't see why a timeout would matter. In addition, I use
MySQL here (3.23.57), and when Bacula waits on me to change
the tape, it is often far more than 8 hours, yet, I never
experience any database disconnects.
If Bacula has a database that is open and it gets
a serious error, Bacula will cancel the
current job.
When Bacula is opening a connection to the database
at the beginning of a job, if it fails, Bacula will
retry a second time. Thereafter it expects the database
to always be connected.
Are you interfacing to MySQL via TCP/IP or are
you using the default Unix socket?
I'll be happy to experiment with setting a different
wait time, but you'll need to be very explicit in
how to do it, because my MySQL documentation mentions
nothing about a wait_timeout variable (maybe the
the feature was added after the book was printed).
Best regards,
Kern

Post by Jan Walzer
Bye, and thanx for the nice work, Jan.
PS: please CC me
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bacula-users mailing list
https://lists.sourceforge.net/lists/listinfo/bacula-user

s