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 issues for TS Solaris 6.72 to Linux 7.0?

dchristie

We're currently running TS 6.7.2 Solaris and are considering switching our next upgrade over to Linux, to TS 7.0. But, wondering of any major pitfalls to look out for, especially when it comes to migrating the Solaris 6.7.2 store? I would think that it would be fine, but just curious if anyone knows of issues with this? Thanks.

Find more posts tagged with

Comments

nipper

The backing store can be copied from Solaris to Linux. I have done that. Whether you really want to or not is another story.

You need to have a solid plan to go forward.

One point, many 6.X implementations use something like /apps/iw-home however 7.X FORCES the new install to be /somepath/TeamSite

That can seriously affect things. If this is true you have to install TS 6.7.2 on Linux in iw-home and then run the upgrade.

I also hope you mean 7.2.1 and not 7.0

Also consider some help, this is not trivial.

Andy

Rick Poulin

The backing store can be copied from Solaris to Linux. I have done that. Whether you really want to or not is another story.

I can also confirm that this works fine. I've done a TS6.5/Solaris9 to TS7.1/RHEL5.3 without any major problems. Note though that for some reason I won't go into, the admins were originally carrying the content store across a Windows server as an intermediary (complicated network), which actually introduced a very subtle content store corruption what wasn't detected with iwfsck (in the form of random truncations of files in random versions of them). Make sure the integrity of your store remains intact (say, by gzipping it and comparing byte size across the transfer) to avoid surprises.

dchristie

The backing store can be copied from Solaris to Linux. I have done that. Whether you really want to or not is another story.

You need to have a solid plan to go forward.

One point, many 6.X implementations use something like /apps/iw-home however 7.X FORCES the new install to be /somepath/TeamSite

That can seriously affect things. If this is true you have to install TS 6.7.2 on Linux in iw-home and then run the upgrade.

I also hope you mean 7.2.1 and not 7.0

Also consider some help, this is not trivial.

Andy

Acutally, we were thinking 7.2.0. Any advantage to going with 7.2.1? Managament here usually opts for a "one-version-behind" methodology.

testingmynewCsvFile.csv

Rick Poulin

I haven't heard of any issues/bugs in 7.2.1 that weren't also in 7.2.0. 721 contains a fix to ActiveMQ (the new messaging system for the event subsys) which corrects a bug that was particularly annoying in 710/720. It's also been around for quite a while, and a number of people are using it as you can see on these forums (there's almost no 7.2.0 -- others are on 7.1 or 6.x). 7.3 must be about to ship in the next few months so maybe that satisfies the "one version behind" Smiley Happy