Primary Server

The primary server is the server that contains the stores on which users normally work. Although the term primary server suggests that there’s only one primary server, multiple primary servers may exist in a multi-server environment. In this document no distinction is made between a single-server or multi-server environment unless explicitly stated.

Archive Server

An archive server is the server that contains the archives for stores that reside on the primary server. An archive server is a Zarafa server with the sole purpose of providing storage for one or more archive stores. In a multi-server environment this server will be just another node in the cluster.

Unlike primary servers, there’s no need for a multi-server environment to have a multi-archive server setup.

Primary Store

The primary store is the store that resides on a primary server and on which a user normally works. Also known as main store

Archive Store

The archive store is the store that resides on an archive server and which is used for storing archived messages from the primary store.

Zarafa-archiver

Zarafa-archiver is the application that performs the actual archiving job. Zarafa-archiver is typically started from a daily or weekly cronjob. It can be installed on any Zarafa server that connects to the primary or archive server using SSL authentication. Running zarafa-archiver can be done on any node in a multi-server zarafa environment.

Stubbed Message

A stubbed message is a message in the primary store that acts as a placeholder for the archived message. These messages occupy virtually no space in the primary store, but show a user that a message was once there. It also acts as an entry point to the archived copy of that message.

Single Instances

Zarafa Collaboration Platform uses single instance storage whenever possible in order to minimise storage requirements when data is stored more than once. Zarafa Archiver makes use of this technology by remembering which instances it copied to an archive server and referencing that instance whenever possible.

Attached/detached stores

An archive store is attached, when a data link is made with a primary store. Making such a link is called attaching a store, removing such a link detaching it. Detached stores are still available for reading.

Hooked/unhooked stores

A hooked store is available for use as a primary or archive store. Unhooked stores are not available. From the perspective of a mail client or the Archiver they don’t exist. Such unhooked stores are also know as orphaned stores. Unhooked stores cannot be read from or written to. The process of making a store available for a user is called hooking, the reverse unhooking. An unhooked store may be removed.