Jeff, I think what will happen if you zap the management classes within a policy
domain, data that was backed up or archived under the zapped managment classes
will be expired per the rules for the policy domain default management class
first for backups and archives. If you do not have a default management class,
then it would go by the policy domain grace period.

George Lesho
Storage/System Admin
AFC Enterprises






Jeff Rankin <Jeff_Rankin AT CARGILL DOT COM> on 03/08/2001 09:43:15 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: George Lesho/Partners/AFC)
Fax to:
Subject:  Management Class Question



We are looking at doing a massive reorganization of our naming
standards within our TSM servers.  During this reorganization, some
management class we have will go away and new ones will be created.
Others will just be renamed.

I know that in order to bind data to a specific management class I can
just use the include statement for the clients and that will start
backing up or archive files to the new management class assignments,
but my question is what happens to the old data that is already backed
up to the TSM server?  Will it be rebound to the new management classes
or will it fall into the grace period retention of the policy domains?
If the policy domain is what controls the data retention in this case,
would it just be safer to leave all of the existing management classes
in place and just start backing up with the new management classes and
let the old data expire off?

We are running TSM 4.1.2. Any help would be greatly appreciated.

--
Jeff Rankin
Jeff Rankin
Associate Technical Analyst, Excel Corporation
Phone:   316-291-2903
Fax:     316-266-4415
Email:   Jeff_Rankin AT cargill DOT com