Scalix Forums

Hi!

Moving from 5 user on a test server to 25 user on new server. Tarred up /var/opt/scalix on old, then untarred the original DB(s) on the new server (with installed 9.4.2.4 version).

OMRC screamed version inconsistancies between sys and lib. Copied old /opt/scalix/lib* to new and did sxmodfqdn (new server name). OMRC no problems...

All works as expected BUT...

The license mechanism obviously exists in /opt/scalix/lib as I'm unable to exceed the 5 user threshold.

Which file needs to be the 9.4.2.4 version??

Thank you!

I answered my own question...

The objective was to take a working server with the 5 user version of Community edition, keep it running, install the 25 user version on a new server, backup the directory and message stores to the new server and get it running with the original server configuration and data...

After installing the new version on a new server and restoring the old data to the new server the following ocurred:

OMRC screamed version inconsistancies between sys and lib. Copied old /opt/scalix/lib* to new and did sxmodfqdn (new server name). OMRC no problems...

All works as expected BUT...

The license mechanism obviously exists in /opt/scalix/lib as I'm unable to exceed the 5 user threshold.

Which file needs to be the 9.4.2.4 version??

The license indicator is located somewhere within /opt/scalix/lib. By keeping the new versions /opt/scalix/lib files the version inconsistancies error ocurred. Within /optscalix/lib is a "version" text file. Simply changing the version number to the older version in text file eliminated the version inconsistancies error and we're up and running with the old data on the new version...

Most if not all configuration dynamic information (configuration, user attributes, email, etc.) exists in /var/opt/scalix...

All static server code exists in /opt/scalix...

The version lables for each area are in :

/var/opt/scalix/sys/version for the server configuration
/opt/scalix/lib/version for the server code

It's irrelevant what numbers are in these files as long as their the same numbers in both files.

:D

You are correct in the fact that the version files need to match but not in the solution.

The server will refuse to start up if the version files do not match because the binaries may be expecting some files to contain data that is only available in that release. If you copy a previous version of a message store to /var/opt/scalix, you are risking things misbehaving.

The solution in every case is to run the command: and this will run through any routines necessary to upgrade the data and config files to the correct formats. It will also update the version files to match.

Cheers

Dave

That's it!

You told me this a long time ago and I couldn't find it! Hence the work around...

Should I go ahead and run ompatchom -a anyway?? All seems to work properly...

You know who this is right??? I don't work for *& anymore!