I am currently running Scalix 11.1.0 on a Fedora 5 server. That is the way it was sold to me. I need to upgrade to 11.4 so Outlook 2007 will work with it better. Can I move this to Centos and upgrade to 11.4 in one move or do I need to move to Centos running 11.1, then upgrade to 11.4. Also, my LVID is 2008-06-11. The way I read it, since 11.4 came out before my MVID date I can upgrade without buying another licence. Is that correct.
My last question is, by using rsync to copy my /etc/opt/scalix directory to the new machine, it should copy all my setting and users, but will this also move the existing email.
Moviing to Centos
Moderators: ScalixSupport, admin
-
kanderson
Your LVID should cover it as long as the LVID in the release is older. Check the release notes.
Build the new machine with the same FQDN but a different IP.
I generally recommend installing Scalix on the new machine, and then setting it so Scalix doesn't autostart (scalix, scalix-tomcat, scalix-postgresql). Then rename /var/opt/scalix/?? to something like junk, or just delete it.
Rsync your data (/var/opt/scalix/??) over. That will copy the users, all the mail, contacts, etc. This is just for prep. It takes a while, but this can happen while the old server is up.
Stop Scalix on the old server. Rsync it one last time. This will run very quickly. Power down the old server.
Start the Scalix installer and uninstall everything, leaving the message store, but deleting postgres.
Change the IP on your new server to the same IP as the old server. Restart it.
Run the Scalix installer, and install normally. It will "see" the mailstore and upgrade it if necessary.
Test.
My experience is that if the Installer runs and sees an existing message store, often it will skip installing a few key files. (instance.cfg, for example) Installing it uselessly in advance seems to be easier.
Deleting and recreating Postgres is MUCH easier than upgrading it. There's no vital data in there, so just let it get recreated after you do the install. Again, I like easy.
Kev.
Build the new machine with the same FQDN but a different IP.
I generally recommend installing Scalix on the new machine, and then setting it so Scalix doesn't autostart (scalix, scalix-tomcat, scalix-postgresql). Then rename /var/opt/scalix/?? to something like junk, or just delete it.
Rsync your data (/var/opt/scalix/??) over. That will copy the users, all the mail, contacts, etc. This is just for prep. It takes a while, but this can happen while the old server is up.
Stop Scalix on the old server. Rsync it one last time. This will run very quickly. Power down the old server.
Start the Scalix installer and uninstall everything, leaving the message store, but deleting postgres.
Change the IP on your new server to the same IP as the old server. Restart it.
Run the Scalix installer, and install normally. It will "see" the mailstore and upgrade it if necessary.
Test.
My experience is that if the Installer runs and sees an existing message store, often it will skip installing a few key files. (instance.cfg, for example) Installing it uselessly in advance seems to be easier.
Deleting and recreating Postgres is MUCH easier than upgrading it. There's no vital data in there, so just let it get recreated after you do the install. Again, I like easy.
Kev.
-
lowroller
Who is online
Users browsing this forum: No registered users and 3 guests