nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Moving a 5.5.3 content store to 6.5...

bpg

Hello there,

I've just read Knowledge Base Article: 55361, which states that it is highly recommended to do an iwmigrate when moving from 5.5.2 to 6.5. It then links you to another article (Knowledge Base Article: 55358) which, in true Interwoven tradition, is spectacularly lacking in details and seems very convoluted.

The processs that is suggested seems very, very lengthy and not very intuitive. Up till now I have simply been restoring the backing stores from 5.5.2 into a clean install of 6.5 and then activating the backing stores, which seems to work well. Except that there seems to be an issue if trying to propagate permissions on the Y: drive....

Has anyone done the same process that i have been doing but experienced serious performance/memory issues in 6.5?

Or has anyone done the iwmigrate process and if so, how involved is it/how long does it take?

Many thanks in advance,

Brendan Gleeson
Rogers IT TS Sys Admin
TS 5.5.2 SP6 W2K SP4
TS 6.5 SP2 W2K3 SP1

Find more posts tagged with

Comments

Adam Stoller

Do you have any content in the 6.5 store - or is this a new server with which you are going to replace the old 5.5.2 server?

If it's a new server - I'd just stop both servers, copy the entire store over, and then start both servers. Afterwhich you'll have to go through doing the iwidmap stuff (there's a good KB article about this on the support site, but I don't remember the number off-hand, sorry) to fix all the SIDs for the local-disk accounts and/or local groups (e.g. "Administrator", "TeamSite Web Preview", etc.)

It tends to be much faster and less error-prone than doing the migration - unless you're looking to prune a lot of your history as part of the upgrade? If that's the case, you can either migrate from one server to the other - or do the backing store copy and then use a temporary second-store to migrate/prune the branches.

bpg

Thanks for the reply Ghoti, much appreciated.

The process that I have been using up till now is to build a completely clean and empty Teamsite 6.5 install, then restore the 5.5.2 backing stores into this clean install and start the stores, just as you described. This is something that I have done countless times and seems to work well...

The concern I have now is that Interwoven is claiming that only an iwmigrate will be a robust method of migrating the stores. So essentially, if I use my process, I become unsupported since I didn't follow recommendations.

How much stock do you hold in Interwoven's assertion that only an iwmigrate will comprehensively maintain integrity of content stores?

Considering that my main content store is 75Gb in size with over 350 branches, you can probably appreciate my concern at peforming an iwmigrate...

Adam Stoller

Thanks for the reply Ghoti, much appreciated.

The process that I have been using up till now is to build a completely clean and empty Teamsite 6.5 install, then restore the 5.5.2 backing stores into this clean install and start the stores, just as you described. This is something that I have done countless times and seems to work well...

The concern I have now is that Interwoven is claiming that only an iwmigrate will be a robust method of migrating the stores. So essentially, if I use my process, I become unsupported since I didn't follow recommendations.

How much stock do you hold in Interwoven's assertion that only an iwmigrate will comprehensively maintain integrity of content stores?

Considering that my main content store is 75Gb in size with over 350 branches, you can probably appreciate my concern at peforming an iwmigrate...

Considering IWOV folks talked me through the full backing store copy process when I did it for a customer, I think you got an unfortunately misinformed support person - or they've changed their mind after the fact.

The one thing you should do is run iwfsck on the 552 backing store before -and on the 65 store after. You should also consider running iwfsshrink on the 65 store.

nipper

I beg to differ with you Adam. I was given the same answer about iwmigrate a month ago.

I suspect that there are some cases where bad things can happen with a copied backingstore and to be extra certain, support suggests the iwmigrate.

In the end the customer ended up migrating. Did not want to take the chance

Andy

Adam Stoller

I beg to differ with you Adam. I was given the same answer about iwmigrate a month ago.

I suspect that there are some cases where bad things can happen with a copied backingstore and to be extra certain, support suggests the iwmigrate.

In the end the customer ended up migrating. Did not want to take the chance

Andy

No need to beg ;-)

Apparently they've changed their mind about this - but I know several projects have been done by just copying the backing store and as far as I know none of them had any problems (and IWOV *did* approve it at the time)

Screenshot.jpg

ravio

We too had done it by copying the 5.5.2 backing store to 6.5 and did not face any issues.

bpg

Cheers guys, I really appreciate your feedback on this.

Brendan