Comparaison des versions

Légende

  • Ces lignes ont été ajoutées. Ce mot a été ajouté.
  • Ces lignes ont été supprimées. Ce mot a été supprimé.
  • La mise en forme a été modifiée.
Commentaire: Published by Scroll Versions from space DA and version BM-4.0

...

Sv translation
languageen
Avertissement
titlePerform 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.

Avertissement
titleLinux 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 change 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.

Volet
borderWidth3

On this page:

Sommaire
maxLevel2

Related:

Installation

Introduction

The BlueMind subscription includes a simplified, tried and tested update system.

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

Remarque
titleMajor Upgrades: Migration

Major BlueMind upgrades (e.g. 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.

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:

      Bloc de code
      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.

Ancre
signature-depot
signature-depot
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:

Bloc de code
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 or interfere with updates.

Points of Caution 

We recommend that you carefully read the page Deploiement BlueMind 4 - points de vigilance before any important version update.

Updating from 4.0 to 4.1

Inbox subfolders

In BlueMind versions 4.0.x, folders created in the inbox by Outlook are not mailbox folders but virtual folders. BlueMind 4.1 brings inbox subfolder support.

When you update from BlueMind 4.0.x to 4.1, virtual folders users may have created will not be migrated and will be deleted. To prevent this and keep these folders, we recommend that you move virtual folders outside the inbox before you perform the update. You can them put them back into the inbox where they will be created again as mail folders.

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.

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

Preparing for the update

Image Removed For Image Added For updates from BlueMind version 4.1 or above, the process must always be prompted. This gives you greater control over versions and reduces the risk of errors: the target version can now be left open to allow updates to the latest published version or, on the contrary, it can be frozen to prevent unintentional updates. This also helps ensure that the server's major version as well as additional packages are conformed to.

This can be done in the admin console OR in command line:

  1. In the admin console:
    1. go to System management > Update BlueMind
    2. Click "Setup": the latest available version will be installed.
  2. In command line:
    1. Install the command line plugin:

      Bloc de code
      languagebash
      aptitude install bm-plugin-cli-setup
    2. type the following command to update to the latest available version:

      Bloc de code
      bm-cli setup version latest
    3. to update to a specific version, pass the version number as a parameter:

      Bloc de code
      bm-cli setup version 4.1.1

      Note: using a major version number (e.g. "3.5" or "4") will have the same results as using the "latest" option: the latest minor version available will be installed. 

    4. to freeze a version and prevent updates to above versions:

      Bloc de code
      bm-cli setup version current

Update Procedure

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:

    Tabs group
    borderall-sides
    navcolornavy
    Debian/UbuntubashDebian/UbuntuRedhat/CentOSbashRedHat
    Info

    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.

Using your web browser:

  1. go to the setup wizard https://<your.server.com>/setup
  2. 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.

Info

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

Using the command line


Bloc de code
# After the packages upgrade:
bm-cli setup upgrade


Appendices

Ancre
note-conf
note-conf
About configuration files

The postfix configuration is overwritten during the installation phase only. From then on, this configuration can be 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.

...