I am using TSM Server 4.1.1 on Aix 4.3.3. NT client version 4.1.3 MC_current is defined as versions exists 21, versions deleted 21, retain extra 21, retain only 90 and set as the default management class.
NODE1 does not have an include so it defaults to MC_current My retention requirements have changed due to some legal issues and I plan on creating MC_new and placing it in the opt file for this node and restarting the scheduler service. As a test, I did this on a node. After a successful backup was run, I made a change to MC_current to ver delete 0, retain only 0 and ran an expiration and a number of files were expired from my tapes for this test node, that I assumed would have rebound to MC_new. >From the client after the backup following the change: Total files scanned: 231,670 Total files rebound: 374,251 >From the Server using audit occupancy before the backup: Total files NODE1 978,249 >From the Server after the expiration: Total files for NODE1 437,875 My Questions: The next time a backup executes, after the include is added, do both active and inactive files rebind to MC_new or just the active ? Is there a way to do either a query or execute a script that lists the files for a client and the Management Class they are bound to on the TSM server ? Duane Ochs Systems Administration Quad/Graphics Inc. 414.566.2375
