Line 30:
Line 30:
−
===== Updating =====
+
==== Updating ====
+
Before updating, '''be sure to do a full backup of zarafa database'''. In certain circumstances, this database may be reinitialized during upgrade. In that case you could lose all zarafa datas (emails, appointments, etc ...)
−
Download newer rpms
+
To upgrade, download newer rpms
rpm -Uvh zarafa-6*.rpm zarafa-webaccess-6*.rpm zarafa-licensed-6*.rpm
rpm -Uvh zarafa-6*.rpm zarafa-webaccess-6*.rpm zarafa-licensed-6*.rpm
/etc/e-smith/events/actions/zarafa-update
/etc/e-smith/events/actions/zarafa-update
+
+
Note that configuration files for zarafa are also updated. Those files are contained into '/etc/zarafa/' directory. If these one were modified to suit your need, remember to merge your modifications into the new one.
==== smeserver-zarafa ====
==== smeserver-zarafa ====
Line 206:
Line 209:
This howto enables SpamAssasin [[:Zarafa Bayesian Learning | Bayesian learning for Zarafa]]
This howto enables SpamAssasin [[:Zarafa Bayesian Learning | Bayesian learning for Zarafa]]
−
====Mail Sorting====
+
==== Mail Sorting ====
Maildrop as configured with
Maildrop as configured with
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29,
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29,
+
+
==== Backup and restore ====
+
===== Backup =====
+
Backup is done normally with [[Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :
+
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok
+
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.
+
+
===== Restore =====
+
'''Warning :''' Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version !
+
+
Restoring a backup of zarafa database is done following those steps
+
*stopping zarafa server
+
/etc/rc.d/init.d/zarafa-server stop
+
*deleting all tables currently into zarafa database
+
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \
+
gawk '{print "drop table " $1 ";"}' | mysql zarafa
+
*import the backup of zarafa database
+
cd /directory/containing/your/backup
+
mysql < zarafa.dump
+
* restart zarafa server
+
/etc/rc.d/init.d/zarafa-server start
=== Bugs ===
=== Bugs ===