These are just short notes on the basic procedure to upgrade a Scalix messaging server.
You might use this procedure if you were replacing the hardware you run your Scalix insallation on. You might also use it when upgrading the underlying OS or as part of disaster recovery.
If you are just upgrading Scalix itself, this can normally be done in place with only an extra backup to comfort you.
Note the UID and GID of the 'scalix' User
If you are moving to new hardware or a new OS installation, you need to recreate the 'scalix' user with the same userid and groupid before running the Scalix installer.
The ombackup script creates a small text file with this information in the backup folder. Otherwise, take a look in /etc/passwd and note the UID and GID.
Backup Scalix
Note: the ombackup script performs this sort of backup as well as backing up individual mailboxes.
Stop Scalix with the following commands:
/etc/init.d/scalix stop
/etc/init.d/scalix-postgres stop
/etc/init.d/scalix-tomcat stop
Then tar up the /var/opt/scalix directory, preserving permissions with something like:
tar -zcvpf /backup.tar.gz /var/opt/scalix
Upgrade the Hardware or OS
Copy (or scp) the tarball to somewhere else, test it to be sure you have it all, then go ahead with the hardware replacement or OS install.
Restore Scalix
Finally, copy back and untar /var/opt/scalix on the new server or OS.
Before running the Scalix installer, recreate the 'scalix' user on the new system with the same UID and GID as on the previous installation.
You can and should normally download and install the latest Scalix version unless you're using external authentication such as Active Directory, or OpenLDAP, in which case do a bit more research first.
| < Prev | Next > |
|---|
