Merging a TS 5.5.2 store with TS 6.5 SP2 store

We are planning to migrate our TS 5.5.2 SP6 environment to a TS 6.5 SP2 environment- both on Solaris 8 and both having content currently being used by two different groups in our company. On the store migration part, the current high level plan is to migrate the 5.5.2 store to make it compatible with 6.5, activate it as a separate store in the 6.5 system and move the branches one by one to the default store in 6.5. Is this the best way to do this and if not what would be the alternatives here. We have 469 branches, 300 GB of content, around 600 users and groups to be migrated from the 5.5.2 system

Highly appreciate your inputs.

TIA

cgi

Find more posts tagged with

Comments

Antharix

What you can probably do is

Do a binary upgrade of 552 to 6.5 then run the iwmigrate on the iwstore and then move it to the other 6.5 environment that you have.

This article may be of help to you :
[color=#333333]https://support.interwoven.com/kb/k...ArticleID=50378

[/color]

You will have to consider the pro and cons of the above steps within the context of your implementation.

cgi

What you can probably do is

Do a binary upgrade of 552 to 6.5 then run the iwmigrate on the iwstore and then move it to the other 6.5 environment that you have.

This article may be of help to you :
[color=#333333]https://support.interwoven.com/kb/k...ArticleID=50378
[/color]

You will have to consider the pro and cons of the above steps within the context of your implementation.

Thanks for the reply.

We will not be doing any installations for this upgrade because we are migrating to an existing TS 6.5 environment - so I do not think we need a binary upgrade if I understood it correctly. I'm looking for the best way to merge a 5.5.2 and 6.5 store with minimum downtime to the 6.5 environment.

Adam Stoller

Thanks for the reply.

We will not be doing any installations for this upgrade because we are migrating to an existing TS 6.5 environment - so I do not think we need a binary upgrade if I understood it correctly. I'm looking for the best way to merge a 5.5.2 and 6.5 store with minimum downtime to the 6.5 environment.

"merge" is a questionable term here.
You can migrate (using iwmigrate) the contents of branches that exist in your 5.5.2 store into a 6.5 store - assuming that those branches do not already exist in the 6.5 store and once migrated, that no work will be done in those branches in the 6.5 store until you have completely cut-over to the 6.5 store.

You can run iwmigrate either by mapping the existing 5.5.2 store onto the 6.5 server - or by placing a copy of the 5.5.2 store on your 6.5 server (I prefer the latter, making the 5.5.2 store a temporary second store on the 6.x server and then doing the iwmigrate completely within the confines o the 6.x server).

cgi

"merge" is a questionable term here.
You can migrate (using iwmigrate) the contents of branches that exist in your 5.5.2 store into a 6.5 store - assuming that those branches do not already exist in the 6.5 store and once migrated, that no work will be done in those branches in the 6.5 store until you have completely cut-over to the 6.5 store.

You can run iwmigrate either by mapping the existing 5.5.2 store onto the 6.5 server - or by placing a copy of the 5.5.2 store on your 6.5 server (I prefer the latter, making the 5.5.2 store a temporary second store on the 6.x server and then doing the iwmigrate completely within the confines o the 6.x server).

Fish,

Thanks for your reply. Do you know how much time does iwmigrate take? - We have 469 branches and 300 GB of content to be migrated. Both TS 5.5.2 and 6.5 environments are heavily used and can be frozen only on a weekend for cutover ie, 2 days or a maximum of 4 days.

Antharix

First try executing the iwmigrate in a branch with sizeable content. this will help you to estimate the time for a complete iwstore migrate.

Adam Stoller

Fish,

Thanks for your reply. Do you know how much time does iwmigrate take? - We have 469 branches and 300 GB of content to be migrated. Both TS 5.5.2 and 6.5 environments are heavily used and can be frozen only on a weekend for cutover ie, 2 days or a maximum of 4 days.

The amount of time it takes varies based on a number of different variables, including, but not limited to:

allow anyone to muck with the content in those branches on the 6.5 server) - you can then do an incremental iwmerge from a fresh copy of the 5.5.2 backing store (with fresh editions cut) - and that incremental merge should take a fraction of the time of the initial migration.Basically - you should not try to rush the process - if you do, you are likely to end up with problems that will taken even longer to resolve.

cgi

Thanks for your replies.

Can the 5.5.2 workflow job instances also be ported to 6.5 SP2? We have atleast 500 workflow job instances invoked everyday and most have a life of around 1 day and a few stay there up to a month.

Adam Stoller

Thanks for your replies.

Can the 5.5.2 workflow job instances also be ported to 6.5 SP2? We have atleast 500 workflow job instances invoked everyday and most have a life of around 1 day and a few stay there up to a month.

I would generally suggest that you not try to merge / migrate / upgrade in-progress jobs.

Find (define) a cut-over point and then start all new jobs on the new server.