Quota for clients?
Hi All, Does anyone know if it is possible to implement some kind of quota per client, so that it will not be possible to exceed a certain amount of data to be backupped (eg. 2GB max. data to be backupped to the TSM Server). The server and client will both be on 5.5. Met vriendelijke groet, with kind regards, Richard van Denzel
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
Re: Quota for clients?
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: ADSM-L@VM.MARIST.EDU 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
Re: Quota for clients?
There are times when a nearly trivial change replicated across a file system (I'm thinking of NTFS permissions changes; I'm sure there are others) will force unusually large backups. In cases like that, I'd like the TSM backups to continue to run into normal business hours but in a way that minimizes network impact on Real Business Operations. Multiply that across hundreds of nodes as a new policy is enacted, and the problem becomes very noticeable. We have to be careful not to let the tail wag the dog. TSM exists to serve the needs of the organization, not to dictate the way the organization does business. If the business needs require that I keep TSM from hogging network bandwidth, it would be nice to have a more delicate method than just cancelling the running backup session. Just a thought, Nick -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Tuesday, June 10, 2008 9:25 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 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
