Product SiteDocumentation Site

Chapter 7. Archive Management

7.1. Automatic
7.1.1. Using OpenLDAP
7.1.2. Using Active Directory
7.2. Manual
7.2.1. Creating an archive store
7.2.2. Attaching an archive
7.2.3. Listing attached archives
7.2.4. Detaching an archive
7.2.5. Listing users that have an archive attached
7.2.6. See details of archive store
7.2.7. Unhooking an archive store
7.2.8. Hooking an archive store
7.2.9. Removing an archive store

7.1. Automatic

The zarafa-archiver can attach archive stores automatically based on user attributes stored in the LDAP or Active Directory. When using this way of attaching stores, zarafa-archiver will create genuine archive stores on the server and attaches the user stores to these archives stores based on the information found in the LDAP or Active Directory.
When using this type attaching and detaching, Outlook and the Webaccess will load the archive stores of the primary stores and all opened shared stores automatically.
To use this feature the enable_auto_attach setting must preferably be set to yes in /etc/zarafa/archiver.cfg:
enable_auto_attach = yes
Alternatively zarafa-archiver can periodically be run to perform the auto-attach operation:
zarafa-archiver --auto-attach

7.1.1. Using OpenLDAP

To add an archive store to a user through LDAP, the following attribute has to be modified zarafaUserArchiveStores. This is is a multi value attribute, which needs to be set to the server name or server names of the servers that should contain an archive store for the user.
A typical ldif could look like this:
dn: uid=user,ou=users,dc=example,dc=com
objectClass: inetOrgPerson
objectClass: organizationalPerson
objectClass: person
objectClass: top
objectClass: zarafa-user
objectClass: posixAccount
cn: User
gidNumber: 0
homeDirectory: /bin/false
sn: User
uid: user
uidNumber: 1000
givenName: User
mail: user@server.com
userPassword:: e1NTSEF9VzlXV0U3N1NEcW54UkJ3SFJkQUYvVkhrUj
zarafaAccount: 1
zarafaUserServer: userServer
zarafaUserArchiveServers: archiveServer
If multiple archives should be attached the ldif might look like this:
dn: uid=user,ou=users,dc=example,dc=com
objectClass: inetOrgPerson
objectClass: organizationalPerson
objectClass: person
objectClass: top
objectClass: zarafa-user
objectClass: posixAccount
cn: User
gidNumber: 0
homeDirectory: /bin/false
sn: User
uid: user
uidNumber: 1000
givenName: User
mail: user@server.com
userPassword:: e1NTSEF9VzlXV0U3N1NEcW54UkJ3SFJkQUYvVkhrUj
zarafaAccount: 1
zarafaUserServer: userServer
zarafaUserArchiveServers: archiveServer
zarafaUserArchiveServers: backupServer

Note

The archive store won’t be created or attached until the next run of zarafa-archiver -A with enable_auto_attach = yes or zarafa-archiver --auto-attach.

7.1.2. Using Active Directory

To add an archive store to a user using ADS, one has to open the user in the Active Directory Users and Computers window and select the Zarafa Features tab.
ADS Features tab
Figure 7.1. ADS Features tab

Next select the archiver feature and click Properties. This will pop up the dialog in which the server names of the servers on which an archive store should exist for the selected user or users.
Select archive servers
Figure 7.2. ADS Select archive servers

Note

The archive store won’t be created or attached until the next run of zarafa-archiver -A with enable_auto_attach = yes or zarafa-archiver --auto-attach.