1 Topic by ajames

  • ajames
  • Member
  • Offline
  • Registered: 2015-09-28
  • Posts: 4

Topic: Correct procedure for multiple version upgrades

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):  0.99
- Deployed with iRedMail Easy or the downloadable installer? installer
- Linux/BSD distribution name and version:  Ubuntu 18.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):  mysql
- Web server (Apache or Nginx): nginx
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Firstly, yes we are delinquent in versions and need to address urgently...

The upgrade procedures for each version are clear, but one of the first steps during each incremental upgrade is to  update iRedAdmin. To request the download link for iRedAdmin Pro, we get the very latest, which doesn't yet support our old version at that step until we get there.

I just want to confirm the correct procedure for ultimately getting to the latest iRedmail and iRedAdmin Pro. Can I step through all intermediate versions to get iRedMail to the very latest *first*, and then apply the latest iRedAdmin Pro single upgrade, or do I need to request/locate the supported iRedAdmin Pro for each specific version, as I step  through the upgrades 1 by 1?

The plan will also be to upgrade 18.04 > 20.04 > 22.04. Are there specific versions best to halt at while the OS is upgraded?

Thanks,

A

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,141

Re: Correct procedure for multiple version upgrades

For iRedAPD, mlmmjadmin, iRedAdmin(-Pro), it's ok to upgrade from an old release to latest one directly.

3 Reply by sorakrates

  • sorakrates
  • Member
  • Offline
  • Registered: 2019-10-08
  • Posts: 8

Re: Correct procedure for multiple version upgrades

Hello,

I hope this won't count as hijacking, but I didn't want to open a new topic for a question that is basically the same topic. But I wanted to specify some things, since the official documentation has some statements contradicting your answer.
That left me in a state of uncertainty of how to upgrade multiple versions and which statements from the documentations are I have to follow.
I have the ungrateful task of upgrading iRedmail openldap edition from 1.6.1 edition to the latest.


Statements against skipping versions from documentation:
°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
"Do NOT skip releases." - https://docs.iredmail.org/iredmail.releases.html)
---
"The latest iRedAdmin-Pro always requires the latest iRedMail stable release, so you MUST upgrade iRedMail to the latest stable release before upgrading iRedAdmin-Pro." - https://docs.iredmail.org/migrate.or.up … admin.html
---

Does these statements only counts for non iRedamin-Pro installations? But the 2nd statement explicitly mentions the Pro-Version.

sincerely,

Sorakrates

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,141

Re: Correct procedure for multiple version upgrades

- For iRedMail, you must upgrade one by one.
- For iRedAPD, mlmmjadmin, it's ok to upgrade from current old version to latest version directly.
- For iRedAdmin(-Pro), please upgrade iRedMail first, then upgrade iRedAdmin-Pro from old version to latest version directly. iRedAdmin(-Pro) relies on the SQL structure / LDAP schema offered by latest iRedMail release.

5 Reply by sorakrates

  • sorakrates
  • Member
  • Offline
  • Registered: 2019-10-08
  • Posts: 8

Re: Correct procedure for multiple version upgrades

Hello.

Thank you for the clarification.
I hope this is helpful for others too.

sincerely,

Sorakrates