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: [email protected] 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
