Post-migration processes

First of all, before starting the migration process it is needed to read the guide on our website (http://dl.icewarp.com/documentation/server/tools/IceWarp_Migrator_Guide.pdf) by this guide you could find all aspects of the migration process.

In this KB article, we will just cover some questions regarding the post migration steps, to restore the target server.

First of all, what you need to know, the target server is stopped. This is done in a similar manner as the source server stop. Modules are not stopped, but services are disabled. Because it is necessary to have RCP working, the web is disabled using the API variable of c_mail_control_disableweb, but c_mail_control_active remains enabled. Thus, there is a green circle in the config services list showing, that web is running. However, only RCP is available – no HTTP service. This can be confusing for an admin that does not finish the migration and ends with a disabled server. The web has to be re-enabled via API, in this case, open the API console from File > API console (or just shortcut Shift + Ctrl + A). Type in filter c_mail_control_disableweb and change the value from true to false, this will enable WebClient.

The second step is testing the availability of features in WebClient. Try to create a meeting in Calendar, send and receive messages, and create a new Task. Also, try to upload and create files in Documents.

If you store data in MySQL, MS SQL, Oracle, or another relational database management system, please make sure that all configurations in the console for DB’s were correctly added at the target server.