Maybe you should have whoever is responsible for the system give you a list of the files they need backed up, not to exceed XXX Mb's. And just backup up what's on the list. That way at least they will know what they have protected.
You could limit the size of each backup by assigning the node it's own disk storage pool, set to the size limit, and don't allow the pool to migrate. But chances are pretty good that Critical files will be missed. Why even bother backing up if you can't restore what's needed? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: Tuesday, June 10, 2008 7:25 AM To: [email protected] Subject: Re: Quota for clients? Schemes to limit client activity are contrary to the overall purpose of TSM, where denying a department the ability to safeguard its data can result in losses which would be painful to the organization. But, TSM server administrators do have to deal with "pests" at various times. Where "social engineering" does not work, and measures are sanctioned to safeguard TSM service to the community as a whole, more draconian measures can be pursued. By various means (e.g., accounting records monitoring), client activity can be gauged and quelled by measures such as setting MAXNUMMP to 0, which stops backup/archive tape use but allows needed restore/retrieve. A real nuisance deserves a LOCK Node for some period of time. Richard Sims at Boston University
