>according to the tar docs, the --listed-incremental will check on the >files listed in the file if the incremental file is not empty. I suppose >the listed-incremental file got filled during the sendsize proceedure?!
No. It got filled by the previous sendbackup run (e.g. yesterday). And, FYI, for a level 0 (full) dump, the listed incremental file comes from /dev/null, i.e. it is used, but empty. >During the sendbackup step, tar is apparently going through and checking >the list, as no data is being transmitted while tar is doing this check. I'm not sure exactly how tar does this. You'd have to look at their code or ask them. I'd be surprised if it completely lost it for 30 minutes, though. >Is this how its suppose to work for a level 0 dump? ( 4 hours >(wall-time) sendsize, ~4hours (wall-time) incremental check, and finally >the transfer of the data ( i suppose longer that 4 hours )) ... Probably true. >Is this how >it will work with other level dumps ( with the exception of the transfer >of data step) ? Yes. Except Amanda may also request a third estimate one level higher than the previous one if it might be time to bump (you can control this with the bump* parameters). You might want to consider using an alternate size calculation tool called calcsize. It's not well supported, and does not handle exclusion lists, but does all the estimates at the same time so you might gain quite a bit of time that way. If you want to go this route, let me know and I'll find the postings from a while back about turning it back on. >/gat John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
