CMOD TSM Expiration

[yousuf_gani]

Hi,

I have a wierd behaviour for TSM with SNAPLOCK and ENABLEARCHIVERETENTIONPROTECTION YES.

My Scenario
TestDocument are loaded to the AG which has 1 DAY retention Storage Node in TSM( which has Data Retention Protection On ; its a SNAPLOCK WORM volumes)

After few days later when i run the arsmaint for that AG.
  :-arsmaint -d -I <instance> -u <>USerid -p <password> -g 'TEST_EQ_2802_SL_1'

It Only Deleted the Object from my CMOD DB, but actual Object and TSM metadata are still available even after Running the "EXPIRE INVENTORY" from TSM.
  :-For the Storage Node : RETINIT = 1; RETVER =0

But Output From System Log for Migrate SHows as follows
ApplGroup Unload DB:    Name(TEST_EQ_2802_SL_1) Agid(5021) LoadId(34FAA-14833-14833) Rows Deleted(10000)
ApplGroup Unload SM:    Name(TEST_EQ_2802_SL_1) Agid(5021) NodeName(-CACHE-) Nid(0) Server(-LOCAL-) LoadId(34FAA) Objects Deleted(0)
ApplGroup Load Expire:          Name(TEST_EQ_2802_SL_1) LoadId(5021-20-0-34FAA-14833-14833)
ApplGroup Unload SM:    Name(TEST_EQ_2802_SL_1) Agid(5021) NodeName(ODPD_S_0002_001D_2) Nid(20) Server(-LOCAL-) LoadId(34FAA) Objects Deleted(0)

Could anybody help how to Clean up the TSM based on CMOD expiration for the SNAPLOCk(WORM Volumes),'Data Retention Protection On' parameter set for the TSM storage.

Thanks
Mohd Yousuf gani

[Justin Derrick]

What do you see in TSM that makes you think it's still available?  What's your expiration type for your test Application Group?

-JD.

[yousuf_gani]

Hi,
Thanks for Responding.
Below is our Answer

1) When we Select the Object from Content Table for that FILESPACE still the CMOD Deleted Object are Listed from TSM metdata.
Select * from Content where FileSpace = '/AACS02U1/FAA'
      VOLUME_NAME: /sbclocal/snaplock/AACS02U1/ODDC_S_0002_001D_2/000006D7.BFS
        NODE_NAME: ODCN_S_0002_001D_2
             TYPE: Arch
   FILESPACE_NAME: /AACS02U1/FAA
        FILE_NAME: /DOC/ 34FAAA
       AGGREGATED: No
        FILE_SIZE: 1887926
          SEGMENT: 1/1
           CACHED: No
     FILESPACE_ID: 1
FILESPACE_HEXNAME:
     FILE_HEXNAME:
       BITFILE_ID: 5271
        OBJECT_ID: 5271
           COPIED: NO
          DAMAGED: NO
2) LOAD : expiration type for your test Application Group

Thanks
Mohd Yousuf Gani

[Justin Derrick]

Where did you get that filespace name to query?  That doesn't look like the filespace names I'm accustomed to seeing.

Which version of TSM are you using?  Which version of CMOD?

-JD.

[yousuf_gani]

Hi,

Thanks for the Reply,
As Said I my earlier post we are Doing Migration Project.

Migrate from TSM(5.4) and CMOD (8.4) Very Old , We are resetting-up the development with these Old Version causing many Problem.

We found the Error, The FILESPACE Name was not same between the TSM and CMOD, which didnt Unloaded the DATA from TSm.

Thanks for your Help...

[Justin Derrick]

Yeah, I suspected something was wrong with your FileSpace name (since the object name seemed to be correct) -- but wasn't sure where you got it from.

Good luck!

-JD.

[Alessandro Perucchi]

Hello Yousuf,

:-) Well well well :-)

first, IBM cannot guarantee anything if you play with retention less than 90 days. So if you're playing with 1 day retention, then it is not valid.

Then, I will advice you to check that all the storage pool of the new TSM are configured as EVENT based.
You can ask Reinhard, we work together in order to ensure that all was clean and proper to use TSM with SSAM and CMOD.
You can reuse the month of experience we had the last few years.

You can PM me to my IBM e-mail, I can give all the information I have to help you.

Yours sincerely,
Alessandro

[yousuf_gani]

Thanks Alex...

This Problem was solved after changing the FILESPACE name properly...

Thanks a lot