Migration from 6.7.2 to 8.1

Hi folks,

We're planning to migrate from 6.7.2 (W2K3) to TeamSite 8.1 (W2K12 R2).

Currently we use 6.7.2, with Index Service, Search, MetaTagger, Access Service, CSSDK, Derby Database, Workflow Models, OpenDeploy 6.2, DataDeploy etc. We've only one branch which we use. We will not be using LiveSite.

Plan:

1) Run iwfsck on the existing store
2) Copy the content store to the new server (need to retain EA's).
3) Install the database, OD 8.1, TS 8.1 (Search, TagUI, CSSDK, WFM etc) on a new server
4) Deactivate the new default & iwadmin stores
5) Run iwfsck on the new store
6) Activate the copied store

7) Deactivate the old iwadmin store and activate the new iwadmin store
7) Migrate users and groups
8) Migrate the workflow models, deployment conf, customizations etc.

Qusetions:

1) Do we need to run iwfsshrink?

2) I read that it'll be possible to migrate the WORKAREA instead of the entire store. Is it recommended if we need to retain EA's and not the version history?
3) If we're copying the entire store (using xcopy), do we need to write any custom script to migrate EA's?
4) Is it required to migrate the Interwoven Derby data?
5) Regarding MetaTagger/TagUI what is it that we need to migrate here?

6) Regarding Search and Index service, is it two separate service in 8.1? What needs to be migrated here?

7) I understand that we need to run Dependency Migration Tool. What exactly this does? Can we skip this if we don't use LiveSite?
8) Anything that we missed or need to check?

Any pointers would be of great help!

Thanks all!!

regards,
Praveen

Find more posts tagged with

Comments

Adam Stoller

It is unclear whether full copying of the existing [6.7.2] store will be fully compliant with the new [8.1] backing store code - so you may need to alter your plans a bit to perform an iwmigrate from the copy of the existing store into a fully compliant new store - this can still be done on the new server as it should perform an in-place upgrade of the copy of the existing store, but the in-place upgrade will not necessarilly make it fully compliant - after doing that, you would then want to run iwfsshrink.

If you truly do not want all the historical versions, you could use the '-s edition-name' flag on iwmigrate to specify that it should start from the most recent named edition. If you haven't been cutting editions on your 6.7.2 server, you should do so before making a copy of it for your new server. Since you indicate you only have one branch, this is a rather trivial understaking. If you had multiple branches, it would be best to make sure that each [content] branch have the same named edition on it (e.g.: "PRE_8.1_UPGRADE") so that you could easily script the process, and - if you end up having to do incremental migrations (because work needs to continue on the 6.7.2 server while you verify everything on the 8.1 server), you can easily use the exact same named edition for the start of any incremental migrations.

Brett Sargeant

We were able to go from 6.7.2 -> 7.5 without running iwmigrate, I'm not sure if going to 8 would be too large a leap.

In answer to some of your other questions:

1) Do we need to run iwfsshrink?

most likely

3) If we're copying the entire store (using xcopy), do we need to write any custom script to migrate EA's?

No, you're copying the store itself, it will contain the EA's. Depending on how large it is, it may take some time to copy across.

5) Regarding MetaTagger/TagUI what is it that we need to migrate here?

If you can get away without using it, remove it completely.

8) Anything that we missed or need to check?

Make sure you have backups. Licensing may be a pain, not sure if it's still around but there was an attempt to move us to a "Golden" license during the upgrade. It didn't work, we had to use the old style.

If you do end up with a golden license, at the time it was meant to expire after a year, at which point you needed a new one. Not sure if that is still the case.

There will most likely be a bunch of scripts and permissions that will need to be changed to suit the new environment and 8.1. Some of the tpl stuff has changed (if you use them).

nipper

I would certainly run iwfsshrink before you migrate. It will trim down the size of you iwstore and make it easier.

Also you certainly SHOULD run iwfsck on the complete store as well. This needs to be done with the store deactivated so plan on downtime. This can also take a while, depending on the parameters and the size of the store. Hours/days are not uncommon (for larger) and I have seen over a week (really large, > 2TB and messed up store).

If that comes back with a clean bill of health, then you do not need to run iwmigrate. Though it is still a good idea to run iwmigrate, but that is time-consuming.

praveen t n

Thanks to you all for the inputs.

Updated the plan as per suggestions:

1) Copy the content store to the new server (need to retain EA's).
2) Install the database, OD 8.1, TS 8.1 (Search, TagUI, CSSDK, WFM etc) on the new server

3) Take backup and Deactivate the new default & iwadmin stores

4) Activate the copied store

5) Run iwfsck & iwfsshrink on the COPIED store and follow-up
6) Run iwmigrate to get ONLY the required EDITIONS
7) Deactivate the existing stores

8) Activate the NEW store with only the required EDITIONS

9) Migrate users and groups
10) Migrate the workflow models, deployment conf, customizations etc.

Any info on these

1) Is it required to migrate the Interwoven Derby data?
2) As we cannot go without MetaTagger/TagUI, what is it that we need to migrate here?

6) Regarding Search and Index service, is it two separate service in 8.1? What needs to be migrated here? Is it required to migrate iw-search-collections?

7) I understand that we need to run Dependency Migration Tool. What exactly this does? Can we skip this if we don't use LiveSite?

thanks & regards,

Praveen

nipper

kingsilvestre wrote:

Any info on these

1) Is it required to migrate the Interwoven Derby data?
2) As we cannot go without MetaTagger/TagUI, what is it that we need to migrate here?
6) Regarding Search and Index service, is it two separate service in 8.1? What needs to be migrated here? Is it required to migrate iw-search-collections?
7) I understand that we need to run Dependency Migration Tool. What exactly this does? Can we skip this if we don't use LiveSite?

thanks & regards,
Praveen

Derby is EOL in 7.X and 8.X, you will need to connect to a different DB. I wouldn't bother migrating the data, don't know if there is a way to anyway. It is used for the index and search functions and you will rebuild the index.

Not certain of the status of MT, you will need to ask OpenText, likely have to install th emost recent version

Search changed significantly in the last several years. You use a product based on an old technology from Verity. That was replaced with Idol search a long time ago. I am not certain if it is a single process or 2 processes in a non-LS environment (there is overlap with Idol and LSCS).

You do not need to run the dependency management tool, but it may be useful down the road. The LS workflow automatically includes dependecies which is nice for non-LS sites too. But you would need the data (hense the app provided) and would need to change your WF to use those classes (never tried it). Whether it is worth the effort, only you will know.

Adam Stoller

kingsilvestre wrote:
Thanks to you all for the inputs.

Updated the plan as per suggestions:
[...]
3) Take backup and Deactivate the new default & iwadmin stores
[...]
10) Migrate the workflow models, deployment conf, customizations etc.

[...]

I'd be very careful with the iwadmin store - there are parts of that store that must be kept in sync with the newer product version, you're better off keeping the new iwadmin store and individually migrating (copy, OpenDeploy, whatever) the custom WFMs, etc. that you need from the workarea or staging area of either the copy of the old store or from the old server itself.