I'd consider looking at something like defining a new policy domain with new
retention rules, then doing an:
update node <node name> domain=<new domain>

(for the node with your new special retention needs) with the consideration
below in mind.

from the manual:

"For servers with data retention protection enabled, an archived registered
node cannot be reassigned to a different policy domain. See the
Administrator's Guide for more information."

never did it myself
----- Original Message -----
From: "Joy Hanna" <JoyHanna AT FREIGHTLINER DOT COM>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Monday, October 22, 2007 12:59 PM
Subject: [ADSM-L] Sropping expiration for specific clients


Hello,
 Due to a legal request we are being asked not to expire any data for
some specific TSM clients. Is there a way to exclude a group of clients
from expiring any data for a time period? I see there is a way to do
this for archived data. I'm talking incremental backup data. If I stop
expiring altogether I think it wouldn't be long before I put my whole
environment at risk. The only way I can think of to do this would be to
rename all filespaces where I suspect there might be data I do not want
to expire. This however would cause all those renamed filespaces to back
up in full tonight. We're talking several TB of file server data. Any
ideas? Sincerely, Joy

Joy Hanna
Enterprise Storage Group
I.T. Computer Operations
(503)745-7748
Joyhanna AT freightliner DOT com