SEP sesam Extension for Scalix

From SEPsesam
Jump to: navigation, search
Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.

Copyright © SEP AG 1999-2018. 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

Installation

The Scalix extension is included in the SEP 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 file system 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

Browse scalix01.JPG

 all:path=<path of Scalix data>:vgpath=<LVM device>:snapsize=<size of snapshot>

Example:

 all:path=/var/opt/scalix:vgpath=/dev/scalixvg/scxlv:snapsize=200M
  • 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:
mail:host=<mailserver>:instance=<Scalix instance>:mn=<mailnode>[:port=<LDAP port>] [,<user1>, <user2> ...]
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 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

  mail:<name of server>:<name of mailnode>, [<user1>, <user2>, ...]

still works, but the new form is preferred.


Example:

 [root@ozeanix ~]# omshowmn
         **      ozeanix,sep

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

mail:host=ozeanix:mn=ozeanix.sep, sxadmin 

If you have more Scalix instances:

 mail:host=ozeanix:instance=ozeanix:mn=ozeanix.sep, sxadmin, Tux Pingi

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

 mail:host=ozeanix:instance=ozeanix:mn=ozeanix.sep, Tux Pingi, sep sesam, test user

Backup all mailboxes:

 mail:host=ozeanix:instance=ozeanix:mn=ozeanix.sep
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:

support@scalix, admin@sep.de

will exclude

support@scalix.com 
support@scalix.sep.de
admin@sep.de
Attention

Do not start both backup types at the same time, because they will block each other.

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:
mail:host=<mailserver>:instance=<Scalix instance>:mn=<mailnode>[:port=<LDAP port>] [,Public Folders]

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 file system 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 specified 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:

 mail:host=ozeanix:instance=ozeanix:mn=restore.ozeanix.sep
Note

If users are created in a different mailnode, you will not see them in the Scalix Admin Console. To delete them you have to use omdelu command. But access via webmail or IMAP is certainly possible.


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:

Scalix restore 1.jpg

Select the last successful save set:

Scalix restore 2.jpg

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:

Scalix restore 3.jpg

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:

Scalix restore 4.jpg

Accessing the Restored Mailbox

After a successful restore, it is time to access the restored data. This can be achieved 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:

root@scalixbox:# omshowu -m all | tail

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

Scalix restore shell 1.jpg

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

root@scalixbox:# omshowu "<useraccount"

Command. This example will show the mailbox details:

Scalix restore shell 2.jpg

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 front end, log in with the right user name and password "scalix".

Scalix restore finish.jpg

Further Links/Literature

Download SEP sesam Extension for Scalix.