Amanda-Users

Re: Proposal: quota limit on backup clients and groupware (Hope to be added on the wishlist)

2003-04-17 15:27:17
Subject: Re: Proposal: quota limit on backup clients and groupware (Hope to be added on the wishlist)
From: Stefano Coletta <creator AT mindcreations DOT com>
To: amanda-users AT amanda DOT org
Date: Thu, 17 Apr 2003 19:30:21 +0200
It would be great if it may be implemented without modifying the source code. This may demonstrate the great modularity of amanda. I'm a newbie of amanda and thus I don't know actually how to interpose this "decision-maker" strata between the planner and the rest of amanda. I thought about integrating it into amanda to make it easy for other people to configure this behaviour without using "special" wrappers and make it standard through the normal config files. If it is not actually possibile to realize it applying a wrapper it may be an interesting theme to discuss on how to make wrapper/plugins addition an easy task and at different levels between amanda processes.

Jon LaBadie wrote:

On Thu, Apr 17, 2003 at 04:04:31PM +0200, Stefano Coletta wrote:
Hello everybody,

 [ snip ]
I hope to receive comments about this because I do not think I'm the only one having this type of need.

I'll be surprised if you get a lot of "ME TOO" replies.  But who knows.


One thought I had might be possible with no changes to amanda.

Lots of one-off requirements are satisfied with "wrappers" for the
standard amanda commands.  For example, people who want to encrypt
their backups substitute their "tar" command with a shell script
that calls the same tar in a pipe with an encryption program.
Consideration has to be given when writing the wrapper whether it
is being called during an estimate phase, an actual dump, or a restore.

What I'm wondering if if you could "wrap" the planner program, or some
part of the estimate phase.  Let it capture the results and take action.
Perhaps based on some lookup table.  Eg. if the result is for /x/foo,
then use these values to make further decisions.  If all is ok, then
pass the planner results to the next amanda component as if the planner
were run without the wrapper.  IIRC, the planner output was pretty simple.
A single line per DLE with the sizes of level 0, level 1, ...