Archive:SEP sesam Extension for Scalix

From SEPsesam
Revision as of 09:30, 19 April 2006 by Rs (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

SEPsesam for Scalix Groupware Server

(C)SEP AG, R. Seyerlein

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

Any form of reproduction of the contents or parts of this manual is only allowed with written permission of SEP AG. During completion of this manual SEP put high diligence on correctness and usability of the information contained in it. SEP AG cannot issue a guarantee on the contents of this manual.

SEP AG internal document identification:

$Id: sesam_scalix_en.tex,v 1.4 2005/11/24 11:31:36 sesam Exp $

Introduction

SEPsesam online module for Scalix provides an online backup of Scalix Grouware Servers. This includes saving and restoring single user mailboxes full backup of the Scalix instance, for the case of a complete system failure.

System requirements

  • Scalix Server on Linux
  • SEP sesam v2.4 (incl. DB-Online-Module for Scalix)
  • the standard Sesam Backup Client is already installed
  • working SEPsesam file system backup for this client
  • for complete online backups, Scalix data should be on a filesystem providing snapshots.

Installation

  • First verify that the standard Sesam Backup Client is already installed
  • File system backup should work 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


  root@scalix:~> cd /tmp                                                     
  root@scalix:/tmp> tar xvzf linux_scalix.tgz                                
  root@scalix:/tmp> cp sesam_scalix_2.4.1.10/sbc_scx /opt/sesam/bin/sesam    
  root@scalix:/tmp> cp sesam_scalix_2.4.1.10/sbc_scxend /opt/sesam/bin/sesam 
                                                                           

Configuration

The further configuration can be done by GUI. So start sesam GUI

Configuration of a full Scalix backup

Full backup will be executed after pruposal of Scalix. The Scalix server will be suspended to make a filesystem snapshot. After this server operation is resumed. Then data is then saved to sesam server.

  • Create a new backup task for the Scalix server
  • Choose Scalix as task type
  • Enter all:<path of Scalix data>:<path of LVM device>:<size of snapshot> for backup source e.g.
   all:/var/opt/scalix:/dev/scalix_vg/scalix_vg:500M directory
  • Schedule the task like any other backup

It's also possible to make an offline backup. Then, sesam will shutdown Scalix server completely and save Scalix data directory directly. After this server is started again. Certainly no access to Scalix server is possible during backup operation.

Configuration of mailbox backup

  • Create a new backup task for the Scalix server
  • Choose Scalix as task type
  • Enter mail:<name of server>:<name of mailnode> <user1> <user> for backup source e.g. mail:scalix:scalix,de

If no users are given, all are saved.

  • Schedule the task like any other backup

Examples for backup source:

 mail:scalix:scalix,de


Attention: Do not start both backup types at the same time, bcs. they can block each other.

Restore of Scalix server

Complete restore

A complete restore can only be done, if Scalix is offline. Bcs. many files depend on each other, a full restore of saveset with option overwrite is recommended. Start the restore wizzard and perform same steps as for a normal filesystem restore.

Single mailbox restore

During restore of mailboxes, data will be restored to Scalix server and then be imported. As target, a (restore) mailnode can be specfied into which data should be imported e.g. scalixrecover,de This is usefull for get back deleted e-mails without overwritting new ones.

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 restore is started without option overwrite, mailbox will not be imported. The password of newly created users will be scalix.

Literature

For further reading on the topic we recommend the following documents:

  • Scalix Backup & Recovery