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.

Major upgrades of Linux distributions (Debian 7 to Debian 8, etc.) must not be performed using automatic distribution update mechanisms (changing package sources and use of the aptitude dist-upgrade command). This is because BlueMind dependencies may be modified 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.

The integrated update system comes with the subscription. Without a subscription, updating a BlueMind system requires installing the new version on a new platform and then migrating the data to this new platform.

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

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.

Update procedure

Prerequisite: access to the setup wizard

In order to perform updates, you must have 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.

Update instructions

The BlueMind subscription enables software updates via software repositories when a new release is available.

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

Major releases

Major BlueMind updates (from v2.x to v3.x for example) require a change of software repository urls. The subscription file must therefore be updated to be able to change versions.

To update to a major release, you must therefore contact the BlueMind team to get a new subscription file.

Updates, whether minor or major, are performed using the same command lines as for installation and must be applied to all the devices concerned:

  1. connect to the server as root
  2. enter the commands below, depending on your OS:

    Debian/Ubuntu
    aptitude update
    aptitude upgrade
    

    Major release

    For a major update, use the following:

    Debian/Ubuntu
    aptitude update
    aptitude dist-upgrade
    
    RedHat
    yum makecache
    yum upgrade
  3. Using your web browser, go to the setup wizard https://<votre.serveur.com>/setup:

    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 in bm-core and bm-tomcat files.

Migrating to BlueMind 3.5

BlueMind 3.0 back-ups cannot be used in version 3.5, there is therefore no need for them to be kept on the sever. Make sure you delete them before or right after the update in order to free up space for future 3.5 back ups.

Updating the BlueMind subscription

Before performing the migration, please make sure that your 3.5 subscription matches the number or your BlueMind users.

To be able to migrate to BlueMind 3.0, your subscription must be up to date.

To do this, you must go over the Setting up Subscriptions procedure in order to install the new packets: a dedicated packet is now needed and the list of packets to install subsequently has been modified.

Updating BlueMind

The update procedure is the same as described in the previous chapter.

Post-installation actions

Email indexation

Once the update is complete, you must perform an email indexation.

Log into BlueMind as global administrator admin0:

  • go to System Management > Scheduled jobs
  • select ReconstructMailSpoolIndexJob (responsible for indexing emails), making sure you select this job only, and click "Start now":

    Email indexation may take a while – 16Gb of data processed every 4600 seconds (1h12).
    However, it is transparent for users who can continue using BlueMind as usual in the meantime.

    As their messages are indexed, users will see the new search engine appear in their webmail interface. This means that all users will not see the new search engine immediately when the update is completed nor all at the same time.

Cyrus Configuration

After a migration, you must set the maximum the number of imap processes allows by Cyrus again.

To do this, you can either edit the /etc/cyrus.conf file directly on the command line or, you can now edit it in the BlueMind admin console:

  • connect to the admin console as admin0
  • go to System Management > System Configuration > Mail tab
  • In the Cyrus section, enter the value you want in the "max child" box:

    Estimating the number of processes required

    Typically, allow 1.5 times the number of users for a mixed webmail/thick client use. On installations where many users use thick clients, allow for approximately 3 times the number of users.

    To count the current number of processes used:

    pgrep -c imap
  • click "Save" sur to apply the changes.
    Cyrus restarts automatically.

Enregistrer

Enregistrer

Enregistrer

Enregistrer

Enregistrer

Enregistrer

Enregistrer

Enregistrer

Enregistrer

Enregistrer

  • No labels