I believe it will be the default management class of the domain where the data lives when expiration runs, not the domain where it originally backed up. So your first idea will work.
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hanover, Cameron Sent: Tuesday, October 21, 2014 2:57 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] verify management class While I search for answers elsewhere, maybe someone already has an answer floating around in their head. TSM server 6.3. I have a user that has about 2 weeks worth of TDP/SQL backups. They have turned off backups on the node. They have a 60 day retention policy currently. They want to retain all two weeks of backups for 365 days, including the inactive ones. My thought was this: Create a new domain with a new default management class that has a 365 day retention. Update the node to that domain, and all of its backups would be assigned the default retention policy of the new domain. I was hoping that I could query the backups table to verify that this was the case, but it doesn't appear to be that simple. select hl_name,ll_name,class_name,state from backups where node_name='BF-SPDB01_SQL' HL_NAME: \WSS_Content_uhr\ LL_NAME: full CLASS_NAME: DEFAULT STATE: ACTIVE_VERSION .... When expiration runs, will it consider the default retention policy of the domain when the backup was performed, or will it look at the new domain? My backup idea is to update the STANDARD management class on another server instance to 365 days retention and export the node over there. -- Cameron Hanover chano...@umich.edu "A parade of thugs and fashion critics could pass through your living room without you noticing, provided you were distracted by a sufficiently shiny piece of tinfoil." --Lore Sjöberg
