Since data retention is at the data item level, you need to go back to that
to extend set things to "no limit".

I had to freeze some past data (only... no future data) so I renamed the
nodes to <existingname>_xxx    (where your xxx can be something like
"frozen")
Build a domain such as outlined below... move your nodes that require their
data be frozen into that domain... then reregister the initial node name
again under their normal domain.
Since their existing management class won't really exist in this new domain,
it will all fall under the retention grace period.
To get that frozen data shifted around you can either:
1) use move nodedata to isolate it into a newly created storage pool
2) simply export the blah_xxx nodes (the unlimited domain gives you time to
perform the export without the required data expiring)
This all allows the node(s) to return to normal nightly processing while you
deal with the frozen data.


tsm: TSMSRV1>q domain unlimited f=d

              Policy Domain Name: UNLIMITED
            Activated Policy Set: STANDARD
            Activation Date/Time: 04/30/2005 12:29:12
           Days Since Activation: 1,188
    Activated Default Mgmt Class: UNLIMITED
      Number of Registered Nodes: 0
                     Description:
 Backup Retention (Grace Period): 9,999
Archive Retention (Grace Period): 30,000
  Last Update by (administrator): xxxxx
           Last Update Date/Time: 04/30/2005 12:29:12
                Managing profile:
                 Changes Pending: No
           Active Data Pool List:

tsm: TSMSRV1>q copy unlimited

Policy        Policy        Mgmt          Copy          Versions
Versions       Retain      Retain
Domain        Set Name      Class         Group             Data
Data        Extra        Only
Name                        Name          Name            Exists
Deleted     Versions     Version
---------     ---------     ---------     ---------     --------
--------     --------     -------
UNLIMITED     ACTIVE        UNLIMITED     STANDARD      No Limit     No
Limit     No Limit     No Lim-

it
UNLIMITED     STANDARD      UNLIMITED     STANDARD      No Limit     No
Limit     No Limit     No Lim-

it


tsm: TSMSRV1>q copy unlimited  t=a

Policy        Policy        Mgmt          Copy            Retain
Domain        Set Name      Class         Group          Version
Name                        Name          Name
---------     ---------     ---------     ---------     --------
UNLIMITED     ACTIVE        UNLIMITED     STANDARD      No Limit
UNLIMITED     STANDARD      UNLIMITED     STANDARD      No Limit

tsm: TSMSRV1>

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 31, 2008 2:33 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes

The specific volumes are determined by a SQL query, the tapes are in the
primary tapepool.  Multiple nodes are affected.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Dwight Cook
Sent: Thursday, July 31, 2008 2:05 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes


Data on specific volumes...
How do you know what is on those volumes?
Need more information...
Is this copy pool data?
Is it data for a single node and you know what is on it because of
collocation?

Dwight

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 31, 2008 1:58 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Change retention policy on specific volumes

Hi All,

I have been asked to move multiple volumes to another storage pool so that I
can change the retention to no limit.  I do not want to change all of the
volumes on a node, only select volumes.  I know that retention is determined
by the management class and if you change the management class it rebinds on
the next backup but I need to be able to change it on existing volumes
without backing up again or changing it on all of the data.  Is there any
way to do this and if so, how can I accomplish this quickly.  We were
informed today and they want it by tomorrow.  Thanks for the help.


Debbie Haberstroh
Server Administration