On Thu, Apr 11, 2002 at 01:05:38PM +0200, Frederic Saincy wrote: > Detect the first abnormal dump, then mail a warning and stop to back > up this tapecycle ?
I don't know that amanda can reasonably do much more than sending an advance notice[1] (Warning: Last level 0 dump of /dev/foo will be overwritten in 2 runs) and trying to shoehorn in a fresh level 0 before the old one gets overwritten. > Does the second dump for a tapecycle in a day can be considered as > "abnormal" ? Not necessarily. If, for example, runspercycle > dumpcycle, then there has to be at least one day per cycle when multiple runs are normal. It's even normal if runspercycle = dumpcycle, but dumps aren't run on weekends. > Does an interactive prompt for amdump would fit for this case ? > > for example: > > "Amanda detects an abnormal dumps [big warning] do you *really* know > what your are doing [y/n]?" IMO, no. Interactive prompts as a part of normal operation (i.e., other than in amflush or amlabel) would be Bad, as they require manual intervention to continue. Not good in a cron job, plus it contradicts the software's apparent intent (the second A in amAnda stands for Automatic). If you really want to do this, it should be controlled by a switch in amanda.conf (userisanidiot yes) so that those who do know what they're doing don't have to worry about 42 filesystems not getting backed up by cron just because one machine's purely-vendor-supplied /usr is about to lose its last level 0. [1] ISTR that it already does this
