On Fri, 13 Jul 2007, John Drescher wrote: > On 7/12/07, Charles Sprickman <[EMAIL PROTECTED]> wrote: >> Hi all, >> >> Yesterday I ran a test backup and made it through about a dozen machines. >> I eventually ended up with this error as the last one that worked was >> despooling to tape: >> >> 11-Jul 21:40 devel2-sd: Committing spooled data to Volume "Monthly0001". >> Despooling 12,781,472,694 bytes ... >> 11-Jul 21:42 devel2-dir: Max configured use duration exceeded. Marking >> Volume "Monthly0001" as Used. >> >> That one I assume is a problem where I only let the tape be used for a day >> but the backup took more than 24 hours. I can fix that. >> >> 11-Jul 21:54 devel2-sd: Despooling elapsed time = 00:13:27, Transfer rate >> = 15.83 M bytes/second >> >> This seems to indicate it despooled? >> >> 11-Jul 21:54 devel2-sd: Sending spooled attrs to the Director. Despooling >> 64,878,705 bytes ... >> > This is usually done as the last step in a job.
That makes sense, as somewhere in the manual I remember seeing something about things not getting into the catalog until after data is actually on the tape. A very good idea. :) >> But then it looks like it's doing it again? >> >> 11-Jul 21:55 h14-fd: h14.2007-07-10_20.41.53 Fatal error: job.c:1749 Comm >> error with SD. bad response to Append Data. ERR=Resource temporarily >> unavailable >> > Ypu are saying this message was after the Sending spooled attrs? Yes. > Are you sure the network did not go down temporarily such that the fd > and the sd could not see each other? This was all local, the director and storage daemon are on the same box. Now I'll start my story that explain this (not the order of the logging, but at least how it got broken)... I honestly just forgot about this thread because the next day the server running amanda and bacula (and lots of other stuff) had a drive start to fail. Not total failure, it still booted, but it simply couldn't read/write certain sectors. One of those was a temp file that lived in /var/db/bacula/ - it seemed to be a list of all the inserts that would need to be done on the db to get info about this spooled job into postgres. When I attempted to manually copy the file or view it, I got I/O errors. This probably wildly confounded the SD and/or Director. The good news is that I, a total bacula n00b, was able to get bacula installed again, stuff my db from the catalog backup, and restore this machine using bacula instead of amanda. Since we were testing, bacula had the most recent backup. It went off without a hitch for the most part, and I found out just how damn fast LTO drives are. There were a few bumps along the way, but I attribute that to this being the first "real" restore I'd done. So next week we turn off amanda and start up bacula. >> And this one is a mystery. I have a 100GB LTO-2 tape loaded, and the >> "Last Volume Bytes" figure below shows that only 46GB have been written to >> the volume so far. I'm also unclear on what happened to the data. After >> this the spool directory was empty, but it doesn't look like it was >> actually written to tape. >> > I assume you expected your jobs to use more of the tape? > >> 11-Jul 21:55 devel2-dir: h14.2007-07-10_20.41.53 Error: Bacula 2.0.1 >> (12Jan07): 11-Jul-2007 21:55:27 >> >> Here's some more info showing the amount of data written in this session >> and the total written to the tape. >> >> ... >> >> FD Files Written: 227,177 >> SD Files Written: 0 >> FD Bytes Written: 12,729,150,491 (12.72 GB) >> SD Bytes Written: 0 (0 B) >> Rate: 553.6 KB/s >> ... >> Last Volume Bytes: 45,978,799,104 (45.97 GB) >> Non-fatal FD errors: 10 >> SD Errors: 0 >> FD termination status: Error >> SD termination status: Error >> Termination: *** Backup Error *** >> >> Can anyone clarify what the above error means? Everything was looking >> good up until this point. >> > The job ended most likely because of the bad response to Append Data. error. I fixed this up. I discovered two very useful bconsole commands that have been my troubleshooting aides as I try to get all my full backups on this one tape: "status" and "update". I was able to do two things to this tape - mark it as "Append" again and set the "Volume Use Retention" to a longer period. I'm finding that for the most part Bacula seems more complicated than it really is. The way it's been "breaking" has been educational, not tiresome. :) Charles > > John > ------------------------------------------------------------------------- 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
