-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Creator wrote:
[snip]
> We have three types of customers (and I think this scenario is common
> for the majority of ISPs)
> 
> 1) Customers on OUR servers managed by US: customer is only
> responsible for updating his data.
> 2) Customers on OUR servers administered by US for disaster recovery,
> monitoring and misc tasks and by CUSTOMER for applications
> configuration and data administration (ie. server rent in a mixed
> administration mode) 3) Customers on THEIR servers administered by
> THEMSELVES (ie. co-location). We have no access to their machines.
> 
> For the customer type 3 disk quotas are not under control of ISP and
> even for the 2nd type you can't be sure that someone is not messing
> up with disk quotas.
> 
> This explains why, unfortunately, your idea is only applicable to the
> 1st type of customers and perhaps to the 2nd type for security
> reasons. 
> 
> I hope that now it is more clear why I need a server-side control
> mechanism rather than a client-side one.
How about different holding disks for each client? Then the only
addition to amanda would be in the dumptype like this:

define dumptype customer {
   comp-root-tar

# -- new option
   holding-disk customer
# -- end of new option
}

and this holding disk has a quota you control. I think this would be
the easiest way to achive, what you wanted... *g*


Cheers
Nicki

- -- 
Linksystem Muenchen GmbH                          info AT link-m DOT de
Schloerstrasse 10                           http://www.link-m.de
80634 Muenchen                              Tel. 089 / 890 518-0
We make the Net work.                       Fax 089 / 890 518-77

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
Comment: Keys at: https://www.link-m.de/pgp

iQA/AwUBPqel/Os1nPm17iBDEQLKNwCfd2w04JTZ0LNRs0AxB0RLSHWjAeMAn1uu
mMg+VT1UpoWnNPbnC1i7zhOS
=4fjQ
-----END PGP SIGNATURE-----