Hi Yousuf,
Well I will explain how to do it then
This works on AIX/Solaris/Linux/HP
For Windows, you cannot use that method exactly, there are some "adaptation" to perform
Please before doing it in production/test/...
Please test it, please do a backup before!!!!!!!!!!!!!!!!!Basically, you need to follow the following steps:
1) You need to have a storage set defined for your AG, either you have it already, or you need to create it.
2) In the CMOD database, you need to get the SID from the storage set (table ARSSET), and the NID from the storage node that you will archive documents into (table ARSNODE)
3) In the cache, you need to create a directory call "migr" at the same location where the directory "retr" exists.
4) You need to know the AGID_NAME from your AG (table ARSAG or you can find it in the Admin Client on the advanced button of the storage management) (for example BAA)
5) in the directory migr, you create a directory with a number, this number is the internal date format of CMOD, which means the number of days since 1.1.1970. That's the moment that CMOD will migrate really the content into TSM, so I assume that you want to migrate it as soon as possible. That means, that you can use a number like 2 (mkdir 2)
6) in the directory migr/2 (for example) you need to create a link for ALL the objects that you need to move into TSM.
6.1) You can have the list of all your files like that with such a command:
find CacheDirectory/retr/BAA -type l -ls | awk '{print $NF}'
you'll get something like that:
...
/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
...
6.2) Now with each of these files, you need to create a soft link with the following naming convention:
<AGID_NAME><DOC_NAME>.<PRI_NID>.0
So with my example, here are the commands I will have (I consider that my NID or PRI_NID is 18 as an example which was found in step 2) )
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
7) You need to stop CMOD (Maybe you don't need to do it, but I prefer to be safe than sorry)
8 ) You need to update the ARSAG table to point to the correct SID you got from point 2)
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 Set
9.1) First get all the tables you must update
select table_name from arsseg where agid in (select agid from arsag where agid_name='BAA')
you'll get a list of tables like this one:
TABLE_NAME
------------------
BAA1
BAA10
BAA11
BAA12
BAA13
...
9.2) Now for each table found in the previous step, you need to change the PRI_NID with the NID you found in step 2) :
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 CMOD
11) Check that you can still retrieve your document
12) Run the command
arsmaint -h <CMODInstance> -m
it will take some time...
I hope that I could explain in a clear way how to do it!! :-)
Again... please be really careful at each step, because this is not something trivial, and you're doing some changes in the database...
---
Alex