This document discusses a hands-on workshop for configuring and using the Zarafa Archiver. The exercises will be done on a virtual machine and cover installing the archiver packages, configuring the archiver controller, enabling archiving for users, performing archive runs, and automating archive runs with cron jobs. Requirements include a central LDAP, ZCP and archiver servers in a distributed setup, and Zarafa version 7.0.4 or higher.

1. Zarafa Archiver handson Workshop

2. Introduction
During this handson lab we will discuss design choices, best pratices
and important configuration options when deploying the Zarafa
Archiver
The exercises will be done on the virtualbox appliance
IP-address: 192.168.56.101
Login: zarafa/zarafa

3. Example configuration

4. How to get and use Zarafa Archiver?
Zarafa Archiver is an additionl Zarafa product.
Professional and Enterprise subscription include 20 free archive mailbox
Zarafa Archiver software is partly included in ZCP packages and as
additional Zarafa Archiver packages. Both can be downloaded from
the portal
To use Zarafa Archiver an additional subscription key has to be placed
in /etc/zarafa/license

5. Requirements
To use the full features of Zarafa Archiver a central LDAP or ADS is
required
Both ZCP and Zarafa Archiver servers will be configured in distributed
setup (also used with multi-server)
Version 7.0.4+ is required
2 server nodes (in this handson session we use only one node)

6. Exercise 1: Installation
Install the Zarafa-archiver packages available in /home/zarafa/Desktop/
packages
Place archiver subscription key from /home/zarafa/Desktop/packages
in /etc/zarafa/license
Restart zarafa-licensed to active new keys

7. Server configuration
The following options should be changed in the server.cfg
user_plugin = ldapms
enable_distributed_zarafa = true
server_name = zarafa
For the user plugin the ldapms.*.cfg template should be used
In this lab appliance, these settings are already done!

8. Available Archive policies

9. Exercise 2: Configure Archiver controller
Edit the following parameters in /etc/zarafa/archiver.cfg
archive_enable = yes
archive_after = 30
stub_enable = yes
stub_after = 30
enable_auto_attach = yes
auto_attach_writable = yes
sslkey_file = /etc/zarafa/ssl/client.pem
sslkey_pass = zarafa
log_level =6
mysql_password = zarafa

10. Exercise 3: Enable archive for user
Login to the phpldapadmin
Set on user demo1, demo2 the
attribute
zarafaUserArchiveServers and
use servername zarafa

11. Exercise 4: Perform archive run
Execute the Zarafa-archiver for user demo1
zarafa­archive ­u demo1 ­A
Check the logfile for the different archive stages
Login to WebAccess to check archive mailbox and archived messages

12. Exercise 5: Enable archive on delivery
To archive directly every incoming email the option
archive_on_delivery in dagent.cfg should be enabled
Archive on delivery only works when user has archive
When keeping a mail history for several years, don't forget to enable
the purge option in Archive controller
Users can have read-only permissions on archive mailbox, so emails
can be deleted in archive mailbox
With option cleanup_action = store in archiver.cfg can be used to keep
all emails in archive mailbox which are no longer in primary mailbox

13. Automate archive runs
To run the Zarafa-Archiver every night or week, set a cronjob to
perform this task
0 1 * * * /usr/bin/zarafa-archiver -A
0 2 * * * /usr/bin/zarafa-archiver -C

14. Archive mailboxes and delegate users
When adding delegate mailbox in Outlook or WebAccess, archive
mailbox will be added as well
In order to access archive mailbox delegate needs permissions
Za-aclsync can be used to propagate permissions from primairy
mailbox to archive mailbox
za-aclsync --sslkey-file=/etc/zarafa/ssl/client.pem
--sslkey-pass=zarafa

15. Questions?