Hallo John,

you are right,  the classical rebinding to another Mgmtclass is not possible.

May be this helps:

One of the ways would be to add (temporarily) another domain to your TSM 
system, specify the according same policy definitions with different retentions 
values 
 and  just add only that one specific node to the new domain
(as schedules are connected also to domains, you would have to adjust/adopt 
here as well).

Rgds Michael

michael.malitz @ tsmpoweradmin.com

c

-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag 
von John Keyes
Gesendet: Mittwoch, 11. Juni 2014 19:13
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Manually Expire Archive

Hello,
 
I have a bit of a problem at hands. We operate a TSM Server for a client. I 
have of course access to the TSM Server but not to the backup clients.
We are doing forever-archives for 3 nodes, but since we are nearly out of 
scratch tapes in the library, the client decided he wants to switch over to 1 
year archives for one specific node.
So how can I expire just the archive data of this one node that is older than a 
year?
As far as I know I cannot rebind existing archive data to other management 
classes and if I change the expiration in this management class, the other 
nodes are also affected.
Does anyone have an idea?
 
Kind regards,
John