Amanda-Users

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

2003-04-22 13:39:27
Subject: Re: Proposal v2: quota limit on backup clients and groupware (Hope to be added on the wishlist)
From: Gene Heskett <gene.heskett AT verizon DOT net>
To: Jon LaBadie <jon AT jgcomp DOT com>, amanda-users AT amanda DOT org
Date: Tue, 22 Apr 2003 13:35:25 -0400
On Tue April 22 2003 12:51, Jon LaBadie wrote:
>On Tue, Apr 22, 2003 at 05:16:49PM +0200, Stefano Coletta wrote:
>[[ snip ]]
>
>> The 2 goals to achieve are:
>> 1) to be informed about over quota events in relation to every
>> globally purchased customer quota and even to notify the
>> customer 2) to effectively deny the backup if the client has
>> exceeded his quota after he has been warned several times
>> 3) to inform technical staff about imminent tape space shortage
>>
>> I propose two different approaches to partially/definitely solve
>> the problem:
>>
>>
>> 1st solution: more easy, the partial one
>> ----------------------------------------
>>
>> Add new parameters in the dumptypes declaration section of the
>> amanda.conf file.
>>
>> Example:
>>
>> define dumptype customername {
>>    global
>
>[[ snip ]]
>
>> # -- BEGINNING OF NEW PARAMETERS
>>
>>    quota 1Gb
>>    quotaexceed 7
>>    quotadeny 1
>>
>> # -- END OF NEW PARAMETERS
>> }
>>
>>
>> In this way you can limit Amanda from doing backups larger than
>> 1Gb for that dumptype that corresponds for example to
>> "customername".
>>
>> NOTE: with the word "limit" I mean not to truncate the backup
>> but effectively avoiding to do it.
>>
>> "quotaexceed" may be the maximum number of times that Amanda
>> does the backup before refusing to do it (ie. 7 days).
>>
>> Obviously, during the amcheck you have to be notified of this so
>> you can contact your customer to extend the quota or just making
>> him to reduce the amount of data to backup.
>
>This would be a MAJOR change.
>Currently amcheck does no checks on the size of the next backup.
>To do this properly would require going through the estimate phase
>of amdump which is a time, disk, and cpu expensive.

Extremely so here Jon, with the machine being virtually un-useable 
while the estimate phase is running here, something in the 20-30 
minute range, during which it may be >10 seconds for what I type to 
actually show up on the screen!  If I had other users that time of 
the night, it would really generate a lot of calls for support.  
But since I'm both caller and callee, I'm torn between killing 
amanda, and letting her run.  Run wins 99.99% of the time of course 
as I'm my own BOFH. :)
 
-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.