Difference between revisions of "SBA Book"

From SEPsesam
Jump to: navigation, search
(Created page with "=Part I: Introduction= ==Imprint== {{4_4_3:Imprint }} =Part II: Architecture Overview= ==SEP sesam Requirements== {{:SEP_sesam_Requirements }} ==Licensing== {{:4_4_3:SEP_s...")
(No difference)

Revision as of 15:43, 31 July 2020

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 from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, the information in 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 provided information and the 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

<translate>

<translate> 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.</translate> <translate> 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, SQLite database is automatically installed. 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.

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 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.</translate><translate>
  • For details on the required Java version, see Java Compatibility Matrix. Si3 is not mandatory, therefore there is no dependency rule in the RPM/DEB packages for it.
  • When estimating the maximum size for a deduplication store, you have to ensure that there is enough space available for dedup trash or the deduplication store will run out of space. You should calculate the required disk space based on the representative sample of your full backup and add the amount of extra space equal to approx. 50% of the representative full backup.

Restriction

To avoid issues arising from combination of too large Si3 deduplication stores and inefficient hardware, the maximum initial Si3 deduplication store size is restricted to 40 TB since Tigon V2 (4.4.3.46). This restriction is valid when creating a new Si3 deduplication store in GUI. Note that customers with special requirements for larger Si3 deduplication store should contact SEP support to be able to increase the value up to an optimum size for their specific environments.

Required additional amount of RAM and CPU cores

The following tables show the required additional amount of RAM and CPU cores for one Si3 data store. The TB value is the capacity of the Si3 data store.

Information sign.png Note
It is not recommended to run Si3 deduplication (SEP sesam Server or RDS) on a virtual machine. If this is the case, like evaluation or test, consider to limit the capacity of Si3 data store to 100 GB thus ensuring normal VM operation. Have in mind that deduplication consumes a lot of server resources for reading, processing, and writing deduplicated data, therefore you should be aware of running Si3 on a VM deployment limitation.
Si3 data store capacity (check initial size restriction) RAM
<20 TB 16 GiB
20-40 TB 32 GiB

To find out how much RAM is required by Si3 at which capacity, enter the command sm_dedup_interface propose jvmconfig <Si3-CAPACITY> at an admin command line (you must set sesam profile to run the command). The MaxDirectMemorySize output is the required RAM value.

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

Backed up data (before dedup) CPU cores
10 TB 4
20 TB 4
40 TB 8
Information sign.png Note
Keep in mind that the stated requirements represent the demand for deduplication only. In addition to these requirements, the amount of memory for the operating system and other services should be taken into account.

Java Compatibility Matrix

Java version SEP sesam version
OpenJDK 11 LTS 4.4.3 Beefalo Note1
Java 11 4.4.3 Beefalo Note1
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 Note1
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 Note2
Java 7 4.4.2
Java 6 4.2.1 & 4.2.2
Note1

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

Note2

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.

</translate>

Licensing

Draft.png WORK IN PROGRESS
This page is a draft. Treat the information on this page with caution as it may be incomplete.

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

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

With version 4.4.3 Beefalo, the SEP sesam GUI has been redesigned with additional functionality to improve usability and provide better access to SEP sesam objects. It offers integrated filtering with different filter types that ease the search for specific content items (task, client, data store, etc.). 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.

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 an administrator, the new SEP sesam Web UI landing page opens by default in ≥ Beefalo V2 (with access to the Web UI, links to documentation, etc). To prevent it from automatically opening when starting SEP sesam GUI, in the GUI menu bar -> Configuration -> Defaults -> General tab deselect the check box Show SEP sesam web client landing page on startup.</translate>}}

<translate> GUI overview Beefalo.jpg</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.

Menu and tool bar Beefalo.jpg</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.

GUI activities display Beefalo.jpg</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.

Master GUI servers.jpg</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.

RDS Beefalo.jpg</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.

Job state filter Beefalo.jpg</translate>

<translate>

</translate>

Customizing GUI

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

Rearranging 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 the individual panes of the main GUI window, including the toolbars. You can simply drag and drop selected windows and create a custom GUI layout.

GUI change-layout Beefalo.jpg

Managing layouts

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

Window Beefalo V2.jpg
</translate>

  1. <translate> In SEP sesam v. < 4.4.3 Beefalo, the first time the GUI is started, the docking functionality is disabled by default. You can activate it by selecting the Docking Mode check box in the Manage Layouts window. If the option is deactivated, all window positions are fixed. Note that as of v. 4.4.3 Beefalo, the Docking Mode option is not available anymore.</translate>
  2. <translate> 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 (previously blue arrow) is the current 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.</translate>
    <translate> Window manage layout Beefalo V2.jpg</translate>

<translate>

Changing data size units

As of SEP sesam v. 4.4.3 Tigon, you can change the default setting for the data size units. The data size can be specified either with decimal (KB, MB, GB, TB) or binary prefix (KiB, MiB, GiB, TiB).

Setting default data size unit

SEP sesam allows you to choose how do you want your data size to 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 different data size unit for the individual table

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

  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 provides a number of filtering options, depending on the GUI context. When available, Filter can be found on the top right side of the GUI window. It provides different options that can be narrowed down, such as date range and clients, state, type, task name, etc.

With version 4.4.3 Beefalo, the SEP sesam GUI has been redesigned with additional functionality to improve usability and provide better access to SEP sesam objects. It offers integrated filtering with different filter types that ease the search for specific content items (task, client, data store, etc.).

Backups filter settings Beefalo V2.jpg

Depending on the pre-selected GUI context, the following filter criteria may be 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
Display or hide particular states (in progress, failed, etc.).
Type
Display 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 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).
Filter settings
Activate (default) or deactivate the automatic refresh of the result 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.

</translate>


GUI: Components

Topology

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

Topology overview Beefalo.jpg</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.

Updating client(s)

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, see Checking update status. If it is, the icon with the orange arrow is shown. For details on GUI icons, Client status icons.

It is possible to check if the installed SEP sesam Client is up to date by right-clicking the location/client and selecting the Check Update State option. Use the Check Access State option to make sure that you have access to your SEP sesam client(s). Note that the availability of of the update/install options depends on your selected update mode.

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

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.</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> Topology client Beefalo.jpg</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 always has to be assigned to a location.</translate>
  • <translate> Platform: Select the relevant platform of the client (Windows, UNIX, 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 relevant access method for the server-client communication.
    • CTRL: Default access mode until version 4.4.3.48 Tigon V2.
    • SMSSH: Default access mode as of version 4.4.3.60 Grolar. 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 installed backup client. The data transfer is executed via vendor specific protocols; 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, NetApp, NDMP and Novell SMS for NetWare 5.1/6.0/6.5.
    • VIRTUAL: (introduced in v. 4.4.3 Beefalo) Access mode for a virtual machine (VM) without installed backup client where there is no direct remote access to this VM. Note that the VIRTUAL access mode is similar to PROXY, but is specifically intended to manage VMs as clients by allowing to configure ACLs for VMs. This means that 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: The communication mode SSH is based on a key-pair operation of the SSH implementation of the used operation system.
    • RSH: Remote Shell; it is a historic old option and is 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.</translate>

  • <translate> SEP sesam version: This field shows the SBC (SEP sesam backup Client) version of the installation.</translate>
  • <translate> VM host and VM name: VM host and name are displayed, if you have specified them during the client creation.</translate>
  • <translate> Additional options</translate>
  • <translate> There are two additional client-related options:</translate>

    • <translate> Client is a virtual machine: Selecting this option allows you to 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.

Client options Beefalo.jpg</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 parralel 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 How To.

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

Client permissions Beefalo.jpg</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> Client VMware Beefalo.jpg</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.

Clients list Beefalo.jpg</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.

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.

</translate> <translate></translate>

Data Store

<translate> </translate>

<translate>===Data stores===

SEP sesam data store is a device type used for writing the savesets directly on one or several configured storage locations – into the file system. SEP sesam uses a data store instead of a conventional media pool to define storage repository. The 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 based on the type of data being backed up, backup technique, and on your storage location (a local disk, virtualized storage device, storage appliances, etc.). The following data store types are supported:</translate>

<translate> The data store types and their properties have been significantly enhanced with SEP sesam Beefalo. Therefore, depending on your SEP sesam version, the data store window might be different and available features and configuration options may vary.

Data store overview Beefalo.jpg</translate>

<translate> 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 is 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 additional View Mode button that enables you to switch between the table view and the tree view with grouped objects.</translate>

  • <translate> Tree view: SEP sesam default view shows the status of individual data stores grouped together in a hierarchical view.</translate>
  • <translate>

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 to the Path data store; other data store types 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 value (HWM; 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.</translate>

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

<translate> As shown in the illustration below, a media pool still points to a drive group. However, there is now an additional level of one or more data stores between the media pool and the drives. The connection between a data store and the related drive is static.

DataStore Principle 403b.jpg</translate>

<translate>====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 will have to obtain a special SEP sesam storage license.

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

<translate> 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 used for triggering the data store purge process, while the Si3 repair area parameter is related to SEP Si3 Deduplication Store only permitting you to specify reserved space for unused Si3 files (DDLs), as explained below.</translate>

  • <translate> 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, a data store purge process is started 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 Managing EOL.</translate>
  • <translate> When setting the HWM parameter, ensure that sufficient space is allocated between data store capacity and HWM for a complete full backup. For details, see Data store calculation recommendations below.</translate>

    {{<translate> Note</translate>|<translate> SEP sesam HWM and purge behavior is version dependent.

    • From SEP sesam v. ≥ 4.4.3.48 Tigon V2, if HWM is set, exceeding it will issue an information message but will not prevent backups to be started.
    • In older SEP sesam versions (≤ 4.4.3.42 Tigon), if HWM was set and exceeded, backups could no longer be started while running backups were allowed to finish. The data store was purged until the low watermark (LWM; if set) was reached.</translate> }}

    <translate> Events that trigger the data store purge are:</translate>

    • <translate> NEWDAY</translate>
    • <translate> Sharing the data store drive after a backup</translate>
    • <translate>

    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, as described in the folowing section.</translate>

  • <translate> Low watermark (LWM): No longer used, relevant only for previous versions of SEP sesam.</translate>
  • <translate> </translate>
  • <translate> Si3 Repair Area: A parameter used by SEP Si3 Deduplication Store for managing disk space dedicated to Si3 files (DDLs) 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.</translate>

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

  1. <translate> In the Main Selection -> Components, click Data stores to display the data store contents frame.</translate>
  2. <translate> 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.</translate>
    <translate> Click Clean Up.</translate>
    <translate> Data store clean up Beefalo.jpg</translate>
  3. <translate> You can check the status of the clean-up action in the data store properties under the Actions tab.</translate>

<translate>==== Data store calculation recommendations==== </translate>

  • <translate> 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.</translate>
  • <translate> 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.</translate>
  • <translate> 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. To do this, sufficient space should be allocated between capacity and HWM for two (2) full backups.</translate>
  • <translate> A virtual drive can handle up to 124 simultaneous backups (channels) for storing data to a SEP sesam data store (depending on the SEP sesam version). Only when it becomes necessary to back up more than 124 channels (SEP sesam Server Premium Edition) should another drive be added to the data store.</translate>
  • <translate>

Because a backup is aborted rather than split up when a data store becomes full, the correlation between the size of the data store and the size of the biggest backup task must be determined carefully. Take the example of a data store with the capacity of 6 TB, where the biggest saveset is 2 TB and sum up of other saveset(s) is around 1 TB. With a retention time=3, a data store three times (3x) the maximum full backup size may be too small to allow the HWM to work properly. In such a case, it is recommended to scale up the data store size, e.g., by summing up all the savesets for 3 days and adding 15%.

==== Limitations ==== </translate>

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

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.

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

  • <translate> 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.</translate>
  • <translate> High watermark: The upper value (in GiB) for the used disk space on the data store. When this value is reached, a data store purge process is started for all EOL-free savesets thus freeing up data store capacity.</translate>
  • <translate> Filled: The size (in GiB/TiB) of the occupied data store space by SEP sesam.</translate>
  • <translate> Used: Total used space (in GiB/TiB) on the partition (incl. SEP sesam external data).</translate>
  • <translate> Total: Maximum available space (in GiB/TiB) on the partition as reported by the operating system.</translate>
  • <translate>

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 another drive group, browse the path for the data store, set access mode, etc. The first drive on the list has an additional Account tab that allows you to specify the credentials (user name and password) required to access the configured drive path.</translate>
<translate> Drive properties Beefalo.jpg</translate>

<translate>====Savesets tab====

Selecting a data store and clicking the tab Savesets opens a list of all savesets with their details. You can change EOL of individual saveset, adjust backup-related EOL, and lock or unlock individual saveset.</translate>

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

<translate> Data store savesets Beefalo.jpg</translate>

  • <translate> 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.</translate>
  • <translate> 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.</translate>
  • {{<translate> Tip</translate>|<translate> 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 Customizing retention policy. These keys may not be supported in previous versions, where failed backups were deleted automatically after 3 days.</translate>}}

  • <translate> 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) in order to retain the backup data. This keeps the backup chain readily available for restore. On the other hand, decreasing EOL of a DIFF or INCR saveset to a date in the past will result in a warning message prompting you to confirm your decision to set the whole backup chain to already passed time. By setting EOL for DIFF or INCR savesets to expired time results in purging and overwriting the complete backup chain.</translate>

{{<translate> note</translate>|<translate> Each saveset can be deleted when 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.</translate>}}

<translate>====Media tab====

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

Data store media Beefalo.jpg</translate>

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

<translate>====Si3 State, HPE Catalyst Store State and HPE Cloud Bank Store State tabs====

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 tab is shown for HPE Cloud Bank stores. They provide an overview of the Si3 deduplication, HPE Catalyst and HPE Cloud Bank store status. 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</translate>

<translate> </translate>

Loaders

<translate>


<translate>===Loaders===

Loaders are devices that consists 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 manufacturers 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.</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.</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.

GUI loader Beefalo V2.jpg</translate>

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

Loader Beefalo V2.jpg</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 different 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>

    <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, configure the auto-clean option in the tape library setup.

  • 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==== The Content view shows a symbolic representation of the loader. It is constantly refreshed and always shows the current status.</translate>

<translate> Loader content Beefalo V2.jpg</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 the 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</translate>

    <translate>

  • 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.</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> Loader archive adjustment Beefalo V2.jpg</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:
    3. </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.
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</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====

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

470pxlink=</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>