after iwmigration iw-store is alot smaller?

Hello,

i run iwmigrate on iw-store with TS 5.5.2 version to migrate/convert it to TS 6.5 sp2... after the migration finished successfully... i checked the size of the new store produced by the iwmigrate and it s almost half size the orginal store from 5.5.2... is this normal?

i checked the migration log, and it shows that it went throw all the edtions from the oldest edition to the newest, so i dont think it skipd anything... also the log says "migration was successful"

what do you think?

Find more posts tagged with

Comments

nipper

What options did you use ? iwmigrate can skip some old versions/editions.

nipper

from a KB on support

Typically when running iwmigrate on old backing stores (that used to run under a 5.5.2 server) a significant reduction in size is seen. This is due to more efficient metadata format in 6.1 and 6.5

CRB

no options i just typed:
Iwmigrate –m Y:/default –o X: /new-iw-store/default –b /default/main –g migration_log.txt 2>$1

i noticed that my old iw-store has this structure:
iw-store/default (11 gb)
/events (2mb)
/workflows (253 mb)

the new one is just:
new-iw-store/default (6gb)

we dont really need any workflows from the previews one.. because we only use ts to maintain to the structure. the production team just downloads files from teamsite to local machine work on them, then upload them bak to his or her workarea... then submit which is a workflow that points eachfile(based on some tags) to the right target.

-------update----------
somethign really strange happend to me:

\>iwstoreadm -a iw-store
Store iw-store is activated.

\>iwstoreadm -l
Name Store Directory ID Comment
---- --------------- -- -------
default

\iw-store\default 0x64
iw-store

\iw-store\iw-store 0x65

\>

do u notice"D:\iw-store\iw-store"? coule you tell how the other iw-store was created?

it might be because the migration cammand i run which is:
Iwmigrate –m Y:/default –o X: /new-iw-store/default –b /default/main –g migration_log.txt 2>$1

the original one in the document was just X:\new-iw-store without the \default:
Iwmigrate –m Y:/default –o X: /new-iw-store –b /default/main –g migration_log.txt 2>$1

ProjectGantt.rptdesign

SampleProjects1.xls

Migrateduser

I think one reason might be that the Workareas and Staging are not migrated.

Frederik

I think one reason might be that the Workareas and Staging are not migrated.

That's right, if you have *LOTS* of modified files in workarea, that could cause huge space diff.

But also, iw-store can blow up initially after iwmigrate, because certain optimisations that may have happened by running iwfsshrink on the source store, are undone by the iwmigrate (you can get them back by running iwfsshrink on the target, after iwmigrate is done). That happened in our migration.

Another possibility is that the new disk partition has a smaller block/inode/fragment size than the old disk partition (assuming source/target stores are on different partitions).

mmm, just noticed that all that is described in the KB 57161 that nipper linked to Smiley Wink

Finally, iwmigrate fails to transfer certain file versions in specific scenarios:
- create edition X
- submit new file A v1
- delete A and submit deleted file A
- create edition X+1

There's a KB about that, but I couldn't find it now.

nipper

mmm, just noticed that all that is described in the KB 57161 that nipper linked to

Yea, but that should not stop you from retyping everything and posting it again. I am certain you have plenty of time to do that. Smiley Very Happy

CRB

thanks guys... yes the decrease in size was due to workareas not being miragted. which are full of modified files...
but did you see my other question about iw-store being created inside iw-store lol Smiley Very Happy

...

no options i just typed:
-------update----------
somethign really strange happend to me:

\>iwstoreadm -a iw-store
Store iw-store is activated.

\>iwstoreadm -l
Name Store Directory ID Comment
---- --------------- -- -------
default \iw-store\default 0x64
iw-store \iw-store\iw-store 0x65

\>

do u notice"D:\iw-store\iw-store"? coule you tell how the other iw-store was created?

it might be because the migration cammand i run which is:
Iwmigrate –m Y:/default –o X: /new-iw-store/default –b /default/main –g migration_log.txt 2>$1

the original one in the document was just X:\new-iw-store without the \default:
Iwmigrate –m Y:/default –o X: /new-iw-store –b /default/main –g migration_log.txt 2>$1

Frederik

-------update----------
somethign really strange happend to me:
\>iwstoreadm -a iw-store
Store iw-store is activated.

\>iwstoreadm -l
Name       Store Directory               ID         Comment
----       ---------------               --         -------
default    \iw-store\default           0x64
iw-store   \iw-store\iw-store          0x65
do u notice"D:\iw-store\iw-store"? coule you tell how the other iw-store was created?

You should probably re-read the doc about "iwstoreadm". The way to activate a store is "

iwstoreadm -a STORENAME

".

so you activated a STORE with name iw-store yourself, earlier in the commands you posted. If STORENAME is not an existing store, an empty one is created by "iwstoreadm -a"

iwstoreadm will get the root data folder for your stores from other config files (iw.cfg and/or (6.5) /etc/defaultiwstore)