Ok, I now understand that amflush doesn't use tapetype. Thanks for
clearing that up.
I went over my amflush logs again, and I see that indeed each amflush
run is writing out some of the images that were in the holding area.
I started with 150 images in the holding area and am now down to 30.
I got confused because I confused the 'filesystems dumped' statistic
with the 'filesystems taped' statistic. 'filesystems taped' clearly
shows the number of images written to tape each time.
Everything is working fine. Thanks again.
P.
On Sweetmorn, the 40th of Confusion, John R. Jackson spake:
> >I then edited my amanda.conf and set tapesize to 3400mb. However,
> >amflush still runs out at over 3500mb before failing.
>
> The "size" parameter in your tapetype is only used by planner (in amdump)
> when it has the estimates to decide what will fit on tape. Amflush does
> not use it at all. It simply keeps writing until it is finished or it
> gets an error.
>
> Is it successfully flushing things? For instance, if your holding disk
> had a lot of "small" images that just totaled up more than 3500 MBytes,
> each time you run amflush should get at least some of them onto tape so
> eventually you will get it all cleared out.
>
> But if you have a single image in there (even if it's in multiple holding
> disk chunks) that is larger than what you can fit on a tape (apparently
> 3500 MBytes), you're stuck. Amanda cannot deal with images larger than
> a tape (yet).
>
> >P.
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
--
Philip J. Hollenback
[EMAIL PROTECTED]
http://www.hollenback.net
