BlueMind Major Version Update: Upgrade from v4 to v5
Changing a major version of BlueMind requires special attention on a number of points complementing the requirements for a regular update.
Points to watch out for
Data not migrated
During data transfer, emails contained in the double bottom of the trash and drafts marked for deletion (old versions of drafts) are not migrated.
CAS configuration
In BlueMind 5, CAS configuration is carried out per domain, rather than for the entire server as in v4. The server's CAS configuration is therefore not migrated.
BlueMind 5 Upgrade Requirements
BlueMind Version
In order to upgrade to BlueMind 5, version 4 must be installed and updated to the latest available version.
System
In view of PostgreSQL's upgrade from version 14 to 16, the /var/lib/postgresql partition must have an occupancy rate of less than 50%.
Eligibility Test
This Eligibility Test must not be completed before updating BlueMind from v4 to v5.
A check-upgrade-v5 eligibility test has been added to the CLI client to avoid any loss of data and ensure a controlled and secure upgrade to v5.
This test checks these 5 major points:
- Checking custom settings
- Checking hotupgrades
- Checking elasticsearch cluster status
- Checking cyrus replication
- Cyrus email checks
Run the test by executing the following command:
bm-cli setup check-upgrade-5 --sampling-percentage=100
Depending on sizing, the chek-upgrade-5 command can take over an hour. It is recommended to run in a screen or tmux session.
Testing and subsequent maintenance operations can be resource-intensive. It is therefore recommended to perform them during long periods of low activity, for example at the end of the day.
Repair commands are then proposed, according to the failures identified. The command list follows as follows (example):
Recommended repair commands to run:
bm-cli hotupgrade start --no-delay --scheduled
bm-cli index coherency --all --run-consolidate --workers=1 all
bm-cli maintenance repair --ops replication.parentUid 1518B471-729C-4C99-AEC0-86D4D87DCB12@734ea413.internal
bm-cli maintenance repair --ops replication.parentUid,message_bodies B9584543-273B-43F0-A450-09FCB38526A6@734ea413.internal
Start a new verification once the recommended repairs are completed. This allows you to refresh the list of errors and potentially track those that have not been reported or repaired.
It is strongly recommended to transmit the results of successive executions of these test commands via Jira ticket creation.
Subscriptions
Upgrading BlueMind to a major version change requires a change in the addresses of the software periods. The subscription file must therefore be updated in order to be able to carry out the version change.
Update
Once the prerequisites and eligibility test have been validated, follow the BlueMind update procedure.
Once the update is complete, we recommend that you purge your BlueMind 4 backups.
BlueMind 5 backs up e-mails using a new method in /var/backups/bluemind/sds-spool. The first backup includes all e-mails, which can trigger a disk saturation alert if the available space is < 50%.
V4 backups are no longer compatible. Removing them saves space.
Post-update operations
Background operations are performed after the update. They have been designed to run without impacting the service in production.
Some features are unlocked over time following these post-ugrade operations. These include advanced e-mail sorting and message conversation settings.
To check the progress of post-upgrade operations, run the command :
bm-cli hotupgrade progress --details --filterSuccess
If these operations fail, a banner appears in the administration console, informing administrators. In this case, create a ticket (or update the one concerning the eligibility test - see above) on our ticket tracking tool.