Zimbra NG Modules/Things To Know Before Upgrading
Zimbra NG - Things to Know Before Upgrading
Zimbra NG - Things to Know Before Upgrading
This wiki will provide an overview on what you need to know when migrating to 8.8 and how the NG Modules will effect your experience.
The NG modules should not be enabled unless you plan to upgrade all nodes in your deployment. Doing so will surface problems in the admin console. This is applicable for upgrades as well as brand new multi-node installations. We recommend disabling the modules on upgraded nodes until all are upgraded and then enabling.
Mobile NG is not currently compatible with two factor authentication or S/MIME. For those who need these two features, please use the legacy mobile sync service at this time.
The beta version of the remote IMAP service (imapd) ships in this release, but defaults does not install by default during installation. Please do not enable for production environments
Current Zimbra Plus and Zextras Suite Users
For customers who are running Zimbra Plus or Zextras Suite on versions 8.7 or below, please note the following
- During the upgrade process, the existing Zimbra Plus or Zextras Suite packages will be removed and the new 8.8 packages will be installed during installation.
- The new 2.6.1 Zimbra Plus or Zextras Suite installer will not install on any Network Edition version.
- Do not install Zimbra Plus or Zextras Suite 2.4.12 or older versions on the 8.8 Network Edition system, it will override the newer packages.
For customers who are already using Zimbra Plus or Zextras Suite Mobile, you will need to block access to http or https before upgrading. During the upgrade process, a switch will be added to LDAP and NG Mobile module will be disabled, because of this, the system will default to the Standard Network Edition Mobile module .
You will need to enable Mobile by doing the following after upgrade on each mail store:
zmprov ms `zmhostname` zimbraNetworkMobileNGEnabled TRUE zmmailboxdctl restart Then go into the NG Management UI and enable Mobile.
If an update occurs without blocking HTTP/S, the mobile device will default back to the Standard Network Edition Mobile module and the device will recognize this as a new sync which will cause all account data on the device to be reloaded. Then enabling NG Mobile module will cause the device to recognize the request to be another new sync request and will cause a second reload of the account data. If this occurs, the user will see their data disappear then reload from the device. In most cases, there is no action required by the user but older devices could have sync issue do to the age of the device.
For customers who are using Zextras Chat, there is no official procedure to migrate existing chat data to Zimbra Chat. There are some postings of blogs and articles by partners and customers but this is not officially supported by Zimbra Support.
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. The following command can be used 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 a new system, for more information, please see Incremental Migration using NG Backup
There are no new license requirements for NG modules. All new modules require a valid license and the number of accounts that can use the Mobile modules will be limited to the number defined by MobileSyncAccountsLimit within the license. You can verify the license by running the following from the command line:
Zimbra Suite Plus (ZSP) or Zextras Suite Network Edition User
Customers who are running Network Edition 8.7 and below and are using Zimbra Suite Plus (ZSP) or Zextras Suite licensing will no longer need to install separate licensing components. If selected, 8.8 will have all features found within ZSP and Zextras Suite installed during the upgrade. You must select zimbra-network-modules-ng during the upgrade process for this to be enabled
Zimbra Suite Plus (ZSP) version 2.5 and higher are only supported on Open Source servers, the installer will no longer allow you to install on network addition.
During the upgrade process you will be prompted to install the new Modules
Install zimbra-chat [Y] Install zimbra-drive [Y] Install zimbra-imapd [Y] Install zimbra-network-modules-ng [Y]
IMAPD is a beta feature but the installer is set to install the packages as part of the default installation for upgrades and new installations. Because the module is independent from the remaining modules and needs to be enabled after installation, this will not effect your current production installation. If you like to exclude the module from your installation, you can enter N when selecting modules section of the installation process.
Install zimbra-imapd [Y] N
Because IMAPD is a beta module, it is not a supported feature and is recommended only to be enabled on non production systems.
If network modules are excluded during a new installation or upgrade, to install them at a later date, you will need to run the installer and select the packages. After installation is complete, please review Missing NG Modules After Installation
NG Features OverView
NG HSM Module: After a successful upgrade the new HSM will be enabled. No action needed
NG Mobile Module:
NOTE: If you are upgrading and/or migrating from an older version of Zimbra to Zimbra 8.8 Production Ready and you plan to enable the new mobile sync for a deployment currently using Zimbra's mobile sync feature, please use caution before enabling the new mobile sync as the token reset will cause all user devices to reload their account data.
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:
- Admin NG is not enabled by default during upgrades from a version earlier than 8.8, so it must be enabled manually before migrating to it.
- Activation of NG Admin module needs to be performed after upgrade.
- When activating NG Admin module all servers in the cluster will be effected.
- 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