Re: "Holdingdisk no" - why does amanda wait to tape those DLEs?
Jean-Louis Martineau schrieb: > It's important to do the dump direct to tape at the end if you have a > small holding disk, Amanda was designed for this case. > > But hard disk are now cheap, what you propose is a good idea. > > Patch is welcome. Maybe we should show this to the hackers-list ? S
Re: "Holdingdisk no" - why does amanda wait to tape those DLEs?
It's important to do the dump direct to tape at the end if you have a small holding disk, Amanda was designed for this case. But hard disk are now cheap, what you propose is a good idea. Patch is welcome. Jean-Louis Stefan G. Weichinger wrote: Dustin J. Mitchell schrieb: However, the driver always schedules its PORT_WRITE (direct to tape) dumps *after* its holding-based runs. The idea is that dumping directly to tape basically monopolizes the entire server infrastructure, so it's better to get the cooperating dumps out of the way first. So the behavior you're seeing with this particular config is intended, although it's not what you expected. I understand the intentions but on the other hand it should be possible to get the behavior I expected as well: Write "holdingdisk no"-DLEs to tape while other stuff gets in via dumpers. In my specific case this would help to speed up things a lot. Stefan
Re: "Holdingdisk no" - why does amanda wait to tape those DLEs?
Dustin J. Mitchell schrieb: > However, the driver always schedules its PORT_WRITE (direct to tape) > dumps *after* its holding-based runs. The idea is that dumping > directly to tape basically monopolizes the entire server > infrastructure, so it's better to get the cooperating dumps out of the > way first. > > So the behavior you're seeing with this particular config is intended, > although it's not what you expected. I understand the intentions but on the other hand it should be possible to get the behavior I expected as well: Write "holdingdisk no"-DLEs to tape while other stuff gets in via dumpers. In my specific case this would help to speed up things a lot. Stefan
Re: "Holdingdisk no" - why does amanda wait to tape those DLEs?
OK, I'll take a swing at this :) On Wed, Apr 1, 2009 at 3:50 PM, Stefan G. Weichinger wrote: > I want to avoid to copy ~60 GB from disk to holdingdisk internally at > every amdump, so I decided to set them to "holdingdisk no" --> write the > to tape directly. > > taperalgo first, btw The taperalgo decides which dump, among those available in holding, the taper will choose. I think the one you are thinking of is dumporder. > Now they sit there and "wait for dumping", I would like them to be taped > asap and the taper shouldn't get idle waiting for other dumpers until > everything local is taped, correct? However, the driver always schedules its PORT_WRITE (direct to tape) dumps *after* its holding-based runs. The idea is that dumping directly to tape basically monopolizes the entire server infrastructure, so it's better to get the cooperating dumps out of the way first. So the behavior you're seeing with this particular config is intended, although it's not what you expected. Dustin -- Storage Software Engineer http://www.zmanda.com
