Solution
The upgrade procedure of your Axigen Mail Server installation must be performed step by step, going through all the intermediary upgrades released up to the latest version. This is required as important structural changes appear from one major release to the next, due to the features that get included in the product.
Upgrade from 1.x to 2.x
If you have a 1.x Axigen version, you cannot upgrade directly to a 3.x or newer version, without upgrading your storage to a 2.x version. So, you must use the tools provided in the AXIGEN 2.x installation kit, in order to first upgrade your storage to a 2.x version. To do that, first download the corresponding tools from the AXIGEN Support Team FTP site.
After downloading them, copy them into the same location as the 'axigen' binary:
For Linux/Solaris: /opt/axigen/bin
For FreeBSD/OpenBSD: /usr/local/bin
For NetBSD: /usr/pkg/bin
For safety, backup the axigen.cfg file corresponding to your 1.x version (located in /var/opt/axigen/run for Linux/Solaris and /var/axigen/run for BSDs), as the upgrade utility will modify this file to automatically register the new domain locations.
After this, stop the axigen daemon, set the execution bit:
chmod +x upgrade-storage
chmod +x upgrade.sh
and then run the ./upgrade.sh script from the specified location.
IMPORTANT: Do not uninstall your 1.x version, as you need to make sure that the upgrade is being done without problems.
For each domain found, the upgrade utility will try to upgrade it into a new domain location, in AXIGEN's data directory:
For Linux/Solaris: /var/opt/axigen/domains/$upgraded_domain
For BSDs: /var/axigen/domains/$upgraded_domain
After the upgrade is finished successfully, you may upgrade your 1.x version with a one newer than 2.x. Also, you can delete the unnecessary files downloaded earlier.
Upgrade from 2.x to 3.x
If you are running version 2.x of the product, the upgrade to version 3.x is very straight forward:
1. Download the installation package for Axigen version 3.0.1 required for your distro / OS.
2. Stop the 'axigen' service.
3. Use the system package manager to upgrade the installed version to the one you just downloaded.
4. Start up again the 'axigen' service.
NOTE: You will notice that the settings you previously had have all been migrated and no further configuration is required.
Upgrade from 3.x to 4.x
To upgrade your 3.x version of Axigen to version 4.x, you need to perform the following steps:
1. Download the installation package for Axigen version 4.0.2 required for your distro / OS.
2. Stop the 'axigen' service.
3. Remove the 'axigenmilter' package if you have it installed.
4. Remove the 'axigendk' package if you have it installed.
5. Use the system package manager to upgrade the installed version to the one you just downloaded.
6. Start up the 'axigen' service again.
Upgrade from 4.x to 5.x
NOTE: Prior to the upgrade process, the mail storage and its objects need to be upgraded. To perform this upgrade, connect to the CLI interface and for each domain use these commands:
upgrade storage
commit
The package upgrade process follows:
1. Download the installation package for Axigen version 5.0.2 required for your distro / OS.
2. Stop the 'axigen' service.
3. Use the system package manager to upgrade the installed version to the one you just downloaded.
4. Start up again the 'axigen' service.
Upgrade from 5.x to 6.x
To upgrade your 5.x version of Axigen to version 6.x, you need to perform the following steps:
1. Download the installation package for Axigen version 6.0.0 required for your distro / OS.
2. Stop the 'axigen' service.
3. Use the system package manager to upgrade the installed version to the one you just downloaded.
4. Start up again the 'axigen' service.
NOTE: As a general rule, after an upgrade to any version is finished, the server should run at least for some time to make sure the settings are migrated. This can take some time especially with larger storages.
IMPORTANT: Always keep a backup of the old Axigen configuration file in case an upgrade goes wrong.
PACKAGE DOWNLOAD NOTES: You may find you cannot locate / download a specific package required by the upgrade procedure. If you encounter this issue, contact the support department for a link to the specific package you require.