From: Felix S. <fel...@os...> - 2012-11-05 14:20:23
|
Am 05.11.2012 11:12, schrieb Marco van Wieringen: > Looks like its busy updating the sqlite database with backup info. > You probably have configured the system with attribute spooling which > means that after the backup is done the director needs to update the > database with all the file data to be able to restore your backup. Btw: What does 'Spool Attributes = yes/no' do? I wasn't able to find much info in the docs on that. > First of all sqlite is just a proof of concept and should not be > used for production use a proper database like mysql or postgresql. I feared as much. I like sqlite for "simple databases" (and I figured Bacula's DB would be one of those) as it is completely maintenance-free. Well, I switched to PostgreSQL 8.4 now. Still a full backup after a base backup does not work for me... With Postgres it's a bit different though: I see that the fd sends some data back but after some minutes the fd goes somehow into "idle": - backup is still running according to bconsole (for dir+sd+fd) - almost no CPU/IO on dir/sd/fd anymore strace on the client (Bacula 5.2.11 on Fedora 17) shows that it just does some writes until it fails with EAGAIN and then waits in a select again. The client doesn't seem to recover. I'll try to play around with the acurate/spool settings to see if that makes any difference. fs |