Server migration (Linux -> Linux)

Migration guide

To migrate, you first must make sure you have a backup of everything, the mail, the groupware database, etc. To be safe, backup the entire /Icewarp folder, so you know you have a full backup.

Migration steps:

1. Install version same version on both servers.

2. During migration, you can use the same license on your production server for up to 30 days in parallel. On the new server activate your license using the remote console - Help - License - Activate License... - insert Order ID from the old server.

3. Activation of Order ID using tool.sh

/opt/icewarp/tool.sh modify system c_onlinelicense EUR2020xxxx-xxxxxx-xxxxx

4. Copy over the following folders from the old to the new server:
Mail (must be copied through a tool that saves timestamps - rsync)
Spam (if using the default anti-spam database)
Calendar (if using the default groupware database)
Config

5. When you successfully migrate everything and have servers on the same version, to upgrade to the latest IceWarp version, you should always install several versions before getting to the latest. (for example, if you are running on v11 and older, first install v11.4.6, then v12.2, followed by v13.0 and 13.0.3.10 to finally land on v14.x)

After doing this you will be running the same settings, users, domains, etc. on the new server.

*** If using the file system for accounts ***

Export users and domains and copy them on the new server:

/opt/icewarp/tool.sh export account "*@*" u_backup > /bck_acc_backup.csv
/opt/icewarp/tool.sh export domain "*" d_backup > /bck_dom_backup.csv

Import of the users and domains from the copied file:

/opt/icewarp/tool.sh import account /bck_acc_backup.csv
/opt/icewarp/tool.sh import domain /bck_dom_backup.csv

*** For the creation of DB in MySQL on the new server ***

(create collation based on the location, more - https://mariadb.com/kb/en/supported-character-sets-and-collations/):

CREATE DATABASE accounts default charset utf8mb4 collate utf8mb4_unicode_ci;
CREATE DATABASE antispam default charset utf8mb4 collate utf8mb4_unicode_ci;
CREATE DATABASE groupware default charset utf8mb4 collate utf8mb4_unicode_ci;
CREATE DATABASE webclient default charset utf8mb4 collate utf8mb4_unicode_ci;
CREATE DATABASE eas default charset utf8mb4 collate utf8mb4_unicode_ci;
CREATE DATABASE dircache default charset utf8mb4 collate utf8mb4_unicode_ci;
CREATE DATABASE asreports default charset utf8mb4 collate utf8mb4_unicode_ci;

*** If using the MySQL databases do a DUMP of DB ******

1. For export of DB do: mysqldump -hDB_HOST -uDB_USER -pDB_PASSWORD --opt --quote-names --skip-set-charset --default-character-set=utf8mb4 --single-transaction EXAMPLEOFDB > /exmpleofdb.sql
2. This will create a DUMP in root (/) location
3. For import of DB to the new server do the following: mysql -hDB_HOST -uDB_USER -pDB_PASSWORD --default-character-set=utf8mb4 exampleofdb < /exampleofdb.sql

You can migrate only these DB's: accounts, antispam, antispam-reports, groupware. The rest of the databases: directory cache, webclient, and EAS are caches and it's not necessary to migrate them.

After this switch value in API console:
system.mysqldefaultcharset utf8mb4

*** After migration ***

If you didn't migrate the directory cache then start a refresh of the dir cache for the whole server in System - Advanced - Directory Cache