Skip to end of metadata
Go to start of metadata

Perform a full system backup

BlueMind makes every effort to provide reliable updates. In some special untested cases or due to external factors, however, data may be lost unexpectedly. BlueMind may not be held responsible for any possible update failure leading to system corruption.

It is your responsibility to prevent this risk by performing a complete system backup.

Linux Upgrades

Major upgrades of Linux distributions (Debian 7 to Debian 8, etc.) must not be performed using automatic distribution update mechanisms (changing package sources and using the aptitude dist-upgrade command) because this may modify BlueMind dependencies which may impact BlueMind services.

To perform major distribution upgrades, please contact your integrator service provider or contact us via our ticket platform.

On this page:

Related:

Installation

Introduction

The BlueMind subscription provides a simplified update system which has been tested and saves having to perform a migration procedure.

Updating BlueMind to a corrective or adaptive version is made easier, safer and faster thanks to the graphical admin tool.

Major Upgrades: Migration

Major BlueMind upgrades (to a newer version, for instance from v2.x to v3.x or from v3.0.x to v3.5.x) require software deposit addresses to be updated. The subscription file must therefore be updated for you to perform the version upgrade.


About BlueMind version 4.0 in particular, current version 3.5 installations cannot be updated to version 4.0. BlueMind version 4 is currently available for new installations only.

Prerequisites

Subscriptions

To access BlueMind update tools, you must have a valid and current subcription installed.

Access to the setup wizard

Updates require access to the setup wizard (https://<your.server.com>/setup) for which you were provided a password at the end of the post-installation process.

In case you lost this password, there are two ways of recovering it:

  1. Before any installation operation: Access the administration console as global administrator admin0 and go to System management > System configuration > "Reverse proxy" tab: enter the new password and save.
  2. Using command line in console mode:
    • connect to the BlueMind server as root and type the following command:

      rm -f /etc/nginx/sw.htpasswd; htpasswd -b -c /etc/nginx/sw.htpasswd admin admin
    • connect to the /setup URL using admin/admin as username/password
      This step is necessary even if you have not reached the update step yet.

Repository signature

Repositories are now signed for all supported Ubuntu/Debian distributions.

Repository signature is required for Ubuntu 18.04 and Debian 9 which are supported by BlueMind 3.5.9.

You may, if you need or want to, manually import the key on all our supported distributions using the following command:

curl https://pkg.bluemind.net/bluemind-deb.asc | apt-key add -

Otherwise, a warning may come up during earlier version updates. This will not disrupt updates however.

Points de vigilance

De même qu'avant une installation de BlueMind 4, nous conseillons la lecture attentive de la page Rolling out BlueMind 4.0: what to watch out for avant une mise à jour de version importante.

Mise à jour 4.0 vers 4.1

Dossiers sous la boîte de réception

Dans les versions 4.0.x de BlueMind (4.0.x), les dossiers créés sous la boîte de réception par Outlook ne sont pas des dossiers de messagerie mais des dossiers virtuels. BlueMind 4.1 apporte le support des sous-dossiers de la boîte de réception (inbox).

Dans le cadre d'une mise à jour de BlueMind 4.0.x vers 4.1, les dossiers virtuels éventuellement créés par les utilisateurs ne seront pas migrés et seront supprimés. Pour se prémunir de cela, il est donc conseillé de déplacer ces dossiers virtuels en dehors de la boîte de réception avant la mise à jour de façon à les conserver, ils pourront ensuite y être remis et seront recréés en tant que dossiers de messagerie.

Update instructions

Repositories are registered as soon as the subscription is installed, as a result, BlueMind will be updated automatically when the system is updated.

If you've modified the configuration files manually, make sure to back them up.
To find out more, please refer to the Appendices: note on configuration files

Préparer la mise à jour

Pour une mise à jour d'un BlueMind déjà en version 4.1 ou supérieure, le processus de mise à jour doit être initié. Cela permet une plus grande maîtrise des versions et limite le risque d'erreur : la version cible peut désormais être ouverte afin de toujours mettre à jour dans la dernière version publiée ou au contraire figée afin d'empêcher les mises à jour involontaires. Cela permet aussi de sécuriser le respect de la version majeure du serveur ainsi que l'installation des paquets additionnels : ils seront installés dans la version du serveur.

Cette préparation peut se faire via la console d'administration OU en ligne de commande :

  1. Via la console d'administration :
    1. se rendre dans Gestion du système > Mise à jour de BlueMind
    2. Cliquer sur le bouton "Paramétrer" : la dernière version disponible sera installée.
  2. En ligne de commande :
    1. saisir la commande suivante pour mettre à jour dans la dernière version disponible :

      bm-cli setup version latest
    2. pour mettre à jour dans une version particulière, passer le numéro de la version en paramètre :

      bm-cli setup version 4.1.1

      NB : l'utilisation du numéro de version majeure ("3.5" ou "4" par exemple) aura les mêmes effets que l'option "latest" : la dernière version mineure disponible de celle-ci sera installée

    3. pour bloquer la version et empêcher les mises à jour dans une version supérieure :

      bm-cli setup version current

Mettre à jour

Updates are performed using the same command lines as for installs and must be applied to all the devices concerned:

  1. enter the commands below, depending on your OS:

    Debian/Ubuntu Redhat/CentOS

    You may get a warning message about repository signature during earlier version updates. This does not disrupt the update, it is a mere warning. To remedy this issue, please refer to 2.3.c: Repository signature above.

  2. Using your web browser, go to the setup wizard https://<votre.serveur.com>/setup:

  3. Click "Update" to start the automatic update process.
    Once this is done, a message informs you that configuration was successful:
     
    BlueMind is then available at its usual url.

In the event of a problem, errors are logged into the bm-core and bm-tomcat files.

Appendices

About configuration files

The postfix configuration is overwritten during the installation phase only. From then on, this configuration is updated using the command postconf.
Configuration files can be configured as desired, with the following restrictions:

  • deleting BlueMind maps: maps can however be added.
  • editing mynetwork: mynetwork must be edited in the admin console.
  • editing relayhost: relayhost must be edited in the admin console.
Concerning NGinx: the virtual host is overwritten with every update.
All VHosts are disabled during updates. Only BlueMind VHosts (bm-client-access and bm-webmail) are enabled again afterwards. Other virtual hosts may be enabled again, but this must be done as part of the update process, in addition to and to complete the BlueMind update process.
BlueMind's virtual host can also be extended through the /etc/nginx/bm-local.d/*.conf files.
  • No labels