It is my understanding that only files the existing on the client (active) can
rebind.  The deleted files (inactive) are not updated by the client and not
rebound.  They are trapped till they expire.  I was instructed to restore the
files, back them up, and delete them again in order to rebind them to the the
new management class rules.  My situation was more about the storage pools that
the files resided in, and not the expiration of the files.  Obviously restoring,
and deleting the files will reset the expiration clock, and thus your problem
may not be resolved.





"Ochs, Duane" <Duane.Ochs AT QG DOT COM> on 06/21/2002 06:16:28 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: Joseph Pendergast/Corona/Watson)

Subject:  Filespaces, rebinding and scripts.



I am using TSM Server 4.1.1 on Aix 4.3.3. NT client version 4.1.3
MC_current is defined as versions exists 21, versions deleted 21, retain
extra 21, retain only 90 and set as the default management class.

NODE1   does not have an include so it defaults to MC_current

My retention requirements have changed due to some legal issues and I plan
on creating MC_new and placing it in the opt file for this node and
restarting the scheduler service.

  As a test, I did this on a node. After a successful backup was run, I made
a change to MC_current to ver delete 0, retain only 0 and ran an expiration
and a number of files were expired from my tapes for this test node, that I
assumed would have rebound to MC_new.