5 1 0:SEP sesam Components

From SEPsesam
Revision as of 07:21, 21 September 2023 by Jus (talk | contribs) (Marked this version for translation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Welcome to the latest SEP sesam documentation version 5.1.0 Apollon. For previous documentation version(s), check documentation archive.


Overview


A complete SEP sesam environment consists of different components or modules that can be combined as needed to implement an optimized backup. Each module is installed separately.

Essential modules of any 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 SEP sesam extensions. The SEP sesam environment is managed centrally by the SEP sesam GUI.

Overview of SEP sesam Components

Overview of SEP sesam Components

Overview of SEP sesam Components with details

Overview of SEP sesam Components with details

SEP sesam Server

SEP sesam Server is the central management module. It contains the SEP sesam database together with all indexes and all metadata and provides backup and other data protection related services for one or more SEP sesam clients. Note that SEP sesam Server is always also a SEP sesam Client. The 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 clients.
  • Manages the SEP sesam database.
  • Saves the log files.

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 the client-related metadata is stored on the master SEP sesam Server. The RDS manages storage devices across locations, receives the data during backup and writes it to the backup media. During a restore, it locates the savesets and sends the data to the client. SEP sesam RDS is always also a SEP sesam Client.

It consists of five components: Sesam Transfer Protocol Server (STPD), Sesam Multiplex Stream Server (SMS), SEP sesam Client (SBC), Si3 Deduplication Server and a remote access. The tasks are controlled via the SEP sesam Server.

The SEP sesam Remote Device Server performs the following tasks:

  • Serves as an interface between the network and the storage device.
  • Controls remote drives at physically distant locations.
  • Inspects archive files with different formats and writes corresponding journal files (LIS) (MTF=Microsoft Tape Format / CPIO=Unix / SIDF=Novell Services).
  • Reads/writes files to and from disk/tape.

SEP sesam Client

SEP sesam Client is a system on which a SEP sesam Client package is installed, added to the SEP sesam environment as a client and included in the backup plans for data protection. Clients can 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 the program that performs 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).
  • SBC_PROXY is using specific APIs to connect with Hypervisor (vCenter Server, Hyper-V resource, etc) to perform Virtual Machine backup or connects with Storage Server systems to manage storage snapshots.

SEP sesam Client performs the following tasks:

  • Waits for the SEP sesam Server to start a backup job.
  • Generates savesets from the information that comes from SEP sesam Server.
  • Transmits the backed up data to the RDS.
  • During the 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, so a Java Runtime Environment (JRE) is required. For details on the required version, check Java Compatibility Matrix.

GUI options are available depending on the user type. If the SEP sesam environment consists of multiple SEP sesam Servers, they are managed from a single location using the Master GUI. For more information, see SEP sesam GUI.

Web UI and Restore Assistant

SEP sesam Web UI is a modern web client consisting of the web dashboard and the Restore Assistant. It allows you to securely monitor your environment from anywhere and perform various operations such as starting or locking backups, restarting failed jobs and starting online restores with the Restore Assistant.

The Web UI is configured to work over HTTP or HTTPS (Hypertext Transfer Protocol Secure) and supports the latest versions of major web browsers. The operations and options available after login may differ depending on the user type. Other Web UI display restrictions may depend on the custom roles with specific permissions and UI mode.

Extensions

SEP sesam extensions represent additional add-ons (modules) and functionality that provide a consistent backup of databases, applications, groupware systems, and virtualization environments. Note that the installation and configuration procedure as well as features differ for each extension. Before selecting the required extension, check the support matrix.




See also

SEP sesam Quick Install GuideUpdating SEP sesamRemote Installation of Windows ClientsApplying Service Packs on LinuxSEP sesam GUISEP sesam Web UIRestore AssistantRelease Notes

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