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

upgrade from 452 to 6.1

sriram

Hi,

We are looking to upgrade from 45.2 to 6.1. Do we need to upgrade 5.5.2 first and then 6.1 or can upgrade directly to 6.1. Can we directly convert backing store from 4.5.2 to 6.1

Thanks

Find more posts tagged with

Comments

gzevin

from FAQ on 6 upgrades (available at support site, BTW):

1. What is the upgrade process to TeamSite Content Server 6.0 going to be?

TeamSite Content Server 6.0 will be an "upgrade" install for all customers on TeamSite Content Server 5.5.2. There will be no backing store conversion necessary as there was in the v5.0 to v5.5.2 upgrade process. If customers are not yet on TeamSite Content Server 5.5.2, they will first have to complete the backing store conversion before upgrade to TeamSite Content Server 6.0.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

sriram

Ok I understand, but In one of the forums somebody suggested that we can directly upgrade from 502 sp2 to 6.1 without going through 5.5.2. Is it possible to upgrade from 452 to 6.1. If we convert backing store what are the consequences.

Thanks!!!

Migrateduser

Tell you what, why don't you do a case study and come back and tell us what happens when you do that. You clearly don't like the valid answer you get, so please go ahead and force the square peg into the round hole. Have fun!

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

nipper

& don't bother with those pesky backups, they just get in the way

Migrateduser

Yikes... if anything, I would upgrade from 4.5.2 to 5.0.1 to 5.5.2 to 6.1. It might mean more steps than necessary but might wind up being a whole lot less work!

Adam Stoller

In order to go from 5.0.2 SP1 to 6.1 you need to have *two* servers - because you need to run iwconvert to update the backing store from the 5.0.2 to the 6.1 server (I did this last week - on Solaris - and other than some annoying - but apparently harmless - error-type messages that show up during the conversion process it actually went very smoothly).

I do not believe you can "upgrade" a single 5.0.2 server into a 6.1 server.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

ela

I would also suggest this, if he's got the possibility.

We did an upgrade from 4.5.1 to 5.5.2 last year, but since there was only one production and one development/test server, we decided to go directly from 4.5.1 to 5.5.2. We knew this would mean loosing the file history and the extended attributes, but decided to do it anyway. Our unix admin copied all the content from the production server and I added the extended attributes with a script. Then we had a test period, before the development server became the production server. Files modified or created in the meantime were copied over. The old production server, now the development server, could be used as a backup for a while.

Eldbjoerg