TeamSite v5.5.2 to v6.7.2 (Solaris to Solaris)

System

Our migration strategy is:
- perform a new install of v6.7.2
- copy the v5.5.2 backing store to the new v6.7.2 server (rsync about 400GB across the WAN)
- run "iwmigrate" to mograte the v5.5.2 backing store to v6.7.2 content store


We're following the migration instructions documented in KB article 55358 (Instructions for Migrating or Recreating a Backing Store on TeamSite 6.5 (or higher).

We DO NOT use "-d" option on "iwmigrate". We have iterated through the branching structure using "iwlist" & "iwattrib" to get a list of all branches in the backing store. We run "iwmigrate" on each of these branches (top down).

At step 4, we're taking option a) because we need to preserve version history over to the v6.7.2 content store.

Up to this point, all goes well. "iwmigrate" takes some time to migrate over the content but that's expected due to the size. We do run "iwfsshrink" a lot during the migration process to keep the v6.7.2 content stores "lean".

We hit the wall trying to migrate over WORKAREAs. Using "iwmigrate -d -w -only" takes *forever*. I've seen some WORKAREAs take nearly 24 hours to migrate.

So, I'm looking at using "iwlistmod" to get the WORKAREA data from the v5.5.2 backing store then using "iwmkwa" & "iwcp" to bring over the changes to the v6.7.2 content store.

Has anyone else run into this problem? Anyone have a handy Perl script that will iterate through a branch structure & find all the WORKAREAs?

Thanks in advance.