On Tue, Nov 02, 2010 at 10:59:38AM -0400, Jean-Louis Martineau wrote: > Jon LaBadie wrote: > > > >My scheme would not scale well or be suitable in a > >production environment. > > > >There is only one config, "Daily". For the amanda > >server, one DLE (called Amanda) uses a disk of "/" > >and "includes" each of the amanda directories. > >My other server DLEs exclude these same dirs. > > > >My crontab executes a script that does two amdumps. > >The first looks like this: > > > > /usr/sbin/amdump Daily \ > > .butch. Root \ > > .butch. Var \ > > <snip bunch of similar DLE lines> > > .bigcow. Opt \ > > .bigcow. Home > > Amanda dump and flush only the listed dle > It is not flushing '.bigcow. Amanda' because it is not on the command line. > > We can change this behavior.
Ahh, if I didn't miss it in the docs, a note should be added. > What user expect from dle on the amdump command line: > - dump/flush only the listed dle (actual behavior) > or > - dump only the listed dle and flush everything? Certainly I expected any DLE from the specified config to be flushed on any amdump run. But now that you describe the behavior I can see either behavior could be wanted at different times. For example, stuff is still on the holding disk but I want to make an archive copy of some DLE(s). Then the current behavior is desired. I presume the disklist would be the arbiter for what things on the holding disk are candidates for flushing. But might there might also be edge cases where the disklist was changed and the holding disk still has dumps from some deleted DLE? It seems to me that the current behavior would be suitable in the majority of cases. I don't think too many amanda installations run a daily amdump with specified DLEs. If the current behavior is retained, what would be the possibility of adding an amdump option to force flushing even when DLEs are specified? jl -- Jon H. LaBadie [email protected] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
