SBA Book

From SEPsesam
Jump to: navigation, search

Contents

Part I: Introduction

Imprint

Any form of reproduction, duplication or distribution of the contents, in part or in whole, is allowed only with the express written permission of SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to provide accurate and correct information. However, the information in the SEP sesam user documentation is subject to change without notice due to continuous product development. SEP AG cannot guarantee the accuracy of the explanation and shall not be liable for the use of the provided information and product implementation.

SEP sesam and SEP-related modules are trademarks of SEP AG. All other trademarks used at this site are the property of their respective owners.

Part II: Architecture Overview

SEP sesam Requirements

For smooth installation of SEP sesam backup software in the network, name resolution must work properly. Specify a fully qualified name for each SEP sesam component, e.g., every server and client in network.

When finding a client, the operating system (Windows or Linux) first checks the hosts file for name resolution. Next, the configured DNS server is checked. If the DNS server is misconfigured or missing, the hosts file must be set up correctly to provide DNS. You have to enter the names and addresses of all SEP sesam components: SEP sesam Server, backup clients and machines running the graphical user interface (GUI). You must not remove or modify any existing entry of localhost in your hosts file. For details, see How to check DNS configuration.

A DNS server is preferred over entries in the hosts files of all devices. A DNS server allows a system-wide solution. All SEP sesam components must have their names and IP addresses (reverse lookup) added to the DNS server.

PostgresSQL/64-bit

  • On 64-bit Linux, FreeBSD and Solaris PostgresSQL is used as the SEP sesam database.
  • When SEP sesam is installed on MS Windows, the SQLite database was automatically installed up to version 4.4.3 Beefalo V2. As of version 5.0.0 Jaglion, you can choose to install a PostgreSQL database that is included in the SEP sesam installer (or use the SQLite database that does not require a server to be set up and is used with SEP sesam by default). For details, see Installation on Microsoft Windows.
  • When SEP sesam is installed on a 64-bit Unix operating system, PostgresSQL has to be installed before the SEP sesam Server to enable the DB instance to be set up for use.

.NET

On MS Windows, .Net Framework 4 is required for SEP sesam Server installation.

Antivirus software

Deactivate or remove the antivirus software before installing SEP sesam components on each computer. Failure to disable active antivirus software may result in a failed, corrupt or incomplete installation. If antivirus software is installed, it is strongly recommended to turn off any on-demand scanning while a backup is running. For more details, see What effect does an antivirus scanner have on SEP sesam.

Hardware Requirements

The following are the hardware requirements for the SEP sesam Server, RDS or SEP sesam Client. They are similar for both servers, SEP sesam Server and RDS, except for the required space on the file system for the SEP sesam database, which is not necessary for RDS.

  • The hardware requirements for the SEP sesam components represent the common requirements. Additional amount of RAM/CPU may be required for bigger Si3 data stores. For details, see Si3 Deduplication Hardware Requirements.
  • (Windows only) Make sure that you are using CPUs with supported AVX versions (AVX, AVX2, or AVX-512) and FMA3 (Fused Multiply-Add 3-operand Form) or FMA4 (Fused Multiply-Add 4-operand Form) to prevent the Sesam Transfer Protocol Server (STPD) from automatically disabling the HTTPS port. This happens when the CPU instructions are missing due to unsupported AVX. Consequently, the TLS key and certificate cannot be created. For a list of supported AVX versions, see Advanced Vector Extensions.
Requirements SEP sesam Server Standard edition SEP sesam Advanced Server edition SEP sesam Premium Server edition SEP sesam Enterprise Server SEP sesam Client
Memory (without Si3 deduplication) 8 GB RAM Minimum 16 GB RAM 32 GB RAM Minimum 64 GB RAM 2 GB (recommended 4 GB)
Memory (with Si3 deduplication) Minimum 16 GB RAM Minimum 32 GB RAM 64 GB RAM Minimum 128 GB RAM Minimum 4 GB
Core (without Si3 deduplication) 1x CPU with 4 cores (≥ 2,4 GHz) 1x CPU with 8 cores (≥ 2,4 GHz) Minimum 1x CPU with 8 cores (≥ 2,4 GHz) Minimum 2x CPUs with 4 cores (≥ 2,4 GHz) -
Core (with Si3 deduplication) 1x CPU with 6 cores (≥ 2,6 GHz) 2x CPUs with 8 cores (≥ 2,6 GHz) 2x CPUs with minimum 8 cores (≥ 2,6 GHz) Minimum 2x CPUs with 8 cores (≥ 2,6 GHz) -
Minimum hard disk space for SEP sesam metadata 100 GB 300 GB 500 GB 500 GB 4 GB (for all client data)
No. of backup clients Up to 15 Recommended up to 50 Recommended up to 150 Recommended for more than 150 -

Si3 Deduplication Hardware Requirements

  • For the minimum Si3 hardware requirements that apply to the SEP sesam Si3 deduplication server, see the above requirements list. Keep in mind that these requirements represent the demand for deduplication only. In addition, the amount of memory for the operating system and other services should be taken into account.
  • For details on the required Java version, see Java Compatibility Matrix. Si3/Si3-NG is not mandatory, so there is no dependency rule for it in the RPM/DEB packages.
  • When estimating the maximum size of a deduplication store, you have to ensure that there is enough space available for dedup trash, otherwise the deduplication store will run out of space. You should calculate the required disk space based on a representative sample of your full backup and add the additional storage space equal to approximately 50% of the representative full backup.

Disk attachment and protocols

Si3/Si3-NG supports all types of direct-attached disk storage, such as serial attached SCSI (SAS), Serial ATA (SATA), and Fibre Channel (FC)/LUN.

Performance tip

Applies to Windows only: SEP AG recommends using the High performance power plan to increase the performance of your backup. Note that Windows sets all computers to the Balanced power plan by default and you must manually switch to the High Performance power plan. This way, your Windows computer will use more power, but the systems with Si3 will always operate at the highest performance level.

  • From the Start menu, go to Control Panel -> System and Security -> Power Options and change the setting to High performance.

Restrictions

  • Si3 NG deduplication store is not supported for NSS volumes.
  • To avoid problems resulting from the combination of excessively large Si3 deduplication stores and inefficient hardware, the maximum initial Si3/Si3-NG deduplication store size is limited to 40 TB. If you would need to increase this limit, contact SEP support.
  • This limitation applies to the creation of a new Si3/Si3-NG deduplication store in the GUI.
Information sign.png Note
It is recommended to run Si3 deduplication (SEP sesam Server or RDS) on the physical host. It is also possible to run it on a virtual machine. In this case, take into account that deduplication consumes a lot of server resources for reading, processing and writing the deduplicated data, as well as for some other deduplication tasks such as housekeeping and various checks. These tasks require a large amount of IO and a large amount of memory. Si3 performance can be affected by other virtual machines running on the same host. Therefore, if you are running Si3 on a VM, you should be aware of possible bottlenecks and shortcomings.

Required additional amount of RAM and CPU cores

Memory requirements are dependent on the number of concurrent streams and expected workload. The following tables show the recommended minimum additional amount of RAM and CPU cores for a Si3/Si3-NG data store to ensure good performance. The TB value corresponds to the capacity of the Si3/Si3-NG data store.

Information sign.png Note
These requirements relate solely to the need for deduplication. In addition, you should consider the amount of memory for the operating system and other services.
Si3/Si3-NG data store capacity (check initial size limit) RAM
<20 TB at least 16 GiB
20-40 TB at least 32 GiB

The following table shows the number of CPU cores required for a Si3/Si3-NG data store. The TB value is the amount of data backed up (before deduplication)!

Backed up data (before dedup) CPU cores Note
10 TB 4
20 TB 4
40 TB 8
Note

This is the minimum amount to ensure good performance. Depending on the number of concurrent streams, more cores may be needed.


Java Compatibility Matrix

Java version SEP sesam version
Java 17 on demand Note1
OpenJDK 11 LTS 4.4.3 Beefalo, 5.0.0 Jaglion, 5.0.0.9 Jaglion V2 Note2
Java 11 4.4.3 Beefalo, 5.0.0 Jaglion, 5.0.0.9 Jaglion V2 Note2
Java 10 is not supported!
X
Java 9 is not supported!
X
Java 8 ≥ patch level 111 (both Windows and Linux) 4.4.3 Grolar; 4.4.3 Beefalo, 5.0.0 Jaglion, 5.0.0.9 Jaglion V2 Note2
Java 8 (at least patch level 111) ≥ JRE 1.8.0_111 (required for Linux) v. ≥ 4.4.3 Tigon V2
Java 8 (required for Windows) v. ≥ 4.4.3
Java 7 (all OS except Windows) 4.4.3 Note3
Java 7 4.4.2
Java 6 4.2.1 & 4.2.2
Note1
  • SEP sesam 5.0.0.9 Jaglion V2, including SP1, supports Java 17 only on demand, if the use of Java 17 from the command line has been enabled with sm_setup set_java_path -f <java_17_installation_path>
Note2
  • Java 1.8 (≥ 1.8.0_111) is only accepted if it is already installed and the computer does not have a 4K display.
  • 5.0.0.9 Jaglion V2 is the last version of SEP sesam that supports Java 1.8.

Note3

SEP sesam versions 4.4.3 until 4.4.3 Tigon V1 running on non-Windows platform require Java 7, however, SEP sesam uses JavaFX for its web dashboard and user-defined schedules features. If you want to have all the 4.4.3 features available, you need OpenJFX package or Oracle®'s Java 8 (already includes JavaFX) on your SEP sesam GUI client.

Directory layout

SEP sesam always creates two directory structures during installation – one for static data and one for variable data. Both structures can be either in the same main directory or in two different directories. On Unix, the installation directories are represented in the file /etc/sesam2000.ini.

SEP sesam directory aliases

Directory aliases are used to refer to the specified paths in the default SEP sesam directory structure.

<SESAM_BIN>
Refers to the part of the directory structure of a Linux package installation in which the unchangeable files (e.g., binaries) are stored. Path /opt/sesam can not be selected during installation.
<SESAM_VAR>
Refers to the part of the directory structure of a Linux package installation in which the variable files (e.g., configuration and log files) are stored. Path /var/opt/sesam/var is not arbitrary during installation.
<SESAM_ROOT>
Refers to the install location of the SEP sesam file structure for a Linux tarball or a Windows installation. This means that both tarball and Windows installations show <SESAM_BIN> and <SESAM_VAR> on the same location in the file system (referred to as <SESAM_ROOT> here). The install directory must be specified during a tarball installation (default path is /opt/sesam) and also during Windows installation (default path is C:\Program Files\SEPsesam).

SESAM_BIN directory

This directory contains all unchanged files, such as programs, templates, etc. The following directory structure is created during SEP sesam installation:

What Where
Database components

SESAM_BIN/bin/db

GUI components

SESAM_BIN/bin/gui

Dedupe components

SESAM_BIN/bin/sds

Server components

SESAM_BIN/bin/sesam

Communication components

SESAM_BIN/bin/sms

Templates incl. raw versions for first installation SESAM_BIN/skel
Templates for programmable interfaces SESAM_BIN/skel/templates

SESAM_VAR directory

This directory contains all changeable data, such as SEP sesam database, protocols and log files. The following directory structure is created during setup:

What
Where
Database

SESAM_VAR/db[_pg]

SEP sesam database backup

SESAM_VAR/db[_pg]/backup

Configuration files

SESAM_VAR/ini

SSH keys for control communication

SESAM_VAR/ini/sm_ssh

SSL certificates for data transfer

SESAM_VAR/ini/ssl

Notification and metadata logs

SESAM_VAR/lis

Main directory for log files

SESAM_VAR/log

Logs of the Pre- and Post- jobs

SESAM_VAR/prepost

Status and daily logs

SESAM_VAR/prot

Media action logs

SESAM_VAR/prot/media

SEP sesam interface logs

SESAM_VAR/prot/notification

Restore logs

SESAM_VAR/prot/restore

Temporary files for transient storage

SESAM_VAR/tmp

Temporary files for longer storage

SESAM_VAR/work

Mountpoint for VMware and other single item restore tasks

SESAM_VAR/work/mnt

Example

 C:\Program Files\SEPsesam

Sample directory structure

The following is common SEP sesam directory layout after an RPM or DEB installation on Linux. The programs are located in /opt/sesam, the files are in /var/opt/sesam:

 barometrix:~ # find /opt/sesam/ /var/opt/sesam/ -type d
 /opt/sesam/
 /opt/sesam/bin
 /opt/sesam/bin/db
 /opt/sesam/bin/gui
 /opt/sesam/bin/gui/html
 /opt/sesam/bin/sesam
 /opt/sesam/bin/sms
 /opt/sesam/skel
 /opt/sesam/skel/db
 /opt/sesam/skel/templates
 ###
 /var/opt/sesam/
 /var/opt/sesam/var
 /var/opt/sesam/var/ini
 /var/opt/sesam/var/ini/root
 /var/opt/sesam/var/log
 /var/opt/sesam/var/log/db
 /var/opt/sesam/var/log/lgc
 /var/opt/sesam/var/log/sms
 /var/opt/sesam/var/tmp
 /var/opt/sesam/var/work
 /var/opt/sesam/var/work/smslis
 /var/opt/sesam/var/work/info
 /var/opt/sesam/var/work/ctl
 /var/opt/sesam/var/work/sem
 /var/opt/sesam/var/times
 /var/opt/sesam/var/lis
 /var/opt/sesam/var/not
 /var/opt/sesam/var/qm
 /var/opt/sesam/var/glbv
 /var/opt/sesam/var/prepost
 /var/opt/sesam/var/prot
 /var/opt/sesam/var/sel
 /var/opt/sesam/var/db
 barometrix:~ #                      
 /opt/sesam/bin
 /var/opt/sesam

The /var/ini directory contains the following initialization files:

sm.ini
sm_java.policy
sms.ini
odbc.ini
debug.ini
sm_lic.ini
stpd.ini

SEP sesam Components

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.

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 four components: Sesam Transfer Protocol Server (STPD), Sesam Multiplex Stream Server (SMS), SEP sesam Client (SBC) 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.
  • Formats files on 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 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).

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.

Caps.png
SEP CAPS (Cloud App Protection Service)

Microsoft 365

G Suite Salesforce Dynamics 365

ownCloud


Licensing

SEP provides a flexible approach to licensing of hybrid SEP sesam backup solutions that simplifies procurement and meets the specific needs of different organizations.

SEP sesam licenses fall into one of the following broad categories:

Component-based licensing

SEP's component-based licensing model begins with the main Backup Server (SEP sesam Server), Remote Device Servers (media agents), clients and databases or groupware agents. Expansion modules are adapted to the existing environment and the license can be adjusted when extensions are added or the data protection environment is restructured.

In complex environments (data zones) where the average amount of backup data per client is more than 250 GB, the classic component-based licensing model will likely be the more economical solution.

The concept behind this model is to license only what the customer actually uses.

Capacity-based licensing

SEP also offers capacity-based licensing models that provide convenient and flexible licensing for ever-changing environments.

SEP sesam's volume licensing model is primarily aimed at large and dynamic security environments where numerous different database or groupware applications are deployed. Rental licenses are based on volume and provide maximum flexibility with minimal administration effort and no additional cost. This license is ideal for large installations, without depreciation expense.

With this model, customers have access to most features and functionality and the only relevant factor is the amount of data backed up. Customers are able to customize their backup solutions to their specific financial blueprint and infrastructure.

SEP licensing models

For more information on SEP licensing models and available licenses, contact SEP sesam sales.

SEP volume perpetual licensing

The SEP volume licensing model is based on front-side data volume size. In addition, further differentiation is made according to the type and complexity of the databases used (Level 2 and/or Level 3). Licenses are perpetual and maintenance is included for the first 12 months. After the subscription expires, SEP sesam savesets can still be used for restores, but backing up data is no longer possible.

Calculating front-side capacity

All SEP sesam capacity-based licenses are calculated by how much original, source-side data is protected (front-side TB). This equates roughly to the sum of all files, databases and hypervisor snapshots of the clients to be backed up. In practice, this means that the maximum volume of all backup jobs (normally the largest FULL) is calculated, provided it is stored on any SEP sesam media (retention policy). The original data is calculated before deduplication or compression.

SEP subscription licensing

SEP sesam subscriptions are purchased per year, based on the data volume per front-side terabyte and depend on the utilization of the SEP database agents. Maintenance is included in each subscription timeframe. Subscriptions are licensed for a period of 12 months and include full maintenance.

After the subscription expires, SEP sesam savesets can still be used for restores, but backing up data is no longer possible.

SEP classic perpetual licensing

The SEP sesam classic model provides item-based perpetual licenses tailored to a customer's individual needs. Licensing is modular and scalable, expansions of any license components such as database and groupware agents can be made at any time. Maintenance is included within the first 12 months.

SAP Business One Edition

SEP sesam SAP Hana Business One Edition is licensed per number of SAP Business One users. The SAP Business One Edition basic license covers the backup of up to 10 SAP Hana Business One users. SAP Hana Business One Edition is recommended for companies with up to 25 SAP users. SEP classic licenses can be added at any time. The entire SAP portfolio can be licensed with a SEP sesam volume or classic license.

SEP maintenance

All SEP sesam Backup Server licenses for volume models, classic models and SAP Business One Edition include 12 months maintenance. SEP maintenance consists of software updates (incl. latest features, patches and bug fixes) or renewal services and technical support. Extensions (at initial purchase or later) are always adopted to the runtime of an existing SEP sesam Backup Server environment and include a maximum maintenance validity of 12 months. Excluded are consulting services, such as analysis of the data to be backed up, infrastructure analysis, determination of the target state, creation of a solution concept, and installation services.

VM Essential Edition

The SEP sesam VM Essential Edition is licensed according to the number of installed sockets. A maximum of 6 sockets can be used in one license environment. VM Essential (Plus) Edition VMware and Essential (Plus) Edition Hyper-V can be mixed. Note that it is not possible to combine VM Essential and VM Essential Plus editions.

It is not possible to extend functionality, but it is possible to switch to the volume licensing model.

Managed Service Provider

The SEP MSP licensing model is suitable for managed service providers and data center operators who use SEP sesam to offer Backup as a Service (BaaS) to their customers. Based on long-term contracts with different service levels, you get a complete full-service package.

Licensing is based on units divided into 3 different tiers (Standard, Enterprise or Enterprise Plus) or based on the TB data volume (front-side capacity), which is divided into service classes for database usage (Level 2 and Level 3). It is not possible to mix these two license models.

Offers, order confirmations and invoices are issued on a monthly basis.

The SEP sesam MSP maintenance consists of the software upgrade, the update service and the SEP sesam 2nd and 3rd level support. Excluded are consulting services, such as analysis of the data to be backed up, analysis of the infrastructure, determination of the target state, creation of a solution concept, and installation service. During the maintenance period, customers can download patches and bug fixes as well as the latest SEP sesam versions.

After the first qualified error analysis, SEP is available to the MSP for 2nd and 3rd level support via the SEP hotline (+49 (0) 8024 464 464 4) from Monday to Sunday (available 24 hours a day). For details on current support information, contact SEP sesam sales: sales@sep.de.

Also available are SEP CAPS (SEP Cloud App Protection Service) licenses for Cloud-2-Cloud backup and restore of SaaS applications such as Microsoft Office 365, Dynamics 365, G Suite, and Salesforce.

Data volume of backed up items is limited to 1 TB per user (Exchange Online 50 GB), but can be split among all users as desired. There is no charge for uploading/downloading data and inactive users (excluded from the backup) are not charged.

SEP Community Edition

SEP sesam now offers a community edition. For more information, please contact SEP sesam sales.

License administration

Requirements

To create an application-specific license, you need the following information about the SEP sesam backup server:

  • Host name
  • IP address
  • Delivery note number
  • Hardware platform (i386, x86, PPC, ia64, ...)

The SEP sesam Server name and IP address can be found in the SEP sesam GUI menu bar: Help -> License Info or by using the keyboard shortcut ALT + L.

Information about the delivery note number and the hardware platform can be retrieved on the Linux console with the command:

uname -i 

or on the Windows command line with the command:

set 

Send this information to sales@sep.de. If you have any questions during the 30-day installation support period, please contact SEP sesam sales.

Information sign.png Note
After installing SEP sesam, all features are available without restriction for 30 days. Seven days before the temporary license expires you will be reminded about the upcoming license renewal. After the 30-day period has expired, the backup functions of the software are disabled. However, restores up to this point are still possible.

Entering a license

Licenses are usually sent as an attachment by email. The attachment contains the license file, which you must enter on the SEP sesam Server.

  • extract the file sm_lic.zip on the target machine
  • copy the file sm_lic.ini to <SESAM_ROOT>/var/ini

To determine the correct hostname and IP address for your SEP sesam license, follow these simple instructions:

  • In the SEP sesam GUI menu bar, select Help -> License Info.
  • UNIX command line:
 #> source <SESAM_ROOT>/var/ini/sesam2000.profile 
 #> sm_info c  
  • Windows command line:

> <SESAM_ROOT>\var\ini\sm_prof

> sm_info c

Information sign.png Note
Before entering a new license, make a backup copy of your existing license. If there are any problems with the new license, you can always restore your working state with the original license.

Changing an existing license

If the IP address or server name of the backup server is changed, you have to transfer a SEP sesam Server license. This includes adapting the existing server license to match the changed server name and/or the new IP address.

Send the old and new license information to SEP AG (by email to sales@sep.de) to ensure that there were no errors during the transfer and to notify the contact person.

The transferred license is sent by email within the warranty response time. New versions of the existing license and service documentation are created and the customer center is updated.

License transfer is free of charge for customers with an existing SEP upgrade contract.

License and service documentation

In addition to the license file, which is sent in digital form (usually by email), the customer also receives license certificates for the purchased modules and an upgrade/support card (if they have opted for an upgrade or support contract).

The documentation contains a summary of all relevant information (IP address, server name, license details, runtime and response times) and is sent by regular mail or as a PDF document by email.

Licensing FAQs

How do I order a new licence?

To obtain a license, contact SEP sesam sales at SEP contact page or sales@sep.de and provide the following information:

  • host name of the SEP sesam Server
  • IP address of the SEP sesam Server

To determine which specific names are used by SEP sesam (for example, if more than one network card is installed on the server), go to Help -> License Info in the SEP sesam GUI menu bar and check the details. Licenses are available immediately after your purchase or renewal is completed and will be sent to you by email.

License Info displays all licensed components which are currently in use. It also shows you the number of clients and modules needed by your configuration if your SEP sesam Server is currently running in trial mode.

Information sign.png Note
Some features require a special license, for example, SEP sesam Exchange Recovery Pro and SEP sesam SharePoint Recovery Pro. SEP sesam licenses are issued on the basis of the size and requirements of your environment, so make sure that you are aware of feature/application specific licensing. For details on newly introduced licenses, see SEP sesam Exchange Recovery Pro license and SEP sesam SharePoint Recovery Pro license.


License info Beefalo V2.jpg

How do I activate a license?

You can activate licenses easily by importing the license in the SEP sesam GUI. Note that the SEP sesam Exchange Recovery Pro and SEP sesam SharePoint Recovery Pro extensions require special licences and specific activation steps, as described in the section Activating special licenses.

Activating licenses in the SEP sesam GUI

After you have received your SEP sesam license by email, proceed as follows:

  1. From the SEP sesam GUI menu bar -> Help, select License Info. The SEP sesam License Info window appears.
  2. Click the button Import New License. A new window opens prompting you to paste a valid license file.
  3. Copy a valid license file sm_lic.ini and paste it from the clipboard or use the file manager to browse and select the required license as .ini or .zip file.
  4. Click Apply to enable the license.
  5. License info import Beefalo V2.jpg

SEP Tip.png Tip
The License Info also enables you to check the expiration date and to upgrade your license. All licensed components currently in use are displayed.

If the program displays any errors (for instance, in the host name or IP address), email the SEP sesam License Info to SEP sesam sales by clicking the Send as Mail button. Clicking the button opens an email with the license information loaded. Address the message to sales@sep.de and send it.

Activating special licenses

To activate the special licenses, such as SEP sesam Exchange Recovery Pro or SEP sesam SharePoint Recovery Pro, proceed as follows:

  1. Go to Start -> All Programs -> SEP sesam Exchange Recovery Pro or Start -> All Programs -> SEP sesam SharePoint Recovery Pro and open the extension. A License file not installed message appears.
  2. Click the License info button and import the license.ini file.

Both, SEP sesam Exchange Recovery Pro and SEP sesam SharePoint Recovery Pro extensions require specific installation and configuration. For details on these procedures, see SEP sesam Exchange Recovery Pro and SEP sesam SharePoint Recovery Pro.

Why does the W008-License TCPIP address not match the local address 127.0.0.2?

This problem usually occurs on SLES-based Linux systems. Check the file /etc/hosts and change the relevant entry for the loopback address "127.0.0.2" or remove it from the /etc/hosts file entirely.


Part III: SEP sesam GUI


SEP sesam GUI overview

The SEP sesam graphical user interface (GUI) provides centralized administration and easy access to configuration and management of SEP sesam and its environment. SEP sesam GUI is platform independent – it is based on Java and requires a Java Runtime Environment. For details on the required Java version and installation, see Java Compatibility Matrix and Installing and Managing Java.

The SEP sesam GUI has been redesigned with additional functionality to improve usability and provide better access to SEP sesam objects. It provides built-in filtering with different filter types to facilitate searching for specific content items (task, client, data store, etc.). The GUI icons have also been redesigned and additional icons and symbols have been added. For details, see SEP sesam Icons Legend.

SEP sesam features a GUI that provides several ways to customize GUI look and feel, e.g., by changing the fonts, view and layout of GUI elements, select appropriate GUI mode, set up authentication, update GUI client, and change the language. Authorized users can monitor SEP sesam operations online by using Web UI (dashboard) or perform the restores online by using the restore assistant. For details, see Managing GUI.

Information sign.png Note
In v. ≥ 5.0.0 Jaglion, the operations and options available after login may vary depending on the user type. See Available interface options according to user type. Further restrictions on the GUI display may depend on user-defined roles with specific permissions and the UI mode.

GUI components

When SEP sesam GUI is started, it creates a connection to the SEP sesam database. Once the connection is established, the main GUI screen appears. This screen controls all SEP sesam procedures and operations.

SEP Tip.png Tip
When running the SEP sesam GUI as administrator, the new SEP sesam Web UI landing page opens by default (with access to the Web UI, links to documentation, etc.). To prevent it from opening automatically when SEP sesam GUI is started, in the GUI menu bar -> Configuration -> Defaults -> General tab, clear the check box Show SEP sesam web client landing page on startup.

GUI overview Beefalo.jpg

SEP sesam allows you to adjust the GUI layout by undocking, repositioning and rescaling the individual panes of the GUI window. For details, see Customizing GUI.

Menu bar

The menu bar contains provides the options File, Activities, Configuration, Window and Help. Clicking on a drop-down menu or pressing Alt + the underlined letter activates the menu. A function, action or command can then be selected from the listed sub-items. Sub-items can also be activated in a similar manner (mouse click or Alt + the underlined letter) to open input masks for additional or more specific actions.

Toolbar

The toolbar enables you to trigger the tasks and get the status overview with just one click. It contains the following icons: Dashboard, Immediate start: Backup, Restore assistant (opens the online restore assistant in the external web browser), Restore Wizard, Backups (index of backups by status), Calendar Sheet, and About SEP sesam (SEP sesam version information). For details, see Toolbar.

Menu and tool bar Beefalo.jpg

Navigation pane – Main Selection

The navigation pane is located on the left side of the GUI window and called Main Selection. It allows you to navigate through the components of the SEP sesam system. Clicking on the sub-menus (the + sign of each component, or right-click to Expand all) expands the tree to access detailed information. Selecting a component in the Main Selection pane opens the corresponding object in the Content pane.

Content pane

The Content pane, located in the middle of the GUI window, displays the corresponding content for the selected component. For example, locations and clients can be configured under the Components -> Topology.

Properties pane

The Properties pane, located on the right side of the GUI window, shows the properties of the object selected in the Content pane.

Filter pane

The Filter pane, located on the right side of the GUI window, enables you to quickly find the relevant objects.

Activities display

The Activities display is located at the bottom of the GUI and shows the messages and log file protocols for the selected drives or activities. It contains the following tabs:

  • Current messages: The Current messages display shows drives, related current sessions and drive status. Last view shows the result of the last activity. If the option Cyclic is enabled, the messages are cyclically refreshed without user intervention.
  • Performance: The Performance display allows you to monitor and control selected drives. It displays the amount of data being backed up and the transfer rate of individual SMS channels for each of the selected drives.

GUI activities display Beefalo.jpg

Master GUI

If the SEP sesam environment consist of more SEP sesam Servers, a powerful Master GUI is used to manage them. Master GUI enables the administrators to utilize multiple GUIs and manage local and remote locations from a single console.

Master GUI servers.jpg

This mode can be activated by connecting additional SEP sesam Servers by clicking Configuration -> Remote server in the menu bar and setting the connection to On. Inaccessible servers will be displayed in the table view. The GUI client must be authorized to administer additional SEP sesam Servers.

RDS Beefalo.jpg

After an additional SEP sesam Server is configured and a connection is established, a server selection window opens in the upper right corner, showing a list of available servers. The data relating to the media, calendar sheet, current messages and logs components as well as the monitoring sub-components corresponds to the server selected in this window.

The object trees displayed within the Content pane of a Master GUI show all available SEP sesam Servers and their objects. This includes a view of the Job state filters, which can be set to the selected server (Client), location or to all active SEP sesam servers.

Job state filter Beefalo.jpg

Customizing GUI

The SEP sesam graphical user interface (GUI) provides centralized administration and easy access to the configuration and management of SEP sesam and its environment. The GUI can be customized to your individual needs – you can set up different GUI layouts, change the default data size units and filter the displayed contents.

Rearranging the GUI layout

The SEP sesam GUI can be rearranged almost without limitation. You can adjust the layout of the GUI window by undocking, repositioning and rescaling individual panes of the main GUI window, including toolbars. You can simply drag and drop selected windows to create a customized GUI layout.

GUI change-layout Beefalo.jpg

Managing layouts

You can save and manage layouts by clicking Window in the menu bar and selecting the Manage Layouts option.

Window Beefalo V2.jpg

Open the layout and arrange all windows and settings to your liking. Once you are satisfied, give the layout a name and save it. The layout identified with a green arrow (previously blue arrow) is the current layout. If you click Set as Standard the selected layout becomes the default layout (black check mark) and is automatically loaded for the current user the next time the GUI is started.

Window manage layout Beefalo V2.jpg

Changing the data size units

You can change the default setting for the data size units, which are specified with either decimal (KB, MB, GB, TB) or binary prefixes (KiB, MiB, GiB, TiB).

Setting the default data size unit

SEP sesam allows you to choose how your data size should be displayed (e.g, in TiB or TB). In previous SEP sesam versions, the data size was always displayed using decimal units.

  1. Open the GUI and from the menu bar select Configuration then Defaults.
  2. Click the Display Format tab (previously Data displays) and from the drop-down list Default data size select decimal or binary prefix.
  3. Defaults data size Beefalo V2.jpg

Setting a different data size unit for the individual table

It is possible to change the data size units for each individual table, for example, in the context window Backups, Restores, Last Backup State, etc. This setting is only applied to the displayed data size in the individual table and is reset to the default data size when the user interface is closed.

  1. Open the target context window, e.g., Main Selection -> Job State-> Backups, select the Data Size column header and right-click it.
  2. From the Unit menu, select the preferred decimal or binary unit display.
  3. Change data size Beefalo V2.jpg


Filtering displayed content

SEP sesam offers a range of filtering options depending on the context of the user interface. It provides built-in filtering with different filter types that ease the search for specific content items (date range and clients, state, type, task name, etc.) and allow you to quickly find the relevant items. When available, you will find the filter area on the right side of the GUI window.

Backups filter settings Beefalo V2.jpg

Depending on the pre-selected GUI context, the following filter criteria are available (you can filter by one or more criteria):

Date range and clients
Filter the displayed jobs by date, by client and/or by location.
State
Show or hide particular states (in progress, failed, etc.).
Type
Show or hide different event types or their properties. The available options depend on the event type. For example, in the Backups window you can filter by events (NEWDAY, backup, migrations, etc.) and further refine the displayed results by backup level (when applicable; Full, Diff, Inc, Copy).
Task name
You can filter the backup tasks by name. They are displayed below the search field. You can select one or more tasks by holding down the CTRL-key and clicking the name(s).
Filter settings
Activate (default) or deactivate the automatic refresh of the results table.
Pools
Filter the media by media pools.
Loader
Filter the media by storage devices.
End of lifetime
Filter the media by their EOL. By default, this filter is disabled (EOL filter off).
Readability check
Activate or deactivate (media) filtering by readability check.

GUI: Components

Topology



Topology represents the SEP sesam backup environment including the hardware, computers, backup devices, etc.

All interconnected computers – SEP sesam Clients and SEP sesam Servers – can be logically grouped into locations and sub-locations. You can use locations to group your clients according to their OS, data type, different geographical location, etc.

The menu item Topology shows all SEP sesam locations, clients, loaders, and drives known to the Master Server as well as the media within the devices. By clicking the symbols they can be expanded into the subordinate structures via a function tree. Each client is assigned to a location and each loader and drive to a client. You can open their properties by double-clicking the relevant component (location, client or drive).

Such grouping enables large organizations at different locations to be managed and represented as a group with separate, centrally-managed units (using a tree view). Locations can be hierarchically organized - multiple sub-locations can be summarized under one Location.

A Master Sesam at the highest level presents all currently accessible regular SEP sesam computers. With a mouse click their individual data can be viewed.

A regular SEP sesam Server shows one node only, namely itself.

Topology overview Beefalo.jpg

With v. 4.4.3. Beefalo, SEP sesam provides additional View Mode button that enables you to switch between the table view and the tree view with grouped objects.

  • Tree view: SEP sesam default view shows the status of individual locations grouped together in a hierarchical view.
  • Table view: A simple flat view that shows the status of individual locations one after another.

To create a new location independent of another location or a sub-location, click Topology, and click the button New Location. A client is always assigned to and created within a location. For details, see Configuring Location.

Updating client(s)

As of v. 4.4.3 Beefalo V2, the sm_update_client command has been extended to automatically install service packs on the SEP sesam Server. Now you can check in the SEP sesam GUI if an update for your clients is available, see Checking update status. If this is the case, the icon with the orange arrow is shown. For details on the GUI icons, Client status icons.

You can use the Check Access State option to make sure that you have access to your SEP sesam Client(s).

To determine if the client is accessible, i.e. to check if the SEP sesam software is present on the client, the network connection is working and thus the client is accessible from the SEP sesam Server, proceed as follows:

From the SEP sesam GUI

  1. In the SEP sesam GUI -> Main Selection -> Topology, right-click the target SEP sesam Client.
  2. Select Check Access State and click Yes.
  3. Check access state.png

Note that the availability of the update/install options depends on the update mode you have selected. If the Update mode is set to Turn off (hide from all users), the option Check Access state is not visible.

Checking the results in the SEP sesam GUI

You can check the results in Topology in the column Access State, Last Access and Last sesam Message.

SEP Tip.png Tip
If the Topology columns are not visible, right-click a column header and select the option Column Visibility. Then simply select the relevant check boxes to specify which columns should be displayed.

In the background, the command for checking the access state (see section below) is executed asynchronously.

From the SEP sesam Server command line

Run the following command on the SEP sesam Server console:

sm_update_client check_client -C r -c <client_name> -m SMSSH

where the option -C r means that remote access of the client should be checked and -m SMSSH means that ssh should be used to check the connection.

In SEP sesam Web UI

You can access the Web UI in one of the following ways:

  • When you run the SEP sesam GUI as superuser or administrator, the Web UI landing page opens by default with a link to the Web UI (and links to documentation, etc).
  • In the GUI, click the Dashboard icon on the toolbar. The Web UI is also available from menu bar -> Activities -> Dashboard or from Main Selection -> Monitoring -> Dashboard.
  • You can also access the Web UI by entering the following information in the address bar of your browser:
  • http://[servername]:11401/sep/ui
    or
    https://[servername]:11401/sep/ui.

Use the SEP sesam Web UI left menu to navigate directly to Status (if not already displayed).

  1. Look for the Clients table: it shows the total number of clients, followed by the number of not accessible, disabled (Backup execution off), and upgradeable (New version available) clients.
  2. Web UI clients Jaglion.jpg

  3. Click the number next to Not accessible clients. A new Clients table is displayed with the Access State tab active. If you click the name of a client in a row, all details about that client are displayed.
    Web UI clients details Jaglion.jpg

You can update all clients within the location at once by right-clicking the location and selecting Update all clients. You can also select to update only the clients running on Windows or Linux by using Update all Linux/Windows Clients. This will update all Windows or Linux clients, respectively, within the selected location. For details, see Performing mass update.

If you want to update an individual client rather than all clients within the location, right-click it and select Update Client. You may want to exclude a particular client from being updated; in this case, double-click it to open its properties and select Do not update this client check box. Note that this setting applies in general for all possible updates.

If you have new Windows clients and would like to install either a SEP sesam Client, RDS (with GUI), GUI (with SEP sesam Client), or a SEP sesam Server on the selected client (with or without BSR), you only need to specify a user name and password (OS access) when selecting Install SEP sesam. For the Exchange and Hyper-V clients, the selected package will be installed by providing the credentials used to connect to the host computer. You can also uninstall SEP sesam from the respective client by clicking Uninstall SEP sesam.

Location properties

Locations are defined as a group of clients and/or further sub-locations. This should help you to organize larger networks so that computers in a building, an external office, etc., can be managed and represented in the separate units.

You can configure new locations from a SEP sesam Server or from an existing location (sub-location). SEP sesam sets up a tree-structure for all locations (e.g., USA-Colorado-Boulder-SEP Software) offering greater visibility. For details, see Configuring Location.

You can also edit the existing location or sub-location settings by double-clicking a relevant location/sub-location to open its Properties.

Location properties Beefalo.jpg

Location tab

  • Name: Name of the location
  • in: Superordinated location (relevant for sub-locations)
  • Description: More exact description of the location
  • Contact: Contact person at this location
  • Note: Additional information

OS Access tab

When configuring a new location, you can enter the credentials that will apply to all clients within a location, instead of specifying it for each client individually. In this case, enter the credentials as an administrator to access the respective systems. You can edit your credentials in the location properties. You have to use DOMAIN\USER format for the domain accounts or HOST\USER for the local accounts.

Permissions tab

Under the Permissions tab, you can configure permissions (ACLs) for your locations, if you have the admin rights. For details, see Using Access Control Lists.

Client properties

Clients are the computers in the network (including the SEP sesam Server) that you want to back up and restore.

The following screenshot shows the input fields and functions of the clients (the options may differ depending on your SEP sesam version).

Information sign.png Note
The client properties are slightly different if you are configuring a new client or when the client is already added and configured and you edit its properties. The Platform is only available when configuring a new client, while tabs for specifying additional settings are only available for the already configured client in its properties.

Topology client Jaglion.jpg

Client tab

  • Name: Enter the name of the client – this has to be the network host name of the computer. The name has to be resolvable either by DNS or etc/hosts file.
  • Location: Predefined location. A client must always be assigned a location.
  • Virtual machine (≥ 5.0.0 Jaglion): Previously referred to as Client is a virtual machine. If you select this option, you can edit the VM server name (host) and the VM name. These values are used to identify the backup client as a VM in a virtual environment.
  • Platform: Select the relevant platform of the client (LINUX, WINDOWS, UNIX, NDMP, VMS, or NETWARE). Depending on the platform, tabs for special access parameters are displayed. The Platform is only available when configuring a new client.
  • Operating system: Select the operating system version of the computer you are adding as a client.
  • Access mode: Select the appropriate access method for server-client communication. The Access mode option is only available in Advanced or Expert UI mode. So if you run the GUI in Basic UI mode, you first have to change the mode to Advanced or Expert, as described in Selecting UI mode.
    • CTRL: Access mode, which was the default mode in older versions of SEP sesam.
    • SMSSH: Current default access mode. SEP sesam SSH-based control communication. SSL libraries include libmicrohttpd, libcurl, and libopenssl. See also FAQ: access permissions.
    • PROXY: Access mode for a hypervisor or other systems without an installed backup client. The data transfer is executed via vendor specific protocols and the client is accessed via the mandatory data mover. For details, see What is a SEP sesam data mover. The following protocols are supported: vSphere (vCenter Server), Citrix Xen Server, Nutanix, NetApp, NDMP and Novell SMS for NetWare 5.1/6.0/6.5.
    • VIRTUAL: Access mode for a virtual machine (VM) without an installed backup client, where there is no direct remote access to this VM. Note that VIRTUAL access mode is similar to PROXY, but is specifically intended for managing VMs as clients by allowing configuration of ACLs for VMs. This means that the administrator can allow explicit restore access to a virtual client while preventing access to the hypervisor server. For details on how to configure permissions (ACLs) for clients, see Using Access Control Lists.
    • SSH: This communication mode is based on a key-pair operation of the SSH implementation of the operating system used.
    • RSH: Remote Shell; this option is deprecated and rarely used.
  • VM server type: If the client should be managed as a VM server, select the relevant type. This enables, for example, browsing the virtual environment when creating backup tasks.
  • Last SEP sesam message: The most recent system status message for the existing client.
  • Last successful access: The last successful access to the existing client.
  • Notes: Optional comment.
  • Interfaces:
  • Information sign.png Note
    Only edit this field if a client is a SEP sesam Server or Remote Device Server (RDS).

    If there is an additional network for backups available, the resolvable and changed DNS-name of a second network card of the SEP sesam Server can be entered into a new line. If several network cards are available, they need to be known to the DNS otherwise the connection to SEP sesam Server will fail.

    The network protocols for data transfer can be set by using the common prefixes ftp:// (default), http:// or https://. For each protocol one interface has to be added in the interfaces box separated by single spaces. One interface for the HTTP protocol http://<hostname>:11000 and one interface for the HTTPS protocol https://<hostname>:11088.

  • SEP sesam version: This field shows the SBC (SEP sesam backup Client) version of the installation.
  • Additional options
  • There are two additional client-related options:

    • Virtual machine (Client is a virtual machine in ≤ 4.4.3. Beefalo V2): If you select this option, you can edit the VM host (name of the VM Server) and the VM name. These values are used to identify the backup client as a VM in a virtual environment.
    • Do not update this client (≥ 4.4.3. Beefalo V2): Checking this option allows you to exclude a particular client from being updated. This setting applies in general for all possible updates.
    • Execution off: If a client needs to be excluded from the backup for technical or other reasons, you can deactivate it by checking this option.
    • Information sign.png Note
      If this option is set, the client will not be backed up until it is unlocked again even if it is scheduled for backup.

Options tab

By default, SEP sesam uses random ports that are assigned by the operating system for its data connections. However, if you want to back up a client which is behind a firewall, you must manually define the ports. The available options depend on the client type.

Client options Beefalo.jpg

  • Access options: The default communication port on the backup client is 11301. If a port other than 11301 is used, it must be configured in the client's sm.ini file. In this field, enter the port over which the client is reachable (e.g., -p 17301).
  • STPD options: The STPD options are used to define the backports from the clients to the SEP sesam Server, e.g. 11003-11006. These ports are then used to carry data during backups and restores. For each backup that runs parallel 2 ports of a client are needed.
  • Listen port: The default STPD-port for Remote Device Servers (incl. SEP sesam Server) is 11001.
  • Wake on LAN: For more information, see WOL - wake on LAN of a SEP sesam client.
Information sign.png Note
In SEP sesam v. ≥ 4.4.3, SEP Si3 source-side deduplication (Si3S) backup does not work if the STPD service TCP port on the client side (in sm.ini and/or stpd.ini) is changed from the default port. With Jaglion you can avoid this issue by setting the STPD service TCP port to the new TCP port in the client properties -> Options tab -> Listen port.

For details, see List of Ports Used by SEP sesam.

OS Access tab

When configuring a new client, you have to enter the credentials as an administrator to access the respective systems. You can also edit your credentials in the client properties. You have to use DOMAIN\USER format for domain accounts or HOST\USER for local accounts.

Client access Beefalo.jpg

Additional tabs

In the client properties two additional tabs are available for specifying additional settings.

Under the Permissions tab, you can add the relevant permissions (ACLs) for your client. For details, see Using Access Control Lists.

Client permissions Beefalo.jpg

If you are configuring clients that must be backed up by special task types, additional settings must be specified. A fifth tab is available for the following task types: Micro Focus Open Enterprise Server (formerly Novell OES), VMware, Citrix XEN, MySQL, PostgreSQL, NetApp, RHV. For example, for Micro Focus OES or NetWare server backup you have to specify the login data for the eDirectory and select the appropriate data mover. For Micro Focus, this is a SEP sesam Micro Focus (formerly Novell) Client which is installed on Linux computer with Micro Focus Storage Management Services (SMS).
Client VMware Beefalo.jpg
For more information on specific task type, see the respective wiki articles under Extensions.


Clients

The Clients component provides a list of all interconnected, in SEP sesam configured computers – SEP sesam Clients – and their properties, e.g., assigned location, operating system, access mode, SBC version, etc. Double-clicking a client opens its properties where you can edit the client's settings. For details, see Client properties.

Clients list Beefalo.jpg

Right-clicking a client opens the shortcut menu, from which you can select the desired action, such as New Client to add your computer to SEP sesam environment. A client is always assigned to and created within a location. You can also create a client-related report, check whether a client is accessible, update UI server, and cancel current running activities related to the selected client. You can delete a client by right-clicking it and selecting Delete.

As of v. 4.4.3 Beefalo V2, the sm_update_client command has been extended. Now you can check in the SEP sesam GUI if an update for your clients is available. You can update all clients within the location at once or update only the selected client. You can also exclude a particular client from being updated or install SEP sesam component(s) on new Windows clients. For details, see Updating client(s).

You can see more details of the clients' list by scrolling the list with the horizontal scroll bar at the bottom, or by widening the content pane by closing or moving the Filter window.

Right-clicking the table header opens a menu that allows you to auto-resize a column or all columns, to hide a column that you are not interested in, and to control which columns are visible by user. Choosing Column Selection enables to select the properties that will be displayed for the clients' list.

Client status icons

As of v. 4.4.3 Beefalo, SEP sesam GUI is redesigned to be more user-friendly. To improve usability, the GUI icons have been redesigned and are now accompanied with additional icons and symbols. The following table shows the client status icons with their description.

Icon Description
Client backup execution off.png The backup execution is disabled on the client.
Client not accessable.png The client is not accessible.
Check update access state.png The system checks if the update is available for the client.
Update client.png An update is available for the client (may be any of the following: a new SEP sesam package, a service pack or in case of a SEP sesam Server, a UI server update).
Server backup execution off.png The backup execution is disabled on the server.
Server not accessible.png The server is not accessible.
RDS backup execution off.png The backup execution is disabled on the RDS.
RDS not accessable.png The RDS is not accessible.



Data stores

The SEP sesam data store is a device type used for writing savesets directly to one or several configured storage locations – into the file system. SEP sesam uses a data store instead of a conventional media pool to define the storage repository. Data is still primarily backed up to a media pool, however, a data store is used underneath to save data to dynamically managed data areas, including disk backups.

SEP sesam can contain multiple data stores of different types and sizes, depending on the type of data being backed up, the backup technique, and the storage location (a local disk, a virtualized storage device, storage appliances, etc.). The following data store types are supported:

  • Path: The default data store type, relevant to the configuration of most storage locations, unless one of the following data store types is required, e.g., for deduplication or backup to cloud storage.
  • SEP Si3 deduplication store: Used for target-based (Si3T) and source-based deduplication (Si3S), replication, backup directly to S3 cloud storage (Si3 NG store) and S3 cloud replication (Si3 store).
    Information sign.png Note
    As of SEP sesam v. Jaglion, two Si3 deduplication store types are available. The common name for both types is Si3 deduplication store, unless it is explicitly stated that the information refers exclusively to Si3 (first generation) or Si3 NG (next generation). SEP sesam recommends using the new generation Si3 NG when creating a new data store. Si3 NG is advantageous over regular Si3 as it offers better performance, scaling, and resource savings. It allows you to back up your data directly to S3 cloud storage and restore the items you want directly from there.
  • NetApp Snap Store: Used for NetApp snapshots backup.
  • HPE StoreOnce: Used for integration with the HPE StoreOnce Catalyst storage system.
  • HPE Cloud Bank Store: Used for replication of data to HPE Cloud Bank Storage.

Data store overview Beefalo.jpg

Data store status icons

The data store status icons consist of three parts.

  • The top bar shows the clone status of the S3 store.
  • The middle bar shows the sanity state of the Si3 store.
  • The bottom bar shows the data store status.
Icon Description
Data store state error.png The data store state has errors.
Data store state ok.png The data store state is OK (good).
Si3 states ok.png The data store and Si3 state are OK (good).
Si3 S3 state ok sanity state ok clone state error.png The Si3 and the sanity state are OK, but the S3 clone state shows an error.
Si3 state error sanitystate ok.png The Si3 store state shows an error, but its sanity state is OK.
Si3 state.png Shows the Si3 status under the Si3 State tab.

View Mode button

SEP sesam provides an additional View Mode button that enables you to switch between the table view and the tree view with grouped objects.

  • Tree view: SEP sesam default view shows the status of individual data stores grouped together in a hierarchical view.
  • Table view: A simple flat view that shows the status of individual data stores one after another.

SEP sesam data store concept

SEP sesam data stores can be of different types depending on the type of data being backed up, backup technique, and used storage. The default and most commonly used data store type is Path. The following information applies generally to a data store, unless explicitly specified otherwise; data store types other than Path may have slightly different characteristics. For details, see the relevant articles: SEP Si3 deduplication store, NetApp Snap Store, HPE StoreOnce, and HPE Cloud Bank Storage.

The difference between a conventional media pool, typically used for backing up directly to tapes, and a data store is in defining the storage space directory directly in the drive by using the operating system's partition functions. Therefore the data store space is managed at the partition level. You configure a data store by specifying its capacity and (optionally) setting the high watermark (HWM) value. This is the upper value for the used disk space on the data store. Take into account that exceeding HWM and filling up the data store may cause backup issues. You should consider this when specifying the data store capacity. For details, see Data store calculation recommendations below.

Information sign.png Note
Only one data store should be used for each hard disk partition. Even though several data stores can be set up on one partition, you are advised against such configuration as each data store reads the values of the other partitions when checking partition allocation. Consequently, such coexisting data stores obstruct each other.

As shown in the illustration below, a media pool still refers to a drive group. The drive group points to exactly one data store between the media pool and the drives. The connection between the data store and the related drive is static.

Data store principle graphic Beefalo.png

Data store capacity

Data store configuration consists of specifying the data store capacity and HWM. The data store capacity is space reserved for the SEP sesam data store and, optionally, non-SEP sesam data that might be stored on the same volume as the SEP sesam data store. If the data store is shared with non-SEP sesam data, you have to obtain a special SEP sesam storage license.

Information sign.png Note
The Si3 deduplication store has specific hardware and sizing requirements. For more information, see Si3 Deduplication Hardware Requirements and Configuring Si3 Deduplication Store.

When specifying the capacity value, a dedicated partition must have enough free space. The method for calculating the required disk space is:
space occupied by SEP sesam + free disk space = DS capacity

where DS capacity is the configured capacity value in SEP sesam's data store configuration. For examples on calculating a data store capacity, see How do I calculate the data store capacity.

More than one data store is required in a media pool only if the media pool uses data from several disk partitions, in which case all the drives of a media pool's data stores must be part of the same drive group. This ensures that the SEP sesam queue manager distributes the backups in this media pool to all data stores (balancing). For details on drive groups, see Drives.

HWM, purge and Si3 repair area

A high watermark is a general parameter that specifies the upper value for the used disk space on the data store. When this value is reached, the status of a data store changes from OK to Warning, but backups continue to be performed.

The Si3 repair area parameter is relevant only for SEP Si3 deduplication store. It specifies reserved space for unused Si3 files, as explained below.

  • High watermark (HWM): A parameter for managing disk space usage; it defines the upper value for the used disk space on the data store. This parameter can be specified manually for the Path, Si3 and NetApp Snap store, and is set automatically during the creation of a SEP Si3 Deduplication store.
    When this value is reached, the status of a data store changes to Warning. It serves as an indication for the administrator that the data store is running out of space, but does not prevent backups to be started. A data store purge process is running automatically for all (EOL-free) savesets. The oldest free savesets are deleted first. Purge is done until all EOL-free savesets are deleted. For more details on EOL, see Automatic Retention (EOL) Management.
  • Events that trigger the data store purge are:

    • NEWDAY
    • Sharing the data store drive after a backup
    • Starting purge manually in GUI

    The manual execution of the data store purge process deletes the obsolete (EOL-free) savesets. Another option for releasing the data store space is to clean up a data store by deleting orphaned savesets, as described in the following section.

  • Si3 Repair Area: A parameter used by SEP Si3 Deduplication Store for managing disk space dedicated to Si3 files that were identified by a garbage collection job and are no longer used. These files are still kept in the repair area to enable possible repair of Si3 if there are any structural problems (may be caused by a file system error or by a crash of an operating system). The files in the repair area are removed automatically after the specified amount of time (SEP sesam default: 4 days) or when the disk usage threshold is reached. If the value is set to 0, the Si3 repair functionality is turned off.
  • Information sign.png Note
    The Si3 repair area is available only in advanced UI mode (formerly expert GUI mode). To see the Si3 repair area field, make sure your UI mode is set to advanced. For details, see Selecting UI mode.

Clean up orphaned savesets

You can manually remove orphaned savesets from the data stores by using the Clean up option in the Data Stores content pane, thus releasing the space that might be occupied by orphaned savesets. This is useful in cases when a data store seems to be inaccessible, its storage space is occupied, or SEP sesam space check shows non-sesam data.

Steps

  1. In the Main Selection -> Components, click Data stores to display the data store contents frame.
  2. In the content pane menu, click Clean up and select the data store (and the relevant drive number) for which you want to free up space by removing orphaned savesets.
    Click Clean Up.
    Data store clean up Beefalo.jpg
  3. You can check the status of the clean-up action in the data store properties under the Actions tab.

Data store calculation recommendations

  • Data store volume sizing and capacity usage should be managed at the partition level. It is recommended that only SEP sesam data is stored on the respective volume.
  • The data store should be at least three times (3x) the maximum full backup size of the planned backup to allow the watermarks to work automatically and dynamically.
  • It may be necessary to scale up the data store to beyond 3x the maximum size when a longer hold-back time is stipulated or very big savesets are to be stored.
Information sign.png Note
The Si3 deduplication store has specific hardware and sizing requirements. For more information, see Si3 Deduplication Hardware Requirements and Configuring Si3 Deduplication Store.

Limitations

  • When a media pool requires more than one data store, all data stores must be connected to the same SEP sesam Device Server (IP host). SEP sesam does not currently support network-distributed data stores being served by a single media pool.
  • When using more than one data store, only negative OR positive values can be used for specifying the capacity and HWM. SEP sesam does not support the use of negative and positive values at the same time. For more details on data store capacity and values, see FAQ: How do I calculate the data store capacity.

Data store properties

Double-clicking the data store displays all its details, e.g., the name of the data store, the store type, the message about the last executed action, the last action performed, its capacity, etc.

The buttons in the lower left corner allow you to create and delete drive, create new media pool, and delete a data store.

Data store properties Beefalo.jpg

  • Capacity: The size (in GiB) of the partition available for the backups. For examples on calculating a data store capacity, see How do I calculate the data store capacity.
  • High watermark: The upper value (in GiB) for the used disk space on the data store. When this value is reached, the status of a data store changes from OK to Warning, but backups continue to be performed.
  • Filled: The size (in GiB/TiB) of the occupied data store space by SEP sesam.
  • Used: Total used space (in GiB/TiB) on the partition (incl. SEP sesam external data).
  • Total: Maximum available space (in GiB/TiB) on the partition as reported by the operating system.
  • Free: Available disk space (in GiB/TiB) for SEP sesam.

You can modify existing drive options and set additional by double-clicking the drive. In the Drive Properties window, you can select a different drive group, browse the path for the data store, etc. Under Access mode, you can also set the following permissions for the data store drive:

  • read/write (default): Allows to perform the read operations (e.g., restore or using a drive as the source of a migration) and write operations (e.g., backup or using a drive as the target of a migration). As the write operations can occupy the drive for a while, consider using certain drives only for write operations and setting up the other drive(s) with read operations only.
  • read: Only read operations, such as restore or as a source of a migration, are allowed. It is recommended to set up additional drives in read mode to allow uninterrupted processing of tasks, such as restore.
  • write: Only write operations, such as backup or as the target of a migration, are allowed. The use of drives in write mode is recommended if these drives are used in combination with additional drives that are only used in read mode.

The first drive in the list has an additional OS Access (previously Account) tab where you can specify the credentials (user name and password) required to access the configured drive path.
Drive properties Beefalo.jpg

Savesets tab

Selecting a data store and clicking the tab Savesets opens a list of all savesets with their details. You can change the EOL of the individual saveset, adjust the backup-related EOL, and lock or unlock the individual saveset. Note that in SEP sesam ≤ 4.4.3 Beefalo V2, the backup locked status is only applied to the selected backup, so you need to manually lock all backups in a backup chain as well as migrated and replicated backups. With v. 5.0.0 Jaglion, the locked status is automatically applied to all savesets of a backup (backup chain, migrated and replicated savesets). You can also lock your backups in SEP sesam Web UI.

SEP Tip.png Tip
The circles next to the EOL (Backup/Saveset) indicate the status of your saveset (gray circle – EOL has expired, blue circle – saveset is protected; EOL has not yet been reached). For details, see SEP sesam Icons Legend.

Data store savesets Beefalo.jpg

  • Saveset EOL: The column Saveset EOL enables you to change EOL for each individual saveset, stored on the respective data store. You can extend or reduce its retention time. If the adjusted saveset is a part of a backup chain, the whole chain is affected as described below in EOL-related backup chain dependencies.
  • Backup EOL: The column Backup EOL enables you to adjust EOL for all savesets containing the same data. This backup-related EOL is applied to all savesets with the same data, including migrated and replicated savesets.
    For example, adjusting EOL of a migrated saveset from 2.12.2017 to 12.12.2018 results in changed EOL for all related backup data, i.e., original backup, replicated backup, as well as for all backups in a backup chain, if a saveset with adjusted EOL is a part of it.
  • SEP Tip.png Tip
    How SEP sesam manages failed backups depends on its version. As of v. ≥ 4.4.3 Beefalo V2, SEP sesam keeps the failed backup according to the media pool retention time together with the last successful backup or migration saveset. This is the default backup retention behavior and can be changed by modifying retention-related keys, as described in Customize the default retention behavior for backups and migration. These keys may not be supported in previous versions, where failed backups were deleted automatically after 3 days.
  • EOL-related backup chain dependencies: You can extend or reduce the retention period for an individual saveset or backup-related saveset, as described above. Keep in mind that increasing EOL of a DIFF or INCR saveset will result in increased EOL of all dependent backups (FULL and other DIFF and INCR) to preserve the backup data. This keeps the backup chain readily available for restore. On the other hand, decreasing the EOL of a DIFF or INCR saveset leads to reduced EOL of all dependent savesets. If the EOL is changed to a date in the past, the savesets will be deleted during the next purge. How SEP sesam manages EOL depends on the version. For more details, see Automatic Retention (EOL) Management for v. ≥ 5.0.0 Jaglion and Managing EOL for v. 4.3.3 Beefalo V2.
Information sign.png Note
Any saveset can be deleted if the following conditions are met:
  1. Its EOL has expired.
  2. Typically, there must be no other savesets that depend on this saveset. You can override this condition by explicitly allowing the EOL for the whole backup chain to be set to expired, thus deleting backup data on all related savesets.

Media tab

The Media tab provides an overview of the configured media pools and media.

Data store media Beefalo.jpg

Actions tab

The Actions tab provides an overview of the media-related events. It displays the media status, the action type, its start/stop time, duration and message.

Data store actions Beefalo.jpg

Si3 State, HPE Catalyst Store State and HPE Cloud Bank Store State

The Si3 State tab is shown for Si3 data stores, HPE Catalyst Store State tab is shown for HPE Catalyst stores and HPE Cloud Bank Store State is shown for HPE Cloud Bank stores. The tabs display the last deduplication message, the status of active tasks, encryption status, number of stored objects, data size before/after deduplication, dedup ratio, saved storage space, etc. You can also review the Si3 deduplication, HPE Catalyst store or HPE Cloud Bank store status in the media actions properties.

Data store state Beefalo.jpg



Loaders

Loaders are devices that consist of drive(s), a magazine with slots for media and a robotic mechanism that moves media between the slots and drives thus enabling automated backups. There is no dependency in SEP sesam to use specific manufacturer's devices or device types. A list of supported hardware is available at Supported Storage Hardware.

Identifying storage devices and their configuration

SEP sesam can detect and automatically configure storage hardware in your environment if the hardware is supported and recognized by the operating system (it must be listed in the OS device driver directory), where the SEP sesam Server or Remote Device Server is installed.

Information sign.png Note
Verify that the operating system properly detects the storage device. On Windows, the hardware must be recognized correctly by the operating system in the Windows Device Manager (must not be shown as Unknown Medium Changer) before SEP sesam is installed! For details, see Checking hardware configuration on Windows.

During SEP sesam Server installation, SEP sesam checks the SCSI API of the operating system for connected storage devices and enters working device files (SCSI address) into SEP sesam database. This auto-detection works for most devices, but for certain types of loaders the connection between a loader and the drives cannot be recognized automatically. Such devices must be manually verified and entered into the configuration. Note that procedure differs depending on your operating system (Linux or Windows).

Information sign.png Note
If you are adding a loader later, e.g., for remote devices, you also have to configure your storage hardware manually. How you configure a loader depends on its type. For details on how to manually configure tape devices, enable persistent naming and use SEP sesam SCSI tool slu topology for detecting devices, see Manually configuring loaders and drives.

The menu item Loaders shows the configured loaders with their drives. You can add a new loader, inspect the contents of the loader, run archive adjustment, and import/export or load/unload the tape cartridges.

GUI loader Beefalo V2.jpg

Loader properties

The following settings are configured automatically if a storage device is recognized by the operating system.

Loader Beefalo V2.jpg

  • Device name: SCSI device filename of the loader; enter the SCSI address of the physical device on Windows systems, for example Changer0, or a device filename on Linux systems, for example /dev/sg2. You can check if the devices are used correctly by SEP sesam and detect available SCSI addresses by running a slu topology command.
  • slu topology is a SEP sesam SCSI loader utility that provides information about the loaders and tape drives connected to the system and their relation. To be able to run the SEP sesam commands globally, you must first set up a profile as described in FAQ: What happens when I set a profile? Then run slu topology command to list all attached SCSI devices. For details on the output, see Using slu topology for detecting devices.

    <SESAM_BIN>/sesam/slu topology
    

    Enter the displayed target device name in the Device name field.

  • Device server: Remote Device Server (RDS) where the loader is installed.
    Device Server refers to the server where the loader is connected. In small environments, the loader or disk array is usually installed directly on the SEP sesam Server. However, more complex backup environments use RDS instead. RDS receives data during backup and writes it to the attached tape device.
  • Type: The device type.
  • Ctrl: The loader type – there are four types of loaders available:
    • DIR_SLU: All loaders, which are connected by SAS/iSCSI/FC to the SEP sesam Server or RDS, and provide a robotic control of tape media.
    • DIR_VIRT: A virtual loader. Only one virtual loader can exist in the entire SEP sesam configuration. This loader type is always configured with the number 0 (zero), and it serves all DISK_HARD drives and DISK_CHNG drives. Even though media are not actually moved, there are entries in specific files to control the data streams.
    • DIR_DISK: Enables you to control a pool of several hard disks. The hard disks have to be addressable by single device ID in the operating system.
    • DIR_ACSLS (≥ 4.4.3 Beefalo V2): ACSLS loader used for the tape libraries controlled by StorageTek Automated Cartridge System Library Software (ACSLS) as SEP sesam backup devices.
  • Slots: Number of slots in the loader.
  • When inserting a cleaning tape, use the last slot in the loader and reduce the number of slots in the loader by one (or by the number of cleaning tapes loaded). Additionally, disable the auto-clean option in the tape library setup or set it to manual execution.

  • Ports: Number of mail slots in the loader.
  • Barcode: Depending on whether the loader has a barcode reader or not, select yes or no.
  • Auto unload function: Almost all autoloaders and tape libraries allow explicit commands to transport tapes to and from the loader mechanism. It is strongly recommended to disable Auto unload function by setting it to No and allow the manufacturer's drive settings to perform as designed.

Contents

The Content view shows a symbolic representation of the loader. It is constantly refreshed and always shows the current status.

Loader content Beefalo V2.jpg

The left part represents the tapes in slots. At the top right corner is the drive, in the middle is the arm or selecting device (changer), below is the exit port.

Frequently there will be other applications also using media in the loader, especially in the case of large tape libraries. In such case, you have to know which subset of media is reserved for SEP sesam (media that are added to the SEP sesam media pool). When running an archive adjustment (scanning a loader to update the SEP sesam information about the tapes in the device), you can limit the scanning to specific SEP sesam loader areas. If the media have barcode labels, this is taken into account for the backup process.

If available, the barcode labels are scanned and synchronized. Otherwise, the media labels are used. You can also verify only specific media labels.

The archive adjustment can be performed for inventory purposes to provide an overview of the media available in the loader, irrespective of which media pool was selected for the adjustment.

You can also perform Loader Action to achieve direct access to disk and loader controls. See the below section Loader action.

  • Legend: The following table lists the icons used for displaying various media and loader status.
  • Loader legend Beefalo V2.jpg

  • Barcode as Label: If available, a barcode will be used instead of the media label.

Archive Adjustment

An archive adjustment makes a comparison between media in the loader carousel or magazine and the SEP sesam media archive database. It is mandatory whenever the contents of a loader carousel have been altered. Typically, it must be performed after inserting new media or used media that have not yet been registered (initialized) by SEP sesam. It must be run after successful installation of a loader, as described in the following section First archive adjustment after new loader installation. For more details on archive adjustment and how to create a media event for it to run automatically, see Setting up Archive Adjustment.

Information sign.png Note
When selecting the option Archive Adjustment, make sure that the autoloader being realigned is selected in the GUI window, i.e., that the target device is at the top of the adjustment task. When using the command line, the task must include the name of the target autoloader or tape device.

Loader archive adjustment Beefalo V2.jpg

  • Media pool: Select a media pool where you want to perform the archive adjustment.
  • Storagepool: If the selected media pool has storage pools assigned to it, you can select it from the drop-down list.
  • Drive group: The drive group is automatically defined by the media pool.
  • Drive (opt.): Optionally, you can select a single drive.
  • Slot range: You can limit synchronization to the specified loader segment by entering the number of the first and last slot.
  • Automatic introduction: If unknown media (without SEP sesam label) are found within the loader, they will be added from the tape library to the specified media pool.
    1. Tape type: Select the relevant tape type from the drop-down list.
    2. Select the preferred way for Handling of unknown SEP sesam media:
      • Accept without initialization: Foreign SEP sesam media, e.g., from another SEP sesam Server, will be automatically inserted into the new media pool without initialization.
      • Overwrite: A tape with unknown SEP sesam label (which is not in the SEP sesam DB) is initialized and added to the selected media pool.
      • Information sign.png Note
        Any media from a competitive manufacturer will be entered into the target media pool and will be overwritten! In other words, any media not recognized by the SEP sesam Server will be overwritten and a new media pool label will be written to the tape.
  • Check label on tape: Every tape label is re-read and verified, while the barcode information is ignored.
  • Adjustment by barcode only: SEP sesam scans only the tapes which are in slots, while the tapes in the drives are not scanned.
First archive adjustment after new loader installation

After the complete installation of the loader, the tapes must first be included in the media pool (to be able to use them) by running the archive adjustment. For details, see Media - Data Carriers.

  1. First, configure a media pool that will be used for backing up directly to tapes which are assigned to this media pool. For details, see Configuring media pools for loaders.
  2. Insert new tapes into the slots of the loader; in our example, we use the slots 3-6.
  3. Start the archive adjustment with the following settings:
    • Select the media pool to which you want to assign the tapes.
    • Specify the slot range for the newly introduced tapes, e.g., 3-6.
    • Select the check box Automatic introduction that the tapes will be added from the tape library to the specified media pool.
    • By default, Accept without initialization is enabled under the option Handling of unknown SEP sesam media. Select the check box Overwrite only if the respective tape has already been registered by SEP sesam.
    • Click Start to start your archive adjustment immediately.

Running archive adjustment results in automatically adding the tapes to the specified media pool, which can now be used for backups.

Loader Action

Selecting Loader Action is the simplest (limited) way to achieve direct access to disk and loader controls. The import or export (load/unload) of a single tape can be initialized in the SEP GUI as well as the sorting of the media within the library. The use of port slots depends on the installed hardware.

Loader action Beefalo V2.jpg

Action

  • Import from port: Transport of the tape cartridge through the input/output port into the magazine.
  • Export to port: Transport of the tape cartridge from the magazine through the input/output port – exit from loader.
  • Load from slot: Move the tape cartridge from the specified magazine slot into the specified drive.
  • Load via label: Move the tape cartridge with certain ID (e.g., S00001) into the specified drive.
  • Unload: Move the tape cartridge from the specified drive back into its slot.
  • Loader number: Selection of the loader.
  • Drive Number: Selection of the drive (within the loader).
  • Label: When loading via label, selection of the label instead of the slot number.
  • Start: Start the corresponding action.
  • Cancel: Cancels the dialog without performing any action.

Drive Action

By clicking the drive within the loader and selecting the Drive Action, you can manage the specific drive and media in the drive.

470pxlink=

  • Identify label: Shows the label of the medium in the drive.
  • Mount media: Mount is a special reservation of the tape media to prevent unnecessary spooling.
  • Dismount media: Cancels the mount status.
  • Dismount and unload media: Cancels the mount status and unloads the tape.
  • SEP Warning.png Warning
    If you have manually removed or inserted the tape from/into the drive, the drive must be dismounted. Dismount and unload media should not be confused with unloading from an auto-loader. While the loader can re-acquire the tape and re-enter it (option Unload via Loader), this option only means that the tape in the drive will be released and ejected.
  • Release drive: Cancels all activities that are running on the drive.
  • Release drive group: Cancels all jobs that are running on the drives that belong to the respective drive group.

The execution and progress of the activity are shown in the cyclically updated Current Messages window.


Drives

Drives are devices used for data storage that read from or write data to media. They are either local drives, connected to the SEP sesam Server, or remote drives, connected to another computer on the local or wide area network. These can be tape devices with removable tape cartridges or disk-based storage devices. Remote drives enable the storage devices, which are used by SEP sesam, to be distributed over WAN.

SEP Tip.png Tip
It is recommended that SEP sesam auto-configures backup devices, but even for the automatically configured tape devices you should check their configuration and in some cases enable persistent naming to avoid errors in SEP sesam operation. For details, see Enabling persistent naming for tape devices.

Shared drives

SEP sesam provides dynamic drive sharing option in SAN environments. Note that a proper SEP sesam SAN Dynamic Drive Sharing (SDD) license is required for each drive you intend to share. For more information, see Licensing.

Drive sharing option allows the drives to be available to multiple Remote Device Servers (RDS) at any time. A physical drive can be seen by any number of RDSs and can be used by relevant systems to store data. Shared drives can be defined by a unique drive designation. This means that multiple drives are labeled with the same device identifier, which is specific SCSI designation, for example: /dev/nst0 (Linux ), Tape0 (Windows). While executing SEP sesam tasks, such as backup and restore, the drives are being shared by multiple servers based on a shared timing.

Drive groups

SEP sesam enforces you to organize drives into different groups. Grouping the drives of the same type into one group facilitates and optimizes backup operation. SEP sesam selects which drive from the group will be used for running a backup job. A backup is performed automatically on the drive that is currently free. In the event of a drive failure, each backup is automatically executed on other available drives.

Even in case you have only one standalone drive, you have to create a drive group first and attach a drive to it. The drive group is directly connected to the media pool. By connecting a media pool to the drive group, you specify where to SEP sesam saves the backup. Later in the process when configuring a backup, you select a target media pool (which is already connected to the drive group) to which the data will be backed up by creating a backup event (where the connected drive group is determined automatically by media pool selection). For details on backup configuration, see Standard Backup Procedure.

Drives overview Beefalo V2.jpg

By double-clicking the drive group or selected drive, its properties are shown and can be modified.

SEP Tip.png Tip
You can double-click the drive group to change it or to set a default interface for it. If you set the default interface, it will be used automatically when you start a task by immediate start and when you create a new backup event under a schedule.

Drive group-default interface.jpg

New drive group

The option New Group is used to configure a new group.

New drive group Beefalo.jpg

  • Name: A meaningful name for the new drive group which is easily recognizable by administrators, support personnel, and users. This should be part of a general design that can be referred to and expanded at any time.
  • Description: Additional information for the user, e.g., input of the loader's location and the relevant employee contact for assistance.

New drive

The option New Drive is used to configure a new drive. Each drive must be assigned to a drive group, therefore a drive group must be created first.

New drive Beefalo.jpg
In the New Drive window, the following fields are available:

  • Drive number: The number is automatically assigned by SEP sesam and determines internal number of the drive.
  • Drive name: Optional description, e.g., logical identifier of a drive. In case of a shared drive within SAN, the name must be the same for all client shared drives, e.g., SAN-Drive-LUN-0.
  • Drive type: Depending on storage type, the relevant drive type must be selected from the drop-down list.
    • For tape drives, select the relevant tape type (LTO, DLT, SLR etc.).
    • If you plan to use the drive in the virtual disk storage, select DISK_STORE. The data will be stored to SEP sesam data store.
    • If the drive is removable media, select DISK_CHNG.
  • Loader: Available options are No loader, 0, 1, and ASCLS (≥ 4.4.3 Beefalo V2). If the drive belongs to the loader, select 1. If it is a single tape drive, select No loader option. Number 0 defines the virtual loader. As of 4.4.3 Beefalo V2, you can also select ACSLS , see Configuring ACSLS-Managed Libraries.
  • Drive no. in loader: Determines how the drives are used within the loader. It is set automatically by saving the new drive configuration. It can also be set manually, but it is strongly advised not to; this order depends on the hardware vendor's numbering scheme for all installed drives. If the order is entered incorrectly, SEP sesam will not be able to access the correct drive.
  • Device server: The name of the server or RDS to which the drive is connected. The drop-down list displays all available hosts.
  • Drive group: The relevant drive group have to be selected from the drop-down list of all available drive groups.
  • Device (non-rewinding): Operating system specific SCSI designation for the device, for example: on Linux (/dev/nst0), on Windows (Tape0). If the drive is installed properly, you can determine its SCSI ID by using a SCSI loader utility slu topology which shows information about the loaders and drives connected to the system as well as their relation. To list all attached SCSI devices, run slu topology: <SESAM_BIN>/sesam/slu topology. For details on its usage, see Using slu topology for detecting devices.
    SEP Tip.png Tip
    It is recommended that SEP sesam auto-configures backup devices, but even for the automatically configured backup devices you should check their configuration by using slu topology. SCSI addresses may be changed during reboots, especially in environments with several tape libraries attached to a server, and the operating system might mix the SCSI addresses between different loaders and library tape drives. Consequently, SEP sesam may have problems accessing devices. In such cases, consider enabling persistent naming. For details, see Configuring Loaders and Drives.
  • Device Block Size: As of v. 4.4.3 Beefalo V2, it is possible to change the default write density for tapes to achieve better tape performance by using the Device Block Size option; see the below section Setting device block size.
  • Tape in drive: If a medium is loaded into the drive, SEP sesam label is displayed.
  • Information: If indicated, the messages from the drive hardware are displayed.
  • Max. channels: The number of parallel streams that can be used during backup to the backup drive. The number of data streams available for backup depends on license.
    For example, with SEP sesam ONE Server license only one backup stream is active. Multiple backup tasks are scheduled to start simultaneously, but will be performed one after another because of only one backup stream. In another example, SEP sesam Standard Server license is purchased for the environment that has has one disk drive and two tape drives attached. The SMS channels are connected to all drives. Multiple backup jobs (e.g., 10) are scheduled to start simultaneously. Backups may run in parallel to either one or both tape drives, but only 5 data streams are open for data transfer.
  • Encryption capable: For already configured drives, it shows whether they are encryption capable. The field is shaded for new drives. Note that SEP sesam provides native support for managing LTO-based encryption; the LTO encryption of tape drives can be enabled on a media pool level. For details, see LTO Encryption.
  • Click OK to configure the drive.
Information sign.png Note
With some drive types, such as DISK_CHNG, the name is automatically assigned based on disk + drive number.

Setting device block size

As of v. 4.4.3 Beefalo V2, it is possible to change the default write density for tapes to achieve better tape performance by using the Device Block Size option in the drive properties. You can increase the tape block size if you are using LTO Ultrium tape drives and your backup environment supports larger tape blocks. Setting the device block size only applies to the LTO tapes when they are initialized; changing this setting cannot be applied for tapes that are still used for backups. For example, once EOM is reached, another tape is required and can be initialized by setting the desired tape block size (0 -> default block size).

The default block size value is 64 KB. If the Device Block Size option is set to 0, then the default block size is determined as follows:

  • On Windows, the value is retrieved from the tape device driver.
  • On Linux, the value is mapped to the LTO drive type, as shown in the table.
  • LTO drive type Value
    LTO-1 128 KB
    LTO-2 128 KB
    LTO-3 128 KB
    LTO-4 128 KB
    LTO-5 128 KB
    LTO-6 128 KB
    LTO-7 256 KB
    LTO-M8 256 KB
    LTO-8 512 KB
    LTO-9 512 KB

To set the tape block size, double-click the tape drive to open its properties. Then select the block size value from the Device Block Size drop-down list. You can increase the block size up to 1024 KB.

Device block size.jpg

Manage multiple drives

Manage multiple drives option enables you to easier change drives properties (e.g., maximum number of parallel streams (max channels), delete drives, create new drives, etc). It lists all configured drives and allows you to change the properties settings of multiple drives, after which SEP sesam restarts the drives automatically. Whether only the modified drives will be restarted, depends on the drive type.

  • If a data store drives are being reconfigured, only the modified drives are restarted.
  • Any change of a tape device drive results in restarting all configured tape drives.

Manage multiple drives beefalo.jpg

Configure all drives

It is possible to reconfigure all drives by using Configure all drives option. Note that this action aborts all running backups, restores and migrations.


Media pools

A media pool is a group of media of the same type that you use for backups. You can have different types of media pools for different types of backup data, backup sources (e.g., file backup, DB backup), or drive types. How you configure a media pool depends on the type of storage device you are using, i.e. tape or disk storage. With loaders, you set up a media pool to be used for backups directly to tapes. For backups to disks or cloud (disk storage, S3 cloud storage), you have to set up a data store first, but still create one or more dedicated media pools for it. You can also configure a spare pool as an additional source of media of the same type that can be used if all tape media in a pool are in use. For details, see Configuring a Media Pool.

Media labels

Once a media pool is configured, SEP sesam automatically provides each media with a unique media label during initialization. The media labels are stored in the SEP sesam database. The labels consist of the pool name (e.g., Day_, Week_, Month_) and a 5-digit number assigned by SEP sesam within the pool. For example, if the media pool name is LTO_month, the media label for media in that pool would consist of the prefix LTO_month followed by an ascending number, e.g., 00001 – the first media label would be LTO_month00001. The next medium would have the media label LTO_month00002, and so on.

Data stores

While media pools are a traditional way of organizing data storage and are typically used for backups directly to tapes, SEP sesam uses a data store for backups to disks (disk storage). Even though the data is still primarily backed up to a media pool, a data store is used underneath to save the data directly to one or more configured storage locations – in the file system. For details, see Data Stores.

Backup strategy

Media pools are the basis for building a backup strategy. Each media pool represents a set of media designated for a specific purpose. For example, media pools can be created and managed for workdays, weekends, specific locations, specific types, databases, etc.

It is possible to configure special GFS media pools for storing data on tape according to the classic GFS (Grandfather-Father-Son) backup rotation strategy. However, there are several backup strategies to protect your environment that can be easily implemented with SEP sesam. For more information, see Backup Strategy Best Practices and GFS Backup Retention Strategy.

You can create a new media pool from Main Selection -> Media Pools -> New Media Pool. For details, see Configuring a Media Pool.

Media pools Beefalo V2.jpg

Media pool properties

Double-clicking a media pool opens its properties, where you can modify the media pool's settings. The media pool properties differ depending on the media pool type (for tape or disk storage). The following example shows the properties for the media pool used for backups on tapes, with two additional tabs: Readability Check and Options.

In the case of LTO tapes, an additional Encryption tab is displayed where you can enable LTO encryption of tape drives at the media pool level. For details, see LTO Encryption.

Media pools properties Jaglion.jpg

  • Name: The name of a media pool; it must not end with five numbers because this form is used for media labeling.
  • Description: Optional description of the pool, e.g., Monthly backup.
  • Drive Group: Selection of the drive group to which a media pool is attached (e.g, Tape_Drives, RDS_LTO_Dives, etc.).
  • Type: If configured, the media pool type (e.g., clone) is displayed.
  • Retention time [days]: The time period for which all media in the respective media pool are protected after the data has been written to the media, thus preserving the savesets and keeping them available for restore. The retention time period starts with the date a saveset is written to the media and lasts for the period defined by the media pool's retention time (in days). The expiration date of the retention time is the EOL of the saveset. When a saveset is stored on tape, every stored saveset has its own saveset EOL; however, the tape expiration date is the maximum retention time (the longest EOL) identified on the tape. For details, see Automatic Retention (EOL) Management.
  • Set media pool inactive: If selected, a media pool is deactivated, so it is not available for use.
  • Information sign.png Note
    In the case of a clone media pool, the option Set media pool inactive controls not only whether a media pool is available for use, but consequently whether the upload – synchronization with the S3 cloud - is performed. If you deactivate a clone media pool by selecting the option Set media pool inactive, the data is no longer synchronized with the S3 cloud. For details, see S3 Cloud Replication.

Readability Check

This is a process that checks the readability of the data on the tape and its structure, and ensures that the backup sets on the tape are recorded in the database and vice versa. The results are displayed in the log.

Readability check is configured by a special media event. For details, see Creating a Media Event.

Media pools read check Jaglion.jpg

  • Readability check limit [days]: By default, the value is 0 (zero) and readability check is disabled. If a number > 0 is set, a medium is checked after the specified number of days and marked with the status Readability check required. Readability check can only be applied if a Media EOL has not expired and is not applicable for EOL-free media. For details, see Configuring a Readability Check.
  • Expiration of read check overdue [days]: The number of days after which a readability check is overdue. It is calculated based on the readability check limit [days] and the value of expiration overdue.
  • Repeat rate for readability check [times]: If Unlimited is selected, the media are checked according to the specified frequency. If Execute is selected, the check is repeated as many times as specified.
Information sign.png Note
To perform the readability check, you have to set up a schedule and link a media event to it. For details, see Creating a Media Event.

Options

You can configure a number of options (depending on your strategy) to enable media sharing across media pools.

Media pool-options Jaglion.jpg

  • May use empty, foreign media: SEP sesam will use unknown or blank tapes for the backup if no tapes are available in the respective pool. (A newly purchased media that has never been used is also considered 'unknown' in this context).
  • May use EOL free media: Media with expired EOL from the same media pool can be used for backup. If this option is not selected, the use of a specific medium can be forced.
  • May use SPARE media: If there is no media (tapes) available in the target media pool, but the SPARE_ media pool is configured, SEP sesam automatically uses the media from the SPARE pool.
  • May use media from another pool: SEP sesam uses available tapes from other media pools if no tapes are available in the target media pool.
  • Another media pool may use media from this pool: A media pool that has run out of its own tapes can use the available tapes from this media pool.

If the data on the tapes is no longer needed, the metadata on the tape media in the media pools can be removed:

  • Delete all metadata of tape media, once the tape becomes EOL free: Data on tapes can only be deleted when their EOL has expired. If you enable this option, the metadata of tapes that are no longer write-protected will be deleted.
  • Delete all metadata of tape media and re-initialize the tape, once the tape becomes EOL free: Enabling this option erases all metadata on the tape media and reinitializes the tape (provided the tape is available to SEP sesam) by loading the tape into a drive and physically erasing it, thus removing access to all existing data on the tape.
Information sign.png Note
Media sharing strategies are based on acquiring media from the different pools, which means that such media are transferred from the original to the respective pool, and are no longer available in the source pool. You should take this into account when planning your media strategy. For details, see Media Strategy.

Permissions (in v. ≥ 5.0.0 Jaglion)

As of. v. 5.0.0 Jaglion, you can specify the required permissions (ACLs) for the media pool under the new Permissions tab. For details, see Using Access Control Lists.

Media pool permissions Jaglion.jpg


Tasks by clients

Tasks by Clients shows a list of configured locations with their clients and configured tasks.

Tasks by clients Beefalo.jpg

The backup task status is shown with the following icons:

Icon Description
Task state active.png The backup task is active.
Task state canceled.png The backup task has been cancelled.
Task state error.png The backup failed with an error.
Task state in queue.png The backup task is in queue.
Task state ok.png The backup has been completed successfully.
Task state warning.png A warning occurs during the backup.
Un read flag.jpg EOL (Backup/Saveset) has expired. The saveset will be deleted with the next purge.
Read flag.jpg EOL (Backup/Saveset) has not yet expired. If the Backup EOL has not yet expired (blue circle) but the Saveset EOL has expired (gray circle), the saveset with the expired Saveset EOL will be deleted. In this example another backup saveset (migrated or replicated) still exists, therefore the backup is not lost.

Clicking Properties or double-clicking the backup task displays all details of the selected task.

Information sign.png Note
You can disable a particular task or a whole task group without deleting it permanently and without cancelling all other events related to the same schedule. For details, see Disabling and Enabling Backup Task and Disabling and Enabling Task Group.

By right-clicking the backup task the following options appears:

Tasks by clients right-click Beefalo.jpg

  • Properties: Shows the details of the backup task.
  • Results: Shows the last backup details for this task, see Properties of a finished backup.
  • Immediate Start: Allows you to initiate a process manually, see Immediate start.
  • Copy (available only for backup task): Copies the selected backup task.
  • New Location: Opens a dialog for configuring a new location, see Configuring Location.
  • New Client: Opens a dialog for configuring a new client, see Configuring Clients.
  • New Backup Task: Opens a dialog for configuring a new backup task.
  • New Restore Task: Opens a dialog for configuring a new restore task. The New Restore Task option opens the restore wizard, as described in Restore. If you select the restore from this location certain parameters will be pre-set. A task name will also be automatically assigned.
  • Delete: Deletes a task from SEP sesam.

Creating a new backup task

Tasks new backup task Beefalo.jpg

When creating a new backup task, specify the following settings:

  • Task name: Enter the name for the backup task. When specifying the source by browsing, the task name is set automatically.
  • Task type: Select the relevant task type from the drop-down list. The default task type is Path backup (files, directories). When specifying the source by browsing, the task type is set automatically.
  • Client: Select the host (client) that should be backed up.
  • Source: Use the browse button to specify the Source and select what you want to back up. If you want to back up individual files, you can either browse for directories and files that you want to include in the backup or enter their names followed by a comma (C:/Program Files/SEPsesam/var/db,C:\Users\AA\Documents\references). Typically, by selecting the source the task type and task name are set automatically. A few special task types are rare exceptions and thus require a manual selection of the relevant type and specifying the task name.
  • Information sign.png Note
    When using a Netware NSS file systems on Linux OES the NSS volumes are normally found below the Linux path /media/nss.
  • Exclude list: Optionally, specify the filenames or patterns which you do not want to back up in the Exclude list. For details on various exclude options, see Creating Exclude List.
  • Information sign.png Note
    If you want to suppress a specific directory, you should enter the complete path name. Multiple excludes are delimited with commas.

    The simplest way to include or exclude the specific files or folders for/from the backup is by using the big browse button (next to the fields Source and Exclude list) and selecting your backup source or source for exclude in the Client File View window.

    Task client browser Beefalo V2.jpg

    The client browser is a kind of cross-platform file explorer. It does not only show files and directories in tree view, but also databases, pipes, sockets, character or block devices if they are relevant for data backup. A progress bar is included for supervising the resulting character string in case of an overflowing enumeration or rather exclude listing. By the Legend button a dialog with a short description of the icons appears.

  • Comment: Optionally, add additional information about the backup.
  • Create New: You can create more than one task for this client.
  • Execution off: If this task needs to be excluded from the backup for technical or other reasons, you can deactivate it by checking this option. If this option is set, the backup of this task will not start until it is unlocked again even if it is scheduled for the backup. For details, see Disabling and Enabling Backup Task.
  • Descend directories on other file systems: Only valid for Unix systems. Other partitions, which are mounted to the file system by symbolic links, are accessible.
  • Save data mounted by NFS: Valid for Linux systems. Follows and saves mount points, which reside on another host system by NFS.
  • Backup with LVM: Automatically triggers a snapshot when the backup source is on a LVM volume. Used to perform consistent backups of open files on Linux. For details, see SEP sesam Logical Volume Manager (LVM) for Linux.
  • Do not report deleted or modified files as errors: As of SEP sesam v. 5.0.0 Jaglion, you can set that deleted or modified files are not reported as errors on Linux systems.
  • Backup with VSS: Activates the using of Microsoft Volume Shadowcopy Service. It works only on Windows operating systems with installed VSS services. For details, see SEP sesam Volume Shadow Copy Service (VSS).
Options

Pre/post options provide a choice to specify a predefined pre/post operation for backup and restore. Setting pre/post actions for backup and/or recovery on or off is applied globally.

Task options Beefalo.jpg

Pre/post are SEP sesam configurable interfaces, intended for system administrators. They are executed on the SEP sesam Client (note that SEP sesam Server is always a backup client too) and perform additional actions (such as exporting a database, restarting a database, sending emails) before a backup or restore is started or after a backup or restore is finished according to the user specified commands.

Information sign.png Note
To use a pre/post interface, you have to activate it first and create your own commands. Interfaces can be activated in GUI: in the menu bar, click Configuration -> Interfaces -> select the interface you want to activate and the client. The interface script window opens, allowing you to configure the desired action. Once done, click Save to activate the interface. The interface is saved to the <SESAM_ROOT>/bin/sesam directory. For more details, see Using Pre and Post Scripts.

Pre/Post: Backup

  • Execute pre: Executes pre script before the backup is started.
  • Ignore pre error: Forces a backup job to start even if the pre-commands were not properly executed.
  • Execute post: Executes post script after the backup is finished.
  • Ignore backup error: Forces the post script to execute after a faulty backup.

Pre/Post: Restore

  • Execute pre: Executes pre script before the restore is started.
  • Start restore in spite of pre error: Forces a restore task to complete even if the pre-command script was not properly executed.
  • Execute post: Executes post script after the restore is finished.
  • Start post in spite of restore error: Forces the post script to execute after a faulty restore, e.g., a paused database will be restored even though the restore task has failed.

Additional call arguments

Under the Additional call arguments -> Backup options/Restore options, you can specify additional parameters which differ from the standard backup/restore procedure (e.g., -v 3 for the higher log level).

Encryption & Compression

Encryption & Compression enables you to select the type of encryption and specify whether you want your data to be compressed.

Task encryption Beefalo.jpg

Cryptography

  • Encryption: Select it if the data stream should be encrypted. You can select between 64-bit Blowfish or 256-bit AES encryption. Keep in mind that the data is encrypted by the client, so it has to carry the (processor) load. The encryption will also slow down the data transfer. You can decide if the password hash will be stored in the SEP sesam database. If it should not be stored in the database, SEP sesam will ask to enter the password for every restore event related to the task.
  • Information: Information regarding the setting of the encryption key.
  • New keyword: Specify your encryption password.
  • Repeat keyword: Re-enter your encryption password - type it manually, do not copy and paste.
Information sign.png Note
The password/keyword must be at least one (1) character and maximum 27 characters in length. It cannot include any special characters or spaces.

Compression (only available for Windows)

Compression is enabled on tape drives by default. If the hardware is not able to perform compression, you can enable software compression here.

OS Access

As of SEP sesam 4.4.3 Beefalo V2, the OS Access tab is used for specifying the credentials to access the resources on the target client. If you have already specified the credentials when configuring the client or its location, select an existing credential set from the drop-down list. Otherwise, click New and enter the credentials for the target client. Use the DOMAIN\USER format for domain accounts or HOST\USER for local accounts.
You can modify the existing credentials by clicking the Edit button.

Tasks OS access Beefalo V2.jpg

Task Groups

Under the Task Group tab, you can directly add a task to one or more of the already configured task groups.

Tasks task groups Beefalo.jpg

Task Groups show the list of all existing task groups in your SEP sesam environment. If you want to add a task to one or more task groups, click the checkmark next to the target task group. Organizing related tasks into groups can simplify your backup scheduling. For details, see Adding a Task to the Task Group.

Schedules

Under the Schedules tab, you can directly add a task to one or more of the already configured schedules.

Task schedules Beefalo.jpg

Schedules show the list of all configured schedules in your SEP sesam environment. If you want to add a task to one or more of the already configured schedules, first click the checkmark next to the target schedule, and then select the target media pool from the drop-down list. For details, see About Scheduling.

Additional tabs in the backup task properties

In the properties of the backup task, additional tabs can be displayed depending on the client's task type (e.g., Micro Focus SMS, Exchange Access, Citrix XenServer, PostgreSQL, etc.). As of v. 5.0.0 Jaglion, these tabs are also available when creating a backup task.

The Micro Focus SMS tab is only shown on Linux clients that can be used as a data mover for Micro Focus Open Enterprise Server (formerly Novell OES) Clients. It is possible to grant every backup task a different login to the eDirectory.

Micro Focus tab Beefalo.jpg

With Jaglion, you can also configure permissions (ACLs) for the backup task with fine-grained access rights under the new Permissions tab. For details, see Using Access Control Lists.

Bck task permissions Jaglion.jpg



Tasks by groups

From Main Selection -> Tasks -> By Groups, you can add multiple tasks to one or more groups. You can also see all tasks assigned to a specific group.

A single event will activate all tasks within the task group. The tasks will then be executed depending on the number of SMS channels available. The remaining tasks remain in the execution queue and are started in chronological order.

Information sign.png Note
It is possible to disable a specific task or a whole task group without deleting them permanently and without canceling all other events related to the same schedule. For details, see Disabling and Enabling Backup Task and Disabling and Enabling Task Group.

Tasks by groups overview Beefalo.jpg

Right-clicking the task group displays the following options. (The order of the available options may vary depending on the version, but the availability of the options does not change).

Tasks by groups right-click Jaglion.jpg

  • Properties: Displays the details of the task group, see Task group properties.
  • Immediate Start: Allows you to start the backup manually, see Immediate start.
  • Results: Displays the details of the last backup for this task group.
  • New task group: Opens a dialog box for configuring a task group. For more information, see Adding a Task to the Task Group.
  • New task: Opens a dialog box for configuring a new backup task in a group. For more information, see Creating a Backup Task.
  • Delete: Deletes a task group from SEP sesam. For details, see Deleting a Task Group.

Task group properties

Tasks bundled into task groups can be executed at the same (specified) time. If possible, the tasks are executed simultaneously on the drives. The other tasks are dynamically assigned to the backup devices by SEP sesam. The last backup status of the whole task group is also displayed.

Information sign.png Note
The Customize Task List button is available when creating a task group or in the task group properties. Clicking it opens the PRE interface script, which is executed before the backup of the task group. It contains suggestions for automatically modifying the list of tasks, e.g., for VM tasks, if there are new VMs in the VM server or those that have been deleted and therefore no longer need to be backed up. See Automatic task generation.

Tasks by groups properties Jaglion.jpg

  • Group name: Task task group name.
  • Note: Additional information of the user.

The > selector assigns a single task to the selected group and >> selector allocates all available tasks. Selector < removes single- and << removes all tasks. You can change the order in which SEP sesam starts tasks using the and arrows.

  • The Execution off option below the list of tasks allows you to temporarily disable a task group (and re-enable it if needed).
  • Hide backup tasks already associated with a backup group: This option allows you to filter the tasks according to whether they are already included in a group or not.

Schedules

A task group has to be associated with a schedule that has a corresponding event attached to it. For more information on creating the entire setup for scheduled events, see Standard Backup Procedure.

If you already have a configured schedule, you can link your task group to it by using the Schedules tab. Then, select the checkbox next to the desired schedule, and then select a media pool by clicking the Media Pool field in the selected schedule row. Once the media pool is selected, you can also select the drive and interface by clicking the corresponding field.

Tasks by groups schedules Jaglion.jpg

Permissions

As of. v. 5.0.0 Jaglion, the Permissions tab is available where you can set the required permissions (ACLs) for the task group with fine-grained access rights. For details, see Using Access Control Lists.


Backup plans

The Backup Plans (Main Selection -> Tasks -> Backup Plans) provides an overview of all configured tasks, task groups, migrations, and replications assigned to a schedule. By default, the displayed backup plans also include unscheduled tasks. To prevent unscheduled tasks from being displayed, use the Hide Unscheduled Tasks option.
With SEP sesam v. 5.0.0 Jaglion, the option Hide Unscheduled Tasks has been replaced with quick filtering. With the new Quick Filter, you can show/hide unscheduled tasks and filter the results by type (backup, backup group, etc.) and/or level (Copy, Full, etc.).

Backup plans Jaglion.jpg

  • Properties: Shows information about the selected object, e.g., task, task group, migration, or replication.
  • New Backup Event: By selecting a backup task or a task group and clicking New Backup Event, you can configure a new backup event, as described in Creating a Backup Event.
  • Backup plans event Beefalo V2.jpg


Migration tasks

About migration

Migration is the process of copying backed-up data from one media pool to another, for example, from a disk to a tape. Backed-up files are organized as savesets that are copied from the source to the target media pool, typically in a disk-to-disk-to-tape (D2D2T) sequence.

This allows for duplication of the savesets. To optimize migration performance, you cannot migrate savesets with errors. It is possible to migrate:

  • savesets with status successful
  • savesets with warnings (status successful or with warnings) or
  • partially restorable savesets (with data from aborted backups).

Provided that the media in the source and target media pools are available after migration, the saveset is duplicated. However, a saveset is considered migrated when it is deleted from the source media pool. Both, the source and target savesets can be accessed using the restore wizard. If only the migrated saveset exists, it will be required in the case of a restore.

Migration tasks are managed under Main selection -> Tasks -> Migration tasks.

Migration tasks Jaglion.jpg

Configuring migration

Configuring a migration job consists of 3 steps: creating a migration task, creating a migration schedule, and creating a migration event.

You can start a configured migration task from the GUI immediately. For more details on configuration, see Configuring Migration.

Migration options

Migration task Jaglion.jpg

When configuring a migration task, you can set the following options:

  • Name: Enter a meaningful for the migration task, e.g., MIG_Si3_mly_to_mig_3mly (max. 50 characters).
  • Media pool: Specification of the source media pool.
    • Pool: Select the source media pool from which the data will be migrated, e.g., source_mediapool (mandatory field).
    • Drive: Drive number of the drive that will be used to read the data. By selecting the source media pool, the drive number is set automatically. However, you can select another drive from the drop-down list (mandatory field).
    • Interface: Optionally, specify the network interface of the server through which the data transfer will be executed, e.g., the name of the Remote Device Server (RDS).
  • Destination: Specification of the target for the migration.
    • Pool: Select the target media pool to which the data will be migrated, e.g., target_mediapool (mandatory field).
    • Drive: Optionally, select the drive number of the drive that will be used to write the data. Typically, you use this if you have configured additional drives and want to assign dedicated drives for migration jobs. For details, see the option Create second drive in Configuring a Data Store.
    • Interface: Optionally, specify the network interface of the server through which the data transfer will be executed, e.g., the name of the Remote Device Server (RDS).
  • Backup date: The time frame of the backups that will be migrated.
    • To define the time frame of the backups to be migrated, you can either specify it by Date or select the option Relative backup date. With the values entered in the from/to fields of the Relative backup date you define the number of days in the past that are considered for data migration, i.e. all data in the source media pool that was backed up within a given period of time is going to be migrated to the target pool. For example, to migrate all data from the past week including the current Sesam day, the Relative backup date is set to -7 while to is set to 0. Or, to migrate all data from the last 10 days, specify the relative time frame from -10 to 0.
    • In the drop-down list Based on, the Sesam days option is selected by default. Sesam day is a backup day you define according to your backup routines. For example, your backups can run after midnight but retain the backup date of the prior day. Sesam day/backup day is defined by the time specified in the NEWDAY event. For details, see SEPuler: SEP sesam backup day.
  • Backup State: Select the backup completion status of the savesets you want to migrate: Successfully or with warnings (default), Only successful or Partially restorable (containing data from cancelled backups).
    • Allow copying of existing migrations (previously Copy migrated saveset again): If selected, a previously migrated saveset can be migrated again.
    • Delete after successful migration: If selected, a saveset is deleted after successful migration.
  • Backup level: Select the backup level you want to migrate (COPY, FULL, DIFF, INC): C F D I G, where G stands for a special backup level generation. Backup level G allows you to migrate a complete backup cycle in one step, giving you everything you need for a disaster recovery. For example, combining the selected backup levels I and G within the specified time frame -1 to 0 in the Relative backup date would migrate all incremental backups from yesterday up to today, as well as all dependent incremental and differential backups of the respective backup chain, including the last associated full backup. This ensures all required backups are available on the storage media in the case of a disaster recovery. .
  • Number of copies: Select how many times may the backed up data be migrated. The default value is 0, which means that data migration is unlimited.
  • Object: Select one of the following objects as the migration source.
    • Task: If you select a particular backup task as the source, only this task within the defined time frame is migrated.
    • Task group: If you select a task group as a source, only the tasks of this task group within the defined time frame are migrated.
    • Client: If you select a particular client, only the backups for this client within the defined time frame are migrated.
  • Special filter:
    • Start media: Optionally, you can select only one medium from the source media pool to be migrated. You should take special care not to break a backup chain that could span across multiple media. If you select only one medium for migration, only the backups stored on that medium will be migrated, whether or not they belong to a wider backup set.
    • Saveset: Optionally, you can select only one saveset to be migrated according to its ID.
    • Paralell migration: Select (default) or clear the check box Parallel migration. If selected, the data can be migrated concurrently using multiple streams, thus improving the migration speed.
  • Note: Optionally, add additional information about the migration.

After you configure your migration task, click Save or Cancel.

Schedules

A migration task can be associated with a schedule that has a corresponding event attached to it. For more information on creating the entire setup for migration, see Configuring Migration.

If you already have a configured schedule, you can link your migration task to it by using the Schedules tab. Then select the check box next to the schedule you want to use. You can also change its priority.


Replication tasks (Si3)

About replication

Replication is the process of copying data from one host to another (between backup-to-disk devices capable of replication) in a block-level, incremental fashion and is an important subset of the larger disaster recovery (DR) effort.

SEP sesam provides different replication types. SEP Si3 replication enables you to replicate data between SEP sesam Server and SEP sesam Remote Device Server (RDS) or between two RDSs. You can also use HPE Catalyst stores and HPE Cloud Bank Storage, or S3 cloud storage as replication targets. For details, see About Replication.

Replication tasks are managed under Main selection -> Tasks -> Replication Tasks (previously Si3 Replications).

Replication tasks Jaglion.jpg

Configuring replication

Configuring replication is quite simple and does not differ significantly between replication types. The first step in configuring replication is to configure the data stores. Depending on the replication type, configure the appropriate data store type:

Then you need to create media pools, test your backups, and create the relevant replication task:

For detailed explanations of replication configuration, its benefits and limitations, see Configuring replication.

Replication options

New replication task.jpg

When configuring a replication task, you can set the following options:

  • Name: Enter a meaningful name for the replication task, e.g., rep-source_mediapool-to-target_mediapool.
  • Media pool: Specification of the source media pool.
    • Pool: Select the source media pool from which the data will be replicated, e.g., source_mediapool.
    • Drive: Select the drive number of the drive that will be used to read the data. Selecting the source media pool automatically sets the drive number. However, you can also select another drive from the drop-down list (mandatory field).
    • Interface: Optionally, specify the network interface of the RDS through which the data transfer will be executed, e.g., the name of the RDS.
  • Destination: Specification of the target for the replication.
    • Pool: Select the target media pool to which the data will be replicated, e.g., target_mediapool.
    • Drive: Select the drive number of the drive that will be used to read the data (mandatory field).
    • Interface: Optionally, specify the network interface of the RDS through which the data transfer will be executed, e.g., the name of the RDS.
  • Backup date: Specify the time frame of the backups that are to be replicated.
    • Date: Set the time frame of the backups to be replicated. It is recommended to use the option Relative backup date instead.
    • Relative backup date: Define the time frame of the backups to be replicated by specifying appropriate values for the from/to fields. These fields specify the number of days in the past that are considered for replication, meaning all data in the source media pool that was backed up within a given period of time is going to be considered for replication to the remote pool. For example, to replicate all data from the past week, set the Relative backup date to -7 and to to 0. Since only new data blocks are ever replicated during replication, you can specify a very high number in the from field, such as -99.999. This way, all backups since the initial replication are always checked, but only the changed data is replicated.
    • Information sign.png Note

      You cannot replicate savesets with errors. It is possible to replicate savesets with status successful, savesets with warnings (status successful or with warnings) or partially restorable savesets (with data from aborted backups).

    • Based on
      The Sesam days option is selected by default. The Sesam day is a backup day you define according to your backup routines. For example, your backups can run after midnight but retain the backup date of the prior day. The Sesam day/backup day is defined by the time specified in the NEWDAY event. For details, see NEWDAY Event.
  • Note: Optionally, add additional information about replication.

After you configure your replication task, click Save or Cancel.

Schedules

A replication task can be associated with a schedule that has a corresponding event attached to it. For more information on creating the entire setup for replication, see Configuring replication.

If you already have a configured schedule, you can link your replication task to it by using the Schedules tab. Then select the check box next to the schedule you want to use. You can also change its priority.


Tasks as list

The menu item Tasks as list shows a list of all configured backup tasks and their properties, such as task type, location and client, source and excludes.

Tasks as list Beefalo.jpg

By double-clicking a backup task (or clicking Properties), you can check the details of the selected task and you can also edit the existing settings.

By right-clicking on the task, the following options are shown:

Tasks as list right-click Beefalo.jpg

  • Properties: Shows the details of the backup task.
  • Results: Shows the last backup details for this task, see Properties of a finished backup.
  • Immediate Start: Allows you to initiate a process manually, see Immediate start.
  • Copy (available only for backup task): Copies the selected backup task.
  • New Location: Opens a dialog for configuring a new location, see Configuring Location.
  • New Client: Opens a dialog for configuring a new client, see Configuring Clients.
  • New Backup Task: Opens a dialog for configuring a new backup task.
  • New Restore Task: Opens a dialog for configuring a new restore task. The New Restore Task option opens the restore wizard, as described in Restore. If you select the restore from this location certain parameters will be pre-set. A task name will also be automatically assigned.
  • Delete: Deletes a task from SEP sesam.

You can add additional task properties to the list by right-clicking on the table header and selecting the relevant columns. The new columns will only be applied if you have clicked the Save view button.

You can also print a list by clicking the Print button.

GUI: Scheduling

Schedules overview


Schedules overview

SEP sesam establishes schedules as a frame, to which you link different events, such as backup, migration, replication, etc. Schedules always contain one predefined task: a NEWDAY schedule. Linked to it is a NEWDAY event which is used by SEP sesam to reorder its database, enable undisturbed activity of the SEP sesam processes as well as to define a new backup day.

Do not deactivate a NEWDAY event or delete a NEWDAY schedule, because this will cause SEP sesam to stop working properly! For details, see NEWDAY Event.

A schedule defines the recurrence of an event and may be executed in minutes, hours, days, months or years. It can be set up to start periodically or to be executed just once. It can be used for any number of events, and a particular task (backup, restore, migration, etc.) can have events in several schedules. All schedules and related jobs are configured and run in the time zone of the SEP sesam Server.

Schedules overview Beefalo.jpg

This window shows an overview of the configured schedules and related events. By using toolbar buttons you can configure the chronology of all processes in SEP sesam. You can create a new schedule or edit an existing one. Then you create a new event for the specific schedule and define its job. The job is run at specified time and, if defined as recurring, executed at specified time interval.

You can also use Without Schedule option, which is available, if you set the value for enable_gui_events_without_schedule in the Defaults window (Configuration -> Defaults -> Settings tab) to 1 manually.

Defaults without schedules Beefalo.jpg
It shows all backup events which are not assigned to a schedule due to the following possible reasons:

  • Events were deliberately created without a schedule for external backups, such as SAP HANA, where the external applications manage the backup scheduling.
  • Events were first linked to a schedule and then disconnected from it by opening the event and selecting the option Without Schedule, as shown in the screenshot below.
  • Changing events Beefalo.jpg

Information sign.png Note
You should only delete events without a schedule if you are sure that they will not be used for an external backup.

You can create a new schedule from Main Selection -> Scheduling -> Schedules -> New Schedule. For details, see Creating a Schedule.

After you have created a schedule, you can link a specific event to it (backup, restore, migration, etc.). In the Main Selection -> Scheduling -> Schedules, right-click on the schedule, and select the event which you want to create, e.g., new backup event.

Schedule properties

Clicking Properties or double-clicking the schedule displays all details of the selected schedule. You can also edit the existing schedule settings.

Schedule Beefalo.jpg

  • Execution off: Execution is enabled by default. Use this option to disable the schedule. If you select it all events that are linked to this schedule will be deactivated. The schedule will still be displayed as shaded in the list of schedules, but the related jobs will not run.
  • Name: The name of the schedule.
  • Start: The start date and time for the schedule. By default, the current date is already entered in the first (date) field. In the next (hour) field, specify the start time <hh:mm> for a job to begin. The schedule will be activated on the specified date and time.
  • Expiration date: Set the validity of the schedule. If the schedule should only be valid for a limited period of time, e.g., until the end of the year, select the check box and enter the date of its suspension. Clicking the arrow displays a calendar. The schedule will be deleted after the Expiration date criterium is met.
    By default, this option is disabled and the schedule will be repeated in perpetuity.
  • Selection of time intervals: Configure the time intervals for scheduled jobs. Jobs can occur once, or recur daily, monthly, yearly, or as defined (custom calendar).
    • Once: no repetition, single run
    • Daily: repetition in days, hours or minutes
    • Weekly: repetition in weeks or weekdays
    • Monthly: repetition on absolute or relative dates: 1st/2nd... or Mon/Tue...
    • Yearly: repetition on absolute or relative dates
    • User Defined: Option for setting up a custom calendar. For details, see Creating Custom calendar.
  • Advanced settings: Allows you to further refine your schedule.
    • Start time frame: Select the check box if you want to specify maximum allowed actual startup time for your event (the amount of time an event can be in the queue). Specify the startup time in days and/or hours. The actual start time depends on the processor load of the system. At the starting time of the event, every event is forwarded to the queue, where it may have to wait until jobs with higher priorities are completed. For jobs with the same priority, the FIFO rule (first in first out) applies. If this option is set and the event cannot be executed within the specified time frame, it will not be executed at all.
    • Repeat task: Select the check box if you want to repeat the event. Choose how often (in hours or minutes) the task should be repeated.
    • For a duration of: Available if the Repeat task check box is selected. You can specify for how long should the event be repeated in days and/or hours.
    • Stop task if it runs longer than: Select the check box if you want to set the amount of time (days and/or hours) following the event's scheduled start time after which the event will be cancelled.

New backup event

Backup event represents the last step in the process of configuring a backup job. First a backup task is created by selecting the task type and source. Next is a backup schedule, to which a backup event is linked. For details, see Creating a Backup Event.

The button New Backup Event opens the following window:

New backup event Beefalo.jpg

  • Name: You can change the displayed backup event name.

Sequence Control

  • Priority: The priority of your backup event. Default priority level is 1, which is the lowest priority (the highest is 99). The only exceptions are schedules with priority 0, which override all other priorities and are always executed. See Setting event priorities.
  • Blocking date: A blocking event is any type of event with a higher priority that obstructs another event. A blocking event only affects other events with the same name when schedules are overlapping. For details, see Blocking Events.

Object

  • Task: Select the task to which you want to link this event.
  • Task group: Select the task group (instead of task) to which you want to link this event.

Parameter

  • Backup level: Select between the backup levels FULL, DIFF, INC, COPY.
  • Hot/Cold backup: You can set execution parameter, e.g., for database backups.
  • Media Pool: Select the target media pool to which the data will be backed up. If you want to enable source-side deduplication, you have to select the media pool which is combined with an Si3 deduplication store backend.
  • SEP Si3 Source Side Deduplication: Source-side deduplication (Si3S) requires a special license and a configured Si3 deduplication store. If the specified target media pool is combined with an Si3 deduplication store backend, the option SEP Si3 Source Side Deduplication is shown and can be enabled.
  • Drive group: (non-editable parameter) The drive group which is specified in the media pool. This field changes depending on the media pool selection.
  • Drive (opt.): Optionally, specify the drive number of the drive that will be used to write the data.
  • Interface (opt.): Selection of an alternate (configured) name of the TCP/IP-name of the client. This can be used to direct the data flow over a particular network connection in order to enable smooth execution of backups or restores without blocking another network activities.
  • Follow up: You can configure events that are triggered on the SEP sesam Server once the initial event has completed. For details, see Follow-up Events.
  • Migration task: You can select a follow-up migration task from the drop-down list.

New restore event

The button New Restore Event opens the New restore event window with the Parameter tab selected. The first tab is Schedule, as explained in the section above. For more details, see Scheduling Restore.

Schedules new restore event Beefalo.jpg
Parameter

  • Restore task: Select the restore task from the drop-down list for which the event is going to be configured.

Backup selection

Select As defined in task option if you want to run the restore exactly as defined by the task parameters using the same backup saveset. If you want to adjust the restore task, for example to use the most recent backup saveset, select the Custom option. In the latter case, you can define the following settings:

  • Relative backup day: from - to as a relative indication of the number of days that have passed since the backup. Negative numbers specify days in the past, while positive numbers specify days in the future. For example, 2 weeks ago until now: from date = -14 to date = 0.
  • State: You can select the condition of the backup that will be used for restore:
    • Successful or with warnings (default)
    • Only successful
    • Only with warnings
    • Partially restorable (cancelled backups)
  • Selection: Provides the criteria according to which the backup saveset to be restored is defined:
    • Youngest: The most recent backup in the range of the relative backup day will be used for restore.
    • Oldest: The eldest backup in the range of the relative backup day will be used for restore.
  • Backup level: You can select the level of the backup which will be restored (C, F, D or I).
  • Pool restriction: You can define that a saveset must come from the specified media pool.

Sequence control

  • Priority: The priority of your restore event. Default priority level is 1, which is the lowest priority (the highest is 99). The only exceptions are schedules with priority 0, which override all other priorities and are always executed. See Setting event priorities.
  • Blocking date: Used together with high priority for special events. See Blocking events.

Destination parameter

  • Drive: Optionally, specify the drive number of the drive that will be used to write the data.

New migration event

Migration event represents the last step in a migration job configuration. First a migration task is created by selecting the backed up data, source and target media pool. Next is a migration schedule, to which a migration event is linked.

Creating a migration event consists of reviewing migration task execution parameters and (optionally) setting event priority. For details, see Configuring Migration.

New migration event Beefalo.jpg

  • Task name: Name of the migration task, e.g., MIG_Si3_mly_to_mig_3mly.

Media pool

  • Pool: The source media pool from which the data will be migrated, e.g., source_mediapool (non-editable parameter).
  • Drive: Drive number of the drive that will be used to read the data (non-editable parameter).
  • Interface: The network interface of the server through which the data transfer will be executed, e.g., the name of the Remote Device Server (RDS) (non-editable parameter).

Destination

  • Pool: You can change the target media pool to which the data will be migrated, e.g., target_mediapool.
  • Drive: Optionally, change the drive number of the drive that will be used to write the data. Typically, you use this if you have configured additional drives and you want to assign dedicated drives for migration jobs. For details, see the option Create second drive in Configuring a Data Store.
  • Interface: Optionally, specify the network interface of the server through which the data transfer will be executed, e.g., the name of the Remote Device Server (RDS).

Backup date

  • To define the time frame of the backups that will be migrated, you can specify it either according to dates – Date or select the option Relative backup date. With values entered in the from/to fields of the Relative backup date you define the number of days in the past that are considered for data migration, meaning all data in the source media pool that was backed up within a given period of time is going to be migrated to the target pool. For example, to migrate all data from the past week including the current Sesam day, the Relative backup date is set to -7 while to is set to 0. Or, to migrate all data from the last 10 days, specify the relative time frame from -10 to 0.
  • In the drop-down list Based on, the Sesam days option is selected by default. Sesam day is a backup day you define according to your backup routines. For example, your backups can run after midnight but retain the backup date of the prior day. Sesam day/backup day is defined by time set in the NEWDAY event. For details, see SEPuler: SEP sesam backup day.

Backup State

  • You can select the backup completion status of the savesets you want to migrate: Successfully or with warnings (default), Only successful or partially restorable (containing data from cancelled backups).
  • Copy migrated savesets again: If selected, a saveset that has already been migrated can be migrated again.
  • Delete after successful migration: If selected, a saveset will be deleted after successful migration.

Backup level

  • Select the backup level you want to migrate (COPY, FULL, DIFF, INC): C F D I G, where G means a special backup level generation. The G backup level enables you to migrate a complete backup cycle in one step thus providing everything you need for disaster recovery. For example, the combination of selected backup levels I and G within the specified time frame -1 to 0 in the Relative backup date would migrate all incremental backups from yesterday up to today as well as all dependent incremental and differential backups of the respective backup chain including the last associated full backup. This ensures that in need of disaster recovery all required backups are available on the storage media.

Number of copies

  • Copies: Select how many times may the backed up data be migrated. Default is 0, meaning that data migration is unlimited.

Object

  • Task: If you select a particular backup task as a source, only this task within the defined time frame is migrated.
  • Task group: If you select a task group as a source, only the tasks of this task group within the defined time frame are migrated.
  • Client: If you select a particular client, only the backups for this client within the defined time frame are migrated.

Special filter

  • Start media: Standard is "*" for all media. Optionally, you can select only one medium from the source media pool to be migrated. You should pay special attention in order not to break a backup chain that might span across more media. If you select to migrate solely one medium, then only the backups that are stored on this medium are migrated regardless whether they belong to a wider backup set or not.
  • Saveset: Standard is "*" for all savesets. Optionally, you can select only one saveset to be migrated according to its ID.
  • Paralell migration: Select (default) or deselect the check box Parallel migration. If selected, data can be migrated concurrently using multiple streams, thus improving the migration speed.
  • Note: Optionally, add additional information about the migration.

New replication event

Creating a replication event consists of reviewing replication task execution parameters and (optionally) setting event priority. For details, see Replication.

New replication event Beefalo.jpg

  • Name: The name of the replication task, e.g., rep-source_mediapool-to-target_mediapool.

Sequence control

  • Priority: Event priority is used for resolving scheduling conflicts. Priorities can be assigned to schedules, from lowest (1, default) to highest (99). For details, see Event Priority.
  • Blocking date: A blocking event is any type of event with a higher priority that obstructs another event. A blocking event only affects other events with the same name when schedules are overlapping. For details, see Blocking Events.

Media pool

  • Pool: The name of the source media pool from which the data will be replicated, e.g., source_mediapool (non-editable parameter).
  • Drive: The drive number of the drive that will be used to read the data (non-editable parameter).
  • Interface: The network interface of the RDS through which the data transfer will be executed, e.g., the name of the RDS (non-editable parameter).

Destination

  • Pool: The name of the target media pool to which the data will be replicated, e.g., target_mediapool (non-editable parameter).
  • Drive: The drive number of the drive that will be used to read the data (non-editable parameter).
  • Interface: The network interface of the RDS through which the data transfer will be executed, e.g., the name of the RDS (non-editable parameter).

Backup date

  • Date: You can define the time frame of the backups that will be replicated. It is recommended that you use the option Relative backup date instead.
  • Relative backup date: You can define the time frame of the backups that will be replicated by specifying appropriate values for the from/to fields. These fields specify the number of days in the past that are considered for replication, meaning all data in the source media pool that was backed up within a given period of time is going to be considered for replication to the remote pool. For example, to replicate all data from the past week, the Relative backup date is set to -7 while to is set to 0. Because the replication will always replicate only new blocks of data, you can specify a really high number in the from field, such as -99.999. This way all backups since the initial replication will always be checked, but only the changed data is going to be replicated.
  • Information sign.png Note
    Only the savesets with status successful and with warnings are selected for replication, while savesets with errors and only partially restorable savesets (containing data from cancelled backups) are not replicated.
  • Based on
    The Sesam days option is selected by default. Sesam day is a backup day you define according to your backup routines. For example, your backups can run after midnight but retain the backup date of the prior day. Sesam day/backup day is defined by time set in the NEWDAY event. For details, see NEWDAY Event.
  • Note: Optionally, add additional information about the replication.

New media event

A media event can be a user-defined event or an internal event created by SEP sesam. For example, if the specified media are unavailable at the start of a backup or if the end of media (EOM) is reached during data transfer, SEP sesam creates an internal media event which determines the next media for the backup. If no other media events are configured in the schedule, only internal media events are executed. For details, see Creating a Media Event.

New media event Beefalo.jpg

Sequence control

  • Priority: Event priority is used for resolving scheduling conflicts. Priorities can be assigned to schedules, from lowest (1, default) to highest (99). For details, see Event Priority.
  • Blocking date: A blocking event is any type of event with a higher priority that obstructs another event. A blocking event only affects other events with the same name when schedules are overlapping. For details, see Blocking Events.

Media actions

  • Initialize: Initializing media prepares it for use with SEP sesam. Initialization process rewrites the tape label. Any existing information on tape are deleted. A media event prepares the medium of the selected pool to be used for backup.
  • Readability check: The readability check tests the backup data readability. During the check the data on medium is read in blocks, and the structure of tape is checked and recorded. For details, see Configuring a Readability Check.
  • Archive adjustment: An archive adjustment scans media in selected loader to update SEP sesam information about the media in the loader. It is required if the media in the loader have changed, for example if new media are added. For details, see Setting up Archive Adjustment.
  • Close tape: Closing the tape means that EOM (End of Media) is created on tape regardless of whether it is full or not. Such a tape can no longer be used for storing the data.

Parameter:

  • Media pool: Defines the media pool that is used for the media event.
  • Drive: Optionally, you can define a specific drive for the event execution. If a drive is not selected, SEP sesam Server automatically selects one of the available drives.
  • Media: Optionally, you can select the medium that you want to use. If no medium is selected, SEP sesam Server automatically assigns the medium with the oldest EOL. For details on GET_OLDEST strategy, see Media Strategy.
  • Drive group: Displays the name of the drive group that belong to the media pool.
  • Loader, First slot, Last slot (non-editable parameters)
  • Options: If required, set additional execution options.

New command event

The command event can be scheduled to run automatically. For details, see Creating a Command Event.

New command event Beefalo.jpg
Sequence control

  • Priority: Define a priority of your command event. SEPuler always executes the schedules with higher priority first. Default priority level is 1, which is the lowest priority (the highest is 99). The only exception are the schedules with priority 0, which override all other priorities and are always executed. For details, see Event Priority.
  • Blocking date: This should be used together with high priority for special events. If checked, the blocking event will block events of the same type of a lower priority, ensuring the command event to be processed in case other command events are scheduled at the same time. See Blocking Events.

Parameter

  • Name: Enter a name for the new event or search for and select an already existing command event. Searching for command opens a new window, where you can add a new command event, copy an already existing command event, select which existing command event you want to use again by clicking the Select button, and change or delete an existing command event.
  • Select command Beefalo.jpg

  • Client: Select a client, on which the command will be executed.
  • User: Enter the user name of a user with sufficient access to execute the command on the client.
  • Retention time: Specify for how long (in days) the command event results and logs will be kept.
  • Command: Enter the complete command.
  • Add to command: Optionally, add additional parameters to command, e.g., sm_sho.
SEP Tip.png Tip
You can also access the configured commands from the menu bar -> Configuration -> Command.
Access limitation of command events

Command event starts any executable command on the chosen client. Since there are certain security issues to consider, not every command can be implemented by each user on specific clients. Without additional entries only commands entered in the system directory at <SESAM_ROOT>/bin/sesam are allowed. Within these commands, e.g., a shell script, any desired commands can be released to selected users.

If a command should be started from another directory before the regular backup starts, this must be entered/permitted at the target client.

UNIX

External commands are executed only if the user and command are inserted into the file /etc/sesam_cmdusers.allow on the client computer. Therefore, if necessary, the template from path <SESAM-BIN>/skel/templates must be copied to /etc and adapted accordingly.

Format: 'user command|*  ( * = all commands can be started)
Windows

External commands are only executed if the user and command are inserted into the registry on the client computer at key //HKLM/SOFTWARE/SEP Elektronik GmbH/sesam/CommandEvents/<user>/<command>.

Command Execution
* all instructions
cmd /c all DOS instructions (dir, etc.)
DOS command (e.g., dir) only specific DOS command (e.g., dir)
specific command (e.g., ping) only specific command (e.g., ping)

Additionally on the client computer the entry CTRLD_Path=ID/bin/sesam;ID/bin/sms in the file ID/var/ini/sm.ini in section [CTRLD_Server] must be extended with the directories where the desired programs reside.

Registryentry.JPG

Information sign.png Note
Many errors are made when setting up the desired user permissions and allowed commands:
  • The necessary entries are not entered in the target client directories, not entered in the server or are entered incorrectly.
  • Instead of entering the command as a key it is entered as a character string.

New Newday event

SEP sesam Newday is a predefined SEP sesam daily event that resets the backup event calendar and is managed by the SEPuler. It is used by SEP sesam to reorder its database and enable uninterrupted activity of SEP sesam processes, therefore it must never be completely deactivated or it will cause SEP sesam to stop working properly. For details, see NEWDAY Event.


Events

Shows an overview of the configured backup, restore, migration, replication, media, command and Newday events. These are the events that SEPuler permanently checks and executes (if the start time is reached) in chronological order. For details, see SEP sesam Events.

Information sign.png Note
  • You can check the status of all events online by using new Web UI. For details, see SEP sesam Web UI.
  • In v. ≥ 5.0.0 Jaglion, you can use the new quick filter when using the GUI to show/hide unscheduled tasks, tasks in the task groups, and filter the results by type (backup, backup group, etc.) and/or level (copy, full, etc.).

Events Beefalo V2.jpg

The View Mode button allows you to switch between the table view and the tree view with grouped objects.

  • Tree view: The default view of SEP sesam shows the status of individual locations grouped in a hierarchical view.
  • Table view: A simple flat view that shows the status of individual locations one by one.

Events Jaglion.jpg


Calendar Sheet

An overview of scheduled as well as completed, expired events and their current status is provided by Calendar sheet from the Main selection -> Scheduling -> Calendar Sheet. All events are recorded by SEPuler.

You can check your backup-, restore-, migration-, replication-, media-, command- and Newday events. For details, see SEP sesam Events.

Information sign.png Note
As of 4.4.3 Beefalo V2, you can also check the status of your events online by using new Web UI. For details, see SEP sesam Web UI.

SEP sesam calculates 14 days offline in advance. Therefore this information can be displayed very quickly. Days further out in the future are calculated online, but this may take some time.

Calendar sheet Beefalo V2.jpg

You can refresh the calendar immediately (Refresh option), or every 10 seconds automatically (Auto update option).

Changes in schedules are also updated online, thus the user can immediately see the updated calendar.

GUI: Job State

All Results by State

From Main Selection -> Job State -> All Results, you can check the details of all jobs (backups, restores, migrations, etc.). You can filter the results by Date range and clients (by time, by client and/or by location), by State (in progress, failed, successful, all states) and by Type (event type and backup level).

As of 4.4.3 Beefalo V2, you can also check the details of your jobs online by using new Web UI. For details, see SEP sesam Web UI.

Information sign.png Note
You can use a force refresh by clicking Shift and Refresh button to clear the GUI cache memory. In some cases clicking only the Refresh button won't show the updated view.

All results Beefalo V2.jpg

The following information is displayed:

  • Job ID
  • Event Type: backup, restore, media, etc.
  • State: successful, active, error, etc.
  • Object: The name of the object being processed.
  • Task: The name of the task.
  • Start/Stop time: Recorded start and stop time of the job.
  • Sesam date: Sesam day is a backup day you define according to your backup routines. For example, your backups can run after midnight but retain the backup date of the prior day. Sesam day/backup day is defined by time set in the NEWDAY event. For details, see SEPuler: SEP sesam backup day.
  • Saveset: Backup copy ID.
  • Client: The name of the client.
  • Backup EOL: The expiry date for all data that belongs to the same backup.
  • Drive: The number of the drive used by a job.
  • Data size: The size of the data specified in KiB, MiB.
  • Throughput: Average throughput of the process.
  • Duration: Duration of the job.
  • Session ID: SEP sesam session ID.
  • Pool: The name of the used media pool.
  • Message: Information of the performed action, e.g., Backup completed successfully.
  • Note: Comment of the user.


Backups by state

From Job State -> Backups, you can check the details of all performed backups, such as status, backup EOL, data size, throughput, etc. You can filter backup operations by time, by client or location, by their status and/or by event type.

Information sign.png Note
You can check the details of your backups online by using Web UI. For details, see SEP sesam Web UI.

Backups by state Beefalo.jpg

You can change the order of the columns by dragging-and-dropping the selected columns. By selecting a task and clicking the button Properties or by simply double-clicking the task you can view its details. An active task can be canceled by selecting it and clicking the button Cancel.

By right-clicking a column header the following pop-up menu appears:

Backups pop-up menu Beefalo.jpg

It enables you to resize the columns, to show all hidden columns or to set up displayed columns. By selecting Column Selection, you can simply select the relevant check boxes to set up which columns will be displayed.

Column selection Beefalo.jpg

View Mode

The View Mode button enables you to switch between table view and tree view and group the same backup task states in one item.

  • Tree view: SEP sesam default view shows the status of individual backup tasks grouped in a hierarchical view.
  • Table view: A simple flat view shows the status of each backup task in turn.
  • Group by: You can group the same backup tasks in one item (by task, by task and date or by task and subgroup by date) and view their current status. Grouping allows you to quickly check the success of backup jobs (useful for backups that run several times a day and generate a large number of backup jobs in one day, such as SAP HANA or Oracle). You can identify the status of a grouped task by the color of the State column. If the grouping contains backup jobs with different states, the icon is displayed in two colors. For example, a square with green at the top and red at the bottom means that the last run of the task was successful, while a previous run ended with errors.

Backups view mode Beefalo.jpg

SEP Tip.png Tip
In some cases, clicking the Refresh button is not enough to display the updated view. You can clear the GUI cache memory by using a force refresh: press the Shift and Refresh buttons to reload the view.

Filter

The Filter is located at the top right of the window. You can filter the jobs by date, by client or location, by their status, by task name, and/or by event type.

Information sign.png Note
The control window all servers is only visible for the SEP sesam Master GUI. With this option, the system administrator can manage specific SEP sesam Servers from a single location.
Filter: Date range and clients

Use Date range and clients to filter backup jobs by date, by client and/or by location.

Backups filter Beefalo.jpg

Date (Sesam Date): Use the date range specification from/to to specify the date range for the displayed backups.

Filter:

  • Location: Filters the backups according to the specified location.
  • Client: Filters the backups according to the selected individual client.
  • All servers: This switch is only available in a Master GUI environment. It is used by the system administrator to display the backups of all servers that are managed with the Master GUI.
Filter: State

Use the State filter to display or hide the backups according to one or more selected states.

Backups state Beefalo.jpg

In Progress

  • In queue: If the start time of a task is reached, but SEP sesam is still busy with other jobs, the task is placed to a job queue and executed by SEPuler according to its priority.
  • Active: The backup job is currently running.

Failed

  • Canceled: Backup job is canceled by user.
  • Error: Fatal error occurred during the backup, therefore the backup has failed.

Successful

  • Successful: Backup has finished successfully.
  • Warning: A warning occurs during the backup.

All states

  • On: If selected, all backup jobs are displayed regardless of their status.
Filter: Type

You can filter the jobs by event type, such as backup, command, etc., and further refine the displayed results by backup level (when applicable; Full, Diff, Inc, Copy).

Backups type Beefalo.jpg

Events

  • Newday: Shows predefined SEP sesam daily event (NEWDAY) which is used to define a new backup day.
  • Backup: Shows all backup events.
  • Migrations (available in v. ≤ 4.4.3 Beefalo V2): If turned on, the migrations are displayed next to the backups. This can be useful when periodic dependencies should be compared.
  • Startup: Shows startup events that are running after the SEP sesam Server is restarted. These events are not running regularly; they are triggered automatically by server startup.
    • Command: Shows all command events.
    • Group: This is a placeholder for grouping of single tasks and can be turned on/off.
    Filter: Task name

    You can filter the backup tasks by their name. They are displayed under the search field. You can select one or more tasks by holding down the CTRL-key and clicking the name(s).

    Backups task name Beefalo.jpg

    Filter: Filter settings

    In the Filter settings you can activate or deactivate the automatic refresh of the result table.

    Backups filter settings Beefalo.jpg

    Properties of a finished backup

    You can view the details of a specific task by selecting and double-clicking it (or by clicking the Properties button).

    Info 1

    Displays information about saveset, level, drives, backup EOL, etc.

    Backups info 1 Beefalo.jpg

    • Saveset: The name of the saveset.
    • Location: The location of the client.
    • Media pool: The name of the media pool used for the backup.
    • Drive: The number of the used drive for backup.
    • Start/Stop time: Recorded start and stop time of the backup job.
    • Backup EOL: You can click the drop-down list for the Backup EOL and modify the expiry date for all data that belongs to the same backup. Note that modifying backup EOL will affect all backups in a backup chain, if a saveset with adjusted backup EOL is a part of it. For details, see Changing Retention (EOL).
    • State: Status of the backup (Successful, Error, etc.)
    • Client: The name of the backup client.
    • Level: Backup level (F=Full, C=Copy, I=Incremental, D=Differential).
    • Size: The size of the backed up data specified in bytes.
    • Throughput: Average throughput of the process.
    • Overall duration: Duration of the backup.
    • Locked: Savesets of this backup must not be deleted.
    • Information sign.png Note
      In SEP sesam ≤ 4.4.3 Beefalo V2, the backup locked status is only applied to the selected backup, so you need to manually lock all backups in a backup chain as well as migrated and replicated backups. With v. 5.0.0 Jaglion, the locked status is automatically applied to all savesets of a backup (backup chain, migrated and replicated savesets). You can also lock your backups in SEP sesam Web UI.
    • Storage Location: All backup task related storage details, e.g., media, saveset EOL, etc.
    • Message: Detailed information about the backup status.
    Info 2

    Information about media number, system backup, backup source, SBC start and runtime, status of encryption and compression, etc.

    Backups info 2 Beefalo.jpg

    Main Log

    Main log is the log of the SEP sesam Client (SBC) processing. It records the events that occur during a backup process (startup/shutdown information, errors, etc.) depending on the configured log level. Every time the EOL is modified, the corresponding information is shown in the main log. Note that as an advanced user it is possible to set up a higher log level than default to get more information about the specific backup. See Setting Log Level.

    The new Download button enables you to download a current main log file or the archive with all files included.

    Backups main log Beefalo.jpg

    Trace Log

    Trace log (lgc log) is the log of the SEP sesam kernel modules. It records detailed information about the backup process depending on the configured log level. Trace logs are typically used for analysis and debugging purposes.

    Information sign.png Note
    The Trace log tab is only available in advanced UI mode (formerly expert GUI mode). To check the Trace log, make sure your UI mode is set to advanced. For details, see Selecting UI mode.

    Running SEP sesam with a higher log level than default might be useful when you want to get more information about specific events or modules or when asked by support in the course of diagnosing your specific problem. Note that increasing the log level increases the amount of information being logged and may negatively affect the performance of SEP sesam. For details, see Setting log level globally for SEP sesam kernel modules.

    The new Download button enables you to download a current trace log file or the archive with all files included.

    Backups trace log Beefalo.jpg

    Pre Log

    Pre log is only shown if you have activated a Pre interface (automatically via GUI: Configuration -> Interfaces) to perform the specific operation before a backup job is started, e.g., stop a database or an antivirus service before the backup. For details, see Using Pre and Post Scripts.

    Post Log

    Post log is only shown if you have activated a Post interface (automatically via GUI: Configuration -> Interfaces) to perform a specific operation when the backup session stops, e.g., starting a database or shutting down a computer after the backup. For details, see Using Pre and Post Scripts.

    Savesets

    The Savesets tab lists all currently saved backups. For details on how to check backup chain dependencies, see Backup Chain Dependencies.

    Backups savesets Beefalo.jpg


    Restores by state

    From Job State -> Restores, you can check all performed restores and their details, such as status, data size, media pool, start/stop time, etc. Restore operations can be filtered by time, by client, by location and by status (successfull, canceled, active, etc.). For detailed description of the filter options, see State Filter.

    SEP Tip.png Tip
    You can also check the details of your restores online by using Web UI. For details, see SEP sesam Web UI.

    Restores by state Beefalo.jpg

    You can change the order of the columns by dragging-and-dropping the selected columns. By selecting a task and clicking the button Properties or by simply double-clicking the task you can view its details. An active task can be canceled by selecting it and clicking the button Cancel. Note that any data transferred before canceling the restore job stays on the target system.

    With the button View Mode you can switch between the table view and the tree view.

    • Tree view: SEP sesam default view shows the status of individual restore tasks grouped together in a hierarchical view.
    • Table view: A simple flat view that shows the status of individual restore tasks one after another.
    SEP Tip.png Tip
    In some cases clicking only the Refresh button won't show the updated view. You can clear the GUI cache memory by using a force refresh: press both Shift and Refresh button to reload the view.

    Properties of a finished restore

    You can view the details of a specific task by selecting and double-clicking it (or by clicking the Properties button).

    Info 1

    Displays information about restore size, restore settings, restore status, etc.

    Restores info 1 Beefalo.jpg

    • ID: The saveset ID.
    • Saveset: The name of the saveset.
    • User: The name of the user running the restore.
    • Size: The size of the restored data specified in GiB.
    • Restore type: Complete, generation or selective restore
    • Tree type: Hierarchical or flat
    • Mode: Specified execution option for the restore, e.g., Overwrite.
    • Used labels: List of the used media.
    • Message: Detailed status report, e.g., Restore completed successfully.
    Info 2

    Displays information about the restore status, target client, target path, etc.

    Restores info 2 Beefalo.jpg

    • State: Restore status, e.g., Successful, Error, etc.
    • Backup task: The name of the backup task used for the restore.
    • Interfaces: If selected the name of the server from which the files have been restored. This is either a Remote Device Server (RDS) or SEP sesam Server.
    • Location: The location of the target client.
    • Client: The name of the target system.
    • Drive: The number of the used disk drive for restore.
    • Backup count: The number of the used backup task.
    • Start/Stop time: Recorded start and stop time of the restore job.
    • Target: Specified target path for restore.
    • Comment: Additional information.
    Info 3

    Shows the expert options which may have been specified in the restore wizard, if the restore was configured in the advanced UI mode (formerly expert GUI mode).

    Information sign.png Note
    The Expert Options button for specifying advanced restore options is available only in advanced UI mode (formerly expert GUI mode). To use Expert Options, make sure your UI mode is set to advanced. For details, see Selecting UI mode.

    Restores info 3 Beefalo.jpg

    • Options: Specified advanced SEP sesam options, e.g., for setting a higher log level: -v 3.
    • Reduction path: Specified new target location for the restore (by relocation).
    • File filter: If specified, only the data that matches the filter criteria is restored.
    Main Log

    Main log is the log of the SEP sesam Client (SBC) processing. It records the events that occur during a restore process (startup/shutdown information, errors, etc.) depending on the configured log level for the restore. Note that as an advanced user it is possible to set up a higher log level than default to get more information about specific restore. See Setting Log Level.

    The new Download button enables you to download a current main log file or the archive with all files included.

    Restores main log Beefalo.jpg

    Trace Log

    Trace log (lgc log) is the log of the SEP sesam kernel modules. It records detailed information about the restore process depending on the configured log level. Trace logs are typically used for analysis and debugging purposes.

    Information sign.png Note
    The Trace log tab is displayed only in advanced UI mode (formerly expert GUI mode). To check the trace log, make sure your UI mode is set to advanced. For details, see Selecting UI mode.

    Running SEP sesam with a higher log level than default might be useful when you want to get more information about specific events or modules or when asked by support in the course of diagnosing your specific problem. Note that increasing the log level increases the amount of information being logged and may negatively affect the performance of SEP sesam. For details, see Setting log level globally for SEP sesam kernel modules.

    The new Download button enables you to download a current trace log file or the archive with all files included.

    Restores trace log Beefalo.jpg

    Pre Log

    Pre log is only shown if you have activated a Pre interface (automatically via GUI: Configuration -> Interfaces) to perform the specific operation before a restore job is started, e.g., stop an antivirus service before the restore. For details, see Using Pre and Post Scripts.

    Post Log

    Post log is only shown if you have activated a Post interface (automatically via GUI: Configuration -> Interfaces) to perform the specific operation when the restore session stops, e.g., shutting down a computer after the restore. For details, see Using Pre and Post Scripts.


    Migrations and replications

    Migration is the process of copying backed-up data from one media pool to another, for example, from disk to tape. You can check the status of your migration or replication job from Main selection -> Job State -> Migrations and Replications.

    Information sign.png Note
    As of 4.4.3 Beefalo V2, you can check the details of your migrations and replications online by using new Web UI. For details, see SEP sesam Web UI.

    Migration and replication use similar filters and selections as does SEP sesam backup system, for details see Backups by State.

    The columns provide details on status, start and stop time, media pools, etc., used for the migration or replication task.

    You can also examine the progress of the replication and see how much data is being transferred; you can check data size, physical and nominal data in the columns Data Size, Transferred, Transferred (Brutto) and Progress, respectively. For details, see Checking replication status.

    With v. 4.4.3. Beefalo, SEP sesam provides additional View Mode button that enables you to switch between the table and tree view.

    • Tree view: SEP sesam default view shows the status of individual migration or replication tasks grouped together in a hierarchical view.
    • Table view: A simple flat view that shows the status of individual migration or replication tasks one after another.
    Information sign.png Note
    You can use a force refresh by clicking Shift and Refresh button to clear the GUI cache memory. In some cases clicking only the Refresh button won't show the updated view.

    Migrations by state Beefalo.jpg

    Properties of the migration or replication

    You can view the details of a specific migration or replication task by double-clicking it (or by clicking the Properties button).

    Information tab

    Displays information about migration or replication status, pool, size, etc.

    Migrations properties Beefalo.jpg

    • Migration task: The name of the migration or replication task.
    • ID: Unique ID of the task.
    • Sesam day: Sesam day is a backup day you define according to your backup routines. Sesam day/backup day is defined by time set in the NEWDAY event. For details, see SEPuler: SEP sesam backup day.
    • Source pool: Media pool from which the data will be migrated or replicated, e.g., disk.
    • Source/target drive: The number of the source or target drive used by a job.
    • Start/Stop time: Recorded start and stop time of the migration or replication.
    • State: Displays the status of the migration or replication, e.g., Successful.
    • Size: Size of the saveset.
    • Target pool: Media pool to which the data will be migrated or replicated, e.g., tape.
    • Throughput: The average throughput of the entire check process.

    Other details show the client and task name, saveset ID, interface, backup state, etc.

    To display the status of a single copy job in a migration task the same dialog is used as for the normal migration task, but the displayed fields are slightly different.

    You can check the migration main log under the Main Log tab. The log of a migration copy job is a subset of Restores by State.


    Media actions

    Media actions provides an overview of all media actions, such as introduction in the SEP sesam environment, initialization, readability check, purge, etc., within the specified time frame. By default, all media actions of the last backup day are displayed. By using Filter, you can filter operations by date range and/or media action and status. Filter settings remain in effect even if you switch to another tab and are dismissed when the Media actions tab is closed.

    Information sign.png Note
    As of 4.4.3 Beefalo V2, you can check the details of your media actions online by using new Web UI. For details, see SEP sesam Web UI.

    The following media actions might be displayed:

    • Introduce (intro): A new medium is registered in the SEP sesam environment.
    • Initialize (init): A process that validates if a medium is available for backup. If a medium meets the requirements (e.g., its EOL has expired and it is not write-protected – locked), it can then be initialized, deleting all data contained on it and preparing it for use again.
    • Inventory: A process that scans media in the device and updates SEP sesam information about the media in the tape library.
    • Check (read check): A process that verifies the readability of the backup on tape media.
    • Purge: A data store related process. When the upper value for the used disk space on the data store – HWM is reached, a data store purge process is started for all EOL-free savesets. The oldest free savesets are deleted first.
    • Fsck: Is a file system consistency check on Unix, Linux, MacOS and FreeBSD.
    • Check space: A process that checks available space on the medium.

    There are also other media actions which might be displayed, e.g., Ballance, Remove, Write protect, Sync, etc.

    Media actions by state Beefalo.jpg

    With v. 4.4.3. Beefalo, SEP sesam provides additional View Mode button that enables you to switch between the table and tree view.

    • Tree view: SEP sesam default view shows the status of individual media action grouped together in a hierarchical view.
    • Table view: A simple flat view that shows the status of individual media action one after another.
    Information sign.png Note
    You can use a force refresh by clicking Shift and Refresh button to clear the GUI cache memory. In some cases clicking only the Refresh button won't show the updated view.

    Properties of the media actions

    You can view the details of each listed media action by double-clicking the desired action (or by selecting a table row and clicking the button Properties). Depending on the media action, the following tabs might be displayed.

    Info tab

    Media actions info Beefalo.jpg

    Depending on the media action, the following information might be displayed:

    • Action: The type of the media action, e.g., purge.
    • State: Current status of the performed action, e.g., OK, Error, Active ...
    • Label: (If relevant) A SEP sesam identifier of the medium.
    • Data store: The name of the data store.
    • Start/Stop time: Recorded start and stop time of the media action.
    • Message: Additional information about the operation's status.
    • ID: SEP sesam unique ID of the action.
    • Planned for: The scheduled start date and time of the media action.
    • Run: The total number of runs for the media action in question.
    • Prio: Priority of the media action.
    • Pool: Media pool that contains the medium.
    • Drive: The drive that added the medium.
    • Device: On physical drives, this is the device ID of the operating system. On virtual drives, this is the SEP sesam logical drive number.
    • Throughput: (If relevant) The average throughput of the operation.
    • Session ID: (If relevant) SEP sesam session ID.
    • Size: (If relevant) Number of the read 64 kByte blocks.
    Main Log tab

    The main log contains log entries for the respective media action. The messages shown in the log depend on media action.

    Media action main log Beefalo.jpg

    For example, the readability check protocol of a medium contains the following information:

    • When the readability check was executed.
    • On which device the medium was checked.
    • The SEP sesam label of the medium.
    • The last time the medium was initialized.
    • The read throughput every minute.
    • Information of the stored savesets on the medium.
    • Display all segment marks of the tape.
    • State of the readability check at the end of the protocol.
    Si3 State, HPE Catalyst Store State and HPE Cloud Bank Store State tabs

    Provide an overview of Si3 deduplication, HPE Catalyst store or HPE Cloud Bank store status. You can check the status of the processes, encryption status, saved storage space, etc.

    Media action Si3 Beefalo.jpg

    GUI: Monitoring

    Last backup state

    In this view you can check previously executed jobs with their last backup state. Furthermore, you can see jobs which have never been backed up. You can filter the results by date range, states, tasks and event types.

    As of 4.4.3 Beefalo V2, you can check the details of your jobs online by using new Web UI. For details, see SEP sesam Web UI.

    Last backup state Beefalo V2.jpg

    The last backup state window shows the last run of a backup event in order to find possible errors and fix them.

    Right-clicking on the successful backup opens the context menu that provides quick access to several functions (properties, immediate start, etc.). Note that the options for canceled or failed backup are slightly different from the options for a successful backup (shown in the screenshot below).

    Successful backups Beefalo V2.jpg


    Processes

    From Main Selection -> Monitoring -> Processes, you can check the status of SEP sesam processes on the SEP sesam Server.

    Information sign.png Note
    As of 4.4.3 Beefalo V2, you can also monitor your processes online by using new Web UI. For details, see SEP sesam Web UI.

    Monitoring processes Beefalo V2.jpg

    You can also use the command line to display all processes and daemons with the following command:

    sm_main status 	
    

    The following output appears:

    2020-01-25 13:11:07: sm_main[11897] started	
    2020-01-25 13:11:07: Arguments: sm_main status	
    2020-01-25 13:11:07: qm [ 19672]: online	
    2020-01-25 13:11:07: Found job: 1 db 1 19680 11:46 2019-12-27	
    2020-01-25 13:11:09: db [ 19680]: online	
    2020-01-25 13:11:09: Found job: 447 passd 1 7970 09:30 2020-01-25	
    2020-01-25 13:11:09: passd [ 7970]: online	
    2020-01-25 13:11:09: Found job: 448 sms 1 7979 09:30 2020-01-25	
    2020-01-25 13:11:09: sms [ 7979]: online	
    2020-01-25 13:11:09: Found job: 446 stpd 1 7961 09:30 2020-01-25	
    2020-01-25 13:11:09: stpd [ 7961]: online	
    2020-01-25 13:11:09: Found job: 5 ctrl 1 19808 11:46 2019-12-27	
    2020-01-25 13:11:09: ctrl [ 19808]: online	
    2020-01-25 13:11:09: Found job: 6 sepuler 1 19813 11:47 2019-12-27	
    2020-01-25 13:11:09: sepuler [ 19813]: online	
    2020-01-25 13:11:09: Found job: 329 rmi 1 13672 12:43 2020-01-18	
    2020-01-25 13:11:09: rmi [ 13672]: online	
    STATUS=SUCCESS MSG=All deamons online	
    

    For example, if the rmi demon is not available the following output would be displayed:

    2020-01-25 13:11:09: rmi [13672]: offline
    

    If a process/daemon is offline, it can be restarted by using the command line.

    Example for rmi:

    sm_main reload rmi
    


    Monitoring drives

    Monitoring drives shows the drive queue. By selecting all (*) or selecting the desired drive number from the drop-down list, and clicking the Refresh button, the information about the queue is displayed.

    A queue is managed by a queue manager (QM). SEPuler and some other internal processes send their tasks as jobs to the queue manager which coordinates the execution. The jobs are processed according to their priority. The required queues are created by SEP sesam during the configuration of drives.

    First, initialization of queues takes place. Then it is determined which job in a queue will first get access (submit) to a busy device. The job limit (channels) of the queue defines the amount of simultaneously running tasks. At the time a task is scheduled to run, it is placed in a queue and executed according to its priority. If the scheduled task cannot run because of the job limit of the queue, it is put in a pending state. For more details on priorities and what happens with pending tasks, see the SEPuler.

    Monitoring drives Beefalo V2.jpg

    GUI: Logging

    State

    SEP sesam creates a state log. One line is written for each backup in chronological order. This information is saved as files in <SESAM_VAR>/prot and can also be used for further processing (print, email).

    Information sign.png Note
    As of 4.4.3 Beefalo V2, you can also check your system logs online by using new Web UI. For details, see SEP sesam Web UI.

    State log Beefalo V2.jpg

    Options

    • From - To: The date selection allows filtering of the output. By clicking Refresh the updated view is displayed.
    • Information sign.png Note
      A backup day is defined by two Newday events. For details, see Newday Event.
    • Today, Yesterday: Shows logs from today or yesterday.
    • Help: Online help.
    • Send: Emails the log to your support service or any other predefined address.
    • Print: Prints the log by using the default printer.
    • Search: Enables searching for specific backups.


    Day log

    SEP sesam writes a continuous protocol for each backup day. All modules write messages with a time stamp attached to it. Each message contains a unique code consisting of message type (I=information, W=warning, E=error ), number and originating module.

    You can filter the day log by using date selection (the from and to date) and search. By clicking Refresh, the updated view is displayed immediately.

    Day log protocols are the first and most important starting point for problem analysis. You can find detailed help for problems and error messages in the Error Messages Guide. These errors and a PuTTy copy of the log file can be sent to SEP sesam support to provide detailed information on SEP sesam operations.

    Information sign.png Note
    As of 4.4.3 Beefalo V2, you can also check your system logs online by using new Web UI. For details, see SEP sesam Web UI.

    Day log Beefalo V2.jpg


    Error log

    The error log contains a record of critical errors that occurred during the backup day. It is a subset of the entire day log where only error messages are recorded.

    Information sign.png Note
    As of 4.4.3 Beefalo V2, you can also check your system logs online by using new Web UI. For details, see SEP sesam Web UI.

    You can filter the error log by using date selection (the from and to date) and search. By clicking Refresh, the updated view is displayed immediately. You can send the log to SEP sesam support to provide detailed information on failures.

    Error log Beefalo V2.jpg


    SEP sesam interface logs

    From Main Selection -> Interfaces, you can check the log information of the SEP sesam Server interfaces (sm_alarm, sm_disaster and sm_notify).

    SEP Tip.png Tip
    As of 4.4.3 Beefalo V2, you can also check your system logs online by using new Web UI. For details, see SEP sesam Web UI.

    You can filter the selected interface by using date selection (the from and to date) and search. By clicking Refresh, the updated view is displayed immediately. The logs can be printed or sent by email.

    Interfaces Beefalo V2.jpg

    SEP Tip.png Tip
    It is recommended that you configure the interfaces (Alarm, Disaster and/or Notify) to automate sending email reports of errors and license violations, log files, and to help carry out the disaster recovery process in case of a SEP sesam Server breakdown. For details, see Configuring interfaces.


    GUI: Toolbar

    The toolbar enables you to trigger the tasks and get the status overview with just one click. It contains the following icons:

    • GUI dashboard icon Beefalo.jpg Dashboard allows you to handily check SEP sesam operations and their status, and provides key metrics about your backup environment.
    • GUI immediate start backup icon Beefalo.jpg Immediate Start: Backup displays the backup dialog where you can select a task including all other parameters and start the backup immediately.
    • GUI restore assistant Beefalo.jpg Restore Assistant opens the online restore assistant in the external web browser.
    • GUI restore wizard icon Beefalo.jpg Restore Wizard opens the wizard that enables you to start the restore immediately.
    • GUI backup by state option Beefalo.jpg Backups displays the list of all performed backups and their status.
    • GUI calendar sheet icon Beefalo.jpg Calendar Sheet displays an overview of all scheduled, completed and expired events with their current status.
    • GUI about SEP sesam icon Beefalo.jpg About SEP sesam displays the SEP sesam version information.

    By activating the option Docking Mode (Menu bar -> Window -> Manage layouts), this toolbar can be moved freely and can also be detached from the main window.


    GUI: Menu

    File

    From the menu bar -> File, you can update SEP sesam GUI and import or export the SEP sesam database.


    File Beefalo V2.jpg

    GUI Update
    Get the latest GUI version from SEP sesam Server if the current version is out of date.
    Import SEP sesam Database
    Replace the current SEP sesam database. You can import the SEP sesam bootstrap database file which was attached in the email sent by the disaster interface. For details on how to prepare for SEP sesam Server self-recovery, see SEP sesam Server Disaster Recovery.
    Export SEP sesam Database
    Execute export of the entire SEP sesam database. In addition to the recommended periodical export of the SEP sesam database, performed as part of the SEP sesam self-backup, you can manually export the SEP sesam database.
    Exit
    Close all open windows. Running processes, such as backup and restore, are not affected.



    GUI configuration options

    You can access the configuration options from the menu bar -> Configuration. Configuration provides different settings and parameters that define SEP sesam look and feel as well as its behavior. The following functions are available by selecting the Configuration option in the menu bar.

    Configuration overview Beefalo.jpg

    Defaults

    The options in the Defaults window allow you to change UI mode, customize GUI font and tables, set the preferred date format, retention periods for logs and restore tasks, define advanced settings (Extras), configure default permissions, and add or modify SEP sesam keys in the global settings.

    General tab

    • Common (available in ≥ SEP sesam 4.4.3 Beefalo V2):
      • Show SEP sesam web client landing page on startup: By default, SEP sesam Web UI landing page is opened when the GUI is started. Deselect the check box to prevent it from opening automatically when starting SEP sesam GUI.
      • Use HTTPS for opening links in the external browser: By default, SEP sesam GUI opens the external links by using the HTTP protocol. By selecting the check box, you can enforce the usage of HTTPS protocol for external links. In this case, you have to accept the Sesam REST server security certificate.
    • UI Mode: You can select the appropriate UI mode: simple or advanced. (The former advanced GUI mode is now replaced by simple mode, while the former expert mode is replaced by advanced mode.) The appearance of the user interface does not change depending on the mode, but simple mode hides complex features and shows the user only a basic subset of options. Advanced mode provides all the features of SEP sesam, such as expert restore options, log level setting, etc. For details, see Selecting UI mode.
    • Restore Settings: You can select the Restore mode – restore interfaces that are available for restore and displayed in the context menu and toolbar (as of ≥ 5.0.0 Jaglion V2). It is recommended to use the web-based Restore Assistant instead of the Legacy restore (deprecated) option, which refers to the GUI restore wizard. Compared to the GUI restore wizard, the online Restore Assistant provides some additional advanced restore options and allows you to restore your data from anywhere with the appropriate permissions. You can also keep both interfaces available by selecting Display both possibilities.
    • Filter panels: You can select that filters are displayed/visible the whole time by enabling the option Show filter panels by default.
    • Help: The field Link to WEB help file sets the path to the SEP sesam Wiki main page, thus providing the latest updated version of help topics online. Use the Test It button to check the access to help files.

    GUI Defaults-General-rts-mode JaglionV2.jpg

    Fonts and Tables tab

    You can customize your SEP sesam GUI appearance by changing:

      Font: The predefined GUI font is plain. You can select Choose button to change the default font, font style and/or size.
      SEP Tip.png Tip
      You can reset GUI font settings to SEP sesam default at any time by using the Reset to Default button.
    • Font used in tables and trees: You can change the default font (proportional) to non-proportional (monospaced).
    • Table Striping: You can change the appearance of GUI tables by selecting one of the zebra striping tables from the drop-down list.
    • Date range (available in ≥ SEP sesam 4.4.3 Beefalo V2): You can set the date range for the displayed data by specifying the Maximum number of days for which the SEP sesam GUI will show the data. By default, it is set to -1 = unlimited.

    Defaults fonts Beefalo V2.jpg

    Display Format tab

    Under the tab Display Format, you can change the default setting for the date format as well as default setting for data size units. The data size can be specified either with decimal (KB, MB, GB, TB) or binary prefix (KiB, MiB, GiB, TiB, etc.). For details, see Changing data size units.

    Defaults display format Beefalo.jpg

    Install/Update tab

    The tab Install/Update allows you to set the desired Update mode. By default, SEP sesam does not check, download and install updates. An icon (yellow ) notifying the user that an update is available is shown for the respective client and a popup notification on hover suggests that there is a new version available.

    Depending on SEP sesam version (Beefalo V1 or v. ≥ Beefalo V2), the following options are available:

    • Turn off (hide from all users) (available in ≥ Beefalo V2): If selected, the install and update feature is not shown in the GUI. No install/update options are visible for any of the users, not even the administrator until this mode is switched on.
    • Do not check or install automatically (default) (in Beefalo V1: Do not download or install any updates): If selected, updates are not checked, downloaded nor installed when a new version is available.
    • Check automatically, but install manually (in Beefalo V1: Download updates automatically, but install manually): If selected, updates are checked by using index.txt from SEP Download Center to get the list of all available packages, but you have to download and install them manually.
    • Check, download and install automatically (in Beefalo V1: Download and install updates automatically): If selected, updates are automatically checked, downloaded and installed, based on SEP sesam NEWDAY, when a new version is available in the SEP Download Center. This option may not be recommended depending on the configuration of your SEP sesam environment and its activity.

    You can also update your SEP sesam Clients by using a SEP sesam custom package source which may be stored locally, on the network drive, or is available at specified URL. The advantage of using a custom package is that you have full control over the version that is getting installed. For details, see Using custom SEP sesam package source.

    Defaults install BeefaloV2.jpg

    Retention Periods tab

    You can set up the retention period in days for SEP sesam logs, readability check logs, calendar sheet entries and restore tasks. The retention period is the time period for which the SEP sesam retaines specified data. Once the retention period expires, the data is removed from the database and is no longer available. Click the arrows to increase or decrease the predefined retention time per file.

    • SEP sesam logs: The default value for preserving the SEP sesam log files is 7 days.
    • Readability check logs: The default value for preserving the readability check log files is 2190 days.
    • Calendar sheet entries: The default retention time for old calendar sheet entries is 35 days.
    • Restore tasks: The default retention time for old restore tasks is 7 days.

    Defaults retention periods Beefalo.jpg

    Extras tab

    Under the Extras tab, the following settings can be activated:

    • Switch off the scrolling for warning "30 days remaining for maintenance authorization": You can switch off the scrolling for notification about the pending expiration of updates. If there is no update permission, the notification never appears. After installing update, this option is reset.
    • Provide selection of "broken backups" in the restore wizard: If this option is checked, you are allowed to perform a restore from incomplete, broken, or interrupted backups. By default, this selection is not provided.
    • Number of trace log lines to display: The default value for trace log lines is 60. Click the arrows to increase or decrease the number of lines.
    • RSS notification polling interval: The default polling interval for RSS notification is 720 minutes. Click the arrows to increase or decrease the polling interval.
    • Compress LIS files: By default, the LIS files are compressed after 14 days. You can change the number of days after which the LIS files are compressed or deactivate the checkbox to prevent compression of LIS files.
    • Globally activate Changed Block Tracking (CBT): By default, the CBT is enabled to provide change tracking thus saving disk space with optimized block level incremental and differential backups of VMDKs. Note that disabling CBT globally will affect your backup performance and use more disk space. For more details, see Changed Block Tracking (CBT).
    • Log Download: In SEP sesam ≥ 4.4.3 Beefalo V2, you can set the maximum size of the log files archive. The default is 25 MiB (0 = unlimited).
    • Task name template: You can configure your own template to define the desired syntax of the backup task name. The backup task name is then generated automatically according to the new template whenever you create a new backup task. The template applies to all backup task types, except in the case that a different template has been entered directly into the SEP sesam database to be applied to the specific task type. For more details on template usage, see Task Name Template – Backup.

    Defaults extras Beefalo V2.jpg

    Permissions tab

    You can configure the default permissons (ACLs) for all top level locations by simply selecting or adding the relevant user or group (ADMIN, OPERATOR, BACKUP or RESTORE), and enabling or disabling access (to locations) per user/group. For details on how to configure ACLs for a specific location or client, see Using Access Control Lists.

    Defaults permissions Jaglion.jpg

    Settings tab

    The Settings tab displays an overview of all internal GUI settings. You can insert or modify the keys, for example, to set up customized retention policy. For details, see Customizing retention policy.

    Defaults settings Beefalo.jpg

    Media types

    Media Types window lists all media types defined in SEP sesam. Entries in black font are the media types currently used. They were set up in the database at the installation of SEP sesam and – contrary to the user defined media types (green font) – cannot be erased nor changed.

    • Media Type: Shows SEP sesam internal identification of the media type.
    • Drive Type: Shows SEP sesam internal drive types.
    • Capacity: Presents storage capacity of allowed media and drive combination. This combination determines which media can be inserted into which drives.

    Media types Beefalo.jpg

    Command

    You can create and define your own commands to be used for various tasks within SEP sesam environment.

    When configuring a new command, you have to define the following:

    • Name: Enter the name for a new command.
    • Client: Select a client, on which the command will be executed.
    • User: Enter a user name of the user with sufficient access to execute the command on the client.
    • Command: Enter the complete command (and parameters, if required), e.g., eventlog.ps1.

    Configuration commands Beefalo.jpg

    Information sign.png Note
    When defining your own commands, some security considerations apply and are explained in Access restriction of command events.

    Remote server (Master GUI only)

    This option is used for the server administration of the Master GUI. It is possible to both configure or remove SEP sesam Servers or add new servers to the backup tree (menu bar -> Configuration -> Remote Server).

    Information sign.png Note
    The Remote Server option is only available in the SEP sesam Master GUI.
    • Server Name: The name of the SEP sesam Server in the network.
    • Connection: Shows if the Server is connected to the network (green = ON, red = broken, gray = OFF).
    • GUI Build: Displays the GUI version.
    • Operating System: OS of the SEP sesam Server.

    Master GUI remote server Beefalo V2.jpg

    The Master GUI allows the administrator to control all SEP sesam Servers in the SEP sesam environment.

    When adding a new server to the SEP sesam Master GUI, the following parameters must be set.

    • Server name: Enter the name of the SEP sesam remote Server that you want to administer by using the master GUI.
    • Connection: You can set the connection to the server (ON or OFF).
    • Port: Define the port number for the client-server connection.
    • Note: Optionally, you can add a comment.

    Master GUI new remote server Beefalo V2.jpg

    User Permissions

    The User Permissions item is only visible if policy-based authentication is activated (default). For details, see Configuring Policy-Based Authentication.

    User permissions Beefalo.jpg

    In the User Permissions you can configure the user authorization. Options are admin (the only user role with full control over the SEP sesam), operator (monitors the SEP sesam Server backup status), backup (only allowed to start backups) and restore (only allowed to start restores). The assignment of permissions is user- and client-specific. If a non-authorized user or non-authorized client tries to create a GUI connection, it is rejected.

    New users permission Beefalo.jpg

    Note 1:

    If the name resolution for the selected client is not complete (IP name and reverse lookup of the IP address), the connection is also rejected!

    Note 2: Alternatively the SEP sesam program sm_setup can be utilized to assign user permissions:

    • Adding a user permission:
    • sm_setup allow_gui -u *|<user> -c *|<client> -m admin|operator|restore
      
    • Removing a user permission:
    • sm_setup disallow_gui -u *|<user> [-c *|<client>] [-m *|admin|operator|restore]
      
    • View permissions of users or clients:
    • sm_setup get_policy [-m user|client]
      

    Permission Management

    Introduced in v. 4.4.3, SEP sesam provides different authentication methods that are mutually exclusive. For details, see About Authentication and Authorization.

    Depending on which authentication mode is active, one of the following options is shown:

    • Policy-based authentication is enabled by default. You can switch to database-based authentication by using the Activate Authentication button in the Permission Management window. If you choose not to activate the database-based authentication, policy-based authentication stays enabled. Policy-based authentication is configured in User Permissions (see previous menu option). For details, see Configuring Policy-Based Authentication.
    • When you turn on database-based authentication by using the Activate Authentication button, upon the restart of a GUI and SEP sesam client, you can use any of the 5 available tabs: Users, Groups, External Groups, Sources and Activation. You can create users, modify their settings, such as adding a user to the group or removing it from the group, delete users, create external groups and add the authentication sources for the LDAP/AD authentication. You can also deactivate the database-based authentication. For details on LDAP/AD authentication, see Configuring LDAP/AD Authentication.
    • Authentication permission management Beefalo.jpg

    Email Settings

    The email settings allow to configure the email accounts that can be used for sending emails from the SEP sesam interface or from the command line. The default email account is sesam.

    Configuration email Beefalo.jpg

    By clicking New, the Email Account window opens:

    Email account Beefalo.jpg

    • Account: Name of the account (mandatory)
    • Customer: Name of the customer
    • Sender: Email address of the sender
    • SMTP server: Name or IP address of the outgoing mail server
    • SMTP user: User name for SMTP server
    • Password: Password for the mail server. Password is mandatory if SMTP server requires authentication.
    • SMTP port: Optionally, specify the SMTP port.
    • Recipient: Email address of the recipient
    • CC: Email address for copy of the email
    • BCC: Email address for hidden copy of the email
    • SSL: Optionally, you can select to connect securely via SSL or TLS.

    If no SMTP user name is specified, it is assumed that no authorization is required at the SMTP server.

    Interfaces

    User interfaces are configurable programs, intended for system administrators that can use them to create their own commands. They can be used to perform additional actions, such as exporting a database, restarting a database, and sending emails. The following interfaces are available: pre (sbc_pre), post (sbc_post), alarm (sm_alarm), disaster (sm_disaster) and notify (sm_notify). The pre/post-interface might affect backup execution; when creating a script, have in mind that any pre/post script should not take a long time to complete as it can delay the backup.

    Interfaces pre Beefalo.jpg

    User interfaces can be programmed using any text editor. To use an interface, you have to activate it first and create your own commands. From the Interfaces menu, select the interface you want to activate; if you are configuring a pre/post interface, you have to select a client too since these two interfaces are created for each client individually and are only executed on the selected client. The interface script window opens, allowing you to configure the desired action. Once done, click Save to activate the interface. The interface is saved to the <SESAM_ROOT>/bin/sesam directory. For details, see Using Pre and Post Scripts.

    Alternatively, you can activate the user interfaces by using the templates that are available in the SEP sesam directory <SESAM_ROOT>/skel/templates. To activate an interface, you have to copy its corresponding template file to the directory <SESAM_ROOT>/bin/sesam. The templates are only active and executed on the client.

    If the email configuration is set, SEP sesam interfaces send messages by email. The default email account is sesam. For details, see How to configure Mail Notification.

    SEP sesam allows the use of Pre-, Post-, Alarm-, Notify-, and Disaster interfaces to be combined into scripts.

    Interfaces pre edit Beefalo.jpg

    PRE interface

    Before a backup starts, an administrator can specify special actions to be executed before and during the backup activity. For example, the system can generate messages to quickly notify the administrator of either backup job success or failure. Pre-interface can be used to create commands that will stop or start the selected programs; for example, it may be used to stop the database before it is backed up.

    POST interface

    Once the backup is finished, some special actions may be required (e.g., notifications/messages, program end/start, restart databases etc.). These actions can be programmed by using the post-interface.

    Alarm interface

    The SEP sesam system needs no special administration during normal operation once SEP sesam Clients are set up and backup tasks are scheduled (except for the restore). If any functional errors occur, e.g., failure of a certain backup, this event is automatically passed on to the alarm interface. This interface is programmable to filter desired messages and their transmission to the authorized person.

    If a license violation has occurred and the alarm interface is activated, an email with the license violation information is sent to the SEP sesam account. The license violations occur when you exceed the conditions set in your license, such as the maximum volume size, the maximum number of configured clients, not licensed backup task types (e.g., BSR), etc. The 16th day upon receiving the violation alarm SEP sesam backups are temporarily stopped until the issue is fixed, while the restores are still available. To avoid license violations, review your license; go to SEP sesam GUI -> Help -> License info. For details, see License administration.

    Information sign.png Note
    • Do not use commands which require input from the user, such as OK buttons. Commands that require user interaction may cause interruption of backups during the night.
    Notify interface

    Similarly, there is a procedure for successful backups and restores which uses the sm_notify. This can be programmed as needed.

    Disaster interface

    The term disaster refers to a catastrophic failure or complete destruction of the SEP sesam Server and its data. The SEP sesam disaster interface must be properly configured to help carry out the disaster recovery process. To prepare for a possible breakdown of the SEP sesam Server, a self-backup of the SEP sesam installation must be performed. For details on how to prepare, see SEP sesam Server Disaster Recovery.

    The disaster interface sends an email describing the recovery procedure in the event of disaster and an attachment containing the SEP sesam bootstrap database with all essential data for the disaster recovery. The sm_disaster file is located in:

    • Linux: <SESAM_BIN>/skel/templates/sm_disaster
    • Windows: <SESAM_BIN>/skel/templates/sm_disaster.ps1

    As an alternative to using Interfaces in the GUI, the disaster interface file can also be copied to SESAM_BIN>/bin/sesam/sm_disaster and modified according to the needs of each environment. For details, see SEP sesam Server Disaster Recovery.


    Window

    The SEP sesam GUI can be rearranged almost without limitation. From the menu bar -> Window, you can show or hide different panels or windows and manage GUI layout.

    Window Beefalo V2.jpg

    By selecting Manage Layouts option, you can save and manage layouts.

    To manage the layout, you have to open and arrange all windows and settings to your liking. Once you are satisfied, give the layout a name and save it. The layout identified with a green arrow is the current (new) layout. By clicking Set as Standard the selected layout will become the default layout (black check mark) and will be loaded automatically for the current user the next time the GUI is started.

    The layout comprises the following settings:

    • Windows and frames: Windows that are open and the position of the windows and frames.
    • Current messages: Default settings, such as refresh interval, automatic refresh of the view (cyclic view on/off) and the selection of the displayed drives.
    • Object selection: Expanding the tree selection.
    • Toolbars: The arrangement and look of the toolbar, e.g., buttons with or without a label.

    Window manage layout Beefalo V2.jpg


    SEP sesam Help

    The Help menu provides access to help topics online, email and link to SEP support, license information with an option to import new license, subscription to RSS feeds, and displays information about SEP sesam version.

    Help Beefalo V2.jpg

    Online manual

    If a client is connected to the internet and has a web browser installed, clicking Online Manual opens the SEP sesam Wiki main page with the latest updated version of help topics online.

    Contact support

    Clicking Email opens a preset email with the email address of already loaded support. Email form provides the Attachment function, allowing you to attach log files to your emails directly from your SEP sesam Client.

    To enable sending email with SEP sesam, you need to configure a valid email account (menu bar -> Configuration -> Email Settings). For details, see How to configure Mail Notification.

    Help mail Beefalo V2.jpg

    Clicking the button Attachment provides the list of log files for your SEP sesam Client. Select the relevant files and attach them to email when contacting support.

    Help attachment Beefalo V2.jpg

    From the Directory drop-down list you can choose the needed directories from the SEP sesam Server. The log files are sorted chronologically in ascending order. The meanings of the tokens are described in the table below. All tokens start with the prefix gv_rw_ and all directories are under <SESAM_VAR>.

    Token Directory Token Directory
    db ./db glbv ./glbv
    info ./work/info lgc ./log/lgc
    lis ./lis not ./not
    qm ./qm prepost ./prepost
    prot ./prot sms ./log/sms
    smslis ./work/smslis stpd ./log/sms
    sbc ./log/sbc sbc_log ./log/sbc
    sbc_times ./times tmp ./tmp
    work ./work sel ./sel
    ini ./ini

    Clicking SEP Remote Support opens SEP online remote support page.

    License information

    Under License Info the local name of the computer and the TCP/IP address are shown as determined by the licensing module. This information is used to build a SEP sesam license.

    You can also check the expiration date and upgrade validity of your license. Displayed are all licensed components which are currently in use.

    To import a license, click the button Import New License. A new window opens prompting you to paste a valid license file sm_lic.ini from clipboard or by using the file manager to browse and select the required license as .ini or .zip file. After you pasted your license, click Apply to enable it.

    Help license info Beefalo V2.jpg

    SEP sesam version information

    About SEP sesam shows the core build and version numbers, i.e., the GUI client, the GUI server and SEP sesam kernel.

    About SEP sesam Beefalo V2.jpg

    Part IV: Web interface

    Restore Assistant

    There are two ways to restore your data in SEP sesam: by using GUI restore or through the web interface Restore Assistant. Even though most of the options are the same in both restore interfaces, the web Restore Assistant interface is designed to be more intuitive, offers additional advanced options, and makes it easy to restore your data.

    You can use the web Restore Assistant to restore data from regular Path backups, NDMP and NSS file system Path backups, emails from Kopano backups, and virtual machines (Hyper-V, KVM/QEMU, OpenNebula, VMware vSphere, Citrix Hypervisor (XenServer), and Red Hat Virtualization (RHV)) to which you have been granted access.

    Authentication required

    Only authenticated users that have been granted the appropriate permissions are able to access the Restore Assistant and restore their data. These permissions are defined according to the user type. For details, see Configuring Database-Based Authentication.

    Restoring encrypted backups

    You can also perform an online restore of data from encrypted backups that are protected with a password. When restoring encrypted data with a password stored in the SEP sesam database, the password is automatically used for decryption during restore. However, if a password is not stored by SEP sesam, you will be prompted to enter it online. In the latter case, if you do not know the password, you won't be able to restore an encrypted backup and it will remain locked.

    Basic and advanced web restore

    With 4.4.3. Beefalo V2, the restore assistant provides basic and advanced features for online restore. Switching between the basic and advanced mode is available via Settings menu (-> UI mode), see Setting UI mode.

    Restore features

    Restore Assistant provides the following features:

    • As of 4.4.3. Beefalo V2, along with restoring data from regular Path backups, NDMP and NSS file system Path backups, emails from Kopano backups, and virtual machines you can now also restore KVM/QEMU VMs.
    • The newly introduced VMware Sandbox restore feature allows you to use a copy of the production environment for troubleshooting, testing and to verify the integrity of the VMs. For details, see VMware Sandbox Restore.
    • You can restore your data to the original or alternative location.
    • The flexibility to switch between basic and advanced restore mode allows more experienced users to fine-tune their restore.

    Accessing Restore Assistant

    You can access the Restore Assistant from the SEP sesam GUI (Activities -> Restore Assistant), from SEP sesam Web UI (left menu -> Restore Assistant) or by entering the following in the browser address bar:

    http://[sesamserver]:11401/sep/ui/restore/

    Information sign.png Note
    If you cannot access the online Restore Assistant, check if you have been granted the appropriate permissions for online restore. For details, see About Authentication and Authorization.

    Setting UI mode

    As of ≥ 4.4.3 Beefalo V2, you can set your preferred UI mode by clicking the Settings icon located in the upper right corner and selecting Basic or Advanced UI mode. The basic restore mode is enabled by default.

    The Settings menu also allows you to change the display language (German or English).

    Restore assistant icons.jpg

    SEP Tip.png Tip
    The Monitoring, Dashboard, Help and Account icons (located in the upper right corner) enable you to quickly check the status of all restore jobs (Monitoring -> Restores), access SEP sesam Dashboard and online help, and log in/log out from the Restore Assistant.

    Online restore in basic UI mode

    The basic restore options cover the most frequent restore cases and are the recommended method of performing a restore. The basic restore procedure involves selecting the savesets which you want to restore, the restore target, etc., and provides the step by step restore wizard depending on the type of data you want to restore.

    Two different procedures can be used for restore according to the data type:

    Restoring files, directories and emails

    1. Open the Restore Assistant in the browser.
    2. From the Start window, select the restore type: Restore files and directories or Groupware Applications -> Restore Kopano Mail. Click Next.
    3. Restore assistant restore type Beefalo.jpg

    4. In the Source window, select your client. You can filter the clients by name, location or operating system. Click Next.
    5. Restore assistant source.jpg

    6. In the Backup window, under the Task selection select your backup task. A backup task defines the source data which was backed up from the client.
    7. Restore assistant select task Beefalo.jpg

    8. Then under the Backup selection select the exact backup version you want to restore. You can use the calendar function found in the upper right corner to filter a date range for the displayed backups. Click Next.
    9. SEP Tip.png Tip
      You can search for a file or a directory by entering your search term in the Search for files or directories in all backups.

      Restore assistant select bck Beefalo.jpg

    10. In the Files window, select the files, directories or emails you want to restore. Click Next.
    11. Restore assistant select file Beefalo.jpg

    12. The options in the Target window differ slightly depending on whether you want to restore from path or mail backups.
    13. Restore from path backups

      1. Check the target client for restore.
      2. Restore assistant select target Beefalo.jpg

      3. The option Restore to original target path is enabled by default. Skip this option to restore the files to the original location. Deselect it if you want to restore your data to a new restore target and specify the new target path; you can enter or browse the path where you want to restore your data.
      4. Restore assistant target directory Beefalo.jpg

      5. Under the Execution options you can set additional restore options:
      6. Do not restore existing items: Files will be restored only if they are not already present on the target system.
        Create new version: Restore files under a new name.
        Overwrite existing items: If the data exists on the target server, it will be replaced by the restored version.

      7. Decide how you want your data to be restored (maintain the original tree structure or flat):
      8. Keep original tree structure: When restoring to original location, the option Keep original tree structure is selected by default. The directory structure of the restored files is the same as the original directory structure of the backed up data.
        Restore all items flat in selected target directory: The backup is simply restored to a file without recreating the directory structure.
        Click Next.
        Restore assistant execution options Beefalo.jpg

      9. In the Finish window, review your restore task (restore type, client, backup level, restore options) and click Start restore.
      10. Restore assistant finish Beefalo.jpg

      Kopano mail restore

      1. Check the target client for restore.
      2. Restore assistant select target Kopano Beefalo.jpg

      3. Under the Target mail folder and user, enter a new mail user (the option Change user to ) and/or folder (Change folder to option) if you want to restore mail(s) to a different user mailbox or folder. Skip this step to restore the mails to the original location (default).
      4. Restore assistant new target Kopano Beefalo.jpg

      5. Under the Execution options you can set additional restore options:
      6. Do not restore existing folders and mails: Folders and mails will be restored only if they are not already present on the target system.
        Overwrite existing folders and mails: If the data exists on the target server, it will be replaced by the restored version.
        Click Next.
        Restore assistant execution options Kopano.jpg

    14. In the Finish window, review your restore task (restore type, client, backup level, restore options) and click Start restore.

    For additional restore options in the advanced UI mode, see Restoring files, directories and emails in advanced UI mode.

    Restoring virtual machines

    When you choose to restore a virtual machine (VM), you can select from a list of VM types what you want to restore. The basic restore procedure is almost the same for all VM types, except that some additional options are available for some VM types. The procedure differs slightly for the VMware instant recovery and VMware sandbox restore. For details, see VMware Sandbox Restore and VMware Instant Recovery.

    1. Open the Restore Assistant in the browser.
    2. In the Start window, select your target restore type: VMware vSphere, Microsoft Hyper-V, Citrix Hypervisor, KVM/QEMU, Proxmox VE, Red Hat Virtualization (RHV), or OpenNebula. Click Next.
    3. Restore assistant VM restore type Beefalo.jpg

    4. In the Source window, under Selection of the server select your target server.
    5. Restore assistant select server.jpg

    6. Then, under Selection of the virtual machine select the VM you want to restore.
    7. Click Next.
      Restore assistant select VM.jpg

    8. In the Backup window, under the Task selection select your source task. A backup task defines the source data which was backed up from the client.
    9. Restore assistant select VM task.jpg

    10. Then under the Backup selection select the exact backup version you want to restore. You can use the calendar function found in the upper right corner to filter a date range for the displayed backups. Click Next.
    11. Restore assistant select VM backup.jpg

    12. In the Backup window, under the Virtual machine from backup review, check or uncheck the target saveset you want to restore.
    13. Click Next.
      Restore assistant select VM saveset.jpg

    14. In the Target window, under the Target selection select your target environment for restore. You can use the drop-down list to select or filter VMs by name.
    15. Restore assistant select VM target.jpg

    16. Set additional restore options under the Execution options:
    17. Do not restore an existing virtual machine: VM will be restored only if it is not already present on the target system.
      Restore an existing virtual machine with a new name: VM will be restored under a new name. In case of Proxmox and OpenNebula restore the target VM name will be automatically created.
      Overwrite an existing virtual machine: If the VM exists on the target server, it will be replaced by the restored version. You can also select to shut down the running VM automatically.
      Click Next.
      Restore assistant VM execution options.jpg

    18. In the Options window, select the data mover and then under the Recovery options select if you want to start VM after restore or not.
    19. Restore assistant recovery options Beefalo V2.jpg

      Information sign.png Note
      As of v. 4.4.3 Beefalo V2, in case of VMware restore you can also select the desired transport mode from the list of available transport modes (HOTADD, SAN, NBD, or NBDSSL); click the displayed transport mode and rearrange the modes according to your preferences.
    20. Click the option Target options of the virtual machine to set additional target options, e.g., target server, data store, network interface(s), folder, and Resource pool/vApp.
    21. Click Next.
      Restore assistant target VM options.jpg

    22. In the last step, review your restore task and click Start restore.

    There are some additional restore options available in the advanced UI mode, see Restoring VMs in advanced UI mode.

    Online restore in advanced UI mode

    For more experienced users, some additional restore options are available in the advanced UI mode (v. ≥ Beefalo V2). For example, in the Start window you can restore backups and VMs to the file system or write your backups and VMs into dump files. If you are restoring VMs, you can select among more specific VM restore types.

    Restore assistant advanced start.jpg

    As with the basic options, the advanced options also differ depending on the type of restore:

    Restoring files, directories and emails in advanced UI mode

    The following additional restore options are available when restoring files, directories or emails in the advanced UI mode:

    • In the Start window, you can restore backups to the file system or write backups into dump files. Although the restore procedure in such cases is similar, some options may not be available (e.g., the Source windows).
    • If you want to write your backups into dump files, you have to specify a restore target path in the Target window (by browsing or entering the path). Optionally, you can modify a name of the dump file. If the dump file name is not specified, it will be generated automatically.

      Restore assistant dump file.jpg

    • In the Backup window, you can select whether you want to perform a Generation, Selective or Complete restore.
    • Restore assistant select bck Beefalo V2.jpg

    • In the Options window (step 5 in the advanced mode of the restore dialog) you can set the following options:
    • Under the Optional data source selection, you can set your preferred media pool, drive, used media|barcode, and interface from the drop-down lists.

      Advanced options optional data.jpg
      Under the Advanced restore options, you can further fine-tune your restore:

      • Use the Include/Exclude Filter tab to specify which files or directories you want to include or exclude from restoring, e.g., enter *.docx to the relevant filter to include or exclude all MS Word *.docx files from restore.
      • Advanced options filter.jpg

      • Use the EOL, Generation, Pre/Post tab if you want to specify the EOL parameter for restore (how long (in days) the restore task will be kept), enable/disable a generation restore, and specify whether any pre- or post script should be applied for the restore task, see Pre/Post options.
      • Advanced options EOL.jpg

      • Use the Log, Special Options tab to change the log level for your particular restore, see Setting Log Level. You can specify additional commands for restore, which can be helpful for special options of the sbc command. For details on commands, see SBC CLI.
      • Advanced options log.jpg

    Restoring virtual machines in advanced UI mode

    If you turn on the advanced UI mode, you can set additional restore options. It is recommended that the advanced mode is only used by expert users as the basic options are sufficient to address most restore use cases. The following additional options are provided by using the Advanced UI mode.

    • In the Start window, you can restore virtual machines to a file system, or write virtual machines into dump files:
      • If you want to restore VMs to a file system, the restore procedure is the same as the restore procedure for files, directories and emails, as described in the above section Restoring files, directories and emails. You only have to select a server and VM as a source instead of a client.
      • If you want to write VMs into dump files, the procedure differs from the usual VM restore only in that you have to specify a restore target path in the Target window and optionally modify a name of the dump file (see the related section above).
    • In the Options window, you can modify the Recovery options: By clicking the Edit button (located in the upper right corner), you can activate/deactivate different recovery actions: conf, remove, start, etc., and perform VM-related checks: VM power state, VM guest tools state and VM network IP address.
    • VMs recovery options.jpg
      To add your custom action or your custom check, select the template from the Actions or Checks drop-down lists or enter your action/check commands manually. To activate your custom action/check, click Save. You can simply remove any action/check by clicking the recycle bin icon.

      VMs recovery options modify.jpg

    • Under the Optional data source selection, you can select your preferred media pool, drive, used media|barcode, and interface from the drop-down lists.
    • Advanced options optional data.jpg

    • An additional set of options is available under the Options for restore: You can specify the EOL parameter for restore (how long (in days) the restore task will be kept), enable/disable a generation restore, and decide whether any pre- or post script should be applied for the restore task, see Pre/Post options.
      In case of a VMware restore, you can also set the transport hierarchy (if you have not modified the transport mode before under the Virtualization restore options); for details, see Selecting the best VMware transport mode for your environment.
    • VMs restore options.jpg

    You can view the status of your restore jobs by using SEP sesam Web UI (Monitoring -> Restores) or SEP sesam GUI (Main Selection -> Job State -> Restores). For details, see Monitoring and Reporting.


    Part V: SEP sesam Events

    Creating a Backup Event

    By creating a backup event, you select the backup level, set event priority and specify where to back up your data to. You can create an event for a specific task or for a task group. The latter enables you to trigger all the tasks in the task group with a single event.

    1. From Main Selection -> Scheduling -> Schedules, right-click the schedule for which you want to create a new event then click New Backup Event.
    2. Schedule-bck event.jpg

    3. Under the Sequence control, set up the Priority of your backup event. SEPuler always executes the schedules with the highest priority first. The default priority level is 1, which is the lowest priority (the highest priority is 99). The only exception are schedules with priority 0, which override all other priorities and are always executed. For details, see Setting Event Priorities. You can also enable Blocking date. This option should be used together with high priority for special events. If checked, events of the same type but of a lower priority will be blocked, ensuring that the backup will be processed even if other backups are scheduled for the same time.
    4. Under the Object, select the task or task group to which you want to link this event. In our example, you would link the newly created event to the task diagnostix_C.
    5. Under the Parameter, specify the Backup level.
      A FULL backup always copies all data specified by the backup task, regardless of whether it has been changed or not. A saveset created as FULL is the basic saveset for subsequent DIFF or INC savesets. While the backup time of a full backup can be significant, restore is fast and simple since only one backup saveset is required. Information about the backup status is stored in the SEP sesam database. Note that the archive bits are not deleted on Windows systems. If you want to force-reset of the archive bits, you can enter the command -o clear_archive in the backup options.
      A DIFF (differential) backup saves only data which was created or changed after the last FULL saveset had been created (of the same task). A differential backup is faster than a full backup, however, to restore the whole data source, first the saveset of the full backup has to be restored followed by restore of the DIFF saveset. For this, SEP sesam provides generation restore that enables browsing for and selecting for restore all generations of backed up files since the last full backup.
      An INC (incremental) backup saves only data which was created or changed after the last backup (FULL, DIFF or INC) of the same task. This is the fastest backup method and requires the least storage space. Restoring from incremental backups is the slowest, because it requires all related savesets to be copied back – the saveset of the last full backup as well as all INC backups. You should consider the advantages of time and resources when planning your backup strategy. A combination of FULL backups stored to tape drives, and DIFF or INC backups stored to virtual disk media is a common method.
      A COPY backup is a full backup that has no influence on following differential (DIFF) or incremental (INC) backups. For the treatment of archive bits, see FULL backup above. COPY backup is usually used for additional full backups, e.g., monthly backups, or backups for archiving, i.e. removal from storage.
      Information sign.png Note
      In case no initial FULL backup exists, differential (DIFF) or incremental (INC) backups are automatically performed as FULL backups.
      SEP Tip.png Tip
      Make sure your INC chains do not get too long. You can use the Enforce FULL option for this (see below).

      Note, however, that it is difficult to give a practical recommendation for the recommended length of the INC chain, as it depends heavily on the performance of the system and also on the size of the FULL and INC backups. As a rule, FULL is recommended once a week and at least once a month. Since long backup chains are inefficient and more vulnerable if something goes wrong because the backups in the chain depend on each other, and because they can simply become too long to restore (no more storage available, takes too long), SEP AG strongly recommends setting up regular FULL backups to avoid such problems, and setting the limit to up to 100 incremental backups. For an example of how to implement a backup scheme, see GFS Backup Retention Strategy.

      You can set the Enforce FULL option for DIFF and INC backups. This option ensures that a FULL backup is run within the specified interval. For example, setting the number to 7 will enforce a full backup every seven days instead of an incremental or differential backup if the planned full backup fails. This ensures that a full backup is always performed within the specified time interval, which in our example is once a week. If the value is 0, each time a backup is performed, the system checks whether the last FULL backup was successful or run with warning. If the last FULL backup was terminated or run with error, the INC/DIFF backup to be started is automatically executed as FULL backup. However, once you have decided on your backup schedule, you should consider the advantages and disadvantages of enforced full backup frequency, as it is slower than other backup levels and has the highest storage space requirements. For details, see Enforcing Full Backup.
    6. From the Hot/Cold backup drop-down list, select the execution parameter (hot or cold backup).
    7. From the Media pool drop-down list, select the target media pool to which the data will be backed up. If you want to enable source-side deduplication, you have to select the media pool which is combined with an Si3 deduplication store backend.
      • Optionally, specify the drive number of the drive that will be used to write the data. Typically, you use this if you have configured additional drives and you want to assign a dedicated drive exclusively for backup. For details, see option Create second drive (introduced in SEP sesam 4.4.3 Tigon) in Configuring a Data Store.
      • You can also define the Interface: from the drop-down list, select another configured TCP/IP-name of the client. You can use this option to direct the data flow over a particular network connection to enable smooth execution of backups without blocking other network activities.
    8. Optionally, enable SEP Si3 source-side deduplication. This check box is only available if you have a configured Si3 deduplication store and you have previously selected the Si3-related media pool.
    9. In the Follow up field you can configure events that are triggered on the SEP sesam Server once the initial event has completed. You can set up a migration, a saveset verify and other actions to be triggered immediately after a backup or other event is completed. For details, see Follow-up events.
    10. SEP Tip.png Tip
      You can set a follow-up migration task by selecting the task from the Migration task drop-down list.

      New backup event Beefalo V2.jpg

    Monitoring backups

    You can view the status of your backup jobs in the GUI (Monitoring -> Last Backup State or Job State -> Backups) or SEP sesam Web UI. The backup status overview provides detailed information about the last run of backup jobs, including the task name, start and stop time of the last backup, backup level, data size, throughput, assigned media pool, etc.

    Standard Restore Procedure

    There are two ways to restore your data in SEP sesam: using the GUI restore wizard (described below), or via the web interface Restore Assistant. Even though most of the options are the same in both restore interfaces, the web Restore Assistant interface is designed to be more intuitive and offers additional advanced options while, on the other hand, it does not support the restore of all tasks types, such as PostgreSQL or Oracle. For details, see Restore Assistant.

    SEP sesam GUI restore is a process that browses for different versions of savesets and copies data from savesets to a client, thus recreating the original data. The restore wizard is triggered from the Menu bar -> Activities -> Restore.

    Restore tasks can be saved, scheduled and run automatically in continuous intervals to check and control data integrity. For details, see SEPuler.

    The data restore granularity depends on the selected data type.

    The following restore types are available:

    Complete restore
    A process by which an entire saveset is restored – all the files of a saveset are selected and restored.
    Selective restore
    Only a subset of a saveset's files is selected – only selected parts of data on the saveset, such as individual files and directories, are restored.
    Generation restore
    All generations of backed-up files, including differential or incremental backup files, can be browsed for and selected for restore. SEP sesam automatically switches to the generation view in which all the generations of the files are presented. The selection list displays all files since the last full backup.

    Configuring a restore task

    Note that the following instructions for creating a restore task apply to using a restore wizard in the GUI. Although the steps and options are very similar, an alternative way for creating a restore task using the web interface is described in Restore Assistant and in Web Single File Restore for Virtual Machines.

    A restore task involves browsing and selecting the desired savesets by time and task/filename, selecting the restore type and restore target (the file system folder, for example) and other additional options. The restore can be run immediately or scheduled to run automatically at a specified time.

    Prerequisites

    • Depending on what you want to restore, make sure that you have the restore permissions and access rights.
    • Make sure that there is enough free space on the target system where you want to restore your data.

    Steps

    1. From the SEP sesam GUI menu bar, select Activities -> Restore. The New Restore Task window opens.
    2. Select the saveset you want to restore. You can search savesets by task name or by filename or path.
      • If searching by task name, use the drop-down list of available tasks and select the one you want to restore from. This option is selected by default.
      • If searching by filename/path, select the option Filename or path in a saveset and enter your search expression in the search pattern field.
    3. Under the Saved in period drop-down lists, specify the time frame for which you want to conduct the search. Click Next.
    4. The search results are displayed. From the list of savesets that match your query, select the desired version by clicking on it, then select other relevant restore options (complete, generation, as path or disaster restore). You can also select the option Mount saveset under Single file restore to mount the target saveset to the disk and make it accessible as if it were a separate volume on the disk. You can mount any saveset stored to default data store Path, Si3 deduplication store or HPE StoreOnce. Mounting is not possible if the savesets are stored on tapes or if the data is compressed or encrypted. For advantages on mounting a saveset, see Cross-platform recovery file system layer (XPRFS). Click Next.
      Information sign.png Note
      • The Mount saveset option is available only in advanced UI mode (formerly expert GUI mode). To use the mount option, make sure your UI mode is set to advanced, as described in Selecting UI mode.
      • To be able to access and mount the VM disk image on Linux, the guestfs-tools package must be installed on your SEP sesam Server or Linux RDS. If the guestfs-tools package is not installed on your SEP sesam Server or Linux RDS, it is not possible to mount VMDK and perform SFR. Refer to Installing guestfs-tools on Linux.
      • As of v. 5.0.0 Jaglion, the Hide migrated option is no longer available. The migrated savesets are only displayed if there is no original (backup) saveset. If you want to use the migrated saveset instead of the original saveset for restore, you need to select it as Preferred Media pool in the Target Settings window (see step 6 below).

      Restore mount saveset Beefalo.jpg

    5. If you have selected the Mount saveset option, a mount action is triggered. The selected saveset is mounted to the SEP sesam home directory var\tmp\mnt, e.g., C:\Program Files\SEPsesam\var\tmp\mnt\save_set_ID.
      Click Next to display the Select Files dialog. If you choose not to mount the saveset, this dialog is displayed immediately. Select the data you want to restore and click Next.
    6. Review your configured restore task and set additional options, if required. The details of the selected saveset are displayed in the upper part of the window. The options diffes slightly when restoring a virtual machine.
      • The name of the restore task is automatically generated in the Name field. You can edit the name and add a comment below.
      • The Target node drop-down list shows the target server to which the data will be restored.
      • Under the Target path settings, select between the following options:
        • Restore to original target path or Restore to original VM (in the case of a VM restore): The data will be restored to the same location from which it was backed up.
        • New restore target or Change VM target selection (in the case of a VM restore): The data will be restored to another location. Use the Browser button to select the target directory for the restore or enter the path to the target directory manually.
        • Restore with new VM name: Relevant only for VM restore; the VM will be restored to the original or a different location with a new VM name.
      • Under the Execution options or VM restore options (in the case of a VM restore) drop-down list, select one of the following options:
        • Do not overwrite existing items (set by default): The data will not be restored if it already exists on the target server.
        • Overwrite existing items: If data exists on the target server, it will be replaced with the restored version.
        • Create a new version: If data exists on the target server, the restored data will be restored under a new name.

        When performing a VM restore, you can also select to automatically start a virtual machine after restore.

      • Preferred media pool: If the data was migrated or replicated and different media pools were used for the process, you can select from the drop-down list of available media pools the source media pool to restore from.
      • Used media | barcode: If the data was migrated, the migrated copy is stored to another media. From the drop-down list of available media you can select the source media to restore from.
      • Optionally, select the drive number of the drive that will be used to read the data. Typically, you specify the drive if you have configured additional drives and want to use dedicated drives for restores. For details, see the option Create second drive.
      • The Interface field shows the SEP sesam Server or RDS with the attached data storage that contains the selected saveset.
      • You can specify additional restore settings by clicking the Expert Options button, for example, modify the log level settings, define the pre/post script for the restore, etc. For details, see Restore Overview.
      • Information sign.png Note
        The Expert Options button for setting advanced restore options is only available in advanced UI mode (formerly expert GUI mode). To use Expert Options, make sure your UI mode is set to advanced. For details, see Selecting UI mode.

      After you have set additional restore options, click Next.

    7. To start your restore immediately, click Start. To save the restore task, click Save.
    8. If you have mounted a saveset, click OK to unmount it and end your restore session.
    Information sign.png Note
    A restore task can be scheduled like any other task. If you want to add a restore task to the schedule, see Scheduling Restore.

    Monitoring restore

    You can monitor the restore progress using the Web UI (Monitoring -> Restores) or view the status in the GUI (Main Selection -> Job State -> Restores). The restore overview provides detailed information on the last run of restore jobs, including task name, status (successful, error, in queue ...), start and stop time of the last backup, data size, throughput, etc. For details, see SEP sesam Web UI or Restores by State in the GUI.

    Creating a Migration Event

    The migration event is the final step in the configuration of a migration job. Creating a migration event consists of reviewing migration task parameters and (optionally) setting the event priority.

    Steps

    1. In the Main Selection -> Scheduling -> Schedules, select the schedule for which you want to create a new migration event, click New (or right-click the selected schedule) and click New Migration Event.
      Select new migration event Beefalo V2.jpg
    2. From the Task name drop-down list, select the name of the already configured migration task for which you want to create a migration job.
    3. In the Priority box, set the Priority for your migration event. SEPuler always executes the schedules with higher priority first. The default priority level is 1, which is the lowest priority (the highest is 99). The only exception are the schedules with priority 0, which override all other priorities and are always executed. For details, see event priorities. You can also enable the Blocking date. This option should be used together with the high priority for special events. When enabled, the blocking event blocks events of the same type with a lower priority, ensuring that the backup is processed if other backups are scheduled at the same time. For details, see Blocking Events.
    4. The settings under Media pool, Destination, Backup date, Backup state, Backup level, Object, and Special filter (previously Parameter and Filter) were defined when you created the selected migration task. If required, you can modify these settings. The changes are only applied to the current migration event and do not affect the values originally set in the migration task. Any changed values (as opposed to the settings in the migration task) are displayed in blue when the event is re-opened. The check box Delete after successful migration sets the saveset EOL to the actual date and time of the successful migration. The source saveset is purgeable immediately after the migration. The saveset EOL has no effect on savesets stored on tape media.
      New migration event Beefalo.jpg
    5. Click OK to save your migration event.
    SEP Tip.png Tip
    You can use the Migration task option in the backup task and event properties to select a follow-up migration task.

    Monitoring migrations

    You can view the status of your migrations jobs in the GUI (Job State -> Migrations and Replications) or SEP sesam Web UI. Migration tasks are listed by name, along with details of completion status, start and end times, and media pools used for the job.

    Creating a Command Event

    <translate> A command event enables the execution of any program on a SEP sesam Client. A user must be authorized to run the commands on a specific client. By default, only commands entered in the system directory at <SESAM_ROOT>/bin/sesam can be executed. If you want to allow starting commands in other directories, see the section Setting permission to run commands.

    In the SEP sesam GUI, you can start command events immediately or schedule the events for automatic execution.

    Steps

    To create a new command event, follow the steps below:</translate>

    1. <translate> From Main Selection -> Scheduling -> Schedules, select the schedule to which you want to add a command event. Then right-click the desired schedule and select New Command Event. The New Command Event window is displayed.</translate>
    2. <translate> Note that if you have not already configured a schedule, you must first configure it by clicking the New Schedule button in the Schedules window. For details, see Creating a Schedule.</translate>

    3. <translate> Under the Parameter tab, specify the following settings:</translate>
      • <translate> Priority: Optionally, define a priority for the command event. SEPuler always executes schedules with higher priority first. The default priority level is 1, which is the lowest priority (the highest is 99). The highest priority level is 99. The only exception is schedules with priority 0, which override all other priorities and are always executed. For details, see Event Priority.</translate>
      • <translate> Blocking date: This should be used in conjunction with high priority for special events. When this check box is selected, lower priority events of the same type are blocked, ensuring that the command event is processed if other command events are also scheduled at the same time. See Blocking Events.</translate>
      • <translate> Name: Select the name of the existing command from the drop-down list. When selected, the full command is displayed in the Preview field below.</translate>
      • {{<translate> tip</translate>|<translate> You can access the configured commands from the menu bar -> Configuration -> Command. You can define your own commands to use when creating a command event, and modify, delete, or copy the existing commands. For details, see Configuration: Commands.</translate>}}

      • <translate> Client: Select a client on which to execute the command.</translate>
      • <translate> User: Enter the user name of a user who has sufficient rights to execute the command on the client.</translate>
      • <translate> Retention time: Specify how long (in days) to retain the command event results and logs (default 30).</translate>
      • <translate> Additional Parameter: Optionally add additional parameters to the command.</translate>
      • <translate> Follow up (available in v. ≥ 5.0.0 Jaglion): Optionally use this field to configure a follow up event to be started on the SEP sesam Server once the command event has completed. For details, see Creating Follow-up Events.</translate>
      • <translate> New command event Jaglion.jpg</translate>


    4. <translate> Click OK to add your command event to a schedule. You can review your schedules and assigned events, trigger events to start immediately, or delete them by right-clicking the selected schedule/event.</translate>

    <translate>===Setting permission to run commands===

    Not every user on a specific client is authorized to run all commands. Without additional entries authorizing selected users to run certain commands, commands can only be run from the system directory <SESAM_ROOT>/bin/sesam. If a command is to be started from another directory before the regular backup is started, this must be entered/allowed on the target client.</translate>

    UNIX

    <translate> Copy the file sesam_cmdusers.allow from the directory <SESAM_ROOT>/skel to /etc on the client and modify the file. You can now enter a line for the user and the command in the format {user} {command}. If you use a wildcard (*), all commands will be executed.

    No explicit permissions are required to execute SEP sesam commands such as sm_loader.</translate>

    Windows

    <translate> To set access rights for the user and command, use the following key:</translate> \\HKLM\SOFTWARE\SEP Elektronik GmbH\sesam\CommandEvents\<translate> <user></translate>\<translate> <command></translate>

    <translate> In addition, on the client computer, the entry CTRLD_Path=ID/bin/sesam;ID/bin/sms in the file ID/var/ini/sm.ini in the section [CTRLD_Server] must be extended to include the directories in which the desired programs are located.</translate>

    1. <translate> Open the Regedit editor.</translate>
    2. <translate> Go to HKEY_LOCAL_MACHINE\SOFTWARE\SEP Elektronik GmbH\sesam\ and create a new key named CommandEvents. If it does not already exist, right click and select New Key.</translate>
    3. <translate> Enter <user> and then <command> with the full path information as the key.</translate>

    <translate> The available commands are:</translate>

    <translate> Command</translate> <translate> Execution</translate>
    * <translate> all commands</translate>
    cmd /c <translate> all DOS commands (dir, etc.)</translate>
    DOS command (e.g., dir) <translate> specific DOS command only (e.g., dir)</translate>
    specific command (e.g., ping) <translate> specific command only (e.g., ping)</translate>

    <translate> If there are other commands, the last command is executed. If you use a wildcard (*), all commands are executed.

    Registryentry.JPG</translate>

    <translate> Below is an example of a registry file (*.reg) that allows all command events for the administrator and the sesam user:</translate>

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\SEP Elektronik GmbH\sesam\CommandEvents\sesam\*]
    [HKEY_LOCAL_MACHINE\SOFTWARE\SEP Elektronik GmbH\sesam\CommandEvents\Administrator\*]
    

    {{<translate> note</translate>|<translate> The most common errors when setting up the desired user permissions and allowed commands are:</translate>

    • <translate> The necessary entries are not entered in the directories of the target clients, are not entered on the server, or are entered incorrectly.</translate>
    • <translate>

    Instead of entering a command as a key, it is entered as a string.</translate>}}


    Creating a Media Event

    A media event can be a user-defined event or an internal event created by SEP sesam. For example, if the specified media are unavailable at the start of a backup or if the end of media (EOM) is reached during data transfer, SEP sesam creates an internal media event which determines the next media for the backup. If no other media events are configured in the schedule, only internal media events are executed.

    A user-defined media event is configured by using GUI and automatically activated by SEPuler. The following media events can be configured:

    initializing
    A process of preparing backup media for use with SEP sesam. If a medium meets the requirements (e.g., its EOL has expired and it is not write-protected – locked), it can be initialized, deleting all data contained on it and preparing it for use again. During initializing, SEP sesam assigns a new tape label for formatted media and deletes all existing content on these media. At the same time, it deletes all information about old backups from the SEP sesam system.
    readability check
    A process that checks the backup data readability. During the check the data on medium is read in blocks, and the structure of tape is checked and recorded. It also checks whether all determined backup sets on the tape are recorded in the database and vice versa. For details, see Configuring a Readability Check.
    close tape
    A process that marks the tape as full by defining EOM and closing the tape, regardless whether the tape is really full or not. Such a tape can no longer be used for storing the data.
    archive adjustment
    A process that scans media in selected loader to update SEP sesam information about the media in the loader. It is required if the media in the loader have changed, for example if new media are added. For details, see Setting up Archive Adjustment.

    Steps

    1. In the Main Selection -> Scheduling -> Schedules, select the schedule to which you want to link the event, right-click it or select New and then New Media Event. A schedule is opened with a new tab Parameter.
    2. Under the Sequence control, set up the Priority of your media event. SEPuler always executes the schedules with higher priority first. Default priority level is 1, which is the lowest priority (the highest is 99). The only exception are the schedules with priority 0, which override all other priorities and are always executed. For details, see Setting Event Priorities. You can also enable the Blocking date. This option should be used together with high priority for special events. If checked, the blocking event will block events of the same type of a lower priority, ensuring the backup to be processed in case other backups are scheduled at the same time. For details, see Blocking Events.
    3. Under the Media action, select the type of event you want to create. You can select among the following: Initialize, Readability check, Archive adjustment and Close tape.
    4. Depending on previously chosen media event, some or all of the following options may be available.
      For options Initialize, Readability check, Close tape:
      • Media pool: Select the media pool for your event.
      • Drive: Optionally, select a drive.
      • Media: Optionally, select media for the event.
      For option Archive adjustment:
      • Media pool: Select the media pool where you want to perform the archive adjustment. Note that all media are shown regardless of the pool selected.
      • Drive: Optionally, select a drive.
      • Loader: Select the loader (tape library) for which you want to synchronize its contents with the SEP sesam database.
      • First slot and Last slot: You can limit synchronization to the specified loader parts by entering the number of the first and last slot.
      • Automatic introduction: Optionally, you can select that any unknown media (without SEP sesam label) found in the tape library is automatically added to the specified media pool. If selected, specify also the Tape type option by choosing the media type for automatic new media entry from the drop-down list.
        • If you have selected Automatic introduction, under the Handling of unknown SEP sesam media, select one of the following options:
          Overwrite option will overwrite all media entered to the target media pool that are not recognized by the SEP sesam Server and assign a new media pool label to them.
          Accept without initialization enables SEP sesam to enter other SEP sesam media, e.g., from another SEP sesam Server, into the target media pool.
      • Check label on tape: Optionally, enable this if you want to scan the tape labels; every tape label is re-read and verified, while the barcode information is ignored.
      • Adjustment by barcode only: Optionally, select this if you want SEP sesam to check the barcodes of all tapes which are not in drives. This enables you to adjust the archive while the drives are in use. SEP sesam scans only the tapes which are in slots, while the tapes in the drives are not scanned.

      New media event Beefalo.jpg


    Setting up Archive Adjustment

    Overview

    Archive adjustment is used to perform a comparison between the media in the loader (tape library) and the SEP sesam media archive database, and to perform a database synchronization with the selected loader by updating the database with the most current inventory information from the scanned device.

    Archive adjustment is mandatory whenever the contents of your loader have changed. Typically, you need to run archive adjustment whenever new media or used media that have not yet been registered (initialized) by SEP sesam are inserted to identify unrecognized tapes.

    You can perform archive adjustment for an entire tape library or run the job for selected tapes only by specifying the selected segment (see Slot range below).

    SEP sesam also supports archive adjustment with media introduction over barcode only. The option Adjustment by barcode only is shown for all libraries that have a barcode reader to quickly locate individual media by reading the barcode attached to the media. The media does not need to be loaded into a drive, which means that the process is faster and does not block all drives for backup or restore.

    Prerequisite

    Make sure your loaders are configured correctly. If you want to run archive adjustment from the command line, the task must include the name of the target autoloader or tape device. You should check your storage device configuration, as described in Configuring Loaders and Drives.

    Steps

    1. From Main Selection -> Components -> Loaders, select the relevant loader and click Archive Adjustment.
    2. Loader options Jaglion V2.jpg

    3. In the Archive Adjustment window, specify the required fields. Note that the available options depend on the loader and SEP sesam version.
      Archive adjust loaders-options.jpg
      • The Drive group is already selected and cannot be changed. You can select a drive from a drop-down list next to Drive (opt.).
      • Slot range: You can limit the synchronization to the specified loader segment by entering the number of the first and last slot.
      • Adjustment by barcode only: If your loader contains a barcode reader, select this option to use it for archive adjustment of tapes in the loader. SEP sesam checks the barcodes of all tapes that are not in drives. This enables adjusting the archive while the drives are in use. SEP sesam scans only the tapes that are in slots, while the tapes in the drives are not scanned.
      • Check label on tape. Ignore barcode labels: Select this option if you want to scan the tape labels; every tape label is re-read and verified, while the barcode information is ignored.
      • Automatic introduction: Select this option if your loader does not contain a barcode reader and you want to automatically add unknown media (without a SEP sesam label) from the tape library to the specified media pool.
    4. Media pool: Select a media pool where you want to perform archive adjustment.
    5. If you have selected the option Automatic introduction, select the appropriate tape type using the Tape type drop-down list. Then set the following:
      1. Select the preferred way for Handling of unknown SEP sesam media.
        All tape media that do not have a SEP sesam tape label stored on the tape will be overwritten. However, for tape media with an existing SEP sesam label, the following applies:
        • If the label is already stored in the SEP sesam DB (media table), the tape remains untouched.
        • If the SEP sesam tape label is unknown, the tape handling depends on the following options:
          • Accept without initialization is enabled by default. This means that if a tape with unknown SEP sesam label (which is not in SEP sesam DB) is retrieved, e.g., a tape from another SEP sesam Server, it will be automatically inserted. Note that such tapes are simply added to the SEP sesam DB without providing meta information about their contents.
          • If you select Overwrite, a tape with unknown SEP sesam label (which is not in SEP sesam DB) will be initialized and added to the selected media pool.
      2. Note that tape media from competing manufacturers are not recognized and will be overwritten.
  • Click Start.
  • Your archive adjustment starts immediately. If you selected the option Automatic introduction, SEP sesam will unload all drives for archive adjustment. If a drive is in use, e.g., for a backup or restore, archive adjustment will start as soon as the drives are no longer used by another process.

    You can also set up a special media event for archive adjustment and schedule it to run automatically, as described in the following section.

    Alternatively, you can use a command event to set up automatic archive adjustment. For details, see How to set up automatic archive adjustment.

    Adding SEP sesam labeled tapes to a new or different media pool

    If you want to use already labeled tapes in a new or another media pool, proceed as follows:

    1. From Main Selection -> Components -> Media, double-click the relevant media and click Delete Media. Note that all metadata of the tape is deleted and the tape entry is removed from the media table.
      Delete media Jaglion V2.jpg
    2. Start archive adjustment by using the option Automatic introduction together with Overwrite (see above steps). The tapes are reinitialized with a new label for the selected media pool.
    3. Information sign.png Note
      Overwriting the existing label will erase all data on the tape.

    Creating a media event for archive adjustment

    By creating a special media event for archive adjustment, you can schedule it to run automatically at specific intervals or set up an archive adjustment template that lets you start it interactively.

    Steps

    1. From Main Selection -> Scheduling -> Schedules, select the schedule you want to associate the event with, select New, and then New Media Event. A schedule is opened with a new tab Parameter.
    2. Under the Media action, select Archive adjustment.
    3. Under Parameter, specify the relevant options for archive adjustment (Loader, Media Pool, Drive, etc.), as described above.
      Click OK.
      Media event archive adjustment Beefalo V2.jpg
    4. You can start the archive adjustment immediately via Activities -> Immediate Start -> Media Action. For details, see Immediate start of a media action.


    Follow-up Events

    Overview

    As of SEP sesam version ≥ 4.4.3, you can configure follow-up events that are triggered on the SEP sesam Server once the initial event is completed. You can set up migration, saveset verify and other actions to be triggered immediately after backup or other event is completed.

    Key features

    Follow-up events allow you to start actions based on events happening on the backup server.

    The following event chains can be combined:

    • Start migration after the backup or task group is successfully completed.
    • Start single backup task or task group after the backup, task group or migration is successfully completed.
    • Start saveset verify after the backup or task group is successfully completed.

    Activating follow-up events

    To activate the follow-up events, enter the following commands in the shell/cmd.

    On Windows:

    c:\program files\sepsesam\var\ini\sm_prof.bat
    sm_glbv w gv_use_follow_up 1
    sm_db "update defaults set value='1' where key ='enable_gui_follow_up'"
    

    On Linux:

    source /var/opt/sesam/var/ini/sesam2000.profile
    sm_glbv w gv_use_follow_up 1
    sm_db "update defaults set value='1' where key ='enable_gui_follow_up'"
    

    Event-based actions are logged within:

    SESAM_INSTALL_DIR/var/log/lgc/sm_event_<date>.log
    
    Information sign.png Note
    If you need troubleshooting assistance, send this log file with a description of your issue to SEP sesam support.

    Configuring follow-up events

    A follow-up event can be configured in the backup event properties: Main Selection -> Scheduling -> Schedules -> New Backup Event. For details, see Creating a Backup Event.

    In the Follow up field, you can configure events to be started on the SEP sesam Server once the initial event is completed. With SEP sesam v. 5.0.0 Jaglion, the Follow up field is also available when configuring the command events. For details, see Creating a Command Event.

    As of version 4.4.3 Grolar, you can use Migration task option to chose a follow up migration task.

    Follow up events Beefalo V2.jpg

    Information sign.png Note
    A follow-up event is always configured for the schedule that should trigger the event.

    Testing events on the command line

    Backup events can be tested on the command line before configuration. As initial start of a backup the command line tool sm_cmd is used.

    The notation of the command has a special syntax:

    sm_cmd <cmd_command> -@ "<event_definition>"
    

    The following example shows an sm_cmd command which then automatically starts a follow-up event to back up a task group:

    sm_cmd backup -m MEDIAPOOL -j TEST_BACKUP -@ "sm_event backup task SESAM_BACKUP - -m MEDIAPOOL -"
    

    See SEP sesam Command Line Interface for details.

    Follow-up examples

    In the following examples the elements within the angle brackets < > indicate that the enclosed element is mandatory and must be appropriately replaced by parameter or actual name. Do not type the angle brackets in the command line. The follow up command must always end with a hyphen (-). If you add additional parameters to the command, they must also end with a hyphen.

    All specified tasks and migration tasks have to be configured in the GUI before the follow-up event is started. For example, first you configure a migration task and then you set up the event migrate saveset after the backup.

    Verify saveset after the backup

    Information sign.png Note
    Verifying savesets is currently only available for Path task type.

    To verify the backup, use the following command:

    sm_event verify saveset -
    

    After the backup is finished, a restore is started and data is being verified. No data is written to the target system. To view the status of your verification job, go to the Main Selection -> Job state -> Restores and check the verification status.

    Migrate or replicate saveset after the backup

    First, create a migration task or a replication task. Once the required task is created, you can set it up as a follow-up event after the backup has completed.

    The following command will start the respective migration after each completed backup task:

    sm_event migrate saveset <migration_task> -
    

    Replace <migration_task> with the actual name of the migration (or replication) task, as it is displayed in Tasks -> Migration Tasks or alternatively in Tasks -> Replication Tasks (previously Si3 Replications).

    SEP Tip.png Tip
    As of version 4.4.3 Grolar, you can use Migration task option in task event properties to chose a follow up migration task.

    Migrate savesets after all backups in the group completed

    First, create a migration task and then set it up as a follow-up event to start the migration for backup-group related savesets.

    The following command will start the respective migration after all backups that are part of the group are completed:

    sm_event migrate group <migration_task> - 
    

    Replace <migration_task> with the actual name of the migration task (or replication), as it is displayed in Tasks -> Migration Tasks or alternatively in Tasks -> Replication Tasks (previously Si3 Replications).

    Migrate saveset after the backup and delete it after successful migration

    First, create a migration task. Once the required task is created, you can set it up as a follow-up event after the backup is completed by entering the following command:

    sm_event migrate saveset <migration_task> - -r 1 -
    

    The additional option "-r 1" will be passed to the migration task and the saveset will be deleted after successful migration.

    Replace <migration_task> with the actual name of the migration task, as it is displayed in Tasks -> Migration Tasks.

    Information sign.png Note
    This follow-up event can only be used for migration, not for replication.

    Start a single backup task after the backup

    To start another backup task after the scheduled backup is finished, specify the following:

    sm_event backup task <task_name> - -m <target_pool> -
    

    Replace <task_name> with the name of the backup task and <target_pool> with the target media pool the data should be saved to.

    Start a single backup task after all backups of a task group

    To start another backup task after all backups of a scheduled task group are finished, specify the following:

    sm_cmd backup -G <task_group> -m <target_pool> -@ "sm_event backup taskgroup <task_name> - -m <target_pool> -"
    

    Replace <task_group> with the name of your task group, <target_pool> with the target media pool the data should be saved to, and <task_name> with the name of your backup task which should be started.

    Information sign.png Note
    The notation sm_event backup taskgroup ensures that all backups of the previous running task group have been completed.

    For example, the name of the task group is MY_GROUP, the name of the target pool is MY_MEDIAPOOL, and the task name is SESAM_BACKUP:

    sm_cmd backup -G MY_GROUP -m MY_MEDIAPOOL -@ "sm_event backup taskgroup SESAM_BACKUP - -m MY_MEDIAPOOL -"
    

    Start task group after the backup

    Sometimes you need to start a task group after the backup is finished:

    sm_event backup group <task_group> - -m <target_pool> -l BACKUP-LEVEL -
    

    Replace <task_group> with the name of the task group and <target_pool> with the target media pool the data should be saved to. With backup-level you can define F/C/D/I.

    Start event on special drive

    To start the target event on a different drive, specify the option -d:

    sm_event backup task <task_name> - -m <target_pool> -d <drive_num> -
    

    Send notification after backup or restore

    You can trigger a notification after the backup or restore event has finished.

    For the backup, use the following command:

    sm_event notify result <username> -
    

    For the restore, use the following command:

    sm_event notify restore <username> -
    

    In the following example, the notification is sent to the account configured as backup in Configuration -> Email Settings.

    sm_event notify result backup -
    

    For more information on e-mail configuration, see Email Settings. For details on how to send a SEP sesam daily protocol to an email account, check FAQ.

    Execute script after backup

    To execute a script after the backup is finished and pass some additional parameters, use the following command:

    sm_event execute <script_name>.sh - <some_additional_parameters> -
    

    Replace <script_name> with the name of the script and <some_additional_parameters> with the desired parameters, e.g., -s savesetID.


    Newday Event

    SEP sesam Newday is a predefined SEP sesam daily event that resets the backup event calendar and is managed by SEPuler. It is accessible under schedules: Main Selection -> Scheduling -> Schedules. A Newday event is used by SEP sesam to reorder its database and enable uninterrupted activity of SEP sesam processes. It must therefore never be completely disabled, otherwise it will cause SEP sesam to stop working properly. See Newday event roles. Newday is used to define a new backup day. All SEP sesam protocol and log files are created with the date of the backup day.

    If a Newday event is set to 08:00 (SEP sesam default), the backup day is defined from 8am of the current day to 8am of the next day. Backups that run after midnight – the actual date change – are given a timestamp with the date of the previous day to avoid creating backups for the same data (one saveset for day 1 and another for day 2).

    With SEP sesam Newday, all media backed up from one sesam day, e.g., from Monday 8am to Tuesday 7.59am, will have the same date. SEP sesam Newday gives system administrators the flexibility to extend backup routines to run after midnight and retain the backup date of the prior day. This is very useful when the computers that need to be backed up exceeds the time span between the end of the day and midnight.

    When checking in SEP sesam GUI, for example, backups by state, the selected/displayed date always refers to the sesam backup day with the timespan of hours defined by Newday. In the above example of a defined backup day (from 8am of the current day to 8am of the next day), 13 November would define the backup day from Monday, 13.11. from 8am, to Tuesday, 14.11. to 7.59am. Keep in mind that the backup day by default does not correspond to the calendar day.

    Information sign.png Note

    To ensure error-free execution of the SEP sesam backup environment, SEP Newday should never be completely deactivated. Switching Newday off prevents SEP sesam from reordering its database. SEP sesam will no longer be able to delete old log files and will cause the system to exceed system disk drive storage.

    Besides resetting the event calendar and setting a new backup day, Newday also performs the following:

    • Deletes files and database entries for savesets that no longer exist.
    • Finalizes the SEP sesam status and daily log files.
    • Reorganizes the SEP sesam database.
    • Advances the event calendar (SEPuler) by one day.
    • Restarts the SMS- and STPD-processes.

    Preventing Newday from cancelling running activities

    You can set a Newday behaviour to allow uninterrupted execution of SEP sesam operations. If you do not want active tasks to be cancelled during the Newday event, go to Schedules -> Newday event properties -> tab Parameter, and then select the check box All Events next to Do not cancel these activities.

    If the Newday is configured as explained above, it does not interrupt any ongoing backup when it starts, so the Newday can be set to be active at all times.

    Newday event Beefalo V2.jpg

    Preventing the sm_alarm or sm_notify interface from blocking the Newday execution

    If you use the SEP sesam email notification based on the sm_alarm and/or sm_notify interface scripts, be aware that adding some long-running actions that take a lot of time can block the execution of the sm_newday event and possibly other SEP sesam actions, such as backups.

    Starting with version 5.0.0 Jaglion, you can use the submit_notify option to let these scripts run in the background and prevent them from blocking SEP sesam actions.

    Steps

    1. From Main Selection -> Scheduling -> Schedules, double-click the Newday event.
    2. In the properties of the Newday event (tab Parameter), enter submit_notify in the Options field and click OK.
    3. Newday-submit notify.jpg


    For details on using SEP sesam email notifications and enabling interfaces, see How to Configure Mail Notification.

    Part VI: Monitoring & Reporting

    Monitoring, logging, reporting and notifications

    SEP sesam enables you to easily monitor your entire SEP sesam environment via the Web UI or SEP sesam GUI. Various monitoring features and real-time monitoring capabilities provide a complete overview of your environment as well as valuable insights into the KPIs of the backup and restore process to effectively manage, control, monitor and restore backups.

    With reports, you can not only check the details of all events, but also get an overview of all active jobs, next events, and different states, e.g., data store status, backups, migrations, etc. You can send these reports and log files in the form of email notifications.

    Note that the options (and operations) available after login may differ depending on the user type. Other Web UI and GUI display restrictions may depend on the custom roles with specific permissions and the UI mode.
    For details, see About Authentication and Authorization and User Roles and Permissions.

    Monitoring the SEP sesam environment

    You can monitor your SEP sesam environment via SEP sesam GUI or via Web UI.

    Note that all monitoring, reporting and notifications functionality accessible in the SEP sesam GUI is also accessible in Web UI with the advantages of being user-friendly and visually attractive, providing immediate access to Web UI from mobile browsers and being easily accessible to anyone you authorize.

    Monitoring in Web UI

    Monitoring in Web UI
    Web UI access

    When running the SEP sesam GUI as superuser or administrator, the Web UI landing page opens by default with a link to the Web UI (and links to documentation, etc.). You can also access the online Web UI from the GUI by clicking the first icon – dashboard – in the toolbar or by selecting Dashboard in Main Selection -> Monitoring. Or simply enter the following information in the browser address bar: http://[servername]:11401/sep/ui or https://[servername]:11401/sep/ui.
    If you cannot access the web Restore Assistant, check that you have been given the appropriate permissions to restore.

    Web UI Status, Dashboard and Monitoring

    Web UI displays all important key information for your environment with a standard dashboard for easy visualization of job completion status, errors, storage usage and more, based on metrics updated in real-time.

    • You can monitor your backup infrastructure on a daily/weekly/monthly basis.
    • You can monitor the status of SEP sesam jobs, such as backups, restores, etc., under various menus:
      • Status (default start page) provides a status overview of your jobs, data stores, events, clients, etc. See Web UI: Status.
      • The Dashboard allows you to check that all your backups and restores have completed successfully and view statistics on the total size of backed up and restored data; see Web UI: Dashboard.
      • Monitoring provides a submenu with several options that allow you to check the details and status of the listed events and active jobs (backups, restores, migrations, replications, and media actions). In v. ≥ 5.0.0 Jaglion, you can also perform various actions such as running or locking backups, restarting failed jobs, starting restores, etc., if you have the appropriate permissions. For details, see Monitoring in Web UI.
    • You can expand the charts for better readability, generate reports, and filter the data.
    • For more details on Web UI and its various report widgets, see SEP sesam Web UI.

    Monitoring in GUI

    SEP sesam GUI provides monitoring capabilities for data protection activities, performance, and resource usage. The Main Selection navigation pane (on the left side of the GUI window) is used to navigate through the components of the SEP sesam system. These include Clients, Data Stores, Loaders, Drives, Media Pools, Tasks, and Scheduling, and provide the following dedicated views for monitoring SEP sesam environment.

    Monitoring

    SEP sesam GUI Monitoring allows you to check the latest backup status and the status of SEP sesam processes, monitor drives, access the online dashboard, and check notifications (see the section Notification Center). You can search for and/or filter and export the data for reporting and analysis.

    Job State

    You can also monitor the status of SEP sesam jobs, such as backups, restores, and migrations, by expanding the GUI item Job State and selecting All results to view details on all jobs, such as the job ID, event type (backup, command, migration, restore, etc.), job status (successful or not), object (what was processed), task (its name, job's duration, start and end time), and other details.

    Clicking the sub-item (Backups, Restores, Migrations and Replications, or Media Actions) provides detailed information on the selected job. For example, Backups provides detailed information on all backup jobs, including the task name, date of the last full backup, backup level, data size, throughput, assigned media pool, etc.

    You can filter each status view to include only the tasks, status, clients, etc., that match certain criteria.

    SEP Tip.png Tip
    You can easily print or export different reports, as described in the section SEP sesam reports.

    Logging

    The Logging view in the GUI and the System logs in the Web UI are the central place to find information about what is going on in your SEP sesam environment. SEP sesam creates the following protocols or log files for each backup day: the status file – State (<date of day>.status), the Day Log (<date of day>.prt), and the Error Log (<date of day>).

    State
    This detailed status log has one line written for each backup in chronological order.
    Day Log
    All SEP sesam modules write messages with a timestamp attached to it for each backup day. Each message contains a unique code consisting of the message type (I=information, W=warning, E=error ), number, and originating module. You can filter the day log by using the time selection (the from and to date) and the search.
    Error Log
    Contains a record of the critical errors that occurred during the backup day. This log is a subset of the entire day log where only error messages are recorded.

    SEP sesam log files are used to detect operations that have caused errors or malfunctions, for example, in case of a failed backup. For details, see Analyzing SEP sesam Log Files and Tips for Backup Troubleshooting. The log files are stored on the backup server in <SESAM ROOT>/var/prot. They can be printed out or sent by email.

    If you want more information about specific events or modules, or or if you are asked by support to diagnose your specific problem, you can run SEP sesam with a higher log level than the default (0 for backup and restore). Note that increasing the log level increases the amount of information being logged and may negatively affect the performance of SEP sesam. For details, see Setting Log Level.

    Information sign.png Note
    You can also generate audit logs to record every action that was triggered by a user in the SEP sesam GUI and Web UI (e.g., triggering a restore or deleting a data store). Audit logs ensure data integrity by providing a complete track record of data-related operations, helping to increase security and compliance. For details, see Audit Logging.

    It is recommended to configure the interfaces (Alarm, Disaster and/or Notify) to automate the sending of email reports of errors and license violations, as well as log files, and to help carry out the disaster recovery process in case of a SEP sesam Server breakdown. See section Email notifications.

    You can check the log information of the SEP sesam Server interfaces by selecting the target interface (Alarm, Disaster or Notify) in the GUI under Main Selection -> Interfaces or in the Web UI under System logs. For details, see Logging in the GUI and System logs in the Web UI.

    Email notifications

    SEP sesam allows you to send the logging messages (daily protocol, events and errors) to an email account. This feature is based on interface scripts that have to be activated via the GUI or manually by copying the templates that are available in the SEP sesam directory <SESAM_ROOT>/skel/templates. For details, see Configuring interfaces.

    SEP sesam interfaces require a configured email account to be able to send the selected notifications by email. You can configure it from the menu bar -> Configuration -> E-mail Settings, select the Use Sesam mail program option, click New and then configure the account with the account name sesam (the default email account; lowercase). For details, see Configuring email account and recipients.

    It is recommended to configure the following interfaces to receive a daily log and notifications when certain events happen in the SEP sesam environment.

    • sm_notify: Notify is executed on the SEP sesam Server. It can be used for reporting on successfully finished and erroneous events, such as backup, restore, migration, media initialization, and start/finish of a NEWDAY event.
    • Click the right "Expand" button to view an example of a failed jobs report

      Reporting failed job.jpg

    • sm_alarm: Alarm is executed on the SEP sesam Server to warn the system administrator when a fatal error occurs or when there is a license violation.
    • sm_disaster: This interface must be properly configured to help carry out the disaster recovery process. For details on how to prepare for it, see SEP sesam Server Disaster Recovery. The disaster interface sends an email describing the recovery procedure in the event of a disaster and an attachment containing the SEP sesam bootstrap database with all essential data for disaster recovery.
    • Click the right "Expand" button to view a sample disaster log

      Disaster log.jpg

    For details on how to configure the interface scripts, see Configuring interfaces.

    SEP sesam reports

    SEP sesam reports provide various information on your backup environment. For example, you can check the status of the last backup, check which clients in your network are not configured for backup, data storage usage, and much more.

    Web UI reports

    SEP sesam Web UI provides various reports by clicking Reports in the left navigation menu of the Web UI (browser: https://[servername]:11401/sep/ui/#/server-report).

    The following reports are available as a drop-down list in the upper left corner: Available Media Report, Backup Storage Report, Clients Report, Failed Jobs Report, Jobs Overview Report, Readcheck Report, Used Media Report, License Report (MSP Unit or Volume Frontside).

    Web UI reporting.jpg

    Reports can be filtered using the date range picker or selector or by sesam_date, start_time, stop_time. For details, see SEP sesam Web UI Reports.

    You can send reports in the form of email notifications, as described in Email notifications.

    GUI reports

    Depending on what you want to check, you can define the criteria and generate various types of reports using the SEP sesam GUI, including:

    • Location reports
    • License reports
    • Client reports
    • License reports
    • All results list
    • Backups list
    • Restores list
    • Migrations and Replications list
    • Media Actions list

    You can manage GUI reports in the following ways.

    • By generating a report for each client or location: Main Selection -> Topology -> Location/Clients, right-click the client/location and then select Client/Location Report.
    • By printing or exporting reports: Use the Print or Export button in the top right corner of the content pane. You can export reports in excel or csv format.
    • Print export.jpg

    • By sending email notifications, as described in Email notifications.
    SEP Tip.png Tip
    You can change the level of reported messages for a backup or restore session by changing the log level. For details, see Setting the Log Level.

    Additionally, you can use the SEP sesam logs to check the recorded events and troubleshoot possible problems, as described above in Logging.

    Notification Center

    The Notification Center is used to dynamically send different types of messages – notifications from SEP sesam Server to all open GUIs. These messages inform the user about license violations, unconfigured interfaces, etc., and contain other important information, such as the announcement of a new release or notification of a bug. The notifications are sent via RSS feeds. You can subscribe to a SEP sesam RSS feed via your email application or web browser, see Subscribing to SEP sesam RSS feeds.

    Notifications can be accessed in the Web UI (by clicking the notification icon in the upper right corner or via the left menu -> Notifications) and in SEP sesam GUI (in the upper right corner by clicking the flag, under Monitoring -> Notification Center, or from the menu bar -> Window -> Show Notification Center). For more details, see Notifications in the Web UI and Notification Center in the GUI.


    Part VII: Managing Media

    Media Strategy

    Media management

    SEP sesam media management provides simple and efficient management of a large number and different types of media. Its powerful features include:

    • Efficient management of large sets of media.
    • Protection against accidental overwrites.
    • Spare pools prevent failed backups due to missing media.
    • Recording and tracking of all media and their status: used capacity, EOL, user-defined write protection, etc.
    • Barcode support on loaders.

    Media pools

    Media used by SEP sesam are administered in media pools using unique labels. The labels consist of the pool name and a five-digit number assigned by SEP sesam within the pool. For this reason, a media pool name may never end with five (5) digits.

    • Media pools are the basis for building a backup strategy. Each media pool represents a set of media designated for a specific purpose. The configuration of a media pool differs depending on whether you are configuring media pools for tape media or for data store (for backup to disk storage).
    • In the GUI, a new media pool is created under Main Selection -> Components -> Media Pools -> New Media Pool. For details, see Configuring a Media Pool.
    Spare pools

    A SPARE pool is a media pool that you can configure to allow sharing of spare media across media pools to prevent blocked backups. Spare pools are used by media events when media from the actual pool cannot be accessed. Spare media are automatically moved from the compatible spare pool to the pool currently being accessed by the backup, eliminating the need for administrator intervention when media is not available. Migration of spare media to the working pools results in a dynamic increase of the media pool size, depending on the amount of data being backed up. The use of spare pools is optional.

    • Unused media are inserted and kept for later use. A compatible spare pool of free media should be created for each drive type.
    • SPARE pools can be used to automatically insert new media into working media pools. The media are then migrated to the working pools on the production system as needed.
    • The name of a spare pool must begin with SPARE_. For details, see Configuring a Media Pool – Spare Pool. For more information on tape management operations, see Tape Management.

    Media

    Media should be fully utilized and written to until EOM (End of Media). SEP sesam automatically requests a new tape from the corresponding media pool automatically when the tape is full.

    Media utilization can be regulated by:

    • Definition of the media pool retention time.
    • Setting write-protection in a media archive.
    • Media events in the SEPuler.
    • Modifying the locking date of media in an archive to exceed the EOL and executing a media event.

    Media event

    Media selection is triggered by setting events that execute media selection strategies, reinitialize media and prepare media for scheduled backups.

    A media event can be a user-defined event or an internal event created by SEP sesam. For example, if the specified media are not available at the start of a backup or if EOM (End of Media) is reached during data transfer, SEP sesam creates an internal media event that determines the next media for the backup.

    User-defined media events are configured in the GUI and can be any of the following:

    • initialization (a process that prepares the backup media for use with SEP sesam)
    • readability check (a process that checks the readability of the backup data)
    • close tape (a process that marks the tape as full and closes it so that no more data can be stored on it)
    • archive adjustment (a process that scans the media in the selected loader and updates the SEP sesam information about the media status; see Archive adjustment section below for details)

    If the media event contains a specific label, the system will attempt to find it and load it into a drive. The autoloader magazine must be accessible to SEP sesam, otherwise the backup will be blocked.

    GET_OLDEST strategy

    The GET_OLDEST strategy determines which media to use next. If a single media pool is associated with a media event or schedule,, the GET_OLDEST policy is always used. This preserves the data on the media for as long as possible.

    Media are prioritized according to the following criteria:

    • Media whose EOL has expired. (If a saveset is stored on tape, the EOL of all stored savesets must have expired.)
    • The oldest media – media with the oldest locked until (is backup day+ media EOL) date in the media pool.
    • Media that is not write-protected (locked).

    For more details on protecting and reusing media, see below section Savesets Protection: Retention time and EOL.

    Archive adjustment

    Archive adjustment is used to make a comparison between media in the loader (tape library) and the SEP sesam media archive database, and performs database synchronization with the selected loader by updating the database with the latest inventory information of the scanned device. It is mandatory and must be performed whenever new media or used media that have not yet been registered (initialized) by SEP sesam are inserted to identify unrecognized tapes.

    You can perform archive adjustment manually (Main Selection -> Components -> Loader -> Archive Adjustment ) or create a special media event for it and schedule it to run automatically at specified intervals. For more details, see Setting up Archive Adjustment.

    Information sign.png Note
    When selecting the option Archive Adjustment, make sure that the autoloader being realigned is selected in the GUI window, i.e. that the target device is at the top of the adjustment task. If you use the command line, the task must include the name of the target autoloader or tape device.

    Savesets protection: Retention time and EOL

    When configuring SEP sesam environment, you set up media pools and define the retention time. The media pool retention time is specified in days and defines how long the backed up data remains protected after it has been written to the media. This is called the expiration date of the saveset - EOL (End of Lifetime). The retention period starts on the day a saveset is written to the media and lasts for the period defined by the media pool retention time. When the protection expires, SEP sesam can re-use the media for backups again.

    The EOL property can be managed for three object types (as described in detail in Automatic retention management - EOL types):

    Saveset EOL
    The expiration date for a single saveset.
    Backup EOL
    The expiration date for all data belonging to the same backup, including migrated and replicated savesets.
    Media EOL
    The time until which backed up data on tape media remains protected. It refers only to tape media and is based on the longest EOL of all different savesets stored on tape.

    If a saveset is part of a backup chain, its EOL follows the rules of dependency-based retention. When retention is considered only from the perspective of an individual backup, it can ensure data restorability only for that particular backup. To enable complete restore of data backed up in the backup chain, SEP sesam maintains control over the dependencies between backup savesets and provides six rules for dependency-based automatic retention. For more information, see Automatic Retention (EOL) Management.

    The EOL parameter is available in several views, for example, in the Backup task properties or the Saveset properties for Backup EOL and Saveset EOL (Components -> Data Stores -> double-click the selected data store to open the properties -> tab Savesets: columns Backup EOL and Saveset EOL) or for the (tape) Media EOL in Components -> Media -> select one or more tapes -> right-click and select Change Media EOL. For more information, see Changing Retention (EOL).

    Information sign.png Note
    The modified EOL is also recorded in the main log and can be generated for audit trail purposes, see Audit Logging.

    The storage space of a saveset can be re-used when the following conditions are met:

    1. Its EOL has expired. (If a saveset is stored on tape, the EOL of all stored savesets must have expired.)
    2. If a saveset is stored on tape, it must not be write-protected (locked).
    3. Typically, there must be no other savesets that depend on this saveset. You can override this condition by explicitly allowing the EOL for the entire backup chain to expire, thus deleting backup data on all related savesets.

    GFS Backup Retention Strategy

    This article describes the classic GFS backup rotation strategy, where backups stored on tapes are rotated daily. However, there are several backup strategies to protect your environment that can be easily implemented with SEP sesam. For more information, see also Backup Strategy Best Practices.
    A backup rotation scheme is a system of backing up data to storage media (such as tapes). This procedure minimises the number of the used media (by re-use). It determines how and when every piece of the removable storage is used for a backup and how long retention time has backup data stored on it.

    Grandfather-father-son (GFS) backup rotation scheme is a common and most widely used scheme for the backup media. The scheme consists of three or more backup cycles, such as daily (son), weekly (father) and monthly (grandfather), in which the backup sets are rotated through at least two levels of backup: daily incremental backup and full weekly & monthly backup.

    SEP Tip.png Before you start planning a backup strategy, take a look at Backup Strategy Best Practices.

    Implementing GFS with SEP sesam

    Backup tape rotation is an essential part of any data backup plan. You need to decide about the effective data backup strategy. GFS backup rotation scheme provides good protection with a reasonable number of tape sets.

    Steps

    The GFS implementation in SEP sesam requires the following steps:

    1. Create a backup task for every client which needs to be backed up and group them into task groups, such as database bck, VM bck group.
    2. Set up schedules (for the daily, weekly and monthly backups).
    3. Create media pools (for the daily, weekly and monthly backups).
    4. Create backup events (for the daily, weekly and monthly backups).

    Creating a backup task

    First you have to create a backup task for every client which needs to be backed up.

    From the Main Selection -> Tasks -> By Clients, select your client and click New Backup Task. In the New Backup Task window, specify the Source and select what you want to back up. If you want to back up individual files, you can either browse for directories and files that you want to include in the backup or enter their names followed by a comma (C:/Program Files/SEPsesam/var/db,C:\Users\AA\Documents\references). For details on how to create a backup task, see Creating a Backup Task.

    Adding tasks to the task group

    After creating backup tasks, you can group them into task groups to be able to schedule the whole group to start at the same time with one backup event. You can also specify that the whole group is backed up to the same media pool with one backup event. Note that you can add different task types to a group, for example, file backup, MS-SQL backup, VMware backup, etc.

    From Main Selection -> Tasks -> By Groups, click New Task Group. In the New Task Group window, enter the Group name and under Tasks for this group, select the tasks (from the list of all available tasks on the left) and add them to your newly created task group list. For details, see Adding a Task to the Task Group.

    Setting up schedules for the backups

    After creating a backup task and adding it to the task group (optionally), you have to set up 3 schedules (for the daily, weekly and monthly backups).

    From the Main Selection -> Scheduling -> Schedules, click on the New Schedule and define relevant options for your daily, weekly or monthly backups as described below. For details on how to set up a schedule, see Creating a Schedule.

    • Set up a daily schedule DLY_Mo_Thu_2000 with matching start time and daily run from Monday to Thursday.
    • Set up a weekly schedule WLY_Fri_2000 with matching start time and run every Friday.
    • Set up a monthly schedule MLY_last_Sat_2000 with matching start time and run every last Saturday of the month.
    Information sign.png Note
    Scheduling offers the User defined option, which allows you to create a calendar customized to your needs. You can also create special events to prevent scheduled jobs from running on certain dates, or events for running additional jobs on certain dates. For details, see Creating Custom Calendar.

    Creating the media pools

    After setting up the schedules, you have to create 3 media pools (MP_<pool_type>_<frequence>) for the daily, weekly and monthly backups, to store the data to tape.

    From the Main Selection -> Components -> Media Pools -> New Media Pool, specify the backup target, retention time, etc. The retention time of tapes depends on the longest save set's EOL identified on the tape. For details, see Managing EOL.

    • MP_tape_day with a retention time of 5 days
    • MP_tape_week with a retention time 27 days
    • MP_tape_month with a retention time 360 days

    Note that you can configure a special set of options to allow sharing the media across media pools. You can use SPARE media, where SEP sesam allocates media from the spare pool, use EOL-free media, etc. For details, see Media pools.

    Creating the backup events

    In the last step, you have to create the new backup events.

    Information sign.png Note
    A backup chain (the full backup and all subsequent incremental backups) is treated by retention management as if it were a single backup. Note, however, that there is currently no limit to backup chains in SEP sesam. Since long backup chains are inefficient and more vulnerable if something goes wrong because the backups in the chain depend on each other, and because they can simply become too long to restore (no more storage available, takes too long), SEP AG strongly recommends setting up regular FULL backups to avoid such problems, and setting the limit to up to 100 incremental backups.

    From the Main Selection -> Scheduling -> Schedules, right-click the previously created schedule (daily, weekly or monthly) for which you want to create a new event, then click New Backup Event. Define relevant options for your daily, weekly or monthly backup event as described below. For details on how to create a new backup event, see Creating a Backup Event.

    • New backup event for a daily schedule DLY_Mo_Thu_2000:
      1. As a Backup level, select DIFF or INC.
      2. Select the MP_tape_day for the target media pool.
      3. Specify other optional parameters (interface, drive, etc.)
      4. Select the relevant task or task group.
    • New backup event for a weekly schedule WLY_Fri_2000:
      1. As a Backup level, select FULL.
      2. Select the MP_tape_week for the target media pool.
      3. Specify other optional parameters (interface, drive, etc.)
      4. Select the relevant task or task group.
    • New backup event for a monthly schedule MLY_last_Sat_2000:
      1. As a Backup level, select FULL.
      2. Select the MP_tape_month for the target media pool.
      3. Specify other optional parameters (interface, drive, etc.)
      4. Select the relevant task or task group.


    Managing EOL

    Overview

    When configuring SEP sesam environment, you set up media pools and define the retention time. Media pool retention time is specified in days and defines how long the backed up data on media remains protected after the data is written to the medium. The retention time period starts with the date a saveset is written to the medium (at the end time of the first backup) and thus defines the expiration date of the saveset (saveset EOL). When the protection expires, SEP sesam can re-use the media for backups again. This is the basic principle and the simplest scenario.

    However, to ensure restorability of the complete backup chain and to protect from data loss, SEP sesam provides dependency-based retention strategy performed by automated EOL adjustment.

    What is dependency-based retention

    For example, INCR backups require all previous savesets (FULL, DIFF and INCR) to be available for a successful restore. If the retention time is viewed only from the perspective of an individual backup, it can ensure restorability of data for this particular backup only. But to enable the complete restoration of data that was backed up in the backup chain, all dependent backup savesets must be tracked and their retention time must be managed according to their dependencies.

    For example, INCR backup that was taken as the third INCR after the FULL, requires the FULL, the first, the second, and the third INCR to provide complete restore capability. If some saveset in the backup chain is missing, you will not be able to recover your data to a specific point in time. For this reason, SEP sesam maintains control over dependencies among the individual backup savesets and provides dependency-based automated retention.

    SEP sesam also allows you to manually adjust EOL. You can adjust:

    saveset EOL
    You can change the expiration date of any individual saveset that is stored in the data store, see saveset EOL.
    backup EOL
    You can change the expiration date for all backup-related savesets. Unlike saveset EOL, which is applied individually to each selected saveset, changing the backup EOL always affects all dependent backup versions that are part of the same backup, see backup EOL.
    tape media EOL
    Some special rules apply to tape media since the expiration date of the tape corresponds to the maximum retention time (the longest EOL) identified on the tape, see tape media EOL.

    Retention behavior and different EOL parameters

    Typically, you specify a media pool retention time (in days) when creating a media pool. This retention time serves as a basis to determine EOL for backed up data. The retention time period starts with the creation date a saveset is written to the medium and defines the expiration date (EOL) after which the saveset may be deleted. For example, a media pool retention time is 30 days and the data is backed up to the medium on the 1st of January, therefore the saveset EOL is 31st of January. Note that in previous versions (v. ≤ Beefalo) this retention time parameter was called media pool EOL. As the use of this term was misleading, it was removed in Beefalo V2 and replaced with retention time.

    Information sign.png Note
    EOL refers only to backups and related migrated and replicated savesets. SEP sesam logs, readability check logs, calendar sheet entries and restore tasks have separate retention parameters. For details, see retention periods.

    The EOL property can be managed for three object types:

    Saveset EOL

    This is the expiration date for each saveset. If a saveset is a part of a backup chain, its EOL follows the rules of dependency-based retention; EOL of a previous saveset in the chain must be the same or longer to enable the complete restoration of data.

    For example, you specify a media pool retention parameter to 30 days and run a FULL backup. This FULL saveset will initially be kept for 30 days, for example, to the 31st of January. If any following INCR or DIFF saveset in the chain has longer EOL, for example, its expiration date is the 3rd of February, the EOL of all preceding savesets, including the FULL, will be adjusted to the longer expiration date. For details on dependency-based automated retention, see automated EOL adjustment. For details on manually adjusting EOL, see manual EOL adjustment.

    Backup EOL

    This is the expiration date for all data that belongs to the same backup. Backup EOL is determined based on the longest EOL of all savesets that belong to the same backup, including migrated and replicated savesets. For example, adjusting backup EOL of a particular saveset from the 3rd of February to the to 3rd of March results in changed EOL for all related backup data, i.e., original backup, migrated backup, replicated backup, as well as for all backups in a backup chain, if a saveset with adjusted backup EOL is a part of it. For details on dependency-based automated retention, see automated EOL adjustment. For details on manually adjusting EOL, see manual EOL adjustment.

    Information sign.png Note
    How SEP sesam manages failed backups depends on its version. In v. ≥ 4.4.3 Beefalo V2, SEP sesam keeps the failed backup according to media pool retention time together with the last successful backup or migration saveset. This is the default backup retention behavior and can be changed by modifying EOL-related keys, as shown in section Customizing retention policy. These keys may not be supported in earlier versions, where failed backups were automatically deleted after 3 days.

    Tape media EOL

    When a saveset is stored on tape, each stored saveset has its own saveset EOL, but this does not represent the actual expiration date of the tape. Its expiration date corresponds to the maximum retention time (the longest EOL) identified on tape. Only when all savesets on tape have expired and the tape is not locked (write-protected) is the entire tape eligible for re-use. For details on how manually extending EOL affects EOL of the tape media, see Manually extending EOL.

    What happens when EOL is reached

    Once a saveset's end of life is reached, its protection expires. The storage space of an expired saveset is not used immediately; SEP sesam uses the GET_OLDEST policy to preserve the data on the media for the longest possible time. The expired saveset can be re-used if the following conditions are met:

    • As a rule, there must be no other savesets that depend on this saveset. For details, see how SEP sesam handles EOL-related backup chain dependencies. You can override this condition by explicitly allowing the expiration date (EOL) of the whole backup chain to expire, thus deleting the backup data on all related savesets.
    • If a saveset is stored on tape, the EOL of all stored savesets must have expired.
    • SEP sesam Server automatically assigns the medium with the oldest EOL for re-use. The oldest medium is a medium with the oldest locked until (is backup day+ retention time) date in the media pool.
    Information sign.png Note
    If the saveset resides on tape media, the tape will not be re-used until all savesets on it have expired. Tape media EOL always corresponds to the maximum retention time (the longest EOL) identified on the tape. More precisely, a tape media EOL is the maximum EOL of all savesets stored on the tape. Only when the retention time of all savesets on tape has expired and the tape is no longer locked (write-protected) can the tape be re-used. Note that the tape media EOL may also depend on savesets that are not stored on this tape. This is when the tape contains savesets that refer to FULL/DIFF/INCR savesets stored on other media or even data stores.

    Automated EOL adjustment

    In some cases, SEP sesam automatically adjusts EOL to retain the consistency of backed up data and ensures successful restore. Every time EOL is modified, the corresponding information is shown in the main log.

    Managing EOL-related backup chain dependencies

    When a new INCR or DIFF backup is run or an INCR or DIFF backup is migrated, SEP sesam automatically adjusts EOL of all related savesets in order to retain the backup data and keep the backup chain readily available for restore. In some special cases, SEP sesam also automatically increases the EOL of the whole FDI backup chain, thus preventing the backup chains from being orphaned. See below sections for details.

    Increased EOL of a DIFF or INCR saveset

    If the EOL parameter of a DIFF or INCR saveset is increased, SEP sesam will increase EOL of all dependent backups (FULL and other DIFF and INCR). This way SEP sesam ensures that EOL for the FULL backup and other related DIFF and INCR is not shorter than the potentially modified DIFF or INCR saveset's EOL.

    Decreased EOL of a DIFF or INCR saveset

    If EOL of a DIFF or INCR saveset is decreased, SEP sesam will decrease EOL of all dependent backups (FULL and other DIFF and INCR). If you use the Expire function to delete the unneeded saveset(s) or backup set(s), SEP sesam will issue a warning message, prompting you to confirm your decision to expire the entire backup chain.

    SEP Warning.png Warning
    Expiring the DIFF or INCR saveset(s) results in purging and overwriting the complete backup chain!
    Too short EOL of DIFF/INC savesets

    If DIFF/INCR backup detects that a saveset belonging to a FDI chain has too short EOL, then any consecutive DIFF/INCR backup that is running on a pool with longer retention time will increase the EOL of the saveset from the respective pool.

    Information sign.png Note
    If EOL of a saveset belonging to a FDI chain has already expired, it will not be extended. In this case, the DIFF/INCR backup will be executed as a FULL backup.
    Example
    The backup chain has the following retention specified: FULL on pool MONTH (retention time:32), DIFF on pool WEEK (retention time:15) and INCR on pool DAY (retention time:7). EOL of such FDI chain is sufficient, therefore EOL is not modified.

    Allow extending retention time of another media pool for migrated savesets

    Typically, a chain of backup savesets is migrated to one target media pool. You may want to migrate savesets of one backup chain (FULL/DIFF/INCR) to different media pools. There are two ways to change the retention time of migration savesets.

    • You can enable extended retention time for migration by using a specific GLBV: 'gv_adjust_eol_migration_increases_eol_on_other_pool'.
    • You can enable migration to increase EOL of the referenced savesets on other media pools (not only on the target media pool) by adding (or modifying) the following key in global settings in GUI:
      1. In the menu bar, click Configuration -> Defaults -> Settings.
      2. Click [+] to add the following key to global settings (or modify the key value, if it already exists): eol_adjust_migration_on_other_pool|1|sesam
        where value=1 means that the key is active and sesam is the user name. For more details about EOL-related keys, see section Customizing retention policy.
      3. EOL adjust migration Beefalo.jpg


    Last successful backup or migration is automatically retained

    SEP sesam automatically retains the last successful backup or migration saveset when the next backup/migration fails. By extending the EOL of the previous successful backup/migration, SEP sesam ensures that at least one successful backup is retained. This behavior is enabled by default and can be changed by setting the values of the respective keys, eol_adjust_failed_backup and eol_adjust_failed_migration, to 0, as shown in section Customizing retention policy.

    COPY backup fails

    If a COPY backup fails, the EOL of the last successful or with warnings COPY backup is increased to the currently calculated EOL (creation date of the failed backup + media pool retention time).

    Example
    COPY backup in pool MONTH (retention time: 32) fails. SEP sesam checks for previous successful COPY backup in the same pool and increases its EOL, unless the backup EOL is not sufficient, e.g., a migrated saveset exists in the pool YEAR (retention time: 375).
    FULL backup fails

    If a FULL backup fails, the EOL of the last successful or with warnings FULL/DIFF/INCR backup is increased to the currently calculated EOL (creation date of the failed backup + media pool retention time).

    Example
    FULL backup in the pool MONTH (retention time: 32) fails. SEP sesam checks for previous successful or with warnings FDI backup chain in the same pool and increases the EOL of the entire chain (FULL/DIFF/INCR backups), unless the backup EOL is not sufficient, e.g., a migrated FULL saveset already exists in the pool YEAR (retention time: 375).

    Manual EOL adjustment

    It is not recommended to manually adjust EOL. This will override the EOL that was defined by the retention time (in days) in the media pool configuration and was started on the date when a saveset is being written to the media. The following options should be used for special cases and exceptions, for example, to allow premature deletion of an individual saveset or to increase the retention time of a particular backup chain that is to be stored longer than specified by the current EOL.

    • You can modify saveset EOL for each individual saveset that is stored in a data store or on tape media. The saveset EOL parameter is available under several views in GUI, e.g., whenever a task with the savesets is displayed (Job State -> Backups -> double-click a backup task -> Properties -> Saveset EOL, right-click to extend or expire), and under all media-related views, e.g., in the Media, Media Pools and Data Stores properties -> Saveset tab -> Saveset EOL. You can extend or shorten the saveset's retention time by setting the exact expiration date (saveset EOL) in the GUI calendar or directly expire (as of ≥ 4.4.3 Beefalo V2) the saveset by clicking the Expire -> Saveset EOL button. If the adjusted saveset is part of a backup chain, the whole chain might be affected.
    • Additionally, there is also the backup EOL parameter. This is the expiration date for all data belonging to the same backup, including migrated and replicated savesets. You can check and modify the backup EOL parameter by setting the exact expiration date for it by using the calendar function or directly expire (as of ≥ 4.4.3 Beefalo V2) the backup by clicking the Expire -> Backup EOL button. Expiring a backup affects all data belonging to the same backup (entire backup chain), including migrated and replicated savesets.

    For details, see the section how SEP sesam handles EOL-related backup chain dependencies.
    Backup EOL can be found in the Savesets properties that are available under several views in GUI, e.g., whenever a task with the savesets is displayed (Job State -> Backups -> double-click a backup task -> Properties -> Backup EOL) and under all media-related views, e.g., in the Media, Media Pools and Data Stores properties -> Saveset tab -> Backup EOL.

    SEP Tip.png Tip
    As of ≥ 4.4.3 Beefalo V2, you can simply right-click the selected saveset for which you want to modify EOL, for example, in all Media-related views, and then select to either extend EOL or to expire the saveset (individual EOL) or backup (EOL of the entire backup set). But be careful with the expire function as the expired backups are irrevocably lost!

    Right-click EOL.jpg

    Manually reducing EOL

    Note that reducing EOL may result in potential data loss due to the inability to restore from a backup.

    • If you are reducing backup EOL, it is adjusted only for the savesets with EOL longer than the newly given EOL, while the savesets with shorter EOL are not affected (their EOL remains unchanged). As of ≥ 4.4.3 Beefalo V2, you cannot set the expiration date to a time in the past (the minimum allowed date is the current date). However, you can expire backup sets that you no longer need by using the right-click Expire function in any of the views showing the Savesets tab/properties -> Backup EOL -> Expire. Expiring backup EOL terminates the selected backup and all related savesets based on the same backup, including migrated and replicated savesets. This means that all dependent saveset versions that are part of the expired backup are deleted during the next purge.
    • If you are reducing saveset EOL, the new expiration date is set immediately for the selected individual saveset. As of ≥ 4.4.3 Beefalo V2, you cannot set the expiration date to a time in the past (the minimum allowed date is the current date). However, you can expire any individual saveset(s) you no longer need by using the right-click Expire function in any of the views showing the Savesets tab/properties -> Saveset EOL -> Expire. In contrast to the backup EOL approach, expiring saveset EOL only terminates the selected saveset(s) (that is/are deleted with the next purge) unless the saveset(s) is/are part of a backup chain; in the latter case, the entire backup chain is affected as described in Managing EOL-related backup chain dependencies.

    Manually extending EOL

    Extending EOL can be used for special cases, such as increasing the retention time of a particular backup data that has also been migrated and is stored on different media pools. How SEP sesam manages extending EOL depends on its version.

    • If you are extending the backup EOL (expiration date), the EOL is adjusted only for the saveset that already has the longest EOL, while EOL of other backups is not affected. This behavior has changed compared to the previous versions, where extended backup EOL resulted in extended EOL for all savesets based on the same backup, i.e., original backup, migrated backup, replicated backup, as well as for all backups in a backup chain, if a saveset with adjusted backup EOL was part of it. For details, see Manually extending EOL in versions 4.4.3-4.4.3 Grolar.
    • If you are extending the saveset EOL (expiration date) and one of the savesets is part of an FDI backup chain, then the EOL of the previous savesets in the chain will also be increased.
    Information sign.png Note
    • Extending backup EOL of savesets stored on tape media may extend EOL of the tape media! For savesets stored on tape media, a specific retention time that would only apply to one of the stored savesets cannot be set. Each saveset that is stored on tape has its own EOL, but this does not represent the actual expiration date of the tape. Tape media EOL is the maximum EOL of all savesets stored on the same tape. Note that the tape media EOL may also depend on savesets that are not stored on this tape. This is when the tape contains savesets that refer to FULL/DIFF/INCR savesets stored on other media or even data stores.
    • To reduce or increase the tape media EOL (shown as Locked until in the tape properties), you can adjust the media EOL (identified by tape label). Manually adjusted EOL applies to all savesets on tape.
    • If the tape media EOL date has been reached, but the tape should not be re-used, you can also lock the tape (by using write protection). This option overrides media EOL.

    Customizing retention policy

    The default backup retention behavior can be changed by inserting or modifying EOL-related keys in the global settings in GUI: SEP sesam menu bar, click Configuration -> Defaults -> Settings. These keys may not be supported in earlier SEP sesam versions, for details check Managing EOL in versions 4.4.3-4.4.3 Grolar.

    To change the retention policy, you can add or modify the following options.

    EOL-related key Value Description Available from version Note
    eol_adjust_migration_on_other_pool 1 (allow)
    0 (disable)
    Allow extending retention time of another media pool for migrated savesets 4.4.3 Beefalo
    eol_adjust_failed_backup 1 (enable)
    0 (disable)
    Automatic retention of the last successful backup saveset 4.4.3.47 Tigon V2
    eol_adjust_failed_migration 1 (enable)
    0 (disable)
    Automatic retention of the last successful migration saveset 4.4.3.47 Tigon V2
    eol_for_failed_backups 0 (use media pool retention time)
    > 0 (specify the retention time in days, e.g., 3)
    Adjust the retention time (in days) for failed backups 4.4.3 Beefalo V2

    By default, the backup retention policy (retention time of media pool) is applied equally to successful and failed backups. A failed backup is retained for the number of days specified by the retention time of media pool. If you want to free up space on the storage repository and shorten the number of days for retaining failed backups, specify the desired length of the retention for failed backups in days. For example, 3 means that SEP sesam will automatically delete all failed backups after 3 days. 0 (default) means that all failed backups are retained according to the media pool retention time.

    eol_for_failed_not_file_system_backups 0 (use media pool retention time)
    > 0 (specify the retention time in days, e.g., 3)
    Adjust the retention time (in days) for all non-filesystem (non-Path) type backups, e.g., SAP Hana, Exchange Server, VMware vSphere etc. 4.4.3 Beefalo V2 The only difference with the previous parameter (eol_for_failed_backups, see above) is that you can specify the desired length of the retention specifically for all non-filesystem (non-Path) type backups. For example, 3 means that SEP sesam will automatically delete all failed non-filesystem backups after 3 days. 0 (default) means that all failed non-filesystem backups are retained according to the eol_for_failed_backups parameter if set to > 0, or according to media pool retention time if none of the eol_for_failed... parameters is set (value 0).

    The screenshot shows the Defaults -> Settings table with the EOL-related paramaters.

    EOL keys-settings.jpg

    Checking backup chain dependencies

    You can use the saveset tree view in GUI to determine dependencies and EOL of an FDI backup chain. You should use this overview before you manually change the EOL parameter to avoid breaking the backup chain.

    SEP Tip.png Tip
    Checking the saveset tree summary will provide instant information about the location and status of the available savesets for restore. By checking the summary, e.g., availability 5, you can search for savesets that are not readily available, and then migrate them to enable mount and selective restore.

    The saveset tree displays details about a saveset together with potential dependent savesets that belong to the same backup chain. The saveset details are read-only. By providing an overview of the backup chain, you gain insight into the recoverability of backups.

    You can open the saveset tree view by double-clicking the selected backup in the backup list:

    1. From Main Selection -> Job State -> Backups or from Main Selection -> Monitoring -> Last Backup State, double-click the selected backup.
    2. In the backup task properties window, open the tab Savesets.

    Bck chain dependencies-Beefalo.jpg

    The saveset tree displays all savesets that belong to the same backup chain with the following details:

    saveset
    SEP sesam unique identification assigned to a saveset.
    starttime
    The time when the backup was started.
    level
    The backup level used for the saveset: F (FULL), D (DIFF), I (INCR) or C (COPY).

    More detailed information displayed for each saveset:

    pool
    The media pool to which the saveset belongs.
    EOL
    The time when the saveset's protection expires. For details, see section EOL-related backup chain dependencies.
    avail
    The priority number, based on the location of the savesets. It is useful for identifying savesets that are readily available for restore. For example, a saveset in the media pool DAY (data store) is migrated to another pool DeDup and then migrated to tape. The tape will have the lowest avail/priority because it is not readily available for restore. Check also the Availability in the Status at the end of the tree view, which is calculated from the avail of all displayed savesets. See below Availability for details.
    reason
    Explains the above avail – availability of individual savesets for restore. The following information shows the relation between the location and avail/prio. Priority is assigned numerically, where 1 is the lowest priority and 6 (or 7 if called with a specific pool) is the highest.
    TAPE_SINGLE = 0
    TAPE_NOT_IN_LOADER = 1
    DISK_OFFLINE = 2
    TAPE_ONLINE = 3
    DISK_HARD = 4
    DISK_STORE_CLONE = 5 
    DISK_STORE = 6 
    REQUESTED_POOL = 7 (shown if called with a specific pool, e.g., all savesets on the pool DAY and the saveset_tree was called with the target pool DAY)
    
    drivegroup
    Displays the name of the drive group related to the saveset's media pool.
    drives
    The number of the drive that was used for backup.
    labels
    Displays an internal identification of a saveset (a media pool name and a 5-digit number), a potential barcode, prio (numerical representation of availability, see above item), and comment.
    status
    Displays the summary of the savesets availability – status, availability message and a numeric representation. For example, as soon as 1 saveset is migrated to another pool and deleted from the original pool, availability is lowered.

    Save set tree status.jpg


    Part VIII: Backup Strategy

    Backup level

    The following backup levels are available:

    A FULL backup always copies all data specified by the backup task, regardless of whether it has been changed or not. A saveset created as FULL is the basic saveset for subsequent DIFF or INCR savesets. While the backup time of a full backup can be significant, restore is fast and simple since only one backup saveset is required. Information about the backup status is stored in the SEP sesam database. Note that the archive bits are not deleted on Windows systems. If you want to force-reset of the archive bits, you can enter the command -o clear_archive in the backup options.

    A DIFF (differential) backup saves only data which was created or changed after the last FULL saveset had been created (of the same task). A differential backup is faster than a full backup, however, to restore the whole data source, first the saveset of the full backup has to be restored followed by restore of the DIFF saveset. For this, SEP sesam provides generation restore that enables browsing for and selecting for restore all generations of backed up files since the last full backup.

    An INCR (incremental) backup saves only data which was created or changed after the last backup (FULL, DIFF or INCR) of the same task. This is the fastest backup method and requires the least storage space. Restoring from incremental backups is the slowest, because it requires all related savesets to be copied back – the saveset of the last full backup as well as all INC backups. You should consider the advantages of time and resources when planning your backup strategy. A combination of FULL backups stored to tape drives, and DIFF or INC backups stored to virtual disk media is a common method.

    A COPY backup is a full backup that has no influence on following differential (DIFF) or incremental (INCR) backups. For the treatment of archive bits, see FULL backup above. COPY backup is usually used for additional full backups, e.g., monthly backups, or backups for archiving, i.e. removal from storage.

    Information sign.png Note
    In case no initial FULL backup exists, differential (DIFF) or incremental (INCR) backups are automatically performed as FULL backups.

    SEPuler

    SEPuler – an event calendar

    SEPuler is a process that controls the scheduling of all SEP sesam tasks, such as backup, migration, replication, restore and other tasks. It acts as an electronic calendar and assistant performing all SEP sesam data protection events.

    SEPuler is a permanently active background routine (daemon), constantly searching for events to be executed. When SEPuler finds a scheduled task or manually triggered event, the execution of the corresponding program is initiated.

    Once the event has started, SEPuler will determine the next execution event for a cyclical task and rewrite the event to the task calendar. For example, if SEPuler starts a weekly backup on January 1, it will schedule a new weekly backup to occur on January 8.

    Backup, migration, replication, media event, command event, restore and newday are all types of SEPuler events.

    Events initiated with the Immediate start command from the GUI or command line are posted in the calendar as non-recurring events.

    All events in SEP sesam start from the SEPuler schedule, even if they are unique, non-recurring tasks. An overview of scheduled as well as completed, expired events and their current status is provided by Calendar sheet from the Main selection -> Scheduling -> Calendar Sheet.

    GUI schedules Beefalo V2.jpg

    Schedules

    Schedules are used for setting events to occur at a specific time. A schedule is a timetable that defines the cyclic behavior of an event, i.e., when the event is to take place and how frequently to repeat it. The fact that a schedule exists does not automatically mean that an event is executed.

    Only when one or more events (backup, migration, command, etc.) are assigned to the schedule, it becomes active. The entries in the schedule are then picked up by the SEPuler. Modifying a schedule affects all the events assigned to that schedule.

    Flexible scheduling features include the following:

    • Any number of events of the same type can be linked to one or more schedules.
    • A task (backup, migration, replication, media action, restore and command event) may have events in several schedules.
    • Schedules provide User defined option that allows you to create a calendar which is customized according to your country or company specific requirements. You can use it to exclude scheduled jobs from running on specific dates, such as holidays, or to schedule additional jobs on selected dates. For details, see Creating Custom Calendar.
    • A schedule's execution can be deactivated: a schedule will remain displayed as shaded (gray) in the list of schedules, but the related jobs will not run.
    • The option Without Schedule is available, if you set the value for enable_gui_events_without_schedule in the Defaults window (Configuration -> Defaults -> Settings tab) to 1 manually. It shows all backup events which are not assigned to a schedule. Such events are typically created for external backups, where the external applications manage the backup scheduling. For details, see Schedules.

    Event Priority

    For complex event strategies, event priority is used by SEPuler for resolving scheduling conflicts. Priorities can be assigned to events, from lowest (1, default) to highest (99). For each SEP sesam backup day all scheduled events are checked according to their type and priority to see whether the events of the same type (for example, a backup) with the same task name and higher priority have already expired or are still planned to run; in the latter case, SEP sesam suppresses execution of lower priority events of the same type. In other words, if there are more equal events (see equality of events) of the same type scheduled on the same backup day, only the event with a higher priority is executed. This prevents the events that might be linked to several schedules, which overlap on certain days, to be executed except for the one with the highest priority.

    If all equal events of the same type have the same priority (for example, the default – 1), then all of them are executed. Events with priority 0 are not checked for dependency of event priorities and are always executed.

    Priorities can be used together with Blocking date option.

    Information sign.png Note
    Event priority determines which job in a queue will first be executed regardless of the equality of events. If there are jobs in the queue and a new event with a higher priority is activated by SEPuler, this job will first access a busy device.
    Equality of Events

    The equality of events is managed according to their type:

    • Backup events are equal if their task name is the same. The same is true for each individual event type: migration, replication, command and restore event.
    • Media events are equal if their drive number or drive group number is the same.

    Example In the following example, backup of the directory /etc of the client stratum1 with the task name stratum1_etc is started via three different schedules.

    Name Time Priority Task
    Daily 8 p.m. 1 daily incremental
    Weekly 6 p.m. 2 differential on the weekend
    Monthly 9 p.m. 3 full at the end of the month
    • On weekends, the weekend event is performed instead of the daily event (prio 2 overrides prio 1).
    • At the end of the month, the end of month event is performed instead of the daily event (prio 3 overrides prio 1).
    • If the end of the month and the weekend coincide, then the end of month event is performed instead the Weekend event (prio 3 overrides prio 2).

    Event priority Beefalo V2.jpg

    Blocking Events

    A blocking event is any type of event with a higher priority that obstructs another event and prevents it from moving to active backup status. It may be used to prevent the activation of certain events on specific days (e.g., end of year, end of fiscal year, holidays, etc).

    Information sign.png Note
    • A blocking event is created by selecting the Blocking date checkbox during the configuration of an event.
    • Switching off a schedule blocks the execution of all events using this schedule (Execution off option in the schedule).
    • A blocking event only affects other events with the same name when schedules are overlapping.
    • A blocking event suppresses any job with the same task name at respective (SEP sesam backup day) day, regardless of whether it is scheduled to be run before, during or after the blocking event.

    Example

    A backup event that executes the task stratum1_etc is configured to run daily with priority 2. A second backup event for the same task stratum1_etc is only scheduled for December 24th every year as a blocking event with priority 9. On December 24th, the priority check detects the stratum1_etc backup with higher priority and overrides the execution of the daily backup. The blocking event itself does not create an entry in the job status, but sends a notification that it was activated.



    Creating Exclude List

    For each backup, you can back up only selected files, files that match a specific pattern, and exclude specific files, file types or directories from backups.

    Some files are only temporary, while others are permanently in use. These files should either be excluded from normal backup or backed up in a special way. For example, you may not want to back up temporary (.tmp) files, read-only files, or files from specific directories (e.g., the download directory). SEP sesam provides a number of ways to set exclusions:

    Exclude list in the GUI

    When creating a backup task, you specify the source for your backup and define any files or patterns you want to exclude from the backup. Note that if the number of files to be excluded from the backup exceeds the allowed length for the exclude list, you should set up the exclusion as described in the section Create a custom exclude list on the client. Such a custom exclude list (e.g., -X C:/sesam/exclude_list.txt) takes precedence over an exclude list set in the GUI.

    1. From Main Selection -> Tasks -> By Clients, select your client and click New Backup Task. The New Backup Task window opens.
    2. Specify the Source. If you want to back up individual files, you can either browse for directories and files to include in the backup or enter their names followed by a comma (C:/Program Files/SEPsesam/var/db,C:\Users\AA\Documents\references). If you want to back up the entire file system, enter all as the source. If you only want to back up files that match a specific pattern, use the include list instead. Note that if you select the source by browsing, the task type and task name are set automatically. If you enter the source manually, you have to enter the task name and select the appropriate task type.
    3. In the Exclude list, specify the files or folders you do not want to back up in one of the following ways:
      Exclude using the browse button
      The easiest way to exclude specific files or folders from backup is to use the large browse button (next to the fields Source and Exclude list) and select the source for exclusion in the Client File View window. In our example, we have excluded logs and program files from the backup, as shown in the screenshot below.
      Basic exclude list Beefalo V2.jpg
      Add files, file types or regular expressions in the Exclude list editor
      In the Exclude list editor, you can specify exclusions using regular expressions. On Windows, you can also use the option Pattern exclude, but on Linux it is only possible to exclude using regular expressions (regex exclude).
      Add the exclusion patterns one after the other, followed by a comma. The procedure for using regex exclude is SEP sesam version dependent. For more details, see Exclude with Regular Expressions. Exclude list Beefalo V2.jpg
      Click OK.

    For more examples of exclusions using regular expression patterns, see Examples for Excluding Matched Patterns.

    Information sign.png Note
    Exclude using regular expressions is the default setting, but you can change it to use the file pattern (?,*) instead of regex by modifying the configuration file <SESAM_VAR>/var/ini/sm.ini on the SEP sesam Client. In the config file sm.ini change the entry
    EXCLUDE_MATCH= REGEXP to EXCLUDE_MATCH= PATTERN.

    Create a custom exclude list on the client

    You can specify a custom exclude list of items to be skipped during backup by creating a special file on SEP sesam Client. Typically, you would create a separate exclude file if the number of files or directories to be excluded for backup exceeds the allowed length for the exclude list (max. 1024 characters). Such a custom exclude list takes precedence over an exclude list specified in the GUI (the latter is ignored if both are specified).

    A custom exclude list must be a text file that is created on the SEP sesam Client where the backup will be executed. The syntax for exclude entries is platform/OS dependent, see:

    Once you have created the exclude file, for example exclude_list.txt, enter it in the backup task properties as follows:

    Create or open the backup task, select the Options tab and under Additional call arguments in the Backup options field, enter the specified file in the form:

    -X C:/sesam/exclude_list.txt 
    

    Exclude list on Linux

    Create the exclude file on the client in the directory /etc/sesam, for example /etc/sesam/exclude_list.txt. The following rules apply:

    • Each file or directory you want to exclude from the backup must be specified on a separate line (one entry per line).
    • Wildcards are not supported.
    • The exclusion entries have to be set up using regular expression syntax.

    This is an example of the exclude_list.txt on Linux:

     \./tmp$
     \./home/John Doe/videos.zip$
     \./home/John Doe/Business Documents/YearEnd Closing for business year 2021$
    

    Exclude list on Windows

    Create the exclude file on the client in the directory C:\Program Files\SEPsesam\var\ini, for example exclude_list.txt. The following rules apply:

    • Use only / (slash) in the exclude file and NOT \ (backslash).
    • Each file or directory you want to exclude from the backup must be specified on a separate line (one entry per line). This also applies to paths that contain spaces.

    This is an example of the exclude_list.txt file on Windows:

    D:/DOWNLOAD
    D:/PREKITS
    D:/Dev
    D:/kit_2_3_1_7
    D:/kit_2_3_1_5
    D:/knoppix
    D:/ACHIM
    D:/gui
    

    Exclude list for Micro Focus OES (formerly Novell OES)

    Create the exclude file on the client in the directory /etc/sesam, for example /etc/sesam/exclude_list.txt. The following rules apply:

    • Each file or directory you want to exclude from the backup must be specified on a separate line (one entry per line).
    • Use only the pattern format for exclude.
    • Wildcards are allowed in the file or directory entries.
    • A folder to be excluded must end with a / (slash).


    This is an example of the exclude_list.txt file:

    /media/nss/VOL1/tmp/
    /media/nss/VOL1/USR/*/Notes/Workspace/
    /media/nss/VOL1/data/do_not_backup.txt
    

    For example, /media/nss/VOL1 is set as the source in the backup task. This means that the entire contents VOL1 will be backed up, except for the items in the exclusion file specified by the following entry in the backup task properties -> Options tab -> Backup options (previously Save options) field:

     -X /etc/sesam/exclude_list.txt
    

    SEP sesam will exclude from backup all files and directories that are listed in the file.

    Creating a special file nosbc to permanently exclude a directory

    You can permanently exclude a directory from all backups on the client by creating a special file in the directory itself – this file is called .nosbc on Unix or nosbc on Windows. By creating such a file in the directory, the directory will not be backed up, even if it is included in the specified source.

    This behavior can be switched off for a specific backup task by entering the -o noexcl switch in the backup task properties, tab Options -> Backup options.

    Using sm.ini to completely exclude files from backups on the client

    You can use the central SEP sesam config file sm.ini to specify the files on the client that should never be backed up. The advantage of this method is that you can exclude files or directories from all backups performed on the respective client.

    The default location of the sm.ini file is <SESAM_ROOT>\var\ini\sm.ini.

    To define the exclusions for the client, open the sm.ini file and under the parameter SBC_EXCLUDE enter one parameter per line.

    • On Linux, use regular expressions to define the exclusions in sm.ini. The following example shows the pattern for excluding the directories /dev, /mnt and /media from backup.
    • [SBC_EXCLUDE]
      ExcludePattern1=\./mnt$
      ExcludePattern2=\./dev$
      ExcludePattern3=\./media$
      
      Information sign.png Note
      The ExcludePattern900 and higher exclude parameters are used for SEP sesam specific exclude patterns. To define your own exclude patterns, use the parameters ExcludePattern1 to ExcludePattern899.
    • On Windows, use file patterns to define the exclusions in sm.ini. This allows you to exclude files that match the specified names or paths (note that <file_name> can also contain wildcard characters, e.g., * and ?).


    Preparing for disaster recovery: Configuring SESAM_BACKUP

    To prepare for a possible breakdown of the SEP sesam Server, you need to perform a self-backup of the SEP sesam installation. This means that you have to configure at least one backup task named SESAM_BACKUP. This backs up the configuration files of SEP sesam, the var directory including all listings, the log files, the database and the INI-files. See Configuration Files.

    To ensure consistent configuration after restoring from backup, this backup should be run daily, either in COPY or FULL mode. For details, see the section Preparing for Disaster Recovery.

    Also, a disaster interface must be properly configured to support the disaster recovery process: sm_disaster (Linux) or sm_disaster.cmd/sm_disaster.ps1 (Windows). The disaster interface sends an email with a description of the disaster recovery process and an attachment that contains the SEP sesam bootstrap database with all the important data for disaster recovery. For details on how to activate this interface, see the section Preparing for Disaster Recovery.

    The self-backup procedure consists of the following:

    • When the SEP sesam self-backup starts (SESAM_BACKUP), the entire SEP sesam database is exported to the path <SESAM_ROOT>/var/<db>[_pg]/backup. The export files have names like sesam_db_20121223-20121224060003.sql.gz and are backed up to a predefined media pool. It is recommended that you configure a SEP sesam DR-dedicated media pool for storing all your SEP disaster recovery savesets.
    • Each time SESAM_BACKUP is run, a bootstrap file of the SEP sesam database (for example, sesam_bootstrap_db_[datetime].sql.gz) is exported to the <SESAM_ROOT>/var/db[_pg]/backup directory. This file contains the SEP sesam configuration and the data history of the SEP sesam self-backups of the last 30 days.
    • sm_disaster copies the content of input arguments (DISASTER or SESAM_BACKUP) from the SEP sesam Server to predefined locations on another computer (emails, copies of files, etc.). Information about the last disaster backup from SEP sesam is also stored.
    • Finally, an email with a brief description of the recovery and the bootstrap file as an attachment is sent regularly to the email address you configured. The bootstrap export is used exclusively for SEP sesam disaster recovery, so you should save any version of this file in a safe place.

    To fully utilize the disaster recovery functionality and ensure that all disaster-relevant information is generated and sent, the following steps must be performed:

    1. The backup task SESAM_BACKUP is normally configured after the installation of a SEP sesam Server. So it should already exist. If this is not the case, you have to configure it:
      Open the GUI and select in the Main selection -> Tasks -> By Clients -> your SEP sesam Server -> New Backup Task. The name of the backup task must be SESAM_BACKUP. It normally includes the directories <SESAM_ROOT>/var and <SESAM_ROOT>/bin/sesam and excludes the directories work and log. Click OK to save the task.
    2. SEP sesam backup task Beefalo V2.jpg

      SEP Tip.png Tip
      Disaster recovery is performed with log level 0. If required, you can set a higher log level for the restore in the properties of the backup task SESAM_BACKUP -> Options tab -> Restore options field. For details, see Setting log level on a per-task basis in GUI.
    3. Once your disaster recovery task is configured, set up a backup schedule (GUI -> Scheduling -> Schedules). The SEP sesam backup should run at a time when no other activities are running in the SEP sesam environment. It is recommended to run this task every day. For details on scheduling, see Creating a Schedule.
    4. Create an event to associate with the schedule. Select the backup level COPY. It is recommended that you select a disaster recovery dedicated media pool for storing all your disaster recovery savesets. For general information about creating a backup event, see Creating a Backup Event.
    5. Activate the inteface sm_disaster: From the SEP sesam GUI menu, select Configuration -> Interfaces -> Disaster Interface. A window with the interface script is displayed.
    6. Activate disaster interface Beefalo V2.jpg

    7. Click Save to confirm the dialog. The file sm_disaster is read and stored in the directory <SESAM_ROOT>/bin/sesam.
      Tip: After installing SEP sesam, the file sm_disaster (Linux) or sm_disaster.cmd/sm_disaster.ps1 (Windows) is located in the directory <SESAM_ROOT>/skel/templates/. Alternatively, you can activate the disaster interface by copying sm_disaster from <SESAM_ROOT>/skel/templates to <SESAM_ROOT>/bin/sesam.
      Information sign.png Note
      The sm_disaster file has been completely redesigned for SEP sesam version 4.4.2. If your SEP sesam Server version is 4.4.2 or lower, you must replace the sm_disaster file after updating to SEP sesam Server 4.4.2:
      • Windows: The MSI Installer will ask you if you want to overwrite the existing interface. Choose <yes> to overwrite the existing interface. Alternatively, copy <SESAM_BIN>/skel/templates/sm_disaster.ps1 to <SESAM_BIN>/bin/sesam/sm_disaster.ps1.
      • Linux: Copy <SESAM_BIN>/skel/templates/sm_disaster to <SESAM_BIN>/bin/sesam/sm_disaster to get the latest version of the disaster interface.
    8. Configure the SEP sesam email for the sesam account so that the interface sends messages after self-backup: From the GUI menu, select Configuration -> Email Settings -> New. An Email Account window is displayed.
      • In the Account field, type the name sesam (it must be lowercase).
      • Optionally, enter the name in the Customer field.
      • Enter the name of the sender (the name of the respective SEP sesam Server).
      • Enter the name or IP address of the outgoing mail server in the SMTP server field.
      • In the SMTP user field, enter the user name for the SMTP server. If the SMTP user name is not specified, the SMTP server probably does not require authorization.
      • If the mail server requires authentication, enter the password in the Password field.
      • Optionally, specify the SMTP port.
      • In the Recipient field, enter the address of the recipient of the DR notification emails. This is usually the address of the backup administrator.
      • Optionally, you can specify additional recipients in the CC and BCC fields.
      Create e-mail account Beefalo V2.jpg


    Part IX: Configuration Tips

    How to check DNS configuration

    Overview

    Certain problems can occur when configuring new clients in SEP sesam if the DNS server is incorrectly configured or missing. SEP sesam needs a correct DNS to work and will not work with just an IP address. All DNS names must be correctly resolved (forward and reverse DNS lookup).

    If the DNS server is missing, you will have to use the hosts file of the client and backup server to make systems available via a DNS name. The hosts file can be found in the following locations:

    Linux
    /etc/hosts
    
    Windows
    C:\Windows\system32\drivers\etc\hosts
    
    Information sign.png Note
    The hostname of the SEP sesam server may not include an underscore "_" sign. For hostname restrictions, see Restrictions on valid host names.

    Tools for checking DNS resolution

    Several tools are available to check DNS resolution. However, SEP recommends the use of sm_setup check_resolution.

    sm_setup check_resolution (recommended)

    The SEP sesam sm_setup tool is part of the SEP sesam Client and Server installation and can be used from the command line to resolve DNS names. Before using this tool, you need to set up a SEP sesam profile as described in FAQ: What happens when I set up a profile?

    SEP recommends that you run this command on the backup server AND on the client with the same arguments. It is important that the client and the backup server are resolved correctly.

    Syntax
    Client:~ # sm_setup check_resolution backupserver
    Calling getaddrinfo with 'backupserver'
    
            Official name: backupserver.sep.de
            IPv4 Address #1: 172.16.1.146
    
    Calling getnameinfo for IP Address #1 '172.16.1.146'
    
            Official name: backupserver.sep.de
            Alternate name: backupserver
    
    Client:~ # sm_setup check_resolution client
    Calling getaddrinfo with 'client'
    
            Official name: client.sep.de
            IPv4 Address #1: 172.16.1.145
    
    Calling getnameinfo for IP Address #1 '172.16.1.145'
    
            Official name: client.sep.de
            Alternate name: client
    
    


    Backupserver:~ # sm_setup check_resolution client
    ' Calling getaddrinfo with 'client'
    
            Official name: client.sep.de
            IPv4 Address #1: 172.16.1.145
    
    Calling getnameinfo for IP Address #1 '172.16.1.145'
    
            Official name: client.sep.de
            Alternate name: client
    
    
    Backupserver:~ # sm_setup check_resolution backupserver
    Calling getaddrinfo with 'backupserver'
    
            Official name: backupserver.sep.de
            IPv4 Address #1: 172.16.1.146
    
    Calling getnameinfo for IP Address #1 '172.16.1.146'
    
            Official name: backupserver.sep.de
            Alternate name: backupserver
    


    The returned addresses and hostnames must match. If the reverse resolve returns an official name that is different from the name specified on the command line, problems will occur when backing up the client (see Common error messages).

    nslookup (Windows and Linux)

    The nslookup tool is a network administration command-line tool for querying the DNS to obtain a hostname or IP address.

    It is useful for troubleshooting DNS issues, but not for full hostname resolution as it ignores the hosts file. SEP sesam resolves its hostnames via the "common library function" and first uses the hostname specified in the hosts file of the system. By default, nslookup translates a domain name to an IP address (or vice versa).

    Use the nslookup command to check that the name resolution is correct: forward with and without FQDN as well as reverse. Check on the SEP sesam Server AND on the SEP sesam Client. If DNS is not used and the verification done via the etc/hosts file, use ping to check individual clients.

    Syntax
           nslookup {client}
           nslookup {IP-Address of client}                         # important reverse lookup
           nslookup {SEPsesam Server name}
           nslookup {IP-Address of SEPsesam Server}                # important reverse lookup
    

    Example: check mysesam name resolution and reverse lookup:

         #>nslookup mysesam
         Server:   dns.domaine.de
         Address:  192.168.1.254
    
         Name:     mysesam.domaine.de
         Address:  192.168.1.1
    
         #>nslookup 192.168.1.1
         Server:   dns.domaine.de
         Address:  192.168.1.254
    
         Name:     mysesam.domaine.de
         Address:  192.168.1.1
    

    host (Linux only)

    The host command can also be used to resolve a hostname into an IP address and vice versa. It defaults to the name server configured in /etc/resolv.conf but can also be used with a DNS server as an additional argument. It will query the DNS server of the system first.

    Syntax
    Client:~ # host backupserver
                         backupserver.sep.de has address 172.16.1.146
    
    
    Client:~ # host 172.16.1.146
                         146.1.16.172.in-addr.arpa domain name pointer backupserver.sep.de
    

    ping

    ping is a network administration software utility used to test the reachability of a destination device on an IP network via ICMP echo request. It is not a suitable tool for checking DNS resolution and will not always be 100% correct. Although ping resolves an IP address, it is not strictly a name server lookup tool and may return a potentially outdated cached result.

    In addition, it is not possible to correctly reverse resolve DNS names. For more details, see the ping description on Wikipedia.

    Common error messages

    The following common error messages indicate that there is a problem with your name resolution:

    CLIENT_HOSTNAME: Login to stpd from <CLIENT_HOSTNAME> to <SESAM_SERVER_HOSTNAME> incorrect.
    
    Login incorrect. Client resolves his IP address [X.X.X.X] to [RANDOM_HOSTNAME], but server resolves it to [X.X.X.X]. Please adjust your name resolution.  (0)
    

    In this case, check your name resolution (DNS or etc/hosts file). The SEP sesam Server and the SEP sesam Client must be reachable with or without FQDN and should be able to resolve each other and also themselves correctly, including reverse lookup.

    If you have changed an entry in your DNS configuration, but Windows still reports a wrong hostname/IP, try running ipconfig /flushdns as administrator.

    Using Pre and Post Scripts

    Overview

    SEP sesam enables system administrators to perform additional actions before and/or after a backup or restore by using pre or post scripts.

    Pre backup scripts are executed before backup jobs starts to perform specific operation. Typically, they are used to create commands that will stop or start the selected programs, for example, to stop a database or antivirus service before the backup. Similarly, pre restore scripts are executed before the restore starts.

    Post backup scripts are executed when the backup session stops to perform specific tasks, such as starting a database or shutting down a computer after the backup. Post restore scripts are executed after the restore, for example, to start a database.

    Pre and post scripts are represented as one of the SEP sesam interfaces. They are configurable programs hat can be programmed with any text editor. Pre and post scripts are not provided by SEP sesam; you must create your own scripts to perform the desired actions.

    Unlike other SEP sesam interfaces, pre/post interfaces apply only to a specific client; they are created for each client individually and run only on the selected client.

    Information sign.png Note
    Configuring pre and/or post scripts is optional. The pre/post interface may affect the execution of backups or restores. When creating a script, keep in mind that a pre/post script should not take a lot of time, as it can delay a backup or restore.

    To use the pre/post script, you have to activate the relevant interface first and then create your own script.

    Configuring pre and post scripts

    SEP sesam provides several interface templates. They are located in the SEP sesam directory <SESAM_ROOT>/skel/templates. You can activate them automatically via the GUI (recommended) or manually by copying them.

    Activating interfaces via SEP sesam GUI

    1. From Configuration -> Interfaces, select the relevant interface type (Pre or Post) that you want to activate.
      Activating interfaces Beefalo V2.jpg
    2. The Edit Pre/Post Interface window opens: Select Backup or Restore interface and the client on which you want to run the script. Click OK.
      Edit pre interface Beefalo V2.jpg
    3. A new window with the Edit <name> interface script opens, allowing you to configure (insert) a specific action at the end of the script.
      Information sign.png Note
      • Before the end of the procedure either STATUS:OK or STATUS:ERROR {text} must be written to the standard output.
      • If you want to change a backup source, STATUS: messages have to include keyword BACKUP_SRC=, for example, STATUS:OK BACKUP_SRC=C:,F:/DATA. In this case, the backup will use this source instead of the source defined in a backup task.

      Pre interface Beefalo V2.jpg

      • For example, you may want to shut down a specific computer after the backup is finished. To configure this action, you have to select Post backup interface for a relevant client and add the following lines at the end of the sbc_post script:
        • For Windows
        • #=== Please insert your specific actions here ===================================== 
          echo "shutdown -s -t 120"
          shutdown -s -t 120
          rem echo STATUS:ERROR {message}
          echo STATUS:OK
          exit
          
        • For Linux:
        • echo "shutdown -h +2"
          shutdown -h +2
          
    4. This action invokes a shutdown of the computer two minutes after the backup has finished.
      • The first line shutdown ... is the message which is written to the Post log file during the backup.
      • If the post process ends with an error, the backup is completed with the Warning status.
    5. After configuring a relevant pre or post action, click Save to activate the interface on a specific client.

    When you save the template, the script is read and copied to the <SESAM_ROOT>/bin/sesam folder. Now you have to add a pre/post script to backup or restore tasks.

    For more examples of how to use pre and post scripts, see Configuring ownCloud restore.

    Manual activation of interfaces

    Alternatively, you can activate the interfaces by copying the existing templates from the SEP sesam directory <SESAM_ROOT>/skel/templates under the name:

    sbc_pre
    sbc_post
    

    into the <SESAM_ROOT>/bin/sesam directory.

    Selecting a pre/post script for backup or restore

    After configuring the desired pre/post actions, specify whether to apply a pre/post script to a specific client by adding the script to the backup or restore task.

    Selecting a pre/post script for backup

    You can select to run a pre/post script when you create a backup task or apply it to an already configured task. For details on how to create a new backup task, see Creating a Backup Task.

    1. From Main Selection-> Tasks-> By Clients, select your client and double-click it or click New Backup Task. The Properties or New Backup Task window opens. Switch to the Options tab.
      Tasks options Beefalo V2.jpg
    2. Depending on the desired action, select either Execute pre or Execute post backup and/or restore option(s):
      • Execute pre: Enable it if you want to run the pre script for this backup task.
      • Execute post: Enable it if you want to run the post script for this backup task.
      • Ignore pre error: Enable it to allow to force start the backup even if the pre script was not properly executed.
      • Ignore backup error: Enable it to allow the post script to run after a failed backup.
    3. Click OK to enable execution of the pre/post script for the selected task.

    Selecting a pre/post script for restore

    You can select to run a pre/post script when creating a restore task or apply it to an already configured task (Main Selection -> Job State -> Restores -> open Properties). For details on how to create a new restore task, see Standard Restore Procedure. In both cases, you can select to run a pre/post script under the Expert Options.

    Information sign.png Note
    The Expert Options button for specifying advanced restore options is available only in advanced UI mode (formerly expert GUI mode). To use Expert Options, make sure your UI mode is set to advanced. For details, see Selecting UI mode.
    1. In the Target Settings dialog, click Expert Options, and then select the Pre/Post tab.
      Restore pre post Beefalo.jpg
    2. Depending on the action you want to take, select either Execute pre or Execute post restore option(s):
      • Execute pre: Enable it if you want to run the pre script for this restore task.
      • Execute post: Enable it if you want to run the post script for this restore task.
      • Start restore in spite of pre error: Enable it to allow to force start the restore even if the pre script was not properly executed.
      • Start post in spite of restore error: Enable it to allow the post script to run after a failed restore.
    3. Click OK to enable execution of the pre/post script for the selected task.


    Part X: Appendices

    How to start and stop SEP sesam

    Overview

    After the installation, the SEP sesam software will start automatically. You can use the command sm_main status to see if all processes are running. You can start and stop the SEP sesam services manually by using the commands below.

    Start/stop SEP sesam on Windows

    One central SEP sesam service is running on Windows systems. It is called SEP Sesam and is running under the system account of the Windows operating system. This service starts all other required services.

    Start
    • using the Windows services control panel
    • in Windows Task Manager using the Services tab
    • on CMD or Powershell: net start sm_main
    • on CMD or Powershell: <SESAM_BIN>\bin\sesam\sm_main start
    • on CMD or Powershell: <SESAM_BIN>\bin\sesam\sm_startup -f
    Stop
    • using the Windows services control panel
    • in Windows Task Manager using the Services tab
    • on CMD or Powershell: net stop sm_main
    • on CMD or Powershell: <SESAM_BIN>\bin\sesam\sm_main stop
    • on CMD or Powershell: <SESAM_BIN>\bin\sesam\sm_shutdown -f

    Start/stop SEP sesam on Linux

    One central SEP sesam service is running on Linux systems that controls all other SEP sesam services. SEP sesam services are always running under the Linux root user account. Depending on the Linux distribution, the following commands can be used:

    Start
    • in the Linux shell: /etc/init.d/sesam start (distrib. with INIT start system)
    • in the Linux shell: systemctl start sepsesam.service (distrib. with SYSTEMD start system)
    • in the Linux shell: <SESAM_BIN>/bin/sesam/sm_main start
    • in the Linux shell: <SESAM_BIN>/bin/sesam/sm_startup
    Stop
    • in the Linux shell: /etc/init.d/sesam stop (distrib. with INIT start system)
    • in the Linux shell: systemctl stop sepsesam.service (distrib. with SYSTEMD start system)
    • in the Linux shell: <SESAM_BIN>/bin/sesam/sm_main stop
    • in the Linux shell: <SESAM_BIN>/bin/sesam/sm_shutdown


    How to check DNS configuration

    Overview

    Certain problems can occur when configuring new clients in SEP sesam if the DNS server is incorrectly configured or missing. SEP sesam needs a correct DNS to work and will not work with just an IP address. All DNS names must be correctly resolved (forward and reverse DNS lookup).

    If the DNS server is missing, you will have to use the hosts file of the client and backup server to make systems available via a DNS name. The hosts file can be found in the following locations:

    Linux
    /etc/hosts
    
    Windows
    C:\Windows\system32\drivers\etc\hosts
    
    Information sign.png Note
    The hostname of the SEP sesam server may not include an underscore "_" sign. For hostname restrictions, see Restrictions on valid host names.

    Tools for checking DNS resolution

    Several tools are available to check DNS resolution. However, SEP recommends the use of sm_setup check_resolution.

    sm_setup check_resolution (recommended)

    The SEP sesam sm_setup tool is part of the SEP sesam Client and Server installation and can be used from the command line to resolve DNS names. Before using this tool, you need to set up a SEP sesam profile as described in FAQ: What happens when I set up a profile?

    SEP recommends that you run this command on the backup server AND on the client with the same arguments. It is important that the client and the backup server are resolved correctly.

    Syntax
    Client:~ # sm_setup check_resolution backupserver
    Calling getaddrinfo with 'backupserver'
    
            Official name: backupserver.sep.de
            IPv4 Address #1: 172.16.1.146
    
    Calling getnameinfo for IP Address #1 '172.16.1.146'
    
            Official name: backupserver.sep.de
            Alternate name: backupserver
    
    Client:~ # sm_setup check_resolution client
    Calling getaddrinfo with 'client'
    
            Official name: client.sep.de
            IPv4 Address #1: 172.16.1.145
    
    Calling getnameinfo for IP Address #1 '172.16.1.145'
    
            Official name: client.sep.de
            Alternate name: client
    
    


    Backupserver:~ # sm_setup check_resolution client
    ' Calling getaddrinfo with 'client'
    
            Official name: client.sep.de
            IPv4 Address #1: 172.16.1.145
    
    Calling getnameinfo for IP Address #1 '172.16.1.145'
    
            Official name: client.sep.de
            Alternate name: client
    
    
    Backupserver:~ # sm_setup check_resolution backupserver
    Calling getaddrinfo with 'backupserver'
    
            Official name: backupserver.sep.de
            IPv4 Address #1: 172.16.1.146
    
    Calling getnameinfo for IP Address #1 '172.16.1.146'
    
            Official name: backupserver.sep.de
            Alternate name: backupserver
    


    The returned addresses and hostnames must match. If the reverse resolve returns an official name that is different from the name specified on the command line, problems will occur when backing up the client (see Common error messages).

    nslookup (Windows and Linux)

    The nslookup tool is a network administration command-line tool for querying the DNS to obtain a hostname or IP address.

    It is useful for troubleshooting DNS issues, but not for full hostname resolution as it ignores the hosts file. SEP sesam resolves its hostnames via the "common library function" and first uses the hostname specified in the hosts file of the system. By default, nslookup translates a domain name to an IP address (or vice versa).

    Use the nslookup command to check that the name resolution is correct: forward with and without FQDN as well as reverse. Check on the SEP sesam Server AND on the SEP sesam Client. If DNS is not used and the verification done via the etc/hosts file, use ping to check individual clients.

    Syntax
           nslookup {client}
           nslookup {IP-Address of client}                         # important reverse lookup
           nslookup {SEPsesam Server name}
           nslookup {IP-Address of SEPsesam Server}                # important reverse lookup
    

    Example: check mysesam name resolution and reverse lookup:

         #>nslookup mysesam
         Server:   dns.domaine.de
         Address:  192.168.1.254
    
         Name:     mysesam.domaine.de
         Address:  192.168.1.1
    
         #>nslookup 192.168.1.1
         Server:   dns.domaine.de
         Address:  192.168.1.254
    
         Name:     mysesam.domaine.de
         Address:  192.168.1.1
    

    host (Linux only)

    The host command can also be used to resolve a hostname into an IP address and vice versa. It defaults to the name server configured in /etc/resolv.conf but can also be used with a DNS server as an additional argument. It will query the DNS server of the system first.

    Syntax
    Client:~ # host backupserver
                         backupserver.sep.de has address 172.16.1.146
    
    
    Client:~ # host 172.16.1.146
                         146.1.16.172.in-addr.arpa domain name pointer backupserver.sep.de
    

    ping

    ping is a network administration software utility used to test the reachability of a destination device on an IP network via ICMP echo request. It is not a suitable tool for checking DNS resolution and will not always be 100% correct. Although ping resolves an IP address, it is not strictly a name server lookup tool and may return a potentially outdated cached result.

    In addition, it is not possible to correctly reverse resolve DNS names. For more details, see the ping description on Wikipedia.

    Common error messages

    The following common error messages indicate that there is a problem with your name resolution:

    CLIENT_HOSTNAME: Login to stpd from <CLIENT_HOSTNAME> to <SESAM_SERVER_HOSTNAME> incorrect.
    
    Login incorrect. Client resolves his IP address [X.X.X.X] to [RANDOM_HOSTNAME], but server resolves it to [X.X.X.X]. Please adjust your name resolution.  (0)
    

    In this case, check your name resolution (DNS or etc/hosts file). The SEP sesam Server and the SEP sesam Client must be reachable with or without FQDN and should be able to resolve each other and also themselves correctly, including reverse lookup.

    If you have changed an entry in your DNS configuration, but Windows still reports a wrong hostname/IP, try running ipconfig /flushdns as administrator.

    About Authentication and Authorization

    Overview

    SEP sesam introduces new authorization concept to grant and restrict access to SEP sesam Server, specific clients and locations. Note that authentication is the first step of authorization. This means that first the identity of a user who is accessing a SEP sesam Server is authenticated by verifying a user credentials (username and password).

    After successful authentication starts the authorization, when SEP sesam validates if an authenticated user has appropriate permissions for accessing a specific resource or operation within SEP sesam Server.

    Authorization is implemented through the following elements:

    • Permissions based on user type
      Users can connect to SEP sesam Server only if they are granted appropriate permissions. Their user rights depend on the user type. SEP sesam user types are admin, operator and restore.
      • Admin is the only user role with full control over the SEP sesam.
      • The Operator monitors the SEP sesam Server backup status.
      • The Restore user is only allowed to start restores.

      Note that the displayed GUI components depend on the user type. For details on GUI elements, see SEP sesam GUI.

    • Access Control Lists (ACLs)
      ACL specifies which users or groups are granted access to specific objects. As of SEP sesam version 4.4.3 Grolar, you can configure ACLs for locations and clients, if you have the admin rights. For details on ACLs configuration, see Using Access Control Lists.

    After the initial installation of SEP sesam, no users are configured except the administrator. Depending on version, SEP sesam provides different authentication methods that are mutually exclusive: database-based authentication (for v. ≥ 4.4.3 Tigon) which is simply called authentication, and policy-based authentication (for all SEP sesam versions). By default, policy-based authentication is active. Note that only one authentication method can be active at any time.

    Information sign.png Note
    In SEP sesam v. ≥ 4.4.3 Tigon, you can bypass authentication for local server for all users by setting the parameter localFullAccess in the <SESAM_ROOT>/var/ini/sm.ini file to true as described in the section below.

    Database-based authentication

    SEP sesam provides database-based authentication that allows administrators to configure users and grant them appropriate permissions to perform SEP sesam operations by setting individual passwords and assigning users to the relevant user group.

    As of 4.4.3 Grolar, SEP sesam can be configured to use LDAP/AD authentication in combination with database-based authentication. This way SEP sesam can authenticate users against an external LDAP/AD directory. If LDAP/AD authentication is enabled in SEP sesam and the users are mapped correctly, they can log in to SEP sesam according to their entry in the LDAP/AD directory and the user mapping information. For details, see Configuring LDAP/AD Authentication.

    The assigned user group (based on user type) determines the actions that the group members can perform. The database-based authentication can be enabled from GUI by activating authentication under the Configuration ‐> Permission Management. This is the only way to set the password for the Administrator.

    If the DB-based authentication is activated via GUI, the authEnabled parameter is set to true in the <SESAM_ROOT>/var/ini/sm.ini file on the SEP sesam Server. For details on database-based permissions, see Configuring Database-Based Authentication.

    Policy-based authentication

    Policy-based authentication represents a traditional approach to managing user's permissions with SEP sesam v. ≥ 4.4.3. SEP sesam GUI is based on Java and uses sm_java.policy file to grant the required permissions. The policy file is by default located at <SESAM_ROOT>/var/ini/sm_java.policy, where <SESAM_ROOT> is the pathname of the SEP sesam home directory.

    With policy-based authentication permissions are assigned to user/host combination in the sm_java.policy file. You can also grant users the required permissions by using GUI: Main Selection -> Configuration ‐> User Permissions. For details on policy-based permissions, see Configuring Policy-Based Authentication.

    Configuring localFullAccess in sm.ini

    localFullAccess defines whether a user that is logged to the SEP sesam Server directly may use SEP sesam CLI and GUI without any authentication. If set to true, authentication is not required. If set to false, the authentication is mandatory for all users. SEP sesam will prompt for the username and password to log in.

    If database-based authentication is enabled, localFullAccess flag is set to false automatically. A certificate is passed from the SEP sesam command line to the SEP sesam Server, where it is verified. The certificate file is stored in <SESAM_ROOT>/var/ini/ssl.

    Information sign.png Note
    • On Unix, only the system root user can access this directory and use the command line without authentication.
    • On Windows, use Windows User Account Control (UAC) to limit the access to certificate file.

    How to change the localFullAccess flag

    1. Locate the <SESAM_ROOT>/var/ini/sm.ini file on the SEP sesam Server (where <SESAM_ROOT> is the pathname of the SEP sesam home directory). Open the sm.ini file using a text editor and set the flag for the localFullAccess parameter to true.
    2. Once you have changed the settings, save your changes and restart the SEP sesam Server for the changes to take effect. The sm.ini file is preserved when you upgrade your SEP sesam Server.
    Information sign.png Note
    For SEP sesam versions ≤ 4.4.3: It is strongly recommended to leave the localFullAccess flag set to true.

    LTO Encryption

    LTO generation 4 and higher includes the ability for data to be encrypted by the tape drive hardware. SEP sesam provides native support for managing LTO hardware based encryption by enabling LTO encryption of tape drives at the media pool level.

    During the LTO encryption process, data files are taken from the server and passed via the SCSI interface to the tape drive. The tape drive then encrypts and compresses the data before writing it (or decrypts it if reading data) to or from the tape cartridge.

    Supported drive types

    Drive type
    LTO generation
    Supported since SEP sesam version
    LTO Ultrium 7 (M8), LTO Ultrium 8 (L8) LTO 8 4.4.3.64 + SP 2019-1
    * This drive type supports encryption, however it has not yet been certified with SEP sesam. LTO 7 4.4.3.42
    * This drive type supports encryption, however it has not yet been certified with SEP sesam. LTO 6 4.4.3
    HP Ultrium 5-SCSI X64D
    (SCSI, single tape drive)
    LTO 5 4.4.2.53
    Tandberg HH Z519
    (SCSI, single tape drive)
    LTO 5 4.4.2.53
    HP Ultrium 4-SCSI B63W
    (Fiber Channel, loader)
    LTO 4 4.4.2.53
    IBM Ultrium-HH4
    (SCSI, loader)
    LTO 4 4.4.2.53
    IBM Ultrium-TD4 BBH4
    (Fiber Channel, loader/single tape drive)
    LTO 4 4.4.2.53

    Setting up LTO encryption

    The LTO encryption process consists of 4 main steps: you have to create a drive group and assign one or more encryption capable (LTO generation 4 or higher) drives to it. Then you need to create a dedicated media pool. The final step is to initialize the media, and only is the LTO tape encryption-enabled.

    Creating a new LTO (generation 4 or higher) drive group

    Typically, large auto-loaders have multiple internal drives that are loaded from a magazine. All drives have to be organized into a group. Make sure to create a separate drive group for the generation 4 or higher LTO drives. Note that encryption will only be available if there are no older LTO drives (e.g. generation 3) in the same group. However such a group can contain mixed generation 4 and higher LTO drives.

    1. In the Main Selection -> Components, click Drives. The Drives contents frame is displayed.
    2. Click New Group to create a new drive group for the LTO 4 (or higher) and enter a meaningful name for it. Click OK.

    Creating a drive for the new LTO (4 or higher) drive group

    1. Right-click the newly created LTO 4 (or higher) drive group and click New Drive to assign a drive to it. SEP sesam follows the automatic drive enumeration and assigns the drive number automatically.
    2. In the Drive name field, enter a meaningful name for the drive.
    3. From the Drive type drop-down list, select LTO.
    4. From the Loader drop-down list, select the relevant loader from the list of configured loaders or leave it empty if it is a single device.
    5. From the Device server drop-down list, select the client to which you want to connect the drive. The list shows all clients configured in SEP sesam.
    6. From the Drive group drop-down list, select the newly created LTO drive group.
      New LTO drive Beefalo V2.jpg
    7. In the Device (non-rewinding) field, enter the name of the relevant device. Non-rewinding means that the tape will not be rewound after the backup.
      SEP Tip.png Tip
      You can get the name of the device by running the command: <SESAM_BIN>/sesam/slu topology
      (e.g. Tape0 on Windows or /dev/nst0 on Unix/Linux).

      Sample output on Linux

      ID=0000 other:   ATA      ST380013AS 
      ID=1000 other:   TOSHIBA  ODD-DVD SD-M1802
      ID=7040 Tape:    Quantum  DLT4000          D67E (/dev/nst0)
      ID=7050 Tape:    Quantum  DLT4000          D67E (/dev/nst1)
      ID=7060 Loader:  HP       C1194F           1.04 (/dev/sg4)
      STATUS=SUCCESS MSG="OK"
      
    8. Click OK to create the new drive. Once an LTO (4 or higher) drive group has drives assigned to it, it becomes encryption-capable. To verify that your LTO drive group is encryption-capable, double-click it or right-click it and click Properties. If the LTO drive group is configured correctly, the message "This drive group is encryption capable" is displayed.
      Information sign.png Note
      Encryption for a drive group is only available if there are no older LTO drives (e.g., generation 3) in the same group. However, a group can contain mixed LTO tapes of generation 4 and higher.

      Drive group encrypt enabled Beefalo V2.jpg

    Information sign.png Note
    If the drive does not display the encryption capability, make sure that application encryption is enabled on the drive. This may require a special license or can be enabled by using the drive or library management interface. Also, make sure that your LTO generation's encryption functionality is already supported by SEP sesam.

    Creating a media pool for the new LTO (4 or higher) drive group

    After you have assigned one or more drives that are all encryption-capable (LTO generation 4 or higher) to the drive group, you need to create a dedicated media pool and enable encryption.

    You must first create a new media pool and then enable encryption in the media pool properties. (In older versions ≤ 4.4.3 Grolar, the Encryption tab for enabling encryption was already available when creating a new media pool).

    1. In the Main Selection -> Components, click Media Pools. The Media Pools contents frame is displayed.
    2. Click New Media Pool to define a media pool for the LTO (4 or higher) drive group. The New Media Pool window is displayed.
    3. In the Name field enter a meaningful name for the media pool.
    4. From the Drive group drop-down list, select the name of your LTO (4 or higher) drive group. The Encryption tab is available after you create a media pool in the media pool properties.
    5. In the Retention time field set the time period for which the media are locked after initialization or the last backup, thus preserving the savesets and keeping them available for restore. The retention time is defined in days.
    6. To enable encryption, click OK to create a media pool. Then double-click this media pool to open its properties. Switch to the Encryption tab and click Enable encryption. Media pool encrypt enabled Beefalo V2.jpg
    7. Set the password for your tape encryption and re-enter it.
    8. SEP Warning.png Attention
      • Make sure you remember the password, otherwise you won't be able to change the encryption properties or access the data on the tape unless the data is read directly by SEP sesam. The encryption key is stored in the SEP sesam database and is read automatically during restore. But if the tape is removed from the drive, the encryption is cleared. Such a tape can still be used for backups, but only SEP sesam can access the stored data.
      • If you change the password, the updated password will only take effect after the tapes have been initialized. Until then, the old password is still valid.
      • The password is also required to disable encryption.

    Initializing media from a single LTO drive

    To enable LTO encryption, you have to initialize the LTO tapes that belong to the LTO media pool. Only after initialization are the LTO tapes ready for encryption. The LTO tapes that were loaded before encryption was set will be encrypted after their EOL (End of Lifetime) expires. As long as their EOL is valid, these LTO tapes are not writable. Therefore, the data will be encrypted after they are EOL-free and reinitialized. For more details on tape availability and retention, see Tape Management.

    To initialize media, go to Activities -> Immediate Start -> Media Action. Choose Media action init, select the Media Pool and the Media you want to initialize. Click OK to start the initialization of the medium. For details, see Initializing media.

    How to verify if encryption is enabled

    There are two ways to check whether encryption is enabled. You can either check each media properties or search the day log for encryption-related messages.

    Checking the media properties

    In the Main Selection -> Components -> Media, look for the Encrypted column in the table. Yes means that the media is encrypted, No means it is not encrypted. You can also double-click a medium in the table to open the Properties dialog. The Encrypted field indicates whether the medium is encrypted or not (Yes/No).

    Media properties Beefalo V2.jpg

    Checking the day log

    For each data protection operation, SEP sesam checks the drive to determine if encryption is enabled. You can confirm this by checking the Day log file in the GUI or in Web UI (System logs -> Day log). For details, see Logging.

    The following example shows how to search the Day log in the GUI.

    1. In the Main Selection -> Logging, click Day Log. The Day Log contents frame is displayed.
    2. In the Search field type encrypt and press Enter. If LTO encryption is enabled, all related messages are displayed. Use the Next and Previous buttons to scroll through all search results.
      Day log part Beefalo V2.jpg

    If LTO encryption is enabled, the data is encrypted before the backup starts. Note that the tape header is never encrypted while the data itself is encrypted before it is written to the LTO tape.