Hi Kern, Kern Sibbald wrote : > It seems to me that there are a few issues here: > > 1. If you shutdown or upgrade a database while Bacula is running a Job, then > Bacula will fail. The solution is: don't do that. Bacula has no explicit > code to reconnect to a database after the database is successfully opened, > and we don't plan to add any such code as it would render the data less > secure. >
No shutdown or upgrade when the problem occurs. > 2. It is possible that the network (if that is what you setup) connection > between Bacula and the database server could be broken. In that case, since > it is the database's client libraries that established the connection, it is > their responsibility to manage the connection and reconnect if it is > possible. If the database API supplies a call or flag that requests the > client libraries to reconnect, we will (and in the case of MySQL where this > exists do) use the API/flag. However, this still leaves it to the client > libraries to manage the interface. > The Mysql Server and Bacula Director are on the same server. Catalogs use nearly 48 GB (over 100 GB dedicated now) Backups use nearly 6 067 GB. > 3. With most databases, you can set them up to use sockets rather than TCP/IP > providing the database and the Director run on the same machine. This might > reduce any disconnects that would occur via TCP/IP. > We use tcp/ip, we can try unix socket, if it helps. > 4. Bacula has a connection to the database open only when it is actually > running a job, so if this error occurs, and the client library cannot > reconnect by itself, Bacula will take the conservative point of view and fail > the job. > Ok > 5. There was one case of MySQL recently releasing a new version where they > changed the API/flag that requests reconnect. This unfortunately resulted in > a few dropped connections until we modified the Bacula code to correspond to > the new MySQL coding. This should no longer be an issue if you are running > any version of 1.38.11. > The only (debian) version with this problem is bacula-xxx-1.38.11-5. bacula-xxx-1.38.11-1 and bacula-xxx-1.38.11-7 don't have this problem. > 6. Some of the test results reported indicate that there may be a bug with > specific versions of MySQL. > Works correctly during 2 weeks : - bacula 1.38.11-1 and mysql 5.0.22-4 - bacula 1.38.11-1 and mysql 5.0.24a - bacula 1.38.11-7 and mysql 5.0.27 Fails after few days : - bacula 1.38.11-5 and mysql 5.0.22-4 - bacula 1.38.11-5 and mysql 5.0.24a > Providing there are no Debian specific modifications to the cats directory > source code, I recommend closing this bug report as there is no planned > change to Bacula and no known bug in version 1.38.11 or greater. > I agree to close this bug report, current version of Bacula doesn't seem to have anymore the described problem. I do have "wishes", but this bug report is not the correct place for them ;-) Bacula is a really good product, you've done a great job ! Thanks. -- Emmanuel DECAEN XSALTO - www.xsalto.com - [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
