Difference between revisions of "CentOS 8.x Zimbra upgrade"

From Notes_Wiki
(Created page with "<yambe:breadcrumb self="Zimbra upgrade">CentOS 8.x Zimbra|Zimbra</yambe:breadcrumb> =CentOS 8.x Zimbra upgrade= ==Patch upgrade== For minor version upgrade or patch upgrades...")
 
m
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
<yambe:breadcrumb self="Zimbra upgrade">CentOS 8.x Zimbra|Zimbra</yambe:breadcrumb>
[[Main Page|Home]] > [[CentOS]] > [[CentOS 8.x]] > [[CentOS 8.x email servers]] > [[CentOS 8.x Zimbra]] > [[CentOS 8.x Zimbra upgrade]]
=CentOS 8.x Zimbra upgrade=


==Patch upgrade==
==Patch upgrade==


For minor version upgrade or patch upgrades we can use:
For minor version upgrade or patch upgrades we can use:
# We can check existing version including patch version via:
#:<pre>
#:: zmcontrol -v
#:</pre>
#: Then check if a updated version or updated patch is available for the same Zimbra major/minor release.
# Take backup of VM through snapshot etc. if possible.  Other option is to take backup of entire /opt/zimbra folder.  
# Take backup of VM through snapshot etc. if possible.  Other option is to take backup of entire /opt/zimbra folder.  
# Take copy of /opt/zimbra/conf at another location for quick reference after upgrade
# Take copy of /opt/zimbra/conf at another location for quick reference after upgrade
Line 14: Line 18:
#:<pre>
#:<pre>
#:: yum -y update
#:: yum -y update
#::</pre>
# For kernel update had to use below once
#:<pre>
#::  yum reinstall cpio
#:</pre>
#:</pre>
#:* Refer: https://forums.centos.org/viewtopic.php?t=79639
# Compare old copy of /opt/zimbra/conf with new copy for any manual changes that might have got overwritten during upgrade.
# Compare old copy of /opt/zimbra/conf with new copy for any manual changes that might have got overwritten during upgrade.
# Start zimbra again
# Start zimbra again
Line 41: Line 50:
; Spamassasin configuration and scores might get overwritten : [[CentOS 8.x Zimbra Configure spamassasin email score based on client RBL]]
; Spamassasin configuration and scores might get overwritten : [[CentOS 8.x Zimbra Configure spamassasin email score based on client RBL]]
; CBpolicyd security configuration via http might get overwritten : [[CentOS 7.x Configure cbpolicyd for Zimbra 8.7]]
; CBpolicyd security configuration via http might get overwritten : [[CentOS 7.x Configure cbpolicyd for Zimbra 8.7]]
 
; Postfix configuration for copying of incoming/outgoing emails get overwritten : [[CentOS 8.x Zimbra forward a copy of all incoming and outgoing emails to audit email ID]]




Line 51: Line 60:




<yambe:breadcrumb self="Zimbra upgrade">CentOS 8.x Zimbra|Zimbra</yambe:breadcrumb>
==Solve AWS Zimbra VM not booting after update issue==
 
In one case VM did not boot after update.  To solve that use:
# We detached root volume (30GB) from mail.example.com
# Attached it to a test VM as /dev/sdf
# Powered on test VM
# In test VM we did <source type="shell">
  mkdir /mnt/sysimage
  mount /dev/sdf1 /mnt/sysimage
  mount -o bind /dev /mnt/sysimage/dev
  mount -o bind /proc /mnt/sysimage/proc
  chroot /mnt/sysimage
 
  yum reinstall cpio
  yum reinstall kernel
</source>
# To change grub timeout modified '<tt>/etc/grub2.cfg</tt>' below at '''two''' places:
#:<pre>
#:: set timeout=60
#:</pre>
#* Also in '<tt>/etc/default/grub</tt>' set '<tt>GRUB_TIMEOUT=60</tt>'
#*:* Refer: https://www.redhat.com/sysadmin/linux-change-boot-options-grub   
# Then exit and reboot chrooted VM
#:<pre>
#:: exit
#:: shutdown -h now
#:</pre>
# Removed the 30GB volume from test VM
# attached 30GB volume back to mail.example.com as '''/dev/sda1''' 
#: Giving name /dev/sda1 for boot volume is very important
# After that the VM booted into updated kernel properly.
 
 
 
[[Main Page|Home]] > [[CentOS]] > [[CentOS 8.x]] > [[CentOS 8.x email servers]] > [[CentOS 8.x Zimbra]] > [[CentOS 8.x Zimbra upgrade]]

Latest revision as of 09:58, 9 April 2024

Home > CentOS > CentOS 8.x > CentOS 8.x email servers > CentOS 8.x Zimbra > CentOS 8.x Zimbra upgrade

Patch upgrade

For minor version upgrade or patch upgrades we can use:

  1. We can check existing version including patch version via: 
    zmcontrol -v
    Then check if a updated version or updated patch is available for the same Zimbra major/minor release.
  2. Take backup of VM through snapshot etc. if possible. Other option is to take backup of entire /opt/zimbra folder.
  3. Take copy of /opt/zimbra/conf at another location for quick reference after upgrade
  4. Stop Zimbra as zimbra user 
    zmcontrol stop
  5. Update packages as root user 
    yum -y update
  6. For kernel update had to use below once 
    yum reinstall cpio
  7. Compare old copy of /opt/zimbra/conf with new copy for any manual changes that might have got overwritten during upgrade.
  8. Start zimbra again 
    zmcontrol start


Major upgrade

For major version upgrade:

  1. Download the updated version of zimbra in .tgz (Zip) format
    We must keep both old and new zimbra setups with us for future recovery / restore operations
  2. Extract the files of updated version
  3. Take copy of /opt/zimbra/conf at another location for quick reference after upgrade
  4. Go through installation of zimbra using "./install.sh" with required platform override, if required
    The installer will automatically detect existing version and go through the update process.
  5. Compare old copy of /opt/zimbra/conf with new copy for any manual changes that might have got overwritten during upgrade.



Caveats from update

Following things have been noticed to get affected due to upgrade, which must be fixed promptly:

Spamassasin configuration and scores might get overwritten
CentOS 8.x Zimbra Configure spamassasin email score based on client RBL
CBpolicyd security configuration via http might get overwritten
CentOS 7.x Configure cbpolicyd for Zimbra 8.7
Postfix configuration for copying of incoming/outgoing emails get overwritten
CentOS 8.x Zimbra forward a copy of all incoming and outgoing emails to audit email ID


Refer:


Solve AWS Zimbra VM not booting after update issue

In one case VM did not boot after update. To solve that use:

  1. We detached root volume (30GB) from mail.example.com
  2. Attached it to a test VM as /dev/sdf
  3. Powered on test VM
  4. In test VM we did 
      mkdir /mnt/sysimage
  mount /dev/sdf1 /mnt/sysimage
  mount -o bind /dev /mnt/sysimage/dev
  mount -o bind /proc /mnt/sysimage/proc
  chroot /mnt/sysimage
  
  yum reinstall cpio
  yum reinstall kernel
  5. To change grub timeout modified '/etc/grub2.cfg' below at two places: 
    set timeout=60
  6. Then exit and reboot chrooted VM 
    exit
    

    shutdown -h now
  7. Removed the 30GB volume from test VM
  8. attached 30GB volume back to mail.example.com as /dev/sda1
    Giving name /dev/sda1 for boot volume is very important
  9. After that the VM booted into updated kernel properly.


Home > CentOS > CentOS 8.x > CentOS 8.x email servers > CentOS 8.x Zimbra > CentOS 8.x Zimbra upgrade

Retrieved from "http://www.sbarjatiya.com/notes_wiki/index.php?title=CentOS_8.x_Zimbra_upgrade&oldid=8154"