4 4 3 Beefalo:User Manual
Copyright © SEP AG 1999-2019. 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.
This User Manual describes the SEP sesam interface and provides guidance on how to use SEP sesam. Some of the GUI features may be restricted by the license agreement between SEP AG and the customer. In addition, some features may be limited by the backup strategy implemented at the customer's site. The limitations may be released by purchasing additional licenses or by changing the actual backup architecture. Please contact your distributor or SEP AG at firstname.lastname@example.org for further information.
For a printable version, click here.
- 1 Introduction
- 2 SEP sesam concepts and principles
- 3 Basic backup configuration
- 4 Directory structure of SEP sesam software
- 5 The SEP sesam Graphical User Interface (GUI)
- 6 Menu bar and Toolbar
- 7 Components
- 8 Tasks
- 9 Scheduling
- 10 Job state
- 11 Monitoring
- 12 Logging
- 13 Appendix
Welcome to SEP sesam
SEP sesam hybrid backup and disaster recovery solution is a high-performance solution for protecting data in hybrid environments – physical, virtual and cloud – of any size. Supporting the widest range of operating systems (Microsoft, VMware, SAP, etc.), databases and applications, SEP is the perfect solution for IT professionals managing data protection and business continuity.
A comprehensive portfolio of modules ensures uninterrupted data protection for a wide variety of applications and databases, including SAP HANA on Intel & IBM Power platforms, SAP NetWeaver & SAP ASE.
The SEP sesam multi-streaming technology enables extremely fast, simultaneous backups of an unlimited number of servers to different backup media such as disk, tape and cloud. After a disaster, SEP sesam Si3 replication technology offers a fast and located independent recovery of single files up to the complete system. In addition, companies with SEP sesam are hardware and software independent, which makes it possible to consolidate several backup systems into a centrally managed backup solution such as SEP sesam. This enables IT managers to flexibly adapt their infrastructure to the constantly growing requirements.
SEP sesam concepts and principles
Basic backup configuration
Make sure that the hardware and software requirements are met before configuring SEP sesam backup. For details, see SEP sesam Requirements.
Directory structure of SEP sesam software
For details on SEP sesam directories, see Directory Layout.
The SEP sesam Graphical User Interface (GUI)
The SEP sesam GUI consists of different areas, as described in SEP sesam Graphical User Interface (GUI).
Menu bar and Toolbar
In the menu bar, you can find the menus File, Activities, Configuration, Window and Help.
Under the Tasks menu, you can configure backup, restore, migration and Si3 replication tasks.
SEP sesam establishes schedules as a frame, to which you link different events, such as backup, migration, replication, etc. A schedule defines the recurrence of an event and may be executed in minutes, hours, days, months or years.
Under the Job State, you can check the status of all jobs (backups, restores, migrations, etc.).
Monitoring provides several features, including a dashboard (displays the state and other details of your backups and restores), last backup state (shows the last status of each configured backup job), shows all running processes/daemons, and the status of all used disk drives (information on queue).
SEP sesam creates two protocols or log files for each backup day: the status file and the day log. These files are available in
<SESAM ROOT>/var/prot. It is recommended to use the SEP sesam log files to detect operations that caused errors or malfunctions, for example, in case of a failed backup. For details, see Analyzing SEP sesam Log Files.