SBA Book: Difference between revisions

From SEPsesam
(quick fix, language suffix)
(In progress.)
Line 1: Line 1:
=Part I: Introduction=
=Part I: Introduction=
==Imprint==
==Imprint==
{{4_4_3:Imprint }}
{{4_4_3:Imprint }}
=Part II: Architecture Overview=
=Part II: Architecture Overview=
==SEP sesam Requirements==
==SEP sesam Requirements==
{{:SEP_sesam_Requirements/en}}
{{:SEP_sesam_Requirements/en}}
 
==Directory layout==
{{:Directory Layout/en}}
==SEP sesam Components==
{{:SEP sesam Components/en}}
==Licensing==
==Licensing==
{{:Licensing/en}}
{{:Licensing/en}}
=Part III: SEP sesam GUI=
=Part III: SEP sesam GUI=
==SEP sesam Graphical User Interface (GUI)==
{{:4_4_3_Beefalo:SEP_sesam_Graphical_User_Interface_(GUI)/en}}
{{:4_4_3_Beefalo:SEP_sesam_Graphical_User_Interface_(GUI)/en}}
==Customizing GUI==
==Customizing GUI==
{{:Customizing_GUI/en}}
{{:Customizing_GUI/en}}
==GUI: Components==


===Topology===
{{:4_4_3_Beefalo:Topology/en}}
{{:4_4_3_Beefalo:Clients/en}}
{{:4_4_3_Beefalo:Data_Store/en}}
{{:4_4_3_Beefalo:Loaders/en}}
{{:4_4_3_Beefalo:Drives/en}}
{{:4_4_3_Beefalo:Media_pools/en}}
{{:4_4_3_Beefalo:Tasks by Clients/en}}
{{:4_4_3_Beefalo:Tasks by Groups/en}}
{{:4_4_3_Beefalo:Backup Plans/en}}
{{:4_4_3_Beefalo:Migration Tasks/en}}
{{:4_4_3_Beefalo:Replication Tasks/en}}{{:4_4_3_Beefalo:Tasks as List/en}}


=GUI: Components=
==GUI: Scheduling==
 
{{:4_4_3_Beefalo:Schedules/en}}
==Topology==
{{:4_4_3_Beefalo:Events/en}}{{:4_4_3_Beefalo:Calendar Sheet/en}}
{{:4_4_3_Beefalo:Topology}}
 
==Clients==
{{:4_4_3_Beefalo:Clients}}


==Data Store==
==GUI: Job State==
{{:4_4_3_Beefalo:Data_Store}}
{{:4_4_3_Beefalo:All Results by State/en}}
==Loaders==
{{:4_4_3_Beefalo:Backups by State/en}}
{{:4_4_3_Beefalo:Loaders}}
{{:4_4_3_Beefalo:Restores by State/en}}
{{:4_4_3_Beefalo:Migrations and Replications by State/en}}
<br />
{{:4_4_3_Beefalo:Media Actions by State/en}}

Revision as of 15:26, 5 August 2020

Part I: Introduction

Imprint

4 4 3:Imprint

Part II: Architecture Overview

SEP sesam Requirements

SEP sesam Requirements/en

Directory layout

Directory Layout/en

SEP sesam Components

SEP sesam Components/en

Licensing

Licensing/en

Part III: SEP sesam GUI


SEP sesam GUI overview

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

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

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

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

GUI components

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

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

GUI overview Beefalo.jpg

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

Menu bar

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

Toolbar

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

Menu and tool bar Beefalo.jpg

Navigation pane – Main Selection

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

Content pane

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

Properties pane

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

Filter pane

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

Activities display

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

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

GUI activities display Beefalo.jpg

Master GUI

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

Master GUI servers.jpg

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

RDS Beefalo.jpg

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

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

Job state filter Beefalo.jpg

Customizing GUI

Customizing GUI/en

GUI: Components

Topology



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

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

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

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

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

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

Topology overview Beefalo.jpg

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

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

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

Updating client(s)

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

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

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

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

Location properties

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

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

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

Location properties Beefalo.jpg

Location tab

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

OS Access tab

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

Permissions tab

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

Client properties

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

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

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

Topology client Jaglion.jpg

Client tab

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

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

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

    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.

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

Options tab

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

Client options Beefalo.jpg

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

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

OS Access tab

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

Client access Beefalo.jpg

Additional tabs

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

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

Client permissions Beefalo.jpg

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


Clients

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

Clients list Beefalo.jpg

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

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

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

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

Client status icons

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

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


4 4 3 Beefalo:Data Store/en


Loaders

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

Identifying storage devices and their configuration

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

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

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

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

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

GUI loader Beefalo V2.jpg

Loader properties

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

Loader Beefalo V2.jpg

  • Device name: SCSI device filename of the loader; enter the SCSI address of the physical device on Windows systems, for example Changer0, or a device filename on Linux systems, for example /dev/sg2. You can check if the devices are used correctly by SEP sesam and detect available SCSI addresses by running a slu topology command.
  • slu topology is a SEP sesam SCSI loader utility that provides information about the loaders and tape drives connected to the system and their relation. To be able to run the SEP sesam commands globally, you must first set up a profile as described in FAQ: What happens when I set a profile? Then run slu topology command to list all attached SCSI devices. For details on the output, see Using slu topology for detecting devices. <SESAM_BIN>/sesam/slu topology Enter the displayed target device name in the Device name field.
  • Device server: Remote Device Server (RDS) where the loader is installed.
    Device Server refers to the server where the loader is connected. In small environments, the loader or disk array is usually installed directly on the SEP sesam Server. However, more complex backup environments use RDS instead. RDS receives data during backup and writes it to the attached tape device.
  • Type: The device type.
  • Ctrl: The loader type – there are four types of loaders available:
    • DIR_SLU: All loaders, which are connected by SAS/iSCSI/FC to the SEP sesam Server or RDS, and provide a robotic control of tape media.
    • DIR_VIRT: A virtual loader. Only one virtual loader can exist in the entire SEP sesam configuration. This loader type is always configured with the number 0 (zero), and it serves all DISK_HARD drives and DISK_CHNG drives. Even though media are not actually moved, there are entries in specific files to control the data streams.
    • DIR_DISK: Enables you to control a pool of several hard disks. The hard disks have to be addressable by single device ID in the operating system.
    • DIR_ACSLS (≥ 4.4.3 Beefalo V2): ACSLS loader used for the tape libraries controlled by StorageTek Automated Cartridge System Library Software (ACSLS) as SEP sesam backup devices.
  • Slots: Number of slots in the loader.
  • When inserting a cleaning tape, use the last slot in the loader and reduce the number of slots in the loader by one (or by the number of cleaning tapes loaded). Additionally, disable the auto-clean option in the tape library setup or set it to manual execution.
  • Ports: Number of mail slots in the loader.
  • Barcode: Depending on whether the loader has a barcode reader or not, select yes or no.
  • Auto unload function: Almost all autoloaders and tape libraries allow explicit commands to transport tapes to and from the loader mechanism. It is strongly recommended to disable Auto unload function by setting it to No and allow the manufacturer's drive settings to perform as designed.

Contents

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

Loader content Beefalo V2.jpg

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

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

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

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

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

  • Legend: The following table lists the icons used for displaying various media and loader status.
  • Loader legend Beefalo V2.jpg
  • Barcode as Label: If available, a barcode will be used instead of the media label.

Archive Adjustment

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

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

Loader archive adjustment Beefalo V2.jpg

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

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

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

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

Loader Action

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

Loader action Beefalo V2.jpg

Action

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

Drive Action

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

470pxlink=

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

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





Drives

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

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

Shared drives

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

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

Drive groups

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

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

Drives overview Beefalo V2.jpg

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

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

Drive group-default interface.jpg

New drive group

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

New drive group Beefalo.jpg

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

New drive

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

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

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

Setting device block size

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

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

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

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

Device block size.jpg

Manage multiple drives

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

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

Manage multiple drives beefalo.jpg

Configure all drives

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


Media pools

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

Media labels

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

Data stores

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

Backup strategy

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

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

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

Media pools Beefalo V2.jpg

Media pool properties

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

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

Media pools properties Jaglion.jpg

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

Readability Check

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

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

Media pools read check Jaglion.jpg

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

Options

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

Media pool-options Jaglion.jpg

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

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

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

Permissions (in v. ≥ 5.0.0 Jaglion)

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

Media pool permissions Jaglion.jpg


Tasks by clients

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

Tasks by clients Beefalo.jpg

The backup task status is shown with the following icons:

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

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

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

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

Tasks by clients right-click Beefalo.jpg

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

Creating a new backup task

Tasks new backup task Beefalo.jpg

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

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

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

    Task client browser Beefalo V2.jpg

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

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

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

Task options Beefalo.jpg

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

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

Pre/Post: Backup

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

Pre/Post: Restore

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

Additional call arguments

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

Encryption & Compression

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

Task encryption Beefalo.jpg

Cryptography

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

Compression (only available for Windows)

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

OS Access

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

Tasks OS access Beefalo V2.jpg

Task Groups

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

Tasks task groups Beefalo.jpg

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

Schedules

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

Task schedules Beefalo.jpg

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

Additional tabs in the backup task properties

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

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

Micro Focus tab Beefalo.jpg

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

Bck task permissions Jaglion.jpg



Tasks by groups

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

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

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

Tasks by groups overview Beefalo.jpg

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

Tasks by groups right-click Jaglion.jpg

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

Task group properties

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

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

Tasks by groups properties Jaglion.jpg

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

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

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

Schedules

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

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

Tasks by groups schedules Jaglion.jpg

Permissions

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


Backup plans

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

Backup plans Jaglion.jpg

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


Migration tasks

About migration

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

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

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

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

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

Migration tasks Jaglion.jpg

Configuring migration

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

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

Migration options

Migration task Jaglion.jpg

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

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

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

Schedules

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

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


Replication tasks (Si3)

About replication

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

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

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

Replication tasks Jaglion.jpg

Configuring replication

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

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

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

Replication options

New replication task.jpg

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

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

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

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

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

Schedules

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

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


Tasks as list

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

Tasks as list Beefalo.jpg

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

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

Tasks as list right-click Beefalo.jpg

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

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

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

GUI: Scheduling

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

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

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

Schedules overview Beefalo.jpg

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

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

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

  • Events were deliberately created without a schedule for external backups, such as SAP HANA, where the external applications manage the backup scheduling.
  • Events were first linked to a schedule and then disconnected from it by opening the event and selecting the option Without Schedule, as shown in the screenshot below.
  • Changing events Beefalo.jpg
Information sign.png Note
You should only delete events without a schedule if you are sure that they will not be used for an external backup.

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

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

Schedule properties

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

Schedule Beefalo.jpg

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

As of. v. 5.0.0 Jaglion, new Permissions tab enables you to set the required permissions (ACLs) for the schedule. For details, see Using Access Control Lists.

Schedule permissions.jpg

New backup event

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

The button New Backup Event opens the following window:

New backup event Beefalo.jpg

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

Sequence Control

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

Object

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

Parameter

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

New restore event

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

Schedules new restore event Beefalo.jpg
Parameter

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

Backup selection

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

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

Sequence control

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

Destination parameter

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

New migration event

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

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

New migration event Beefalo.jpg

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

Sequence control

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

Media pool

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

Destination

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

Backup date

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

Backup State

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

Backup level

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

Number of copies

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

Object

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

Special filter

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

New replication event

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

New replication event Beefalo.jpg

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

Sequence control

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

Media pool

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

Destination

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

Backup date

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

New media event

No longer available in the ≥ Jaglion version. The following explanation is therefore only relevant for versions ≤ Beefalo V2.

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

New media event Beefalo.jpg

Sequence control

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

Media actions

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

Under the Parameter, depending on previously chosen media event, some or all of the following options may be available:

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

New command event

The command event can be scheduled to be executed automatically.

Information sign.png Note
The procedure for creating command events is version dependent. Be sure to follow the appropriate instructions:

New command event Beefalo.jpg
The following screenshot and the explanation of the options show the command event in SEP sesam version Beefalo V2.

Sequence control

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

Parameter

  • Name: Enter a name for the new event or search for and select an already existing command event. Searching for command opens a new window, where you can add a new command event, copy an already existing command event, select which existing command event you want to use again by clicking the Select button, and change or delete an existing command event.
  • Select command Beefalo.jpg
  • Client: Select a client, on which the command will be executed.
  • User: Enter the user name of a user with sufficient access to execute the command on the client.
  • Retention time: Specify for how long (in days) the command event results and logs will be kept.
  • Command: Enter the complete command.
  • Add to command: Optionally, add additional parameters to command, e.g., sm_sho.
SEP Tip.png Tip
You can also access the configured commands from the menu bar -> Configuration -> Command.
Access limitation of command events

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

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

UNIX

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

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

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

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

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

Registryentry.JPG

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

New Newday event

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



Events

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

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

Events Beefalo V2.jpg

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

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

Events Jaglion.jpg


Calendar Sheet

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

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

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

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

Calendar sheet Beefalo V2.jpg

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

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


GUI: Job State

All Results by State

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

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

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

All results Beefalo V2.jpg

The following information is displayed:

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


Backups by state

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

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

Backups by state Beefalo.jpg

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

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

Backups pop-up menu Beefalo.jpg

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

Column selection Beefalo.jpg

View Mode

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

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

Backups view mode Beefalo.jpg

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

Filter

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

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

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

Backups filter Beefalo.jpg

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

Filter:

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

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

Backups state Beefalo.jpg

In Progress

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

Failed

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

Successful

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

All states

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

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

Backups type Beefalo.jpg

Events

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

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

    Backups task name Beefalo.jpg

    Filter: Filter settings

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

    Backups filter settings Beefalo.jpg

    Properties of a finished backup

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

    Info 1

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

    Backups info 1 Beefalo.jpg

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

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

    Backups info 2 Beefalo.jpg

    Main Log

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

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

    Backups main log Beefalo.jpg

    Trace Log

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

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

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

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

    Backups trace log Beefalo.jpg

    Pre Log

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

    Post Log

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

    Savesets

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

    Backups savesets Beefalo.jpg


    Restores by state

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

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

    Restores by state Beefalo.jpg

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

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

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

    Properties of a finished restore

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

    Info 1

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

    Restores info 1 Beefalo.jpg

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

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

    Restores info 2 Beefalo.jpg

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

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

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

    Restores info 3 Beefalo.jpg

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

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

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

    Restores main log Beefalo.jpg

    Trace Log

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

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

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

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

    Restores trace log Beefalo.jpg

    Pre Log

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

    Post Log

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


    Migrations and replications

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

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

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

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

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

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

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

    Migrations by state Beefalo.jpg

    Properties of the migration or replication

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

    Information tab

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

    Migrations properties Beefalo.jpg

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

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

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

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


    Media actions

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

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

    The following media actions might be displayed:

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

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

    Media actions by state Beefalo.jpg

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

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

    Properties of the media actions

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

    Info tab

    Media actions info Beefalo.jpg

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

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

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

    Media action main log Beefalo.jpg

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

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

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

    Media action Si3 Beefalo.jpg