SEP sesam Extension for Scalix.

(C)SEP AG

Copyright 1999-2011 by SEP AG. All Rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Introduction

SEP sesam online module for Scalix provides an online backup of Scalix Groupware Servers. This includes saving and restoring single user mailboxes; and full backup of the Scalix module, and in the event of a complete system failure, a complete Groupware database restore.

System Requirements

• Scalix Server >=9.4 or greater on Linux
• Sesam Server >= 3.4
• SEP sesam Extension for Scalix.
• Previous installation of the standard Sesam Backup Client
• working SEP sesam file system backup for this client
• for complete online backups, Scalix data filesystem should be on an LVM volume providing snapshots.

Installation

Installation Sesam Client Version 3.4.x

• First, verify that the standard Sesam Backup Client is already installed
• File system backup must be active for this sesam client
• Login as root user
• Unpack the file <OS>_scalix_x.x.x.x.tgz in a temporary location
• Copy scalix/sbc_scx scalix/sbc_scxend into $<$SESAM_ROOT$>$/bin/sesam directory

Installation Sesam Client Version 3.6.x

Beginning with Sesam 3.6 the Scalix extension is included with the Sesam Client installation. No special packages need to be installed.

Backup Configuration

The further configuration can be accomplished using the SEP sesam GUI.

Configuration of a full Scalix backup

Full backup will be executed after reconciliation with Scalix. The Scalix server will be suspended to make a filesystem snapshot. After this the server operation is resumed. At this point Scalix data is then saved to the sesam server from the client.

• Create a new backup task for the Scalix server
• Choose Scalix as task type
• Enter path or browse via GUI

Example:

• Schedule the task like any other backup

path

Scalix data directory (mandatory)

vgpath

path name of the LVM volume (mandatory)

snapsize

size of the snapshot volume

instance

Scalix instance: only needed, if you are running more then one Scalix instance on the same server

The old backup source format all:<path of Scalix data>:<path of LVM device>:<size of snapshot> is still supported.

It's also possible to make an offline backup. In this case, sesam will shutdown Scalix services completely and save the Scalix data directory directly without a file system snapshot. After backup the Scalix services are restarted. There is no access to Scalix services during this backup operation.

Configuration of mailbox backup

• Create a new backup task for the Scalix server
• Choose Scalix as task type
• Enter backup source in the following format:

host

hostname of mailserver (mandatory)

instance

Scalix instance: only needed, if you are running more then one Scalix instance on the same server

mn

name of the mail node (mandatory)

user1 ...

user name for mailboxes to saved. If no users are given all mailboxes of mailnode are saved

port

Listen port for Scalix LDAP servers. Only necessary if your not listening on default port 389

• If no users are given, all are saved.
• Schedule the task like any other backup (See SEP sesam User Manual for Details)

The format of backup source has changed from version 2.4. The old format

still works, but the new form is preferred.

Example:

then the source for a backup of all user mailboxes and only on Scalix instance would be:

If you have more Scalix instances:

For backup of mailboxes of users Tux Pingi, sep sesam and test user:

Backup all mailboxes:

Exclude list

Exclude list can be used to omit certain mailboxes from backup. Exclude patterns are regular expressions which are compared against e-mail addresses.

Example:

will exclude

Configuration of Public Folder backup

• Create a new backup task for the Scalix server
• Choose Scalix as task type
• Enter backup source in the following format:

Restore Configuration

Complete restore

A complete restore can only be done, if the Scalix services are offline. Because many files are interdependent, a full restore of the full saveset with option overwrite is recommended. Start the restore wizard and perform the same steps as for a normal filesystem restore.

Single mailbox restore

During restore of a single mailbox or multiple mailboxes, data will be restored to the Scalix server and then be imported. As target, a (restore) mailnode can be specfied into which data should be imported e.g. recover.scalix.com. This is useful to recover deleted e-mails without overwriting new ones. Because of license restrictions in Scalix 10, the restore mail node must be a sub domain of the original instance.

SEP sesam tries to create the mailnode. An already existing one will be reused. Then the users of the original mailbox will be added. If a user already exists and a restore is started without option overwrite, the mailbox will not be imported. The password of newly created users will be scalix.

Example for target path:

Single Mailbox Example Restore

The following example is a quick guide on how to restore a single mailbox onto a Scalix instance.

Restore Wizard

First select the backup job you want to restore the single mailbox from:

Select the last successful save set:

In this example, we want to restore the mailbox for the user "Alka Kapadia", as such, we only choose this user's mailbox in the selective restore:

After the selection, we set the mailnode target to "restore". The so called "restore" mailnode will be added to the system by SEP Sesam if it doesn't exist. It is a virtual mailnode which can hold an unlimited amount of user mailboxes for restore purposes:

Accessing the Restored Mailbox

After a successful restore, it is time to access the restored data. This can be archived by logging into the users account on the restore area. For this step log into your scalix system using an administrative account (root).

First of all we have to see if the user was created in the restore area, this is possible with the command:

The command will list all existant Scalix users as shown in this example:

The highlighted username is the successfully restored mailbox.

After ensuring the Mailbox has been restored, we need to find out which user name is going to be used to log into the Scalix System. This can also be shown with the

Command. This example will show the mailbox details:

The highlighted string is the user name which is used to log into the restored mailbox.

Open your web browser and go to your Scalix Web Access frontend, log in with the right user name and password "scalix".

Further Links/Literature

Download SEP sesam Extension for Scalix.

Scalix Extension datasheet