"no problem :-) This is not impossible to do it, but this is not that easy. If you really want, then I can explain it to you :-) in another thread, so we don't confuse the readers" |
find CacheDirectory/retr/BAA -type l -ls | awk '{print $NF}'
...
/data/ars/archive/cache/01/15667/BAA/DOC/2FAAA
/data/ars/archive/cache/01/15667/BAA/DOC/2FAA1
/data/ars/archive/cache/01/16603/BAA/DOC/6FAAA
/data/ars/archive/cache/01/16603/BAA/DOC/6FAA1
...
<AGID_NAME><DOC_NAME>.<PRI_NID>.0
ln -sf /data/ars/archive/cache/01/15667/BAA/DOC/2FAAA /data/ars/archive/cache/01/migr/2/BAA2FAAA.18.0
ln -sf /data/ars/archive/cache/01/15667/BAA/DOC/2FAA1 /data/ars/archive/cache/01/migr/2/BAA2FAA1.18.0
ln -sf /data/ars/archive/cache/01/16603/BAA/DOC/6FAAA /data/ars/archive/cache/01/migr/2/BAA6FAAA.18.0
ln -sf /data/ars/archive/cache/01/16603/BAA/DOC/6FAA1 /data/ars/archive/cache/01/migr/2/BAA6FAA1.18.0
update ARSAG set SID=18 where agid_name='BAA'
9) You need to update all your segment tables to point to the correct Storage Node / Storage Setselect table_name from arsseg where agid in (select agid from arsag where agid_name='BAA')
TABLE_NAME
------------------
BAA1
BAA10
BAA11
BAA12
BAA13
...
update BAA1 set PRI_NID=18
update BAA10 set PRI_NID=18
update BAA11 set PRI_NID=18
update BAA12 set PRI_NID=18
update BAA13 set PRI_NID=18
...
10) Start CMODarsmaint -h <CMODInstance> -m
it will take some time...Alessandro,
Is there a way you can verify the documents get stored to TSM? I tried your above procedure and after I cleared the cache the documents were not retrievable. I have the same issue. I have two nodes in my storage set. One TSM and one CACHE only. I now need to migrate the cache only docs to TSM before they have to be cleared by the arsmaint daily run.
The SID is the same for both nodes.
SID 5017 has NID 2, NID 3
NID 3 is CACHE only
NID 2 is TSM/cache
I need to move from 3 to 2 in the same Storage Set. I think what I did worked its just looking for the resource files which I did not include in the migration.