SBA Book

Part II: Architecture Overview

SEP sesam Requirements

• On 64-bit Linux, FreeBSD and Solaris PostgreSQL is used as the SEP sesam database.
• When SEP sesam is installed on MS Windows, PostgreSQL is installed for the SEP sesam database. The SQLite database was automatically installed up to version 4.4.3 Beefalo V2. In 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, PostgreSQL has to be installed before the SEP sesam Server to enable the DB instance to be set up for use.

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 32 GB RAM	Minimum 32 GB RAM	64 GB RAM	Minimum 128 GB RAM	Minimum 8 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	200 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 the minimum Si3/Si3-NG hardware requirements that apply to the SEP sesam Si3/Si3-NG deduplication server, see Hardware Requirements.

• 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 and MooseFS 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.

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.

	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

SEP sesam version	Java version
5.1.0 Apollon [V2]	Java 17 Note1, Java 11, OpenJDK 11 LTS
5.0.0 Jaglion V2	Java 17 Note1, Java 11, OpenJDK 11 LTS, Java 8 ≥ patch level 111 (both Windows and Linux) Note2 Note3
5.0.0 Jaglion	Java 11, OpenJDK 11 LTS, Java 8 ≥ patch level 111 (both Windows and Linux) Note3
4.4.3 Beefalo V2	Java 11, OpenJDK 11 LTS, Java 8 ≥ patch level 111 (both Windows and Linux)

Note¹

• On Windows, SEP sesam recommends Java 17.
• On Linux, SEP sesam versions ≥ 5.0.0.9 Jaglion V2 and 5.1.0 Apollon support 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>.

Note²

5.0.0.9 Jaglion V2 is the last version of SEP sesam that supports Java 1.8.

Note³

Java 1.8 (≥ 1.8.0_111) is only accepted if it is already installed and the computer does not have a 4K display.

Licensing

THE CONTENT OF THIS PAGE IS OUTDATED

SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.

<translate>

<translate> SEP sesam offers a variety of licensing possibilities:</translate>

<translate>

SEP volume licensing:Volume licenses are based on the data volume per front-side terabyte and on the utilisation of SEP database agents. They include unlimited usage of clients, hypervisors, disk storage, tape, Si3 deduplication, and replication. The licenses are perpetual and maintenance is included within the first 12 months. 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 biggest FULL) is calculated, provided that it is stored on any SEP sesam media (retention policy). The original data is cumulated before deduplication or compression.

Example: If there is a system full backup (Path backup type), an image backup on hypervisor level and a database backup agent, the data will be counted three times if the database is part of all three backup jobs.

For each additional 50 TB volume license extension, 1 TB of deduplication storage is included.

The SEP volume license basis can be extended by increments of 25, 50, 100, 250, etc., terabytes and includes upgrade services and technical entry support. Extensions for disaster recovery and archiving are available.</translate>

<translate>

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

After the subscription period, SEP sesam save sets can be further used for restores, however, backing up data is no longer possible.</translate>

<translate>

SEP classic licensing:The SEP sesam classic model provides item-based, perpetual licenses that are individually tailored to a customer's needs. Licensing is modular and scalable, expansions of any license components such as database and groupware agents can be carried out at any time. Maintenance is included within the first 12 months. SEP’s classic licensing model is based on the following SEP sesam building blocks:</translate>

• <translate>

Main Backup Server</translate>

• <translate>

Remote Device Servers</translate>

• <translate>

Client licenses</translate>

• <translate>

Autoloader support</translate>

• <translate>

Storage pools</translate>

• <translate>

Databases or groupware modules</translate>

• <translate>

Application and virtualization modules</translate>

• <translate>

Disaster recovery

Depending on the requirements, all available modules can be combined and a dedicated license to the environment is generated.

==SEP sesam license comparison== </translate>

* <translate> without additional streams expansion</translate>

	<translate> Volume</translate>		<translate> Classic</translate>
	<translate> Professional</translate>	<translate> Ultimate</translate>	<translate> ONE</translate>	<translate> Standard</translate>	<translate> Advanced</translate>	<translate> Premium</translate>	<translate> Enterprise</translate>
<translate> Streams</translate>	unlimited	unlimited	1	5	25	100	250
<translate> Storage pool incl.</translate>	<translate> unlimited</translate>	<translate> unlimited</translate>	1 TB	2 TB	4 TB	4 TB	10 TB
<translate> SEP sesam Si3 deduplication: max. extension</translate>	<translate> unlimited</translate>	<translate> unlimited</translate>	∼	25 TB	50 TB	150 TB	<translate> unlimited</translate>
<translate> Level 2 agents</translate>	✓	✓	✓	✓	✓	✓	✓
<translate> Level 3 agents</translate>	∼	✓	∼	∼	✓	✓	✓
D2D2T	✓	✓	∼	✓	✓	✓	✓
<translate> Typical system environment</translate>
<translate> Backup clients</translate>	<translate> up to 30 </translate>	<translate> up to 50 </translate>	<translate> up to 5</translate>	<translate> up to 15</translate>	<translate> up to 50</translate>	<translate> up to 150</translate>	<translate> any</translate>
<translate> Drives</translate>	1 – 2 *	2 – 4 *	1	1 – 2	2 – 4	5 – 8 <translate> in distributed environment</translate>	<translate> several computing centers or distributed environments</translate>

<translate> You can find detailed descriptions of the SEP licensing models and technical support in the documents SEP sesam License Guide and SEP Support Definitions & Explanation of Terms, both available in the SEP Partner Lounge.</translate>

Part III: SEP sesam GUI

SEP sesam Graphical User Interface (GUI)

<translate>

</translate>

<translate>==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.

	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.</translate>

{{<translate> Tip</translate>|<translate> 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.</translate>}}

<translate> </translate>

<translate> 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.

</translate>

<translate>====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.

</translate>

<translate>===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.

</translate>

<translate> 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.

</translate>

<translate> 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.

</translate>

<translate>

</translate>

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.

GUI configuration options

You can access the configuration options from the menu bar -> Configuration -> Defaults. Configuration provides different settings and parameters that define SEP sesam look and feel as well as its behavior.

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

The following options are available:

• 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: SEP sesam GUI opens the external links by using the HTTPS protocol. Note that you have to accept the SEP sesam REST server security certificate. This option is selected by default and cannot be changed.
• Sort case insensitive: You can enable the Sort case insensitive check box to ensure that upper- and lowercase letters are treated the same when sorting results.

• UI Mode: You can select the appropriate UI mode: simple or advanced. 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.
• Color theme: You can select light or dark color theme for the GUI.

• Restore mode: You can select which restore interfaces are available for restore and displayed in the context menu and toolbar. 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.
• Delay reloading data on filter change: You can specify a time interval, in seconds, to delay the reloading of data when a filter is changed. To disable this option and enable data to reload immediately upon filter change, set the value 0 (zero).

• 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.

Fonts and Tables tab

• Font: The predefined GUI font is plain. You can select Choose button to change the default font, font style and/or size.

	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 options for tables from the drop-down list.

• Date range: 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.

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.

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.

The following options are available:

• Do not check or install automatically (default): If selected, updates are not checked, downloaded nor installed when a new version is available.
• Check automatically, but install manually: SEP sesam automatically checks for updates at SEP Download Center, and gets the list of all available packages, but you have to download and install them manually.
• Check, download and install 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.

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 past calendar entries is 35 days.
• Restore tasks: The default retention time for old restore tasks is 7 days.

Extras tab

In 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).
• Maximum Logs Archive states: 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.

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.

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.

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.

Managing layouts

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

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.

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.

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.

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.

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

<translate> </translate>

<translate> 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.

</translate>

<translate> 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. </translate>

====<translate> 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 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.</translate>

====<translate> 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.

</translate>

<translate> Location tab

• Name: Name of the location</translate>

<translate> *in: Superordinated location (relevant for sub-locations)</translate> <translate>

• Description: More exact description of the location</translate>

<translate> *Contact: Contact person at this location</translate> <translate>

• 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.</translate>

====<translate> 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).</translate>

{{<translate> note</translate>|<translate> 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.</translate>}}

<translate> </translate>

<translate> Client tab</translate>

• <translate> 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.</translate>
• <translate> Location: Predefined location. A client must always be assigned a location.</translate>
• <translate> 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.</translate>
• <translate> 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.</translate>
• <translate> Operating system: Select the operating system version of the computer you are adding as a client.</translate>
• <translate> 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.</translate>
• <translate> 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.</translate>
• <translate> Last SEP sesam message: The most recent system status message for the existing client.</translate>
• <translate> Last successful access: The last successful access to the existing client.</translate>
• <translate> Notes: Optional comment.</translate>
• <translate> Interfaces:</translate>
{{<translate> Note</translate>|<translate> Only edit this field if a client is a SEP sesam Server or Remote Device Server (RDS).</translate>}} <translate> 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. You can set the default interface for a drive group in Main Selection -> Components -> Drives. Double-click the drive group you want to modify and select the required interface in the Default interface drop-down list. All events that do not have an interface set and are using the drives in this drive group will use the interface, selected for the drive group as default.</translate>
• <translate> SEP sesam version: This field shows the SBC (SEP sesam backup Client) version of the installation.</translate>
• <translate> Additional options</translate>
<translate> There are two additional client-related options:</translate>
• <translate> 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.</translate>
• <translate> 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.</translate>
• <translate> 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.</translate>
{{<translate> Note</translate>|<translate> If this option is set, the client will not be backed up until it is unlocked again even if it is scheduled for backup.</translate>}}

<translate> 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.

</translate>

• <translate> 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).</translate>

<translate>

• 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.</translate>

<translate>

• Listen port: The default STPD-port for Remote Device Servers (incl. SEP sesam Server) is 11001.</translate>
• <translate>

Wake on LAN: For more information, see WOL - wake on LAN of a SEP sesam client.</translate> {{<translate> Note</translate>|<translate> 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.</translate>}}

<translate> 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.

</translate>

<translate> 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.

</translate>

<translate> 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).</translate>
<translate> </translate>
<translate> For more information on specific task type, see the respective wiki articles under Extensions.

</translate>

Clients

<translate>

</translate>

<translate>

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.

</translate>

<translate> 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.</translate>

Icon	Description
	The backup execution is disabled on the client.
	The client is not accessible.
	The system checks if the update is available for the client.
	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).
	The backup execution is disabled on the server.
	The server is not accessible.
	The backup execution is disabled on the RDS.
	The RDS is not accessible.

<translate> </translate>

Data Store

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).

  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 V1 (first generation) or Si3 (next generation). SEP sesam recommends using the new generation Si3 when creating a new data store. Si3 is advantageous over regular Si3 V1 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 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
	The data store state has errors.
	The data store state is OK (good).
	The data store and Si3 state are OK (good).
	The Si3 and the sanity state are OK, but the S3 clone state shows an error.
	The Si3 store state shows an error, but its sanity state is OK.
	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.

Note

Only one data store should be used for each hard disk partition. While it is possible to set up multiple data stores on a single partition, it is not recommended due to potential conflicts. Each data store reads the values of other partitions when checking partition allocation, which can create conflicts and obstruct their coexistence. Additionally, storing third-party data on the data store storage often leads to issues, as SEP sesam may not have the storage capacity guaranteed in the specification. This can cause backup operations to abort.

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 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.

	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.

	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.
   
   
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.

	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.

• 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.

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.

	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.

• 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.
• Saveset state: The column Saveset State shows the status of a saveset (for example, Successful, Warning, Error). In case of a failed migration or some kind of data store corruption, a saveset may be incomplete or corrupted. Such savesets cannot be used for restore.
• 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.

Tip

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.

	Note
	Any saveset can be deleted if the following conditions are met: Its EOL has expired. 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.

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.

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.

Loaders

<translate>

<translate> Loaders</translate>

<translate> 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. </translate>

<translate> Identifying storage devices and their configuration</translate>

<translate> 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.</translate>

{{<translate> note</translate>|<translate> 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.</translate>}}

<translate> 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).</translate>

{{<translate> note</translate>|<translate> 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.</translate>}}

<translate> 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.

</translate>

<translate> Loader properties</translate>

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

</translate>

<translate>

• 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.</translate> <SESAM_BIN>/sesam/slu topology <translate> 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:
</translate>
• DIR_SLU: <translate> All loaders, which are connected by SAS/iSCSI/FC to the SEP sesam Server or RDS, and provide a robotic control of tape media.
</translate>
• DIR_VIRT: <translate> 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.
</translate>
• DIR_DISK: <translate> 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.</translate>
• DIR_ACSLS (≥ 4.4.3 Beefalo V2): <translate> ACSLS loader used for the tape libraries controlled by StorageTek Automated Cartridge System Library Software (ACSLS) as SEP sesam backup devices.
</translate>

<translate>

• 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.
</translate> <translate>
• 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.
</translate> note</translate>|<translate> As of v. 5.0.0 Jaglion, the Auto unload function option is only available in the Expert UI mode. It is not available for users that run the GUI in Basic or Advanced mode. In the latter case, if you want to access this option you first have to change the Basic/Advanced UI mode to Expert, as described in Selecting UI mode.</translate>}}-->

<translate> Contents</translate>

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

<translate> </translate>

<translate> 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.
</translate>

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

<translate> Archive Adjustment</translate>

<translate> 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.</translate> {{<translate> note</translate>|<translate> 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.</translate>}}

<translate> </translate>

<translate>

• 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.
</translate> <translate>
• 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:
</translate>
• <translate> 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.
</translate>
• <translate> 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.</translate>
{{<translate> Note</translate>|<translate> 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.</translate>}}

<translate>

• 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.
</translate>

<translate> First archive adjustment after new loader installation</translate>

<translate> 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.</translate>

<translate> Loader Action</translate>

<translate> 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.

</translate>

<translate> 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.
</translate> <translate>
• 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.

</translate>

<translate> Drive Action</translate>

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

</translate>

• <translate> Identify label: Shows the label of the medium in the drive.</translate>
• <translate> Mount media: Mount is a special reservation of the tape media to prevent unnecessary spooling.</translate>
• <translate> Dismount media: Cancels the mount status.</translate>
• <translate> Dismount and unload media: Cancels the mount status and unloads the tape.</translate>
{{<translate> warning</translate>|<translate> 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.</translate>}}
• <translate> Release drive: Cancels all activities that are running on the drive.</translate>
• <translate> Release drive group: Cancels all jobs that are running on the drives that belong to the respective drive group.</translate>

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

<translate> </translate>