Introduction

Starting from version 9.1, Community Server uses MySQL v. 5.7 instead of MySQL v. 5.5 that had been used in earlier versions. Besides, a different installation scheme is used when MySQL is running in a separate container. If your current portal version has been installed using the old installation scheme, the Mail Server database is located within the Mail Server container and the Community Server database is in the Community Server container. According to the new installation scheme, the MySQL container contains both the Community Server database (named 'onlyoffice') and the Mail Server database (named 'onlyoffice_mailserver').

The first section of this article describes the update procedure for old versions that have been installed using the old installation scheme with MySQL databases located within the Mail Server/Community Server containers.

If you want to update your Mail Server integrated with an old Community Server version (lower than 9.1) to the latest available version that uses MySQL v. 5.7 running in a separate container, please refer to the second section.

Updating to versions that use MySQL 5.5 within the Mail Server/Community Server containers

Step 1: Check if all the external data storage folders are mounted

Make sure that all the container volumes used to store Mail Server data are mounted using the following command:

Your domain that will be used for maintaining correspondence must be valid and configured for this machine (i.e. it should have the appropriate A record in the DNS settings that points your domain name to the IP address of the machine where Mail Server is installed).In the command above, the "yourdomain.com" parameter must be understood as a service domain for Mail Server. It is usually specified in the MX record of the domain that will be used for maintaining correspondence. As a rule, the "yourdomain.com" looks like mx1.onlyoffice.com

Make sure that you run the new image with the folder paths mapped exactly as they had been mounted before you deleted Mail Server image, otherwise the data stored in these folders will not be picked up automatically.

If you have not mounted the folders during the previous version installation, you will need to restore data manually before installing the Mail Server new version. To do that you can copy the backup data from the folders on your host machine to the new folders on the host that will be mounted during the further installation:

Where /home/user/Backup/MailServer stands for a path to any folder on your host machine. When the backup is restored, install Mail Server as described above.

Step 5: Run the Document Server & Community Server images with the same map paths

Run a new Document Server container and then the Community Server container connecting them as described here. When running the containers, you will also need to mount data folders exactly as they had been mounted in the previous version.

Now you can run the portal and check the data for consistency and correct work.

Updating to the latest version that uses MySQL 5.7 within a separate container

To update your Mail Server integrated with an old Community Server version (lower than 9.1) to the newest version you'll need to make a dump for both the Mail Server and Community Server MySQL databases and then restore them in the corresponding databases within a new MySQL container. Restoring the Mail Server backup data should be performed before installing the new version of Mail Server.