How can I upgrade my CoS (Class of Service) installation?
- atmail CoS
Requirement to upgrade CoS version.
CoS v2.x can be installed on top of v1.x, which will leave all existing CoS 1.x data unchanged. This document covers how to migrate existing data from CoS 1.x into CoS 2.x.
Extra Database privileges
Migration process needs mysql database user having following privileges
|cos_default, cos_accounts, cos_bundle, cos_profile, cos_profile_settings, cos_service_definition, cos_account_settings||full control|
|other||create temporary table|
Please make sure your mailserver database backup has been done.
Login to your pre-existing atmail customer portal account. Download the atmail CoS software packages from within the atmail client portal.
Install CoS v2
Install downloaded package via yum.
# yum install atmail-cosadm-<version>.x86_64.rpm -y -q
Upgrade mailserver database
CoS shares it's database with mailserver. Please use Cos Database Schema v2.1.x to update mailserver database.
For on-premises installation, CoS needs to create a default virtual customer in order to function properly. We call this process 'initialise onprem'.
Please run below command:
# cosadm init-onprem
Create Profiles to cover legacy settings
Since CoS v2.x, a profile is used to control CoS settings for each user or domain. A profile is a set of preset CoS settings.
CoS profiles can be managed via the mail server admin portal. Login to mail server admin panel, go to Services > COS SERVICE > Manage Profile.
In Select a profile field, select
Create new profile
Then input name (e.g Free) in New profile name area
Overwrite any system default settings as needed,
Then Save profile
Repeat above step to create other profiles.
Profiles need to be created to cover all current scenarios. For example:
There are some services (e.g total_quota, calendars etc), which are supported since CoS v2, should be assigned to proper profiles in above list, if system default value doesn't suit.
Above profile names are just examples, which can be changed to any text.
Below command will perform the upgrade
# cosadm upgrade
If the upgrade goes well, below message will be displayed
# cosadm upgrade Congratulations! CoS upgrade completed.
The upgrading script will try to match cos 1.x user settings into cos 2.x profile which should have been created. If it cannot find proper profile to match, it will abort with below error.
Please create a profile to cover the combination: <settings>
If multiple profiles match same cos 1.x settings, the first one found by the upgrading script will be chosen and the rests will be ignored.