>>>>> On Thu, 16 Jul 2009 16:28:28 -0400, teksupptom said: > > Hello, > > We've been intermittently having an issue with backups failing due to the > error "Spool block too big". It's happened exactly 10 times since > 4/27/09. It generally happens during large backups (900GB+). > > The most recent error happened after the data had been spooled, and was > being written to tape. These usually occur overnight so I don't always get > to see what's going on, but this one happened during my normal shift. Prior > to it happening I had noticed that the SD status showed the correct data > spool file size, but showed 0 bytes for the attribute spool size. I double > checked the directory we use to store the attribute spool file (same > directory where the mail files are kept, but different from where we spool > the data), and there was a 6GB+ attribute spool file for the job. > > Not sure if this is what other people are seeing when this error occurs, but > I'm hoping it can help in tracking down the source. > > We're running Bacula 2.4.4 using PostGreSQL 7.4.19.
I think this can only be caused by a bug, so it is probably a good idead to upgrade to Bacula 3.0.1 to see if that fixes it. Are you using simultaneous jobs? What values does the error give for the sizes of the blocks? __Martin ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users