SEP sesam Components
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 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 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, receives data during backup and writes it 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 four components: Sesam Transfer Protocol Server (STPD), Sesam Multiplex Stream Server (SMS), SEP sesam Client (SBC) and a 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 the program, which is 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).
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) is required. For details on the required version, check Java Compatibility Matrix.
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 GUI.
SEP sesam recently introduced additional web interface – SEP sesam dashboard which constantly tracks SEP sesam operations and their state and provides key metrics of your backup environment. For details, see SEP sesam Web UI.
SEP sesam extensions represent additional modules and functionality that provide 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.