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

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.

Find more posts tagged with

Comments

nipper

This should work:


#!/bin/sh
eval 'exec `/usr/bin/iwgethome`/iw-perl/bin/iwperl -x -S $0 ${1+"$@}';
#!iwperl -w
use TeamSite::Config;
(my $iwmnt=TeamSite::Config::iwgetmount()) =~ tr|\\|/|;
$start = $iwmnt."/default/main";
readSub($start);
sub readSub {
my $dir=shift;
opendir (DIR, $dir) || die "Cannot opendir $dir: $!";
my @list = readdir (DIR);
closedir(DIR);
foreach my $folder (@list) {
next if ($folder =~ m|STAGING|);
next if ($folder =~ m|EDITION|);
next if ($folder =~ m|\.\.|);
next if ($folder =~ m|\.|);
if ($folder =~ m|WORKAREA|) {
opendir (DIR, $dir."/".$folder) || die "Cannot opendir $dir"."/"."$folder: $!";
my @workareas = readdir (DIR);
closedir(DIR);
foreach (@workareas) {
next if (m|\.\.|);
next if (m|\.|);
print "$dir/$folder/$_\n";
}
next;
}
readSub($dir."/".$folder);
}
}

Migrateduser

Thanks for the quick reply & the script nipper!

Works like a charm & runs extremely fast!

Any hints on how I could modify it to produce a list of branches? I'm currently using this code to [manually] iterate through my branches.

IWMNT=`iwgetmount`
VPATH="$IWMNT/internet"

for i in `./iwlist $VPATH`; do ATTRIB=`./iwattrib $VPATH/$i branchcount`; WORKAREAS=`./iwattrib $VPATH/$i workareacount`; echo $VPATH"/"$i":"$ATTRIB":"$WORKAREAS; done

...which returns
/iwmnt/internet/main:10:0

I know I have 10 branches & 0 WORKAREAs so I now do

VPATH="$IWMNT/internet/main"

for i in `./iwlist $VPATH`; do ATTRIB=`./iwattrib $VPATH/$i branchcount`; WORKAREAS=`./iwattrib $VPATH/$i workareacount`; echo $VPATH"/"$i":"$ATTRIB":"$WORKAREAS; done

...which gives me a new list of branches with sub-branch count & WORKAREA count.

I keep repeating this process until my "branchcount" = 0.

BTW, where can I fins documentation on the Perl modules that come with TeamSite & some of the other InterWoven products (e.g. OpenDeploy).

Thanks again!

Adam Stoller

This should work:
...

Ahh - haven't had fun writing code in a while - I like this version (which will just show branches):

use strict;
use warnings;
use TeamSite::Config;
use TeamSite:irwalk;

my $iwmount = TeamSite::Config::iwgetmount();
my $start_dir = "$iwmount/default/main";
my $obj = TeamSite:irwalk->new(dir_handler => \&dh);
$obj->dirwalk($start_dir);
exit 0;

sub dh {
    my ($self, $dir) = @_;
    return 0 if ($dir =~ m{/(EDITION|WORKAREA|STAGING)$});
    $dir =~ s|^$iwmount||;
    warn("$dir\n");
    return 1;
}

Adam Stoller

BTW, where can I fins documentation on the Perl modules that come with TeamSite & some of the other InterWoven products (e.g. OpenDeploy).

Documentation on Perl modules is (mostly) in POD format in the modules themselves, so running perldoc should do the trick. The modules are located within

iwhome/iw-perl/vendor/lib/TeamSite

In addition, the perldoc for the modules which are located in the PT subdirectory of the above, can be found in HTML format by going to

http://ts-server/iw/help/tst/pt

The one module that I know does not have good documentation is

TeamSite::Flexroles

- for that, you'll have to actually read the comments in the code.

As for product manuals - you get those via Autonomy Interwoven Support.

Migrateduser

Fish, thanks for the replies & the code snipet.

nipper

Ahh - haven't had fun writing code in a while - I like this version (which will just show branches):

use strict;
use warnings;
use TeamSite::Config;
use TeamSite:irwalk;

my $iwmount = TeamSite::Config::iwgetmount();
my $start_dir = "$iwmount/default/main";
my $obj = TeamSite:irwalk->new(dir_handler => \&dh);
$obj->dirwalk($start_dir);
exit 0;

sub dh {
my ($self, $dir) = @_;
return 0 if ($dir =~ m{/(EDITION|WORKAREA|STAGING)$});
$dir =~ s|^$iwmount||;
warn("$dir\n");
return 1;
}

My code was much more brute force. I typically use File::Find but figured the brute force method will be more than fast enough and likely easier for Bill to understand and modify.

Migrateduser

Don't worry... I'm not grading anyone or judging anyone's scripting techniques. :-)

I had 2 requirements: correct output & speed.

Both scripts met both requirements. Thanks to both of you for taking the time to post those scripts.

It was nice to see both approaches.