Although there have been several times that I wish there was such a command. Like right now, where I have walked into a system that is in desperate need of simplification and housekeeping, but not being able to manually rebind legacy data to new mgmtclasses is really tieing my hands. Of course it was easy to implement the client option sets to rebind existing files where I want them - the problem is the tons of data no longer on the client nodes that I can't root out of the rat's nest they are currently hiding in. After all, "tinkering" is part of our TSM Admin job description ;-} (sigh), maybe in 5.4
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Wednesday, July 20, 2005 11:49 AM To: [email protected] Subject: Re: [ADSM-L] How can I change the management class of a node? In TSM, files (not nodes) are associated with management classes. When files are sent from the client to the TSM server, they are bound to a management class, as can be controlled from the client. Once in TSM server storage, file management classes cannot be changed by any command. The only way to change the management class of a file is to send the file to the TSM server again, with a reformulated Include statement in effect for Backup, or an Include,Archive or ARCHMc spec for Archive. This discipline is in effect because enterprise level data retention calls for retention values which are set and known at file commit time, and which are not subsequently tinkered with by someone beyond the client realm. Refer to "Binding and rebinding management classes to files" in the client manual. Richard Sims Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
