Peter Mueller wrote:

As this tends to be a general "where should amanda development go" discussion

I throw in my opinion too:

fine. thank you.

.) The "localhost" issue comes up in a daily basis here.
  --> The localhost issue must be reconsidered more general!

If we keep this discussion alive, we will maybe find the way to go.

.) Things like the binding to binaries (dump, tar etc) must be configurable, without recompiling -> config files!

This could be done as Mike Delaney suggested.

.) Client side "plugins" that may be run before and after each "disk" must be easily configurable - wrappers are a hack! (and need recompiling - see above)

A short term solution would be to add standard-wrappers to the tarball and

  precompiled packages which may be changed by the operator ...

I give that back to the audience:
What do you think of a plugin-structure?
What kinds of plugins could or should be there?

.) Furthermore I am missing a standard procedure how to cope with a failed

disk backup which is bigger than the available tapes sticking around in your holding disk - maybe only a doc - problem - but I think amadmin should have

  something like a cancel command ?

.) And there is the long promised "multi tape" solution for disks larger than tapes .... Be honest - disks grow ten times faster then tapes - we have to accept this - and furthermore most of us use some kind of virtualisation of disk space which makes the filesystem to be managed independend of available disk sizes ....

Best regards, Stefan.

--
Stefan G. Weichinger
AMANDA core team member
mailto://sgw AT amanda DOT org
--
oops! linux consulting & implementation
http://www.oops.co.at
--