Zimbra Next Generation Modules/Things To Know Before Upgrading

Revision as of 20:43, 1 September 2017 by Jhurley (talk | contribs)

Upgrading from version between 8.0 to 8.6

Upgrading to 8.8 is supported but there are a number of items you need to be aware of:

  • 8.8 requires the installation of the proxy server on all setups. In most cases a single server installation does not have proxy installed and configured. You run the following command to see if proxy is installed and enable.

[zimbra@Server ~]$ zmprov gs `zmhostname` |grep zimbraService |grep proxy 
zimbraServiceEnabled: proxy
zimbraServiceInstalled: proxy

If proxy shows as installed and enabled then proxy is running within your system. If not, then you will need to enable proxy by following the Enabling Zimbra Proxy and memcached wiki.

Upgrading from version between 6.0.8 to 7.2.x

In most cases, Zimbra Support recommends doing a migration to new system


NG HSM Module After a successful upgrade the new HSM will be enabled. No action needed

NG Mobile Module: With a successful upgrade, you will need to know the following:

  • Activation of NG mobile module needs to be performed on each mail store
  • All accounts on the mail store will be migrated to the new NG mobile module at the time of activation
  • The existing sync profiles will be used by the NG mobile module.
  • Users do not need to update the profile on the device(s)
  • Sync tokens will automatically be reset, which causes all data to automatically be reloaded on each device.
  • Legacy data will be removed before new data is synced. Users could see the data on the device disappear the reappear, but all data should be the same.
  • After device has been fully synced, users will be able to sync shared calendars, contacts and mail folders.
  • Zimbra Support recommends planning activation of NG mobile module during off hours to limit the confusion and user interruption that may occur do to re-syncing data.
  • For customers running multiple mail stores, Support recommends staggering activation of NG mobile modules to limit end user confusion, network traffic and IO issues.

NG Admin Module -With a successful upgrade, you will need to know the following:

  • Activation of NG Admin module needs to be performed after upgrade.
  • When activating NG Admin module all servers in the cluster will be effected.
  • Activating NG Admin module will convert existing ACL’s rules into NG Admin rules
  • Existing ACL’s rules will be removed from the system.
  • There is no option to restore legacy ACL’s.
  • Support recommend testing NG Admin Module on a test system to verify it meets your origination needs.

NG Backup Module - With a successful upgrade, you will need to know the following:

  • NG Backup Module will be installed on each Mail Store doing the upgrade or installation.
  • NG Backup Module will only backup the account on the mail store
  • NG Backup Module needs to be manually enabled
  • NG Backup Module will perform a full scan at initialization - we recommend during after hours to limit system performance
  • Legacy backup needs to disabled after completion of first scan
Jump to: navigation, search