Release upgrade from Ubuntu 16.04 to 18.04

[Ardrad]

Hi all, I'm currently in the process of testing a distribution upgrade to bionic on a xenial zimbra box.
The zimbra version originally setup was zcs-8.8.12_GA_3794.UBUNTU16_64.20190329045002 and it is currently updated to patch 6.
The system is running as a single mailserver with its own dnsmasq so zimbra-dnscache is not installed.
Other packages installed are: zimbra-ldap, zimbra-logger, zimbra-mta, zimbra-snmp, zimbra-store, zimbra-apache, zimbra-spell, zimbra-memcached, zimbra-proxy, zimbra-drive, zimbra-chat.
I did several release upgrades in the past, so I have some familiarity with the process, but looking at https://wiki.zimbra.com/wiki/Ubuntu_Upgrades it looks like things may have changed a bit during the last few years.

Here is what I came up so far with:

- Update to zcs-8.8.15_GA_3869.UBUNTU16_64.20190918004220:
install.sh will take care of everything as usual apart from installing zimbra-ldap-patch package (see also: viewtopic.php?f=13&t=70845&start=20#p305689).

Code: Select all

sudo ./install.sh

Once the upgrade process to 8.8.15 is completed run:

Code: Select all

sudo apt-get install zimbra-ldap-patch
sudo su - zimbra
zmcontrol restart

If everything is ok then:

Code: Select all

zmcontrol stop

- Make a backup copy of /opt/zimbra/conf/localconfig.xml
As stated by the wiki article localconfig.xml will get deleted during the zimbra package removal that will run at the end of the ubuntu release upgrade process.
I'm not sure if localconfig.xml removal is expected behaviour and if there are other configs that need to be backed up.

- Delete /etc/apt/sources.list.d/zimbra.list then run the release upgrade process:

Code: Select all

sudo apt-get update && sudo do-release-upgrade

- Reboot


- Prevent systemd-resolved from listening on port 53 since I'm using dnsmasq:

Code: Select all

sudo sed -i 's/#DNSStubListener=yes/DNSStubListener=no/' /etc/systemd/resolved.conf && sudo systemctl restart systemd-resolved.service && sudo systemctl restart dnsmasq.service

- Download zcs-8.8.15_GA_3869.UBUNTU18_64.20190918004220 then do a software install only. apt-get update will prevent you from getting an error while importing zimbra gpg repo key.
Note that a normal install will not detect the previous installation, forcing you to start fresh:

Code: Select all

sudo apt-get update 
sudo ./install.sh -s

do not delete /opt/zimbra when asked
do not install zimbra-dnscache when asked

- Once the installation is completed, restore localconfig.xml from backup:

Code: Select all

sudo cp -p /opt/zimbra_backup/localconfig.xml /opt/zimbra/conf/localconfig.xml

- reinstall zimbra-ldap-patch:

Code: Select all

sudo apt-get update && sudo apt-get install zimbra-ldap-patch

- Start zimbra services

Code: Select all

sudo su - zimbra
zmcontrol start

Check if everything is ok.


Am I missing anything important here?
I've seen suggestions of doing a last install.sh (without the -s) as a final step, but I'm not finding any info on why this would be required.

Thanks

[phoenix]

Is this to a new server or an in-place secnario? Take a look at this article and see if it helps: https://syslint.com/blog/tutorial/zimbr ... ct-method/

[Ardrad]

In-place upgrade, zimbra 8.8.12 patch 6 Ubuntu 16.04 to 8.8.15 Patch 32 Ubuntu 18.04.
I would avoid building from scratch and reimporting user data to a new install, if possible.

[barrydegraaff]

Zimbra 8.8.12 has been out of support for a long time, you should consider a side-by-side migration https://wiki.zimbra.com/wiki/Zimbra_NG_ ... _NG_Backup

[Klug]

Have a look here (different ZCS version but same OS): viewtopic.php?f=13&t=67390
TLDR: Allow Third party package repos

What I'd do, after upgrading the OS (keeping the same ZCS version) is upgrading ZCS to last version+last patch.