Install 11.2 on sue 10.1

[friedmar]

Hi everybody,

is ther a way to upgrade to 11.2 on opensuse 10.1 without upgrading opensuse to 10.2?

Thank you

Friedmar

[techsharp]

Friedmar -

Take a look at this thread: viewtopic.php?t=8830

Florian says "... updated community platform support (Fedora 7 replacing FC5 and OpenSUSE 10.2 replacing OpenSUSE 10.1) "

It looks like support is for now for OpenSUSE 10.2.

[friedmar]

techsharp,

I have read that article and understand that support is now for suse 10.2.

What I want to know is if 11.2 will also work with suse 10.1 if I install it with the --override-release=id option.

Due to some reason I need to migrate to 10.2 but are not able to upgrade my suse to 10.2 at present time.

Regards,

Friedmar

[florian]

we haven't done any testing of such install on older platform versions and very obviously will not provide support for such a system.

Florian.

[gravety]

I would be interested to know if anyone has done this as I am in the same position

[willi-uce]

Hello,
I'm in the same position and I think that there are many users who want to upgrade to 11.2 on an suse 10.1 system. Scalix 11.1 was not supported on opensuse 10.2, so I installed opensuse 10.1. We want to upgrade to scalix 11.2 because we have some troubles with 11.1.

It's a little bit funny that Florian says this is an older system, because the installation on newer system (10.2) was not supported.

Willi

[Valerion]

Remember that Scalix only supports OSS and Fedora for evaluation purposes. As such, they only support (and test) one version of each, which is usually chosen somewhere in the development cycle for a release.

To keep up with Scalix you will have to keep upgrading OSS as well.

[florian]

It's a little bit funny that Florian says this is an older system, because the installation on newer system (10.2) was not supported.

well, i guess that's what life in IT space is like - today's news is yesterdays rotten fish. It's fast. those OSS distros run at a fast pace and testing and supporting them is a major effort, more than one we just can't handle and that's why valerion is right. For more stable environments, please consider using an enterprise distro like SLES or RHEL - we've been supporting RHEL4 since it first came out and are planning to do so for at least 1,5 or 2 years, even though RHEL5 is readily available. The upgrade cycles of those distros play much better with the long-term stability requirements of a message system, especially one used inside companies.

Hope this helps,
Florian.

[jaime.pinto]

Just out of curiosity, why would there be a reluctance on upgrading opensuse 10.1 to 10.2 at the time of the scalix upgrade. is there something holding you back, such as cost of opensuse or is it something else?

I say this because I always considered the scalix server as an appliance, almost to the exclusion of everything else. So why wouldn't any one want to maintain a well oiled and streamlined engine within the recommenced configuration by scalix?

[mhoroschun]

Just out of curiosity, why would there be a reluctance on upgrading opensuse 10.1 to 10.2 at the time of the scalix upgrade. is there something holding you back, such as cost of opensuse or is it something else?

In my case, I won't try that because of the warning on the openSUSE site regarding upgrading:

Updating from one version to another is unsupported and may result in system inconsistencies. Performing distribution upgrades in the running system increases the risk of causing damage.

So, it looks like I'm going to have to blow the machine away and start again, and this time I'm going to use SLES10. I should have done that in the first place, but I guess I didn't read the "evaluation purposes only" bit closely enough!

Any suggestions on actually doing this? If I build up a test box with SLES10, and copy the /opt/scalix and /var/opt/scalix directories across, and then do an install, should I be able to successfully upgrade?

[florian]

You never copy /opt/scalix because that has the binaries, which are actually version specific.

What I prefer to do:

1. Build the new system, if possible preserve hostname and IP address or at least the hostname (otherweise, check the hostname change procedure at wiki.scalix.com)
2. Make sure you create user and group scalix with the SAME Linux user and group id as on the old system (copy entries in /etc/passwd, /etc/shadow, /etc/group)
3. Copy /etc/opt/scalix/instance.cfg and the whole /var/opt/scalix/??/s directory. The other directories under /var/opt/scalix/?? contain config and logfile information for the Scalix applications, however, unless you've customized the configuration heavily within those files, you're better of to have the installer generate fresh ones.
4. Run Scalix Installer. It should see/find the existing message store and pick it up.

Other people prefer to run a fresh install on a blank box and then to shut scalix down and copy over the "s" directory - I don't have a very strong opinion, but the above has always worked for me.

SLES10 is a very solid platform for Scalix, actually my own production account is sitting on a box running SLES10.

Cheers,
Florian.

[jaime.pinto]

... and copy the .... /var/opt/scalix directories across ...

Word of caution, do not use copy. Use rsync or prepare a tarfile instead, and untar it later.

[florian]

... well ... use a copy method that preserves all of permissions, ownership, etc.

thanks Jaime...

[swagner]

hello,

today we want to switch to the new scalix version from 11.1 to 11.2.
But we are changing from opensuse 10.1 to SLES 10 too.

We have installed the new Server with same hostname, IP etc and already installed scalix.
Now we saw in this topic that we should first rsync the files and then install scalix.

Which is the better way for our situation:
1. Uninstall scalix - rsync an reinstall ?
2. rsync and reconfigure?
3. Other possibility?

Regards,
Sven

[jaime.pinto]

Uninstall scalix - rsync an reinstall

Be very careful with this. Last time we uninstalled scalix it also "uninstalled" the mailstore, so it doesn't seem like a very safe thing to do with your primary mail server.