On Mon, Mar 18, 2013 at 05:43:03PM +0800, Amit Karpe wrote: > Reply in-line: > > On Mon, Mar 18, 2013 at 1:59 PM, Jon LaBadie <j...@jgcomp.com> wrote: > > > On Mon, Mar 18, 2013 at 12:55:40PM +0800, Amit Karpe wrote: > > > Brian, > > > Yes, initially I was using holdingdisk for all config. But when I see > > > backup is low and taking more time, I had doubt that my backup & > > > holdingdisk are on same disk (NAS) which is 19TB. So I change it & force > > > not to use it. > > > > > > But now I realized its required so I will use for next usage of Amanda. > > > > > > Could someone let me know use of chunksize ? > > > It should big enough like 10GB or 50GB ? > > > As I am using Vtape, finally all these temporary files are going > > > to merge into one file. So why should we create these chunks ? Why not > > let dumper directly dump into final vtape's slot directory ? > > > > > The holding disk chunksize was added to overcome the 2GB max file size > > limitation of some filesystems. It is also useful if you allocate > > multiple holding disks, some which may not be big enough for your > > large DLEs. > > > > The parts of amanda doing the dumps do not peek to see where the data > > will eventually be stored. Taper does that part and it is not called > > until a DLE is successfully dumped. If you are going direct to tape > > taper is receiving the dump directly but then you can only do one DLE > > at a time. > > > > So using chunksize 10GB/ 50GB/ 100GB kind of option, will help amanda to > run dumper parallely ? > No, has no impact on parallelism.
It is a workaround IF you holding disk(s) does not allow big files. jl
