sysbk problem with mysql databases

I suppose sysbk could be rewritten to try shutting down MySQL over and over again until it succeeds, but this certianly isn't a sysbk problem, but rather a problem with timeout on shutting down MySQL.

Try to run sysbk when there's no MySQL traffic.

Or make changes to the MySQL shutdown routine to allow more time.

Jeff
 
jlasman said:
I suppose sysbk could be rewritten to try shutting down MySQL over and over again until it succeeds, but this certianly isn't a sysbk problem, but rather a problem with timeout on shutting down MySQL.

Try to run sysbk when there's no MySQL traffic.

Or make changes to the MySQL shutdown routine to allow more time.

Jeff
Click to expand...

hm
any ideas why it needs to shut down mysql?
 
It needs to shut down MySQL so it'll get consistent databases.

I came across a response on another thread tonight that implies there might be a timeout value in sysbk.conf.

I found it; it's in:

/usr/local/sysbk/mod/mysql.bk

in line 10; change the number after sleep to the number of seconds you want to wait.

Jeff
 
jlasman said:
It needs to shut down MySQL so it'll get consistent databases.

I came across a response on another thread tonight that implies there might be a timeout value in sysbk.conf.

I found it; it's in:

/usr/local/sysbk/mod/mysql.bk

in line 10; change the number after sleep to the number of seconds you want to wait.

Jeff
Click to expand...

hm...
but it doesn't shut down exim while backuping... just before, isn't it?
 
To make sure the databases are in a consistent state (that is to make sure all pending changes have been committed and written to the hard disk).

Jeff
 
You must log in or register to reply here.
Back
Top