Am 19.09.2017 um 15:46 schrieb Can Şirin: > My jobs have almost 30M > files x 8 parallell jobs, and it takes about 20 hours to despool > attributes.
So you are saying that the whole backup run times out because the database is taking so long? From what I could see with "top", the DB never created noticable load on the system. I must admit that I do not know what "despooling" in this case means. Does it mean "updating the database entries for the present backup run"? If so, why do I finally get a "FD error"? fafnir Fatal error: Network error with FD during Backup: ERR=Connection reset by peer fafnir Fatal error: No Job status returned from FD. Would breaking the job up into smaller jobs help? Matthias ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
