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; } } }

Migrating from Solaris to Linux

mike_jaixen

I'm noticing a lack of documentation on installing TeamSite 6.7.1 on Linux. I could assume that the Solaris documentation should be 99% correct for Linux, but I wanted to confirm that.

I've also noted that we need to make sure that 32 bit version of RedHat installed.

Any other "best practices" or suggestions folks have to offer as I get started? Should I get the environment working first before attempting to try to migrate content, or should I try copying existing content first?

Find more posts tagged with

Comments

Bill Klish

What version are you migrating from on solaris?

We are in the process of doing this and were told to run iwmigrate first. That has proved a little challenging, but for the most part things function more or less the same.

gzevin

I'm noticing a lack of documentation on installing TeamSite 6.7.1 on Linux. I could assume that the Solaris documentation should be 99% correct for Linux, but I wanted to confirm that.

I've also noted that we need to make sure that 32 bit version of RedHat installed.

Any other "best practices" or suggestions folks have to offer as I get started? Should I get the environment working first before attempting to try to migrate content, or should I try copying existing content first?

don't forget that the hardware has to be a 32-bit one as well. otherwise you will be in dangerous territory

we are wating for SP1 with 64-bit support

gzevin

What version are you migrating from on solaris?

We are in the process of doing this and were told to run iwmigrate first. That has proved a little challenging, but for the most part things function more or less the same.

I am more and more inclined not to iwmigrate at all. I think it'll be cheaper to keep one Sun box running with 6.1. on it, for reference purposes.

IWOV were promising 'easy migration'.. hot air again.....

mike_jaixen

5.5.2 (An upgrade to 6.5 got deferred last year, and now we're thinking, bite the bullet and jump to 6.7.1 on Linux and new hardware.)

The iwmigrate process doesn't sound particularly pleasant or even realistic to use; some of the documentation suggests it might take a week to run. (Like we can afford to shut things down for a week or longer...) What's the risk factor of not running iwmigrate? I was under the assumption that we could just copy the /iwstore; not sure if that was wishful thinking either on my part or Interwoven's...

nipper

Taking a chance without iwmigrate. Basically if there are backingstore issues with the old store, they propagate over.

How much history do you need ? Can you move some editions but not the whole thing ? Can you bring in an overpriced consultant ? Smiley Very Happy

If you can bring in a limited number of editions, then you can deploy from one server to another and bring the EAs. By using editions diffs, you should be able to limit the files to only the ones that changed.

HTH

Andy

firstpageonly2.rptdesign

mike_jaixen

Taking a chance without iwmigrate. Basically if there are backingstore issues with the old store, they propagate over.

How much history do you need ? Can you move some editions but not the whole thing ? Can you bring in an overpriced consultant ?

If we had budget for a consultant (let alone overpriced), we'd probably have been off of 5.5 a long time ago. Smiley Very Happy

We've had some subtle backingstore issues with some stale file handles that we've been living with, so that doesn't sound promising. We haven't been using editions though. (We do occasionally use the old versions of files though...)

nipper

Then follow Greg's advice. Take the Staging area and import it into the new server, submit, copy the workareas over and submit again (if needed).

Keep the old server for historical purposes, you should not need old versions for very long (I am guessing).

HTH

Andy

CRB

i dont think you have to shut down things during the iwmigrate... just use the latest copy of iw-store with the iw-migrate, and yes it will take days to finish and keep doing an incremental migration.... and when you are ready to do the cutover to the new box,migrate the latest content over the weekend, i think this will take u one day to do...
my strategy to migrate the latest content, is by requesting the users(business) to not make any changes to teamsite content for a the weekend (sat and sun) before you go live, publish an edition from latest and run incremental migration... then recreate areas from latest...

in case of the business has to make an urgent change while you are doing it, track the workarea and the change, then use Opendeploy to send those changes to the same location on the new one. <-- that assuming that the change is minor, or limited to few folders.. not to the entire content...

my strategy will work because i know exactly how much content i have, and how the business makes the changes... and i run enough testing on the current test box... so it all depends on how much content and how much time it will take to move or migrate the content around. and the best thing to do is to allow enough time for the upgrade...

Adam Stoller

If we had budget for a consultant (let alone overpriced), we'd probably have been off of 5.5 a long time ago.

We've had some subtle backingstore issues with some stale file handles that we've been living with, so that doesn't sound promising. We haven't been using editions though. (We do occasionally use the old versions of files though...)

If you haven't been using editions - iwmigrate will be a beast - because it operates on replaying all the events that occurred between one edition and the next (and you must have an edition prior to starting the iwmigrate because otherwise it won't work at all).

If you have the option of using an additional server (development server? perhaps work out a deal for a temporary license with IWOV for use on a "spare" machine?) - you could copy the backing store there, set up a secondary store, do the migration (for as long as it takes) and then for the final cut-over do the incremental migration there, shut down TS on both the temporary server and your to-be new production server and transfer the entire converted backing store to there ... or something like that.

Otherwise - you basically have to consider it as starting from the last version of each file and create a brand new store using either OpenDeploy (as previously suggested) or basic copy (including script to record and then re-apply EAs) - it's not a picnic either way - but ultimately it comes down to a business decision about what is needed versus what is desired.

gzevin

Then follow Greg's advice. Take the Staging area and import it into the new server, submit, copy the workareas over and submit again (if needed).

Keep the old server for historical purposes, you should not need old versions for very long (I am guessing).

one of the clients of mine have their policies in TeamSite - and this spans hundreds of editions.... But the editions need to be available - SLA does not say which platform - so it somes to business decisions - as Fish has said

mike_jaixen

don't forget that the hardware has to be a 32-bit one as well. otherwise you will be in dangerous territory

we are wating for SP1 with 64-bit support

Hmm...I believe that the hardware that we are going to be assigned is going to have "INTEL(R) XEON(TM) CPU 3.00GHZ (X86_64)"... I assume this is "not a good thing" as far as the current version of 6.7.1 goes...

gzevin

Hmm...I believe that the hardware that we are going to be assigned is going to have "INTEL(R) XEON(TM) CPU 3.00GHZ (X86_64)"... I assume this is "not a good thing" as far as the current version of 6.7.1 goes...

talk to IWOV to see whether they will support your settings.

My understanding was that IWOV has developed TS on Linux using development desktops and now they are unable to provide me a server that would support it in production environment. I am actually yet to see ANY true 32-bit server that is commercially available. IWOV has not been able so far tell me what they think their clients are supposed to buy to be fully supported.

As I said, my client is wating for SP1 to install TS on 64-bit hardware running 64-bit Linux.

or.. you might want to run it under VMWARE