Upgrading to 6.40

From Zarafa wiki

With the 6.40 release of the Zarafa Collaboration Platform a lot of new features are available, some of these features need to be setup properly for them to work. The most important new features are:

• addition of a Lucene based indexer
• new threading model for performance improvements and less open sockets
• deleted stores are orphaned (not moved to the Public folder), since 6.30.7
• offline data streaming, for faster offline syncing
• complete rewrite of user plugins
• support for contacts in the GAB (ldap only)
• possibility to hide users, groups and contacts from GAB (ldap only)
• support for dynamic groups (ldap only)
• support for email aliases (ldap only)
• More user details available in GAB (ldap only)
• New options for resource scheduling

WebAccess functionality:

• a Today View
• Advanced Find
• better Calendar interface
• many new features in the address book
• Zarafa delegates configuration wizard
• keyboard shortcuts

We also changed the behaviour in some cases, most notably:

• the 'sendas' property, which is switched to support groups

Before upgrading

First make sure you BACK UP ALL DATA (the data contained in MySQL and your config files). Quite some LDAP parameters have changed. If the Zarafa Storage Server sees no users, it thinks those users have been removed and then 'removes' the stores of those users. Removed stores are simply "orphaned" so nothing will be deleted, but it is not easy to revert that operation.

To prevent users deletion or creations the safe mode can be used. Add the following option to the /etc/zarafa/server.cfg before restarting the Zarafa-server.

 user_safe_mode = yes

This option can be disabled after the upgrade is done and everything is tested.

Upgrading

For most people, upgrading is as easy as upgrading the packages. But before you restart the services you should manually update your configuration files and optionally make some changes to your LDAP (or Active Directory) server. Debian packages will automatically restart services. Some services will not correctly restart because of configuration options that change. You might see errors on your screen, but this is normal, and not destructive. All your data will still be present.

The config files have changed quite a bit. Use the diff command to find the differences between your version of the config file and the version shipped with ZCP in /usr/share/doc/zarafa/example-config. Most important are the server.cfg and ldap.cfg (in case you use LDAP or Active Directory) files.

Check /etc/zarafa/ldap.openldap.cfg or /etc/zarafa/ldap.active-directory.cfg and make the following changes: (ADD = new, MOD = should change, DEL = should remove, (!) = mandatory)

• ADD: ldap_search_base (!)
• ADD: ldap_object_type_attribute
• ADD: ldap_user_type_attribute_value
• ADD: ldap_group_type_attribute_value
• ADD: ldap_contact_type_attribute_value
• ADD: ldap_company_type_attribute_value
• ADD: ldap_addresslist_type_attribute_value
• ADD: ldap_dynamicgroup_type_attribute_value
• ADD: ldap_server_type_attribute_value

• MOD: ldap_nonactive_attribute
• MOD: ldap_user_search_filter
• MOD: ldap_group_search_filter
• MOD: ldap_company_search_filter
• MOD: ldap_server_search_filter
• MOD: ldap_addresslist_search_filter

• DEL: ldap_user_scope
• DEL: ldap_group_scope
• DEL: ldap_company_scope
• DEL: ldap_server_scope
• DEL: ldap_addresslist_scope
• DEL: ldap_user_search_base
• DEL: ldap_group_search_base
• DEL: ldap_company_search_base
• DEL: ldap_server_search_base
• DEL: ldap_addresslist_search_base

It might be a good approach to fill in everything in the new ldap.cfg file to get an optimal configuration for future upgrades too.

Run ldap-switch-sendas.pl from /usr/share/doc/zarafa/ (or [get it from our forums]) to upgrade 'send as' settings in LDAP from 6.x to 6.40.

When using LDAP or Active Directory (ADS), set applicable shared stores to 'room' or 'equipment' resource types to extend the addressbook. (for ADS a new plugin is required, for LDAP there is a new zarafa.schema file required)