SEP sesam Components

From SEPsesam
Revision as of 19:26, 17 January 2017 by Sta (talk | contribs) (Draft - meant for inclusion to printed guides.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Draft.png WORK IN PROGRESS
This page is a draft. Treat the information on this page with caution as it may be incomplete.

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

Overview of SEP sesam Components

A complete SEP sesam environment consists of different components or modules, which can be combined according to your needs to implement optimized backup. Each module is installed separately.

Essential modules of each SEP sesam environment are: SEP sesam Server, SEP sesam Remote Device Server, SEP sesam GUI, SEP sesam Client(s), and optionally other modules represented as the SEP sesam extensions. The SEP sesam environment is managed centrally by the SEP sesam GUI.

SEP sesam Server

SEP sesam Server is the central management module. It contains the SEP sesam database together with indexes and metadata, and provides backup and other data protection related services for one or more SEP sesam clients. Note that SEP sesam Server is always a SEP sesam Client too. Server module can be installed on any server or workstation (Linux, Windows, etc.). SEP sesam support matrix is available online at SEP sesam OS and Database Support Matrix.

SEP sesam Server performs the following tasks:

  • Starts backup/restore jobs on the clients.
  • Administers the SEP sesam database.
  • Saves the log files.
  • Controls the SEPuler.

SEP sesam Remote Device Server (RDS)

RDS is a storage management component that enables backing up data at a remote location to disk or tape on a server. The backed up data is stored on the RDS, while client-related metadata is stored on the master SEP sesam Server. RDS manages storage devices across locations, controls the preparation of data to be backed up on a SEP sesam Client, and writes the data to backup media. During a restore, it locates the save sets and sends the data to the client. SEP sesam RDS is always a SEP sesam Client too. It consists of three components: Sesam Transfer Protocol Server (STPD), Sesam Multiplex Stream Server (SMS), and SEP sesam Client (SBC) including remote access. The control of the tasks is maintained by the SEP sesam Server.

SEP sesam Remote Device Server performs the following tasks:

  • Serves as an interface between network and storage device.
  • Controls remote drives in physically distant locations.
  • Formats files on the tape (MTF=Microsoft Tape Format / CPIO=Unix / SIDF=Novell Services)
  • Reads/writes files to and from disk/tape.

SEP sesam Client (SBC)

SEP sesam Client is a system that has a SEP sesam Client package installed, is added to the SEP sesam environment as a client and is included for data protection in the backup plans. Clients may be workstations, PCs, virtual machines or file servers with gigabytes of data. The abbreviation SBC(sesam backup client)is used in a more technical sense for programs, which are executing backup, migration and restore tasks.

SBC collects and consolidates the backup data on the client system, and delivers it to STPD (Sesam Transfer Protocol Server). The SBC module can be controlled directly without other SEP modules by using SEP sesam CLI.

SEP sesam Client performs the following tasks:

  • Waits until the SEP sesam Server starts a backup job.
  • Generates save sets from the information that comes from the SEP sesam Server.
  • Transmits backed up data to the RDS.
  • During restore, it receives stored data from the RDS.

SEP sesam Graphical User Interface (GUI)

SEP sesam GUI is the central management interface for the SEP sesam environment, providing easy access to SEP sesam configuration and management. SEP sesam GUI is platform independent – it is based on Java, therefore a Java Runtime Environment (JRE) 1.7 or higher has to be installed. GUI’s options are available according to the type of user. In case the SEP sesam environment consist of more SEP sesam Servers, they are managed from a single location by the Master GUI. For more information, see SEP sesam Graphical User Interface (GUI).

SEP sesam extensions

SEP sesam provides ongoing availability of business-critical applications on virtual servers with extensions which were specifically developed for virtual environments (VMware vSphere, Citrix XenServer, Microsoft Hyper-V).

It supports online backup of all modern and most widely-used databases, including Oracle, DB2, MS-SQL, SAP R/3 and MySQL.

SEP sesam also provides backup and restore of mail and groupware servers, such as Open-Xchange, MS-Exchange, Scalix, Zarafa, Lotus Domino and GroupWise.

Check the support matrix before selecting the required extension.

Extensions for databases

OracleSAP R/3SAP HanaMS SQLIBM DB2InformixSAP R/3 with MaxDBMySQLPostgreSQL

Mail / Groupware / ECM extensions

MS ExchangeMS SharePointJIRALotus DominoGroupWiseOpen-XchangeScalixZarafaJIRA

Extensions for virtual environments

VMware vSphereHyper-VCitrix XEN ServerRedHat Enterprise Virtualization (RHEV)

Extensions for disaster recovery

Bare Metal Recovery Linux Bare Metal Recovery WindowsSEP sesam Disaster Recovery

OS, storage & archiving extensions

Si3 DeduplicationSI3 ReplicationNDMPNetAppNovellMac OS

What's next

Installation