Ajcody-Notes-OS-Upgrade-And-ZCS-Options

From Zimbra :: Wiki

Jump to: navigation, search
Attention.png - This article is NOT official Zimbra documentation. It is a user contribution and may include unsupported customizations, references, suggestions, or information.

Contents

ZCS Upgrades Requiring OS Upgrades Also

Actual Upgrade Options Notes Homepage


Please see: Ajcody-Notes-OS-Upgrade-And-ZCS-Options

Notable RFE To Follow


I have asked in this RFE for the QA/Dev. teams for more input on these OS upgrades and server move options.

I am waiting for an update to my last comments on it. I would expect at some point more RFE's being filed that deal with specific issues and OS issues.

FOSS Open Source ZCS To Network Edition ZCS First Steps

FOSS ZCS servers must first upgrade to the EXACT same version of ZCS but using the Network Edition installer tarball. Only then can you proceed with ZCS version upgrades.

Preliminary Notes And OS Upgrade Steps Through ZCS Versions


All existing servers should first be upgraded to ZCS 7.2.1 [latest ZCS7 as of today] prior to upgrade plans for ZCS8. For SLES and Ubuntu, you should be running an OS version that is also supported under ZCS8 and ZCS 7.2.1 .

For ZCS 7.2.x To ZCS 8


  • ZCS 8 Supported OS's
    • RHEL 6 [x64 only]
    • Ubuntu 12.04 LTS [x64 only]
    • Ubuntu 10.04 LTS [x64 only]
    • SLES 11 [x64 only]
  • ZCS 7.2.x or greater supported OS's
    • RHEL 6 [x64 only]
      • Can be upgraded to ZCS8 from ZCS 7.2.x.
    • RHEL 5
    • RHEL 4
    • Ubuntu 10.04 [x64 only]
      • Can be upgraded to ZCS8 from ZCS 7.2.x.
      • Your Ubuntu servers should be on 10.04 LTS and ZCS 7.2.x before you can do the ZCS8 upgrade.
      • Once your Ubuntu servers are on Ubuntu 10.04 and ZCS8, you can :
        • Upgrade to Ubunto 12.04
          • zimbra should be disable from the init scripts during this phase until your on the right matching version of ZCS for your platform.
        • And then reinstall/update zimbra using the ZCS 8 installer for Ubuntu 12.04.
      • Detailed steps are here:
    • Ubuntu 8.04 LTS
      • Need to upgrade to Ubuntu 10.04 and then reinstall/update zimbra using the ZCS 7.2.x installer for Ubuntu 10.04
        • zimbra should be disable from the init scripts during this phase until your on the right matching version of ZCS for your platform.
    • SLES 11 [x64 only]
      • Can be upgraded to ZCS8 from ZCS 7.2.x.
      • Your SLES server should be on SLES 11 and ZCS 7.2.x before you can do the ZCS8 upgrade.
      • It is recommended that SP2 be applied to SLES 11 on ZCS 7.2.+ before upgrading to ZCS 8.
    • SLES 10
      • You can upgrade to SLES 11 and then reinstall/update zimbra using the ZCS 7.2.x installer for SLES 11.
        • zimbra should be disable from the init scripts during this phase until your on the right matching version of ZCS for your platform.
      • You can also from SLES 10 and ZCS 7.2.x, migrated the data or make zimbra services redundant with a SLES 11 and ZCS 7.2.x server. The SLES 10 boxes could then be decommissioned or rebuilt fresh with the transition to ZCS8.

For ZCS 6 And Lower Getting To ZCS 7.2.x


Just apply the same logic in the above table to the choices you have from your existing OS & ZCS version up to ZCS 8. zmmboxmove does not come about until ZCS 7.2 [matured].

You might also need to switch from x32 to x64 hardware at some time, ZCS 8 is only supported on x64.

  • ZCS 7.0.x Supported OS's
    • Get to ZCS 7.2.x before following the steps below and continuing to ZCS 8.
    • RHEL 6 [x64 only]
      • Upgrade to ZCS 7.2.x for RHEL 6
    • RHEL 5
      • Upgrade to ZCS 7.2.x for RHEL 5
      • You can stay on RHEL 5 until ZCS 7.2.x .
      • RHEL 5 and ZCS 7.2.x data will be migrated or made redundant with a RHEL 6 and ZCS 7.2.x server. This box will be decommissioned or rebuilt fresh with the transition to ZCS8.
    • RHEL 4
      • Upgrade to ZCS 7.2.x for RHEL 4
      • You can stay on RHEL 4 until ZCS 7.2.x .
      • RHEL 4 and ZCS 7.2.x data will be migrated or made redundant with a RHEL 6 and ZCS 7.2.x server. This box will be decommissioned or rebuilt fresh with the transition to ZCS8.
      • EXCEPTION If you are using Redhat Clustering, ZCS 7.2+ requires RHEL 5. See the ZCS 7.2+ Release Notes.
    • Ubuntu 10.04 LTS [x64 only]
      • Upgrade to ZCS 7.2.x for Ubuntu 10.04 LTS.
    • Ubuntu 8.04 LTS
        • Upgrade to Ubuntu 10.04 LTS
          • Zimbra should be disable from the init scripts during this phase until your on the right matching version of ZCS for your platform.
        • And then reinstall/update zimbra using the ZCS 7.0.x [what you were running] installer for Ubuntu 10.04 LTS.
        • Then proceed with upgrading to ZCS 7.2.x for Ubuntu 10.04 LTS.
    • SLES 11 [x64 only]
      • Upgrade to ZCS 7.2.x for SLES 11.
    • SLES 10
      • Upgrade to SLES 11
        • Zimbra should be disable from the init scripts during this phase until your on the right matching version of ZCS for your platform.
      • And then reinstall/update zimbra using the ZCS 7.0.x [what you were running] installer for SLES 11.
      • And then upgrade to ZCS 7.2.1 for SLES 11.
  • ZCS 6 Supported OS's
    • Get to ZCS 6.0.16 before following the steps below and continuing to ZCS 7.2.x
    • RHEL 5
      • Upgrade to ZCS 7.2.x for RHEL 5
      • You can stay on RHEL 5 until ZCS 7.2.x .
      • RHEL 5 and ZCS 7.2.x data will be migrated or made redundant with a RHEL 6 and ZCS 7.2.x server. This box will be decommissioned or rebuilt fresh with the transition to ZCS8.
    • RHEL 4
      • Upgrade to ZCS 7.2.x for RHEL 4
      • You can stay on RHEL 4 until ZCS 7.2.x .
      • RHEL 4 and ZCS 7.2.x data will be migrated or made redundant with a RHEL 6 and ZCS 7.2.x server. This box will be decommissioned or rebuilt fresh with the transition to ZCS8.
    • Ubuntu 10.04 LTS [x64 only]
      • Upgrade to ZCS 7.2.x for Ubuntu 10.04 LTS.
    • Ubuntu 8.04 LTS
        • Upgrade to Ubuntu 10.04 LTS
          • Zimbra should be disable from the init scripts during this phase until your on the right matching version of ZCS for your platform.
        • And then reinstall/update zimbra using the ZCS 6.0.16 installer for Ubuntu 10.04 LTS.
        • Then proceed with upgrading to ZCS 7.2.x for Ubuntu 10.04 LTS.
    • Ubuntu 6.06 LTS
        • Upgrade to Ubuntu 8.04 LTS
          • Zimbra should be disable from the init scripts during this phase until your on the right matching version of ZCS for your platform.
        • Upgrade to Ubuntu 10.04 LTS
        • And then reinstall/update zimbra using the ZCS 6.0.16 installer for Ubuntu 10.04 LTS.
        • Then proceed with upgrading to ZCS 7.2.x for Ubuntu 10.04 LTS.
    • SLES 11 [x64 only]
      • Upgrade to ZCS 7.2.x for SLES 11.
    • SLES 10
      • Upgrade to SLES 11
        • Zimbra should be disable from the init scripts during this phase until your on the right matching version of ZCS for your platform.
      • And then reinstall/update zimbra using the ZCS 6.0.16 installer for SLES 11.
      • And then upgrade to ZCS 7.2.x for SLES 11.
    • Mac OS X 10.4 Tiger
      • You'll need to restore to another hardware platform using the DR/zmrestore process before you can upgrade to ZCS 7.
  • ZCS 5 Supported OS's
    • Get to ZCS 5.0.26 before following the steps below and continuing to ZCS 6.0.16
    • RHEL 5
      • Upgrade to ZCS 6.0.16 for RHEL 5
      • You can stay on RHEL 5 until ZCS 7.2.x .
      • RHEL 5 and ZCS 7.2.x data will be migrated or made redundant with a RHEL 6 and ZCS 7.2.x server. This box will be decommissioned or rebuilt fresh with the transition to ZCS8.
    • RHEL 4
      • Upgrade to ZCS 6.0.16 for RHEL 4
      • You can stay on RHEL 4 until ZCS 7.2.x .
      • RHEL 4 and ZCS 7.2.x data will be migrated or made redundant with a RHEL 6 and ZCS 7.2.x server. This box will be decommissioned or rebuilt fresh with the transition to ZCS8.
    • Ubuntu 8.04 LTS
      • Upgrade to ZCS 6.0.16 for Ubuntu 8.04 LTS.
    • Ubuntu 6.06 LTS
        • Upgrade to Ubuntu 8.04 LTS
          • Zimbra should be disable from the init scripts during this phase until your on the right matching version of ZCS for your platform.
        • And then reinstall/update zimbra using the ZCS 5.0.26 installer for Ubuntu 8.04 LTS.
        • Then proceed with upgrading to ZCS 6.0.16 for Ubuntu 8.04 LTS.
    • SLES 10
      • Upgrade to ZCS 6.0.16 for SLES 10. Once at ZCS 6.0.16 you can:
        • Upgrade to SLES 11
          • Zimbra should be disable from the init scripts during this phase until your on the right matching version of ZCS for your platform.
        • And then reinstall/update zimbra using the ZCS 6.0.16 installer for SLES 11.
    • Mac OS X 10.4 Tiger
      • Mac support is offered for ZCS 6.0.16 .
      • You'll need to restore to another hardware platform using the DR/zmrestore process before you can upgrade to ZCS 7.

ZCS8 Upgrades Requiring OS Upgrades Also - Same Server


Reference: https://www.zimbra.com/downloads/ne-downloads.html

ZCS6 or ZCS7 On RHEL5 To ZCS8 or ZCS7 on RHEL6


UPDATE - [Developer Feedback] Any ZCS 6/7 customer on RHEL4/5 should upgrade to the latest release of ZCS 7.2 first. And then look to migrating to RHEL6 and ZCS8.


With ZCS8, we can only support it for RHEL6. RHEL 5 and RHEL 4 is not supported for ZC8.

Redhat is not supporting upgrades from RHEL5 to RHEL6. The option is available, but they state they do not support it. You will need to decide if you will or will not do the in-place upgrade or not.

In-Place RHEL Upgrade to RHEL6 With Dedicated Zimbra Partitions

If you currently don't have dedicated zimbra partitions and have the options to move /opt/zimbra data to a new partition - then you can also follow this method below. You can move zimbra to this new partition if you modify the steps at Ajcody-Notes-Server-Move.

  • Get dev path for zimbra partitions or saved your /etc/fstab for later consulation.
  • Start your OS upgrade, make sure you don't reformat zimbra partition and DO NOT mount them using their normal zimbra paths.
  • Once upgrade is done, download ZCS version you had but for new OS version.
  • Install by the software only switch ./install.sh -s
  • Once done, remove the 'dummy install' rm -rf /opt/zimbra or move it mv /opt/zimbra /opt/zimbra-dummy
  • Now setup /etc/fstab to mount your old zimbra partitions , mount them [mount -a] , confirm write access and perms.
  • Now rerun the installer , ./install.sh ,the installer should act like it's doing a upgrade .
In-Place RHEL Upgrade to RHEL6 - Unsupported -

Redhat and our developers are not supporting this option.

  • From ZCS6-RHEL5 ; Upgrade ZCS to ZCS7-RHEL5 ; Upgrade to RHEL6 ; then to ZCS7-RHEL6, and finally to ZCS8-RHEL6:

Overview of steps to take:

  • Download all ZCS installer packages you'll need. [Download ZCS7 for RHEL5, ZCS7 for RHEL6, and ZCS8 for RHEL6]
  • Read the Release Notes - the actual upgrade process is detailed in there for ZCS.
  • Make sure you have a proper backup.
  • During schedule downtime:
    • Block client/mail type network access to server.
      • You'll need access to our license server [license.zimbra.com] .
      • If you have multiple ZCS servers, they'll need network access to each other.
  • Upgrade to ZCS7 on RHEL5
    • Disable the zimbra services from starting on reboot/start.
  • Perform the RHEL6 upgrade
  • Then install ZCS7 for REHL6.
  • Confirm operations. Decide if you want to now proceed with the upgrade to ZCS8, upgrade to ZCS8 for RHEL6 if so.
  • Confirm operations and re-enable the init startup for zimbra.
  • Remove network access blocks.

If you want to bypass the one upgrade, you would:

  • From ZCS6-RHEL5 ; Upgrade to RHEL6 ; and then upgrade ZCS to ZCS8-RHEL6:

Overview of steps to take:

  • Download all ZCS installer packages you'll need. [Download ZCS8 for RHEL6]
  • Read the Release Notes - the actual upgrade process is detailed in there for ZCS.
  • Make sure you have a proper backup.
  • During schedule downtime:
    • Block client/mail type network access to server.
      • You'll need access to our license server [license.zimbra.com] .
      • If you have multiple ZCS servers, they'll need network access to each other.
    • Disable the zimbra services from starting on reboot/start.
  • Upgrade your server from RHEL5 to RHEL6.
  • Then install the ZCS8 installer for RHEL6.
  • Confirm operations and re-enable the init startup for zimbra.
  • Remove network access blocks.

If you are planning on using a new server, then I would need to know your disk infrastructure to see what the best course would be.

Concerning RHEL7 Support

Update - [Sep 5, 2014] RHEL7 is support with ZCS 8.5 . We are plan on continuing to support RHEL6 going forward also.

Please see the following RFE's concerning RHEL7 support :

Redhat Supports In-place Upgrades From RHEL 6.x To RHEL7 Server-x64

See:

https://access.redhat.com/solutions/637583

Ubuntu 12.04 LTS


Ubuntu 12 Kernel Bug Warning

At this time, Dec 16, 2013, we are recommending customers that run Ubuntu 12 to use a customer kernel due to kernel bugs that cause performance issues. Details on this issue can be followed in the this bug:


ZCS 8 is available for Ubuntu but only for Ubuntu 12.04 and 10.04 LTS . Since Ubuntu 12.04 LTS is not available for ZCS7x or earlier Ubuntu versions, you will have to do the upgrade to ZCS 8 first on Ubuntu 10.04. Once the ZCS 8 upgrade is done, you can then proceed with the Ubuntu 12.04 upgrade and reapply ZCS8 but with the ZCS8 for Ubuntu 12.04 installer.

Overview of steps to take [Update per developer comments]:

  • Download all ZCS installer packages you'll need. [Download ZCS 8 installer for 10.04]
  • Read the Release Notes - the actual upgrade process is detailed in there for ZCS.
  • Make sure you have a proper backup.
  • During the scheduled downtime for the ZCS8 upgrade:
    • Block client/mail type network access to server.
      • You'll need access to our license server [license.zimbra.com] .
      • If you have multiple ZCS servers, they'll need network access to each other.
  • Upgrade to ZCS8 - Ubuntu 10.04 from ZCS 7- Ubuntu 10.04
  • Confirm operations and re-enable the init startup for zimbra if you disabled it.
  • For the next scheduled downtime for the OS upgrade to Ubuntu 12.04
    • We advise taking the time to confirm ZCS8 is running correctly in production before the next phase.
  • Download all ZCS installer packages you'll need. [Download ZCS 8 installer for Ubuntu 12.04]
  • Read the Release Notes - the actual upgrade process is detailed in there for ZCS.
  • Make sure you have a proper backup.
  • For the Ubuntu 12.04 upgrade downtime window:
    • Block client/mail type network access to server.
      • You'll need access to our license server [license.zimbra.com] .
      • If you have multiple ZCS servers, they'll need network access to each other.
      • Disable the zimbra services from starting on reboot/start.
  • Do OS upgrade. [Ubuntu 12.04 LTS]
  • Do Zimbra upgrade. [ZCS8 for Ubuntu 12.04 LTS]
  • Confirm operations and re-enable the init startup for zimbra.
  • Remove network access blocks.
  • Make sure you have a proper backup.

The above is for a single server install and where the option of using another server for the transition isn't an option.

Ubuntu 14.04 LTS


Is supported with ZCS 8.5 . ZCS 8.5 also has support for Ubuntu 12.04, so you can update to ZCS 8.5 on Ubuntu 12.04 and then plan your future OS upgrade. Following steps similar to the Ubuntu 12.04 section above.

ZCS8 Upgrades Requiring OS Upgrades Also - Switching To A New Server OR Adding More Servers


The Zimbra Support has asked the Developer and QA teams to confirm, test, and document the following options below. This request is currently a private comment in the following bug/rfe :

Data Migration Notes:

  • zmmboxmove was new in ZCS 7.1.3 , this move accounts between mailstores using the same LDAP master.
    • Prior to ZCS 7.1.3, the command to do this was called zmmailboxmove.
  • zmztozmig export / imports account data from one ZCS server to another ZCS server.

Possible options


Add New Servers To Replace ZCS Services And Use zmmboxmove - Necessary For RHEL 4/5 to RHEL6

This option would be to add servers to your ZCS environment with the intention of "turning off" the ZCS services on the old servers.

  • Add a ZCS LDAP slave running the OS and ZCS version you want. Prompt the new ldap slave to become the ldap master and later decommission the older one.
  • Add new mta servers running the OS and ZCS version you want. Decommission older boxes once done.
  • Add new mailstores running the OS and ZCS version you want. Use the zmmboxmove command to move all the accounts to the new mailstores. Decommission the older mailstores once this is done.
  • Add new proxy servers running the OS and ZCS version you want. Decommission older boxes once done.
Active ZCS partition/mount is able to be relocated to new server

This process basically follows http://wiki.zimbra.com/wiki/Ajcody-Notes-Server-Move [RSYNC] but ignores all the rsync copy references.

The below is a summary, you should read the wiki above in FULL. We have yet to fully test this against various options and confirm it works when the last step is an actually a new ZCS version that is installed.

    • A new head node/server is used and is attached to the network storage that held the ZCS data.
      • [we are currently testing this to confirm what way will work best]
      • Move from RHEL 4/5 to RHEL6 Example:
        • Install new OS version on new system/VM
        • Install Zimbra software of current ZCS version on the "old" server on to the "new" server. Your version of ZCS on the old server should be at a version of ZCS that also offers RHEL6 support.
          • Confirm ZIMBRA User And UID Match between the two servers.
          • Confirm /etc/hosts and DNS resolution is setup
          • New server should be setup to be the same hostname/zmhostname and ip addresses. The ip address change would happen when your ready to bring down the old server, make sure you reassign a new ip address for that network interface incase someone accidentally boots it back up.
          • Run installer with the -s option, installing only the software. [ ./install.sh -s ]
          • Remove the dummy install [ rm -rf /opt/zimbra ; mkdir /opt/zimbra ]
            • This is necessary to have the full install/upgrade we do later to know zcs is on the system.
          • Now mount zimbra data volumes on new system [data was zcs 6 or zcs7 running rhel 4/5] like it was on the old server. Please make sure all your zmvolumes and zimbra backup volumes are accounted for.
          • Optional - /opt/zimbra/libexec/zmfixperms --verbose --extended
          • Run the zcs installer again [same version of zcs that was on the other box] ./install.sh . The installer should indicate it's an "upgrade", if it seems like it's doing a new installation - you should stop here and troubleshoot.
          • Confirm ZCS operations.
        • You can now do your ZCS upgrade, higher version than what you were running, normally.
Rolling Upgrade References

Our current rolling upgrade wiki stopped at ZCS6 in regards to updates:

We have an RFE in to get a new dedicated Rolling Upgrade wiki that will handle ZCS 7 and ZCS 8 or simply update the existing one.

RSYNC

Zimbra Backup/Restore

Additional Notes


Moving Logger Services To New Server


rsyslog

Notes shared with me from customer.


Changing logger services from one server to another. This document describes the procedures taken in a multi server install running zimbra 7.2. The original logger server is a mailboxserver running on RHEL 5. The new logger server is also a mailbox server but it is running RHEL 6. This document was created for the purpose of replacing servers from a RHEL 5 environment to a RHEL 6 environment. This environment is also running rsyslog and not syslog, so this document is tailored toward that. This document will not go into detail of about rsyslog, for tutorials on that please visit http://www.rsyslog.com/ .


Assumptions:

  • An existing running multi server environment running rsyslog and zimbra 7.2.
  • Custom rsyslog configuration.
  • New logger server is needed and old logger services need to be disabled.
  • The version of rsyslog is consistent among all your nodes
  • Logger package is installed on a message server


  1. Install a new mailbox server with the logger package into your multi server environment.
  2. With the new logger server installed the ldap server will attempt to change the "zimbraLogHostname" attribute on each host, it is not always successful at doing that especially if your "ldap_url" differs from host to host due to splitting your ldap load.
    • Check each host to ensure that the change to the new logger host occured
      • zmprov gcf zimbraLogHostname
    • If it is not, make the correction and change it.
      • zmprov mcf zimbraLogHostname Newhost.FQDN
  3. Make a back up of your rsyslog.conf files on every host
    • cp /etc/rsyslog.conf /etc/rsyslog.conf`date '+%Y%m%d'`
  4. Edit the rsyslog.conf on every node except for the two logger nodes. The zimbra section should be at the bottom of the file.
    • Change the hostname entries that have old logger to the new logger hostname.
  5. Restart rsyslog on the hosts with the newly edited rsyslog.conf files.
    • service rsyslog restart
  6. Copy the rsyslog.conf from the old logger server to the new logger server from the new logger server and restart rsyslog on the new logger server.
    • cd /etc
    • scp -p root@old_logger_server:/etc/rsyslog.conf .
    • service rsyslog restart
  7. On the old logger server copy the rsyslog.conf from another message server in your cluster. The file that you are copying over should be from a machine which you just recently edited the rsyslog.conf file and restarted rsyslog. The file should not come from any logger host. If you do not have another machine to copy that file from you can always run "/opt/zimbra/bin/zmsyslogsetup" and and restart rsyslog. If you do have to run "zmsyslogsetup" ensure to re-add any customizations that you may have had prior to running the command.
    • cd /etc
    • scp -p root@other_message_server:/etc/rsyslog.conf .
    • service rsyslog restart
  8. By this point you should be able to log into the web admin interface and see that there are still green check marks on the "Server Staus" of each host on the "Server Staus" page. Now you have to disable logger on the old logger server and verify.
    • Remove service [on old_logger_server.FQDN]
      • zmprov ms `hostname` -zimbraServiceEnabled logger
    • Verify the logger service is removed [on old_logger_server.FQDN]
      • zmprov gs `hostname` zimbraServiceEnabled
    • Verify that the logger service is no longer running [on old_logger_server.FQDN]
      • zmcontrol status
  9. As the zimbra user edit the crontab on the old logger machine to ensure that it does not send out mail reports or attempt to generate graphs. Ensure that following lines arecommented out (these lines should be located below the section labeled "crontab.logger"):
    • 00,10,20,30,40,50 * * * * /opt/zimbra/libexec/zmlogprocess > /tmp/logprocess.out 2>&1
    • 10 * * * * /opt/zimbra/libexec/zmgengraphs >> /tmp/gengraphs.out 2>&1
    • 30 23 * * * /opt/zimbra/libexec/zmdailyreport -m
  10. You are done. You can always check on the web admin interface to see that the logger host no longer shows the logger service running under the "Server Status" page.
Personal tools