Hi, On 6/13/2007 4:38 PM, Wes Hardaker wrote: > I've just recently been playing with bacula (2.0.3 in self-compiled > rpms on fedora)... > > I have it working with DVDs and the situation in question as I can > tell went like this: > - it was backing up the main system. > - I believe it tried to store the information in: BaculaDVD0009.8. > - However, the disc doesn't actually contain that part, but the log > shows success: > > 12-Jun 23:05 machine-sd: Ready to append to end of Volume "BaculaDVD0009" > part=8 size=3040970041 > 12-Jun 23:05 machine-sd: Job write elapsed time = 00:00:04, Transfer rate = > 57.92 K bytes/second > 12-Jun 23:05 machine-sd: Part 8 (233000 bytes) written to DVD.
It might be that the part file in question still is in your temporary storage directory. Do you have "Write Part After Job" set in the job definition? > So the questions I have that I can't seem to answer via manuals nor > via bconsoles interface is: > > 1) what happened... I doubt anyone can answer this. At least no easily... > the disc is not full yet and mounting it shows about 3G in use: > /dev/hda 2972194 2972194 0 100% /mnt/cdrom > and the missing part was very small: > FD Bytes Written: 228,657 (228.6 KB) > SD Bytes Written: 231,716 (231.7 KB) I did experience problems with small part files myself and think that, for (some) DVD writers, a "session" has to have certain minimum size. No hard facts, though, that's just what I observed quite a while ago. My workaround (or rather the one I implemented for my customer) was to set "Write Part after Job" to No for all jobs except the BackupCatalog one. Like this, All normal jobs would have a good chance to get written correctly, and only the Catalog backup was in danger of ending up corrupted. > 2) what to do about it? Choices are, I think: > 2a) invalidate the whole volume > 2b) somehow tell bacula that just that part is missing and to rewrite > just that part... Yes, look for the part file in the spooling directory you set up for the DVD storage device. > I can't find anywhere that the part number is > actually stored though. I did a quick search of even the DB > tables and came up blank. I don't believe this is user-editable > data (which is fine). Well, user-editable is a term that can be stretched a bit :-) But you are right, the part file informatio is not stored anywhere in the catalog. > 3) how do I prevent this in the future? Doubt anyone can answer this > either, since it would require answering (1) above. Well, "Write Part After Job" is my only suggestion here... and, of course, closely observing things, running SD and DIR with debug logging, and eventually, if this repeats, filing a bug report. > (I turned on tracing on the sd to figure out this problem and it > finally pointed out that the next backup was failing because it tried > to mount the disc and couldn't find BaculaDVD0009.8... I didn't have > tracing on during the failure time though unfortunately) Arno -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
