Yep... that is it the files are bound to the management class you
     change.

     ONLY BACKUPS REBIND...
     ARCHIVES DO NOT REBIND ! (kind'a)

     if you smoke the management class an archive was bound to it is kept
     for the "grace period" for archives associated with the domain

     if you alter the archive copy group of a management class that an
     archive is bound to... the existing archives retain their origional
     expiration date.

     if you alter the "default" management classes backup copy group and
     the files are bound to that, the changes are reflected in existing
     backup versions of files

     if you alter a non-default management class backup copy group and
     files are bound to it, OR if a client rebinds files (see
     include/exclude statements for the client machine) then the changes
     are reflected in existing backup versions of files

     IF A CLIENT WANTS TO CHANGE THE CHARACTERISTICS OF AN ARCHIVED FILE...
     tell them thay have to retrieve it, then archive it into the proper
     management class (to extend its retention) OR delete it if they want
     to get rid of it


______________________________ Reply Separator _________________________________
Subject: Here's an easy one
Author:  debbie (debbie AT ADMIN.USF DOT EDU) at unix,mime
Date:    7/7/98 10:50 AM


Here's a simple question for you guys...If I change the copy control of
a management class and activate it, does it make the changes for all
data that was already backed up using that management class, or just
future backups?  For example, if I change the number of versions - data
exists from 5 to 3, will expiration eliminate the 2 extra versions that
I have decided I no longer want to keep?

Debbie Weeks
University of South Florida
Information Technologies/Technical Support
*********
*Debbie AT admin.usf DOT edu
*(813) 974-6926   *  S/C 574-6926
Fax(813) 974-6926