5.5.2 Backingstore conversion

We are in the process of finalizing plans for our upgrade to TeamSite 5.5.2. I am trying to come up with revised plan for the backingstore conversion, due to timing issues. And would like to get some additional information.

Does the newly converted backingstore maintain information regarding the server from which it was created? For example if you have two servers with identical backingstores and begin converting from one server then a final conversion from a second server will the conversion script assume that it is a new conversion and start over? Or will it verify chain of editions and go to the next with no problem? If it does maintain information is it the server name or license information?

Opposite question. Can you start the conversion on one destination server, then prior to the final conversion mv the iw-store directories to a different destination server, then start the final conversion?

I will be testing our final plan, but since the conversion process takes so long, didn't want to waste time on something that by design would fail.
Thanks,
Gwen

Find more posts tagged with

Comments

Adam Stoller

I'm not sure that what you are proposing (or seem to be proposing) would work. I'm not sure it won't work - but I'd be very skeptical.

Yes, converting a good sized backing store will take time - but as you can do the conversions while the old server is running - consider planning to start the process sufficiently before the cut-over date. If you take the time to plan it out at the beginning you could set up processes to perform conversions of 1 branch each night, or even N editions of 1 branch each night. By the time you get closer to your cut-over date, you can be doing full conversions of all the branches and the conversion process will just pickup from wherever it last left off - and it won't take that much time.

I think that's a far more reliable way of doing it than trying to play around with switching source and/or target servers in mid-stream.

--fish
(Interwoven Senior Technical Consultant)

gwen1

Thank you for responding. We are not purchasing a new server(s), I had the plan all worked out based on some initial testing on dev teamsite. (converting our production server from the remote failover production server) But testing last week indicated that the time for the conversion was longer and we may be pushing to get everything installed/tested during our implementation. I will most likely end up converting in stages on our UA teamsite server and move to production. More testing is scheduled for this week, on a more robust server so we will see a more accurate test of the time it will take.
Thanks,
Gwen

Adam Stoller

Also try to make sure that the two servers are on the same network - i.e. not going through routers and hubs and such - the more direct the network, the fatter the pipe - the faster the transfer process will go...

--fish
(Interwoven Senior Technical Consultant)

gwen1

Have any problems arisen with converting on a different version of Solaris? My production server is Solaris 8 but I have another server on same subnet which I might be able to install TeamSite 5.5.2 for the conversion, but it is on Solaris 2.6. Following conversion & software installation I woud move newly converted backingstore back to production server. This is one option I am considering. We have other servers just not on the right subnet, but we may just accept the slower conversion rate.

Typically does conversion run faster on a TS 5.5.2 server with a lot of CPU power or is that not a factor at all? Did not really see reference other than min requirments for the destination server.

Thanks,
Gwen

Adam Stoller

I don't believe that using a 2.6 system for the 5.5.2 conversion should be a problem.

I'm not sure about the CPU question - I'd imagine that, as in most cases, more is better - I'm not sure how significant a role it plays in the conversion. I'd imagine it does play a part since we're talking about doing a bunch of system reads/writes - but I think network optimization is of higher importance (unless you're talking about something with virtually no CPU power...)

--fish
(Interwoven Senior Technical Consultant)

gwen1

Thank you for your assistance. You have been very helpful.

Gwen

Migrateduser

Hi,

I need some clarification regarding MultiStore in Teamsite5.5.2.We have migarted to TS5.5.2. Right we have only one backing store /default/main

We have three branches on same server and they are not related. So i am planning to use diff. stores for each branch. Is it possible ?? I think it is So what is best way to do

If i use diff. stores can i use diff. config files like iw.cfg and templating.cfg ??

Thanx in advance

gwen1

iw.cfg, templating.cfg --only one config file per TS server. In fact your stores are defined in the iw.cfg file. TS will not utilize the additional stores if they are not defined in the file. There was good documentation in the upgrade supplement documentation on the multistores, determining how to implement, etc.

Gwen

txtLookupSrc.zip

Output.pdf

Adam Stoller

Also- while you're planning to use different stores - did you purchase license for the different stores?
You may need to check with your local Interwoven Sales representative before you go too far down this line just to make sure you're not circumventing licensing issues.

--fish
(Interwoven Senior Technical Consultant)