Hello, during execution of expiration process on TSM/SP server each backed up/archived object is processed, currently active backup/archive copy group retention (versions and/or days) is applied. Based on result if object is eligible for deletion, it is deleted; otherwise object is kept until next expiration process. Unfortunately you cannot rebind mgmt class of archived objects. So if you now change retention of copy groups, it will apply from now on for all existing and new objects.
If you change the retention, you can check the deletion date via 'dsmc query archive -detail /path/to/api/file' Bye M. Janosik "ADSM: Dist Stor Manager" <[email protected]> wrote on 2017-09-20 14:18:41: > From: "Rhodes, Richard L." <[email protected]> > To: [email protected] > Date: 2017-09-20 14:20 > Subject: [ADSM-L] rebinding objects for API client archives > Sent by: "ADSM: Dist Stor Manager" <[email protected]> > > We have a TSM instance that is dedicated to "applications". These > are applications that use the API client to store some kind of > object in TSM. An example is IBM Content Manager. Nodes are in > domains with a default Mgt Class with 7 years retention, and store > their data as Archives, although one application uses Backups. > > We received a legal hold request to keep some of this data for 12 years. > > It's my understanding that you cannot rebind archive data. That is, > changing the MgtClass will do nothing to keep this data longer. > > Do we have to change the Mgt Class and have the users retrieve/re- > archive the data? > > > Is this correct? Thoughts? > > Thoughts? > > Rick > ------------------------------------------------------------------------------ > > The information contained in this message is intended only for the > personal and confidential use of the recipient(s) named above. If > the reader of this message is not the intended recipient or an agent > responsible for delivering it to the intended recipient, you are > hereby notified that you have received this document in error and > that any review, dissemination, distribution, or copying of this > message is strictly prohibited. If you have received this > communication in error, please notify us immediately, and delete the > original message.
