User Manual 4.4 - printable version

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Hint:

This user manual describes the SEP sesam features. Some of these features may be restricted by the license agreement between SEP AG and the customer. In addition, some features may be limited by the backup strategy implemented at the customer's site. The limitations may be released by purchasing additional licenses or by changing the actual backup architecture. Please contact your distributor or http://www.sepsoftware.com at
sales@sep.de for further information.

Introduction

Welcome to SEP sesam

SEP sesam | Backup - Restore - Disaster Recovery

The SEP sesam backup solution has been specifically designed for Server/Client environments. From a single data server to large, complex heterogeneous data centers with very large data bases and scalable Storage Area Networks (SAN), SEP sesam provides consistent, accurate, reliable and efficient backup and recovery of enterprise critical data. The modular design means that SEP sesam is perfectly adaptable for all companies, regardless of size or backup strategy from centralized to decentralized backup strategies.

To allow backup of large amounts of data in the shortest amount of time SEP sesam offers true multi-stream/multiplexed backup. From five data streams with our Standard Server offering up to 250 data streams with the Enterprise Server license. Opening up multiple streams for backups minimizes the amount of system resources for both planned and unplanned data backup tasks.

Online modules for all popular database and groupware solutions offer the ability to back up while the applications are active, providing the highest data availability possible. Restores are also possible while the apps are running, including the ability to restore single mail boxes and single mails.

SEP sesam has extremely efficient, patented algorithms. Their implementation requires only limited processor overhead, and combined with our high transfer rates (over 400GB/hr) we deliver some, if not the best, performance in the industry. SEP sesam is platform agnostic, it runs exactly the same on Linux, Unix or Microsoft. The platform independent GUI allows backup and restore in the Network, or remotely via WAN, VPN, etc.

Overview

SEP sesam is an automatic data backup system for heterogeneous computing environments.
All standard tape drives, disk drives and auto loading devices are supported and can be used for backup. In order to easily and effectively construct the configuration of the system, a design based on the following six basic components was chosen.

Principle of SEP sesam

Let's start off with the SEP sesam principle of the interaction of the individual components of a backup. After installing the SEP sesam Server the first thing you need to do is the basic configuration. This means that before securing any data you'll have to configure the backup hardware, set up the drive groups as well as drives and initialize the media pools with the according physical and/or virtual media.

In order to start a backup automatically you first need a task that defines which data of which client you want to save. Additionally you'll need a medium (via a media pool) that is inside a drive (via a drive group) and finally an event to define when the backup should run.

These basic components have to be created and adjusted in the configuration phase. The menu system of SEP sesam supports the user when creating the backup jobs as well as the schedules with the according backup events. The illustration above shows this interaction. The red arrows from the media pool to the right show the direct connection of the media Pool to a drive group. This drive group has 1-N drives assigned to it.

After this the backup media (tapes, virtual disk media, changeable media, etc.) can be added to the according media pool. This means that media pools define WHERETO the backup is saved. The data source is connected directly to the backup task and states WHAT is to be saved. The interlink that connects these two components is the schedule. The schedule states WHEN the backup is executed. The backup event is then attached to the schedule and it contains the backup task and information about HOW (e.g. Full, Diff, Inc) and WHERETO (which media pool) the backup is done.

After installing SEP sesam it is recommended to proceed the basic configuration in the following order:

Create the clients. Install client software on target computers to be backed up along with any online modules that are required.

Define tasks (WHAT should be backed up).

Define schedules (WHEN the backup takes place).

Link the schedule with an event (WHAT will be backed up WHERETO and HOW).

Grouping of SEP sesam Components

The following is an example of an embedded SEP Sesam command within a network using various storage devices.

Most of the objects described above can be arranged hierarchically and organized into groups.

Location

A Location is used to describe one or more clients/servers that may be backed up to the Sesam server. Each client must be assigned to a specific location for clarity. This is especially true when Sesam is used within a WAN-application. Locations can be hierarchically organized, i.e. multiple sub-locations can be summarized under one Location.

Drive Groups

Often several drives are used on one SEP sesam Server system. If the drives are of one type, it is preferable to bind them into a Drive Group and to direct the backup to the group. In this way, a backup is performed automatically on a drive that is currently free. In the event of a drive failure, each backup is automatically executed only on the available or operable drives. This is particularly true in cases of large autoloaders with multiple drives.

Task group

Pooled tasks within a task group can be activated with a single, scheduled event. Backup tasks can be streamed simultaneously using SEP sesam multi-streaming technology.

Media Pools

To administer media relating to the different types of backup data, backup sources (e.g. file backup, DB backup) or drive types, media must be inserted into media pools. SEP sesam requires the configuration of media pools.

Media Management

SEP sesam media management provides simple and efficient management of a large number and different types of media. Among its powerful features are:

Efficient management of large sets of media.

Protection against accidental overwrites.

Spare pools prevent failed backups due to missing media.

Recording and tracking of all media and their status: used capacity, EOL, user-defined write protection, etc.

Barcode support on loaders.

Media Pools

Media used by SEP sesam are administered in media pools using non-ambiguous labels. The labels consist of the pool name and a five-digit number assigned by SEP sesam within the pool. For this reason, a media pool name may never end with five (5) digits. In the GUI, a new media pool is created under Main Selection -> Components -> Media Pools -> New Media Pool. For details, see Configuring a Media Pool.

Media

Media should be fully utilized and written on until the EOM (end of media). No entry for EOM is necessary – SEP sesam will request a new medium from the corresponding media pool automatically when the medium or tape is full.

Media event

Media selection is triggered by setting events, which execute the strategies for media selection, reinitialize the media and prepare the media for the scheduled backups.

GET_OLDEST strategy

When there is a single media pool linked to a media event or schedule, the GET_OLDEST policy is always applied. This preserves the data on the media for the longest possible time.

If the media event includes a specific label, the system will attempt to find it and load it into a drive. The autoloader magazine must be accessible to SEP sesam or the backup will be blocked.

The GET_OLDEST strategy determines which medium is to be used next. Preference is given to media according to the following criteria:

Media whose EOL has expired. (If a save set is stored on tape, the EOL of all stored save sets must be expired.)

The oldest medium – medium with the oldest locked until (is backup day+ media EOL) date in the media pool.

Spare Pools

Blocked backups can be prevented by using SPARE pools. Spare pools are used by media events when media from the actual pool are inaccessible. A medium is moved from the compatible spare pool to the pool currently being accessed by the backup. From here, the spare media migrate to the working pools, resulting in a dynamic increase of media pool size, depending on the amount of data being backed up.

Unused media are inserted and kept for later use. For each type of drive, a compatible spare pool with free media should be created.

SPARE pools can be used to automatically insert new media into working media pools. The media are then migrated as necessary to the working pools on the production system.

Modifying the locking date of media in an archive to exceed the EOL and executing a media event.

Archive Adjustment

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.

Select the Automatic New Entry option to enter the new media automatically.

To start the adjustment using the GUI, select Main Selection -> Components -> Loader -> Archive Adjustment. For details, see Setting up Archive Adjustment.

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.

Save sets protection: Retention time and EOL

When configuring SEP sesam environment, you set up media pools and define the retention time. Media pool retention time is specified in days and defines how long the backed up data on media remains protected after the data is written to the medium. The retention time period starts with the date a save set is written to the medium and lasts for the period defined by media pool's EOL. When the protection expires, SEP sesam can re-use the media for backups again.

SEP sesam allows you to adjust EOL for individual save set (saveset EOL) or for all backup-related save sets (backup EOL).

This parameter is available under several properties views, for example, as Locked until option in the backup task properties, or as Saveset EOL (e.g., Components -> Data Store -> Properties -> tab Savesets -> Saveset EOL). It enables you to change EOL for each individual save set, stored on the respective medium. You can extend or reduce its retention time. If the adjusted save set is a part of a backup chain, the whole chain is affected. See EOL-related backup chain dependencies.

Note

Every save set that is stored on tape has its own EOL, but this does not represent the actual expiration date of the tape. Its expiration date corresponds to the maximum retention time (the longest EOL) identified on tape. Only when all of the save sets on tape have their retention time expired and the tape is no longer locked (write-protected), the entire tape is eligible for re-use.

The tape designated for re-use can then be initialized, deleting all data contained on it and preparing it for use again. If the tape is removed from the loader and then re-inserted, archive adjustment must be performed before SEP sesam can re-use the tape.

If a tape should be re-used (init) or deleted before the current EOL is reached, the media EOL (identified by tape label) can be manually reduced (note that the reduced EOL is valid for all save sets on tape). If the media EOL date has been reached, but the tape should not be re-used, the media EOL can be increased or the tape can be locked (write-protected).

Backup EOL

The parameter Backup EOL (Components -> Data Store -> Properties -> tab Savesets -> Backup EOL) enables you to adjust EOL for all save sets containing the same data. This backup-related EOL is applied to all save sets with the same data, including migrated and replicated save sets. For example, adjusting EOL of a migrated save set from 2.12.2016 to 12.12.2017 results in changed EOL for all related backup data, i.e., original backup, replicated backup, as well as for all backups in a backup chain, if a save set with adjusted EOL is a part of it.

EOL-related backup chain dependencies

You can extend or reduce the retention period for an individual save set or backup-related save set, as described above. Keep in mind that increasing EOL of a DIFF or INCR save set will result in increased EOL of all dependent backups (FULL and other DIFF and INCR) in order to retain the backup data. This keeps the backup chain readily available for restore. On the other hand, decreasing EOL of a DIFF or INCR save set to a date in the past will result in a warning message prompting you to confirm your decision to set the whole backup chain to already passed time. By setting EOL for DIFF or INCR save sets to expired time results in purging and overwriting the complete backup chain.

Note

The storage space of each save set can be re-used when the following conditions are met:

Its EOL has expired. (If a save set is stored on tape, the EOL of all stored save sets must be expired.)

If a save set is stored on tape, it must not be write-protected (locked).

Typically, there must be no other save sets that depend on this save set. You can override this condition by explicitly allowing the EOL for the whole backup chain to be set to expire, thus deleting backup data on all related save sets.

SEPuler – an event calendar

SEPuler is a process that controls the scheduling of all SEP sesam tasks, such as backup, migration, replication, restore and other tasks. It acts as an electronic calendar and assistant performing all SEP sesam data protection events.

SEPuler is a permanently active background routine (daemon), constantly searching for events to be executed. When SEPuler finds a scheduled task or manually triggered event, the execution of the corresponding program is initiated.

Once the event has started, SEPuler will determine the next execution event for a cyclical task and rewrite the event to the task calendar. For example, if SEPuler starts a weekly backup on January 1, it will schedule a new weekly backup to occur on January 8.

Events initiated with the Immediate start command from the GUI or command line are posted in the calendar as non-recurring events.

All events in SEP sesam start from the SEPuler schedule, even if they are unique, non-recurring tasks. An overview of scheduled as well as completed, expired events and their current status is provided by Calendar sheet from the Main selection -> Scheduling -> Calendar sheet.

Schedules

Schedules are used for setting events to occur at a specific time. A schedule is a timetable that defines the cyclic behavior of an event, i.e. when the event is to take place and how frequently to repeat it. The fact that a schedule exists does not automatically mean that an event is executed.

Only when one or more events (backup, migration, command, etc.) are assigned to the schedule, it becomes active. The entries in the schedule are then picked up by the SEPuler. Modifying a schedule affects all the events assigned to that schedule.

Flexible scheduling features include the following:

Any number of events of the same type can be linked to one or more schedules.

A task (backup, migration, replication, media action, restore and command event) may have events in several schedules.

From v. 4.4.3 onwards, schedules provide User defined option that allows you to create a calendar which is customized according to your country or company specific requirements. You can use it to exclude scheduled jobs from running on specific dates, such as holidays, or to schedule additional jobs on selected dates. For details, see Creating Custom Calendar.

A schedule's execution can be deactivated: a schedule will remain displayed as shaded in the list of schedules, but the related jobs will not run.

As of 4.4.3 Grolar, a new option Without Schedule is available. It shows all backup events which are not assigned to a schedule. Such events are typically created for external backups, where the external applications manage the backup scheduling. For details, see Schedules 4.4.

Event Priority

For complex event strategies, event priority is used by SEPuler for resolving scheduling conflicts. Priorities can be assigned to events, from lowest (1, default) to highest (99). For each SEP sesam backup day all scheduled events are checked according to their type and priority to see whether the events of the same type (for example, a backup) with the same task name and higher priority have already expired or are still planned to run; in the latter case, SEP sesam suppresses execution of lower priority events of the same type. In other words, if there are more equal events (see equality of events) of the same type scheduled on the same backup day, only the event with a higher priority is executed. This prevents the events that might be linked to several schedules, which overlap on certain days, to be executed except for the one with the highest priority.

If all equal events of the same type have the same priority (for example, the default – 1), then all of them are executed. Events with priority 0 are not checked for dependency of event priorities and are always executed.

Event priority determines which job in a queue will first be executed regardless of the equality of events. If there are jobs in the queue and a new event with a higher priority is activated by SEPuler, this job will first access a busy device.

Equality of Events

The equality of events is managed according to their type:

Backup events are equal if their task name is the same. The same is true for each individual event type: migration, replication, command and restore event.

Media events are equal if their drive number or drive group number is the same.

Example
In the following example, backup of the directory /etc of the client stratum1 with the task name stratum1_etc is started via three different schedules.

Name

Time

Prio

Task

Daily

8 p.m.

1

daily incremental

Weekend

6 p.m.

2

differential on the weekend

End of Month

9 p.m.

3

full at the end of the month

On weekends, the weekend event is performed instead of the daily event (prio 2 overrides prio 1).

At the end of the month, the end of month event is performed instead of the daily event (prio 3 overrides prio 1).

If the end of the month and the weekend coincide, then the end of month event is performed instead the Weekend event (prio 3 overrides prio 2).

Blocking Events

A blocking event is any type of event with a higher priority that obstructs another event and prevents it from moving to active backup status. It may be used to prevent the activation of certain events on specific days (e.g., end of year, end of fiscal year, holidays, etc).

Note

A blocking event is created by selecting the Blocking date checkbox during the configuration of an event.

Switching off a schedule blocks the execution of all events using this schedule (Execution option in the schedule).

A blocking event only affects other events with the same name when schedules are overlapping.

A blocking event suppresses any job with the same task name at respective (SEP sesam backup day) day, regardless of whether it is scheduled to be run before, during or after the blocking event.

Example

A backup event that executes the task stratum1_etc is configured to run daily with priority 2. A second backup event for the same task stratum1_etc is only scheduled for December 24th every year as a blocking event with priority 9. On December 24th, the priority check detects the stratum1_etc backup with higher priority and overrides the execution of the daily backup. The blocking event itself does not create an entry in the job status, but sends a notification that it was activated.

Automatic backups

SEP sesam introduces a powerful scheduling service called SEPuler. It is constantly checking for backup, restore and other predefined tasks to be executed. When such a task is found, a SEPuler initiates the execution of the event. To prevent possible tasks conflicts and efficiently manage tasks in execution queue, SEP sesam uses the event priorities.

You can schedule your backups to run automatically once you have configured your SEP sesam environment and created required backup tasks for the clients you wish to protect. SEP sesam provides a comprehensive and flexible schedules.

You can create a number of schedules for any kind of events. For example, you can create a schedule daily for a number of events or configure more schedules (e.g., weekly full, daily incremental) for the same data protection. Besides the custom and daily schedule, weekly, monthly and yearly are also available. Note that a schedule must have at least one event assigned to it.

Step 5: Configuring a backup task – select WHAT you want to back up: select the appropriate predefined task type (previously called backup type), according to which the data is backed up (default is Path, others are SAP Hana, Exchange Server, Lotus Notes, MySQL, VMware vSphere etc.), specify the data you want to backup (source) and optionally set additional parameters and define pre/post scripts

Backup level (C, F, D, I)

When creating a backup event in the Main Selection -> Scheduling -> Schedules -> New backup event, you also specify the backup level (note that the naming was changed from Backup type to Backup level in Grolar).

The following backup levels are available:

A FULL backup always copies all data specified by the backup task, regardless of whether it has been changed or not. A save set created as FULL is the basic save set for subsequent DIFF or INCR save sets. While the backup time of a full backup can be significant, restore is fast and simple since only one backup save set is required. Information about the backup status is stored in the SEP sesam database. Note that the archive bits are not deleted on Windows systems. If you want to force-reset of the archive bits, you can enter the command -o clear_archive in the backup options.

A DIFF (differential) backup saves only data which was created or changed after the last FULL save set had been created (of the same task). A differential backup is faster than a full backup, however, to restore the whole data source, first the save set of the full backup has to be restored followed by restore of the DIFF save set. For this, SEP sesam provides generation restore that enables browsing for and selecting for restore all generations of backed up files since the last full backup.

An INCR (incremental) backup saves only data that which was created or changed after the last backup (FULL, DIFF or INCR) of the same task. This is the fastest backup method and requires the least storage space. Restoring from incremental backups is the slowest, because it requires all related save sets to be copied back – the save set of the last full backup as well as all INC backups. You should consider the advantages of time and resources when planning your backup strategy. A combination of FULL backups stored to tape drives, and DIFF or INC backups stored to virtual disk media is a common method.

A COPY backup is a full backup that has no influence on following differential (DIFF) or incremental (INCR) backups. For the treatment of archive bits, see FULL backup above. COPY backup is usually used for additional full backups, e.g., monthly backups, or backups for archiving, i.e. removal from storage.

Note

In case no initial FULL backup exists, differential (DIFF) or incremental (INCR) backups are automatically performed as FULL backups.

Parallel Backups

Modern tape drive manufacturers are dramatically increasing device performance and capacity. Few of today's backup software products are able to fully utilize the new functionality to its greatest advantage. The drive is often in a 'stopped' or waiting mode for data from the backup source.

SEP sesam is one of the few backup software products that can be used for receiving data from other backup sources. Sesam Multiplex Stream now offers up to 124 channels for a single drive. Each of 124 channels can serve one backup source.

Data of the different streams are distributed into packets, each packet is supplied with an identification mark and copied to the backup media. The data of a certain stream is not contiguously positioned on the media, but interrupted by packets of other streams. The identification marker of the packets enables SMS to restore the initial stream during reading.

Furthermore, SMS is able to split save sets across several media that still have some free space left (specified by media properties parameter EOM – End of Media).

The maximum number of parallel streams that can be used during backup to the backup drive is specified under the Drive properties by parameter Max. channels. Note that the number of available data streams depends on the type of Server License, e.g., ONE provides 1 backup stream, Standard provides 5 backup streams while Advanced provides unlimited number of streams (dependent on the system configuration and available throughput).

SEP sesam encryption for save sets can be enabled in the backup task properties under the tab Encryption and compression for each backup task. Supported encryption algorithms are the Advanced Encryption Standard (AES) 256-bit encryption and the Blowfish encryption. You can select the type of encryption by clicking the Encryption and compression tab in the backup task window (Main Selection -> Tasks -> By clients -> select a client and a task, and double-click to open the properties window).

You must create an encryption key for the data to be encrypted, but you can decide whether the encryption key (password) will be stored into SEP sesam results database or not. If the encryption key is not stored by SEP sesam, you will be prompted to enter it before the restore is started in the restore wizard.

If the encryption key is stored in the SEP sesam database, the key itself is also encrypted and is used automatically for decryption during restore. Data is encrypted before it is transferred over the network and copied to a save set.

You can determine which backup tasks are encrypted by checking the backup task properties, where you can also reset your password, or in the backup results table (Main selection -> Job state -> Backups -> click the selected task to display its properties and look for the Encryption key field).

If you change the encryption key, all backups started after the password has been changed will be encrypted with the new key. This new key will be stored with the backup, however you will have to enter the password to restore your data.

Note

A password cannot be longer than 28 characters and may not use any special characters (underscore, hyphen, etc.) Spaces are also not permitted.

Setting encryption

Backup with VSS (Volume Shadow Copy Service) on Windows

Microsoft Volume Shadow Copy Service (VSS) is a Windows service for backing up running applications. VSS coordinates with other VSS-aware applications and services, and creates a shadow copy or snapshot of data for backup purposes. VSS uses a copy-on-write snapshot, allocating a small temporary storage space for it. Once the snapshot is completed, the temporary storage space is freed up again.

From SEP sesam client version 4.0, every file system – Path backup of a Windows client has the option to backup with VSS enabled by default. This option is available in the backup task properties and should only be used with the task type (previously called backup type) Path. All other task types, for example System state, use the required VSS writer by default.

NDMP backup

As of version 4.4.3., SEP sesam enables you to protect and manage your storage file servers by providing support for Network Data Management Protocol. NDMP is a common protocol for backing up and restoring data on storage devices that do not support installation of a backup agent.

It ensures interoperability between NAS file servers and SEP sesam, and is used as an interface that enables SEP sesam to backup various NAS appliances and copy this data to a SEP sesam Server or Remote Device Server. SEP sesam supports version 4 of the NDMP protocol.

HSM-aware backup for Windows

Hierarchical Storage Management (HSM) is a method for reducing the costs of data storage and facilitating data management tasks. Starting with SEP sesam version 4.4.2, HSM-aware backup for Windows comes as an integral part of the SEP sesam package.

It provides efficient backup of data on Windows systems that is managed by HSM. SEP sesam as an HSM-aware solution recognises the reparse tags in stub files and does not trigger a recall of the original files, but performs a backup of the placeholder files without retrieving their contents. For more details, see HSM-aware Backup for Windows.

Support for NTFS alternate data streams (ADS) for Windows

As of version 4.4.3, ADS are backed up by default when backing up an NTFS file system. They are automatically restored to any ADS-aware system. ADS are backed up by default, but can be excluded from backup by using a special option in the backup task properties.

Alternate data streams are a unique data-hiding feature of NTFS file systems. A file in NTFS consists of the unnamed data stream where the data is actually contained, and of alternate data streams that can store additional metadata. Applications may use ADS for storing file attributes. For details, see Support for NTFS alternate data streams (ADS) for Windows.

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

As of SEP sesam 4.4.3. Tigon v.2, it is possible to restore save sets online with the Self-Service Restore Assistant, if you are granted appropriate permissions. For details, see Self-Service Restore Assistant.

Selective restore

During selective restore only a subset of files of a save set is selected. Sesam positions the media at the last mark before the selected data, skips unselected files and transfers only the desired files. This guarantees a quick and network-optimal restore.

Generation restore

Selective restores from differential or incremental backups require a chain of several restores starting from the last full backup. Sesam automatically switches to the generation view and handles the arrangement of these single steps for the user.

In the generation view, all generations of files are presented: The selection list displays not only the files from the selected differential or incremental backup, but all files since the last full backup.

In the SEP sesam GUI a specific view can be chosen, either the view for single backups or the generations view. The single backups view enables the user to specify only works on the selected type, whether it is an incremental or a differential restore (similar to a normal restore).

Scheduled restores

Scheduled restores are performed by creating an event or task. It is also possible to schedule a restore for data that has not yet been backed up. The selective restore can be set to run at the completion of the daily backup routine, e.g., the last backed up file can be restored, preferably to a new directory and the data validity established.

Restore wizard

Restore wizard is triggered from the menu bar -> Activities -> Restore. The following restore options are available in the restore wizard to define how your data will be restored.

Step 1: Welcome page
By default, the welcome page is not displayed when starting the wizard. It provides only general information on specifying restore process.

Step 2: Filter
You can select how you want to search for your backed up data. Save sets can be searched by task name in the save set, or by filename or path.

All task for which backups are available can be selected from the Task drop-down list, or a regular expression can be entered into the Search pattern field to search for files by their name or path. In the latter case, if all tasks should be searched, use the All button. Note that searching might take some time (depending on the amount of processed tasks). Saved in period allows searching for save sets only within the specified time frame. Show external results extends the search to the save sets generated with supplementary backup tools and interfaces, such as BSR Pro, MySQL, DB2, etc.

Step 3: Select task
The results of the search are displayed in the table.

You can enable any of the following options:

Complete restore of selected task will restore everything in the task.

Hide migrated means that the save sets that have been moved with a migration task will not appear in the results.

Broken tasks will also display the save sets with the status cancelled.

Generation restore must be enabled if you are restoring from an incremental or differential backup.

Disaster restore should be enabled if you are restoring a server from a disaster scenario.

For details on disaster recovery, see SEP sesam Server Disaster Recovery. If a client server is being recovered, simply select the server’s disaster recovery backup task.

As of SEP sesam v. 4.4.2, a checkbox Mount save set under the Single File Restore becomes available after selecting the save set for restore. You can mount any non-compressed and non-encrypted file-based save set stored to default data store Path or to Si3 data store. Mounting is not possible if the save sets are stored to tapes. For more details, see Cross-Platform Recovery File System Layer.

Note

It is recommended that this option is enabled for restoring specific data, such as Exchange, Hyper-V and V-Sphere backups, because it provides faster restore time and performance. The target save set is mounted to the SEP sesam home directory var\tmp\mnt, e.g., C:\Program Files\SEPsesam\var\tmp\mnt\save_set_ID. This way the save set is instantly accessible for browsing and searching before the actual restore is even triggered, providing you with quick access to your data, such as single mailboxes. The mounted save set is basically a virtual read-only file system, therefore it cannot be altered or otherwise damaged.

Step 4: Select files

Individual files can be specified for restore.

The file explorer is used to specify the files to be restored.

The Search button below provides an additional option to search for files within the target save set.

Step 5: Save and start

The final step of the restore wizard provides an overview of the restore task. In the table above the save set that is selected for restore is displayed with its attributes. In the Name field, the name of the task is assigned automatically and can be modified.

Most of the following options already have default values or are enabled by default and can be used in most cases. Some provide fine-tuning needed for more specific data restore.

Drive: The number of the drive with backed up data (more relevant for tape backups without a loader). Optionally, select the drive number of the drive that will be used to read the data. Typically, you use this if you have configured additional drives and you want to assign dedicated drives for the restores. For details, see the option Create second drive (introduced in SEP sesam 4.4.3 Tigon) in Configuring a Data Store.

Interface: The name of the server FROM which the files are being restored. This is either a Remote Device Server (RDS) or the SEP sesam server.

Target node : The name of the server where the files are being restored TO.

Preferred media pool: If the data was migrated or replicated and different media pools were used for the process, the source media pool to restore from can be selected from the drop-down list of available media pools.

Used media | Barcode: If the data was migrated, the migrated copy is stored to another media. Here the source media to restore from can be selected from the drop-down list of available media.

Target path settings provides the following options:

Restore to original path is selected by default and restores the data to the same location from which it was backed up. Note that this only applies if the target node is the same server from which the data was backed up, i.e. when source and target server are the same.

Original tree structure is enabled by default when restoring to original location. The directory structure of the restored files is the same as the original directory structure of the backed up data. If this option is disabled, the directory structure is not recreated and only the files are restored (flat structure).

New restore target should be selected when restoring files to some other location. The path to the directory to which the data should be restored can be entered manually or by using the Browser button to open the file explorer.

Execution options provides the following options:

Do not overwrite existing files is selected by default. Files will be restored only if they are not already present on the target system.

Overwrite existing files will replace files on the target system with their restored version.

Create a new version will restore files under a new name.

Expert options
Clicking the button Expert options will open a new window, where more specific options and actions can be defined.

Options tab

Verbose level allows user to change the verbosity of the main log to display more information than the default logging mode. Verbose logging is divided to levels 0 to 6.

0: Print only standard and error messages together with summary.

1: Add a line for every item when its processing starts: sbc-3008: Info: Processing item: [xxx]...

2: Add a line when processing for item is finished: sbc-3108: Info: Item processed successfully: [xxx]

3: Add backup module processing information (with DB_API modules).

4: Add underlying module processing XBSA and detailed DB_API modules.

5: Add packing data (mtf, cpio, sidf) trace messages.

6:

Restore options text box allows for other specific options to be entered.

Based on the specification in the previous parts of the wizard, one of the following is already selected: Restore the complete save set , Restore according to composed list or Disk_info disaster recovery. Changes of these restore options will override the specification made in the restore wizard.

Restore the complete save set will restore all files of the save set.

Restore according to the composed list will create a selective restore according to the regular expressions used in filter (see Filter tab below).

Disk_info disaster recovery will restore disk info, for example a master boot record and registry during disaster recovery.

Relocation tab
By default, no relocation is selected, restoring files to original path . If with relocation is enabled, a new target location can be specified for restored files. Individual files can be restored to separate paths.

Filter tab
Files for a selective restore can be defined using regular expression-based filtering.

Task type tab
By default, the task type according to which the data is backed up is selected (default is Path; other task types are, for example, Hyper-V, SAP Hana, Exchange Server, Lotus Notes, MySQL, VMware vSphere etc.).

When you have backed up data with task type other than default Path, for example Hyper-V, you can still use the option As path backup. This option allows you to restore your data directly to the file system without any additional action, for example, files from a Hyper-V backup, rather than restoring according to your special type, for example, restoring (and importing) Hyper-V data to the Hyper-V manager.
The option Write save set into file allows you to restore the entire save set into a single file.

Pre/Post tab
Specifies whether any pre or post script should be applied for this restore task.

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.

EOL tab
Specifies for how long (in days) this restore task will be kept and can be accessed using GUI. Default is 7 days. The value 0 means that a restore task will be kept permanently unless you manually delete it.

Start time tab

Instead of starting your restore immediately, you can specify the Start time by entering the desired date and hour.

In the Delay start for up to, the maximum allowed startup time (the amount of time an event can be in the queue) can be specified in days and/or hours. The actual event startup depends on the processor load of the system. At the starting time of the event, every event is forwarded into the queue, where it might wait until jobs with a higher priority are finished. For jobs with the same priority, the FIFO rule (first in first out) applies. If the event cannot be executed within this specified time frame, it will not be executed at all.

Stop task if it runs longer than can be defined by setting the amount of time (days and/or hours) after the event's scheduled start time at which the event will be cancelled.

Additionally, Stop task at can be used to define the exact date and time when the task should be stopped.

A Follow Up event can be specified to trigger the predefined event on the SEP sesam Server once the restore is completed. For details, see Follow-up Events.

Duplication and Migration

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

This allows for the duplication of save sets. To optimise migration performance, only successfully backed-up save sets or save sets with warnings (status successful or with warnings) can be selected for migration, whilst save sets with errors or partially restorable save sets (containing data from cancelled backups) are not migrated.

Provided that the media in the source and target media pools are available after migration, the save set is duplicated; however, a save set is considered to have been migrated if it is deleted from the source media pool. Both, source and target data sets can be accessed with the restore wizard. If only the migrated save set exists, it will be required in the event of a restore.

Migration tasks are managed under Main selection -> Tasks -> Migration tasks menu. The source and target media pool must be defined in a new migration dialog. Additionally, a number of filter options are available (including by task, task group or backup client). You can also migrate backups from a specific medium to a different pool.

You can start a configured migration task from the GUI immediately or attach it to a scheduled migration event so that it starts automatically at a predefined time.

Storage Time Limit, Media Cycle

Before implementing an automatic data backup, the user should consider the overall backup concept.
In particular, the storage time limit and the number of required media and media cycles must be determined.

If the data is of a rather homogeneous structure, relatively few different media pools will be needed. For a heterogeneous structure a pool should be created for each category or operating system to enable flexible and adaptable strategies. All media can, of course, be kept in one pool.

It is necessary to distinguish between and make decisions regarding short term and long term storage of backed up data. Short term storage is a media cycle, i.e. media are reused for backups on a weekly to biweekly rotational basis. The effect of a proper strategy and implementation is a full, uninterrupted history of data. This will enable the restoration of small, granular changes in the data if required.

In addition to this cyclical usage of the storage media for daily or weekly backups, the user should also store backup snapshots in long term storage. These snapshots would include end of month, end of quarter and/or end of year.

Implementation of a cohesive and understandable backup strategy is critical to the smooth operation of the customers IT infrastructure.

Ultimately the customer must make the decision how data will be stored. It is always a compromise between the data volume that is possible and the requirement both for legislative data retention and historical data retention to keep the enterprise fully operational. SEP Software or its resellers can help in the overall determination of both data volume and data retention.

Attention

Two different possibilities for backup strategies are:

Keep and store all backups.

Advantages: All data can be recovered for any time slot.
Disadvantages: Loss of oversight - too much data on too many tapes (clarity), excessive storage capacity required, cost.

Use a single media,

Advantage: easy restores
Disadvantage: only the last day's changes are available.

Basic Configuration

This is a step-by-step description of how to configure SEP sesam to perform a simple data backup using the components mentioned above. The detailed description of the interface elements can be found further below.

Step 1: Locations

Once you decided which computers you want to protect in your environment and have installed relevant SEP sesam component(s) on them, you can set up your backup environment. Make sure that you have permission to access the respective systems.

In the Main selection -> Components -> Topology, you can view your backup environment: displayed are SEP sesam server(s) and clients as well as the configured loaders and drives. This grouping of clients and storage devices is referred to as a location. Each client must be clearly assigned to a location. By default, the location is set to 'LOCAL'.

You can use locations to group your clients according to their OS, data type, different geographical location etc. The name of locations can be freely assigned and is used for orientation purposes. The following screenshot shows the backup environment, which consists of several locations. You can create a new location by using the New location option in the main window menu.

Step 2: Clients

You can configure a new client in the Main selection -> Components -> Topology -> New client.

Tab Client

Depending on the operating system of a client, either Windows, UNIX, VMS or NetWare platform is selected. You can select a location to which you want to add a new client from the drop-down list of configured locations.

The client name which will be backed up (target client) is inserted into the GUI associated with the name of respective server within the network performing the backup tasks. The backup data may reside on the server (typical); on the client (Remote Device) either on second disk drive or tape; or the data may be sent over a LAN or WAN to a Storage Area Network.

If there is a name server (DNS) in the network, SEP sesam automatically selects the TCP/IP address. Otherwise it must be entered in the etc/hosts file.

Operating system

Select the operating system version of the computer you are adding as a client.

Access mode

Select the access method for the server-client communication.

CTRL: Default access mode.

SSH: SSH method is an encrypted network connection, based on SSH implementation of the used operation system. You must configure automatic login from SEP sesam Server to client using the public key.

PROXY: Use this method if there is no direct remote access to the client. The data transfer is executed via vendor specific protocols, the client is accessed via the mandatory data mover. For details, see What is a SEP sesam data mover. The following protocols are supported: vSphere (vCenter Server), Citrix Xen Server, NetApp and Novell SMS for NetWare 5.1/6.0/6.5.

RSH: Remote Shell is a historic old option, which is rarely used.

Last message

Once configured, the most recent system status message is displayed (e.g. communication error during client creation).

Notes

Optional comment.

Interfaces

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.

VM Server Type

If the client should be handled as a VM server, select the relevant type. This enables, for example, browsing the virtual environment when creating backup tasks.

SBC Version

In the left corner, there are two additional options:

Locked for backups

If a client needs to be excluded from the backup for technical or other reasons, you can deactivate it by checking this option.

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.

Client is a virtual machine

Selecting this option allows you to edit the VM host (name of the VM Server) and the VM name. These values are used to identify the backup client as a VM in a virtual environment.

Tab Options

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. For details, see Topology: Firewalls.

Additional tab

If you are configuring clients that must be backed up by special task types, additional settings must be specified. A third tab is available for the following task types: Micro Focus Open Enterprise Server (formerly Novell OES), VMware, Citrix XEN, MySQL, PostgreSQL, NetApp, RHEV. 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).

For more information on specific task type, see the respective wiki articles under Extensions.

Once all the options are set, click Create or OK. Clicking Create will leave the dialog window open, allowing you to quickly configure several clients one after another. Then a new dialog box appears asking whether you want to create a new backup job for this client. Click Yes to create a backup task or No if you intend to configure your backup later. For details, see Standard Backup Procedure.

Your new client is displayed in the Topology content pane.

Step 3: Storage Hardware - Drives and Loaders

During installation SEP sesam checks the SCSI-connected storage devices and enters their data into its database. For certain types of loaders the connection between loader and drives cannot be recognized automatically. In this event these devices must be verified manually and entered into the configuration.

To enter devices manually, go to Main selection -> Components -> Loaders. Each loader is marked and its properties are entered. By clicking OK the device is entered into the configuration. It is highly recommended to set the "Automatic Unload" function to 'NO'.

Note

When using 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 drives, an analog procedure is applied. You can view the properties of each drive in the Main selection -> Components -> Drives -> Drive groups. The default drive group is Tape drives.

If the drive characteristics in the field Loader states No Loader but should be serviced by an autoloader, the drive was not recognized/configured properly. You can enter this drive into the configuration location by selecting OK.

Note

The first drive in the loader is Drive 0. If there are more drives in the loader, they will be numbered sequentially.

</div>

Step 5: Tasks - Select what you want to backup

In the Main Selection -> Tasks -> By clients, select the location of your client and then the client which you want to back up. Right-click it and select New backup task.

In the New backup task window enter the parameters for your backup task.

From the Task type drop-down list, select the appropriate type, default is Path.

Specify the Source: enter which drives, directories and/or files you want to backup. If you want to backup everything, enter source all.

Optionally, you can specify the filenames or patterns which should not be backed up in the Exclude list. For details on different exclude options, see Creating Exclude List. If you want to add a comment, enter it in the Comment field.

If you want to define other options, such as the pre/post backup and restore commands, set encryption or compress data, add a task to the task group, or assign a task to the schedule, click the corresponding tabs in the New backup task window.

By clicking OK you create a new task. If you want to start the newly created task immediately, right-click the name of the task and click Immediate start. If you want to schedule the task, click New schedule in the Main Selection -> Scheduling -> Schedules.

Step 6: Schedules

In the Main Selection -> Scheduling -> Schedules you can view all configured schedules and events that are connected to them. Use the buttons in the toolbar to configure scheduling of all processes in SEP sesam.

You can create a new schedule or use an already existing one. In the schedule a new event is created and its job is defined. The job is then processed at the set time and, if necessary, forwarded to the next execution time in the calendar.

Depending upon your SEP sesam version (4.4.2 or 4.4.3), schedule options may be slightly different. For more information about the options and more details, see Creating a Schedule.

The 4.4.3 version provides a few additional options, such as user-defined dates (custom calendar), described in Creating a Custom Calendar.

Step 7: Starting a Backup

For a one-time backup, click the button Immediate Start: Backup in the main toolbar. Then choose a task and a media pool (default settings apply) so the task can be initialized.

To configure a normal, periodic backup, a schedule is created which implements the desired recurrence of the backup. Next, create a new event using this schedule. The backup is now inserted into the event calendar and will be initialized by the SEPuler at the specified time.

When the backup is finished, its execution and completion can be verified in the Main selection -> Scheduling -> Calendar Sheet or Main selection -> Job state -> Backups. This save set also appears in the restore wizard. It can also be accessed from the command line under backups > Status.

Directory structure of SEP sesam software

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

SEP sesam directory aliases

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

<SESAM_BIN>

Refers to the part of the directory structure of a Linux package installation in which the unchangeable files (e.g., binaries) are stored. Path /opt/sesam can not be selected during installation.

<SESAM_VAR>

Refers to the part of the directory structure of a Linux package installation in which the variable files (e.g., configuration and log files) are stored. Path /var/opt/sesam/var is not arbitrary during installation.

<SESAM_ROOT>

Refers to the install location of the SEP sesam file structure for a Linux tarball or a Windows installation. This means that both tarball and Windows installations show <SESAM_BIN> and <SESAM_VAR> on the same location in the file system (referred to as <SESAM_ROOT> here). The install directory must be specified during a tarball installation (default path is /opt/sesam) and also during Windows installation (default path is C:\Program Files\SEPsesam).

SESAM_BIN directory

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

What

Where

Database components

SESAM_BIN/bin/db

GUI components

SESAM_BIN/bin/gui

Dedupe components

SESAM_BIN/bin/sds

Server components

SESAM_BIN/bin/sesam

Communication components

SESAM_BIN/bin/sms

Templates incl. raw versions for first installation

SESAM_BIN/skel

Templates for programmable interfaces

SESAM_BIN/skel/templates

SESAM_VAR directory

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

What

Where

Database

SESAM_VAR/db[_pg]

SEP sesam database backup

SESAM_VAR/db[_pg]/backup

Configuration files

SESAM_VAR/ini

SSH keys for control communication

SESAM_VAR/ini/sm_ssh

SSL certificates for data transfer

SESAM_VAR/ini/ssl

Notification and metadata logs

SESAM_VAR/lis

Main directory for log files

SESAM_VAR/log

Logs of the Pre- and Post- jobs

SESAM_VAR/prepost

Status and daily logs

SESAM_VAR/prot

Media action logs

SESAM_VAR/prot/media

SEP sesam interface logs

SESAM_VAR/prot/notification

Restore logs

SESAM_VAR/prot/restore

Temporary files for transient storage

SESAM_VAR/tmp

Temporary files for longer storage

SESAM_VAR/work

Mountpoint for VMware and other single item restore tasks

SESAM_VAR/work/mnt

Example

C:\Program Files\SEPsesam

Sample directory structure

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

The SEP sesam Graphical User Interface (GUI)

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

It consists of title-, menu- and tool bar (top). On the left, it provides the Main selection window (left), the content pane (middle), the properties pane (right), and activities display window (bottom).

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.

In the Main Selection window on the left components of the SEP sesam system are shown.
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.

At the bottom activities display window, messages and log file protocols for the selected drives or activities are shown.

Master sesam

The Master GUI is used to administer multiple SEP sesam Server environments from a single location. This mode can be activated by starting the GUI with parameter -M1 (default -M0).

In Master mode, additional SEP sesam Servers can be connected to GUI by selecting Configuration -> Remote server in the menu bar, then adding the additional servers, and setting their connections to On. Inaccessible servers are displayed in the table view. The GUI client must be authorized to administer additional SEP sesam Servers.

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 or to all sesam servers.

Windows

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

Example of an adjusted GUI

Main Selection

In the Main Selection Window (Left) you can see a list of the components of the SEP sesam system. By clicking further down the tree where you can find more detailed information (or right click to Expand all). Once you select a component in the main selection window a corresponding work window is opened.

Content pane

In the work window the corresponding object class for the required function is displayed, e.g., selecting Components -> Topology enables you to configure locations and clients.

Activities display

The activities window at the bottom of the GUI displays two tabs: Current Messages and Performance.

Current Messages

Last notification shows the result of the last activity. If the option cyclic is enabled, cyclical refreshing of the Report Interval will return the relevant messages.

You can select desired drive for the output of the "running notifications".

Example for the Drive Selection:

*

all drives

1

drive 1

1,2

drive 1 and drive 2

2-5

drive 2 to drive 5

Performance

To select the drives you wish to watch or control, select the Performance tab (default position: bottom left).

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 features

SEP sesam GUI can be adjusted almost without limitations. For details, see Window.

Menu bar and Toolbar

In the menu bar you can find the menus File, Activities, Configuration, Window and Help.

Toolbar

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

Dashboard allows you to handily check SEP sesam operations and their state, and provides key metrics of your backup environment.

Immediate Start: Backup displays the backup dialog that enables you to select a task incl. all other parameters and start the backup immediately.

Restore Wizard opens the wizard that enables you to start the restore immediately.

Calendar Sheet displays an overview of all scheduled, completed and expired events with their current status.

About SEP sesam displays the SEP sesam version information.

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

File

GUI update

Get the most recent GUI version from the SEP sesam Server if the current one is outdated.

Export Sesam Database

Execute export of the entire SEP sesam database. In addition to the recommended periodical export of the SEP sesam database, performed as a part of SEP sesam self-backup, you can manually generate export.

Import Sesam Database

Replace the current SEP sesam database. You can import the SEP sesam bootstrap database file which was attached in the email sent by disaster interface. For details on preparing for a SEP sesam Server self-recovery, see SEP sesam Server Disaster Recovery.

Exit

Close all opened windows. Running processes, such as backup and restore are not affected.

Activities

Dashboard

By clicking the dashboard item SEP sesam web dashboard is displayed. This online monitoring tool constantly tracks SEP sesam operations and their state and provides key metrics of your backup environment. You can check if all your backups and restores have been completed successfully and review other various useful information, such as daily, weekly, monthly or custom statistics on SEP sesam events, on total size of backed up and restored data and on data store utilization.

You are able to filter the reports by events, clients, tasks and state; check backups and restores per client or application over time; get an overview of up-coming events and data store utilization. Note that all information provided by SEP sesam dashboard is currently read-only. For details, see SEP sesam Dashboard.

Restore

By clicking the restore item you start the restore wizard which leads you through the process of restoring backup files from backup media (tape, disk, etc.) to the desired computer (client). Note that the options in the restore wizard change depending on the selected task type for restore, therefore some options may not be available.

Searching by task name

Search for a certain task intended for restore by using the fields Task and Saved in period. If you use the wildcard [*], all tasks are selected. After clicking the Next button, all save sets created within the given period are shown in tabular form.

Searching by filename or path

Search for the known files or directories to find the backups that match the search term. Use input-field Search pattern for filename or path together with drop-down boxes Task and Saved in period to narrow the search requirements.

Note

By using the wildcard [*], all tasks are selected which may take a long time to process.

After clicking the Next button, all save sets created within the given period and matching the search pattern are shown in tabular form.

Show external results

If this option is selected, the "external" backups will be displayed. Typically, these are the backups that would normally not be restored directly by the restore wizard (e.g., Oracle, DB2). You can restore a save set directly from the backup media into the file system and then process it in a special way.

Select Task

Select the backup you want to restore. Choose one of the following options:

Complete restore of selected task

If this option is selected, no further selections or additional options are available. You go directly to the final step of the restore wizard (start of the restore). If it is not selected, the file selection is available for selective restore.

Hide migrated

If a backup job has been migrated, the restore wizard will by default provide the original save set if it is accessible. Hide migrated is enabled by default. To force the access to the migrated data, you have to deselect it. If the original save set was deleted, the migrated save set will be displayed by default.

Broken tasks

If you select this option, broken backups will also be displayed. Keep in mind that it is only possible to restore data from the backups that have completed successfully.

Generation restore

If a DIFF or INC backup is chosen for restore and this option is enabled, SEP sesam calculates all required restore steps from the last FULL backup to the selected DIFF/INC version. The whole backup chain is processed for restore without user intervention, including all media changes, etc. If this option is disabled, only the selected backup (INC or DIFF) will be used. Once you selected the desired save set for restore, click Next to display the Select Files window.

Disaster restore

This option is only available when a SEP sesam self-backup (SESAM_BACKUP) is going to be restored. This function provides a recovery of the SEP sesam Server after a system failure. For details, see SEP sesam Server Disaster Recovery.

Mount save set

As of SEP sesam v. 4.4.2, you can select the option Mount saveset under Single File Restore to mount the target save set to the disk and make it accessible as if it was a separate volume on the disk. It is a recommended option for restoring specific data, such as Exchange, Hyper-V and V-Sphere backups, because it provides faster restore time and performance. You can mount any non-compressed and non-encrypted file-based save set stored to default data store Path or to Si3 data store. Mounting is not possible if the save sets are stored to tapes. The target save set is mounted to the SEP sesam home directoryvar\tmp\mnt, e.g., C:\Program Files\SEPsesam\var\tmp\mnt\save_set_ID. For more information, see Cross-Platform Recovery File System Layer.

As path restore

This option is available for restoring from task types that store directories and files similar to path backup. For example, you can use it instead of a Hyper-V or VMware task type, but it is not available for other types, such as MS SQL Server, SAP and DB2. It provides a simple and straightforward restore – by selecting the files from directory tree – also for special task types without their specific processing, e.g., restoring a Hyper-V VM to original location or with relocation. Compared to similar option As path backup option under the Expert options, choosing As path restore allows you to select individual files for restore while the As path backup restores all files.

Tip

If the number of actual backup tasks is too big to show in a list, set a filter string by task name in the above search field.

You can also store a default table view: After you have selected the columns you need and arranged them, you can save the settings by moving the mouse pointer over the column header, right-click it and select the Save View option.

For each task in the list, the following attributes are displayed:

Task type: The type, according to which the data is backed up (path, system state, SAP Hana, Exchange Server, etc.).

Backup day: Date of the backup. Note that backup day defines a time interval between two NEWDAY events.

Media pool

The name of the source media pool.

Saveset

Identification of the save set.

Select Files

The previously selected task is visible in the upper part of the window. In the lower part all directories and files from the saved backup are displayed in a standard tree view. Clicking [+]/ [-] (the plus and minus control) expands/collapses the folder content.

Checking the box next to the folder/file selects items for restore. The absolute path of the selected folders or files is shown above in the field Position.

Note

When you select a folder/directory, its subfolders/subdirectories are automatically selected.

The button Search opens a search function that allows you to search the save sets by task name or by filename or path or by any part of it.

Find Pattern

The results of the search are listed below. Select the files you want to restore and click Next. The last step of the wizard opens Save and Start window is shown.

Save and Start

In the upper filed, the save set that is selected for restore is displayed with its attributes. The available restore options depend on the selected task type for restore.

Name

The name of the task is assigned automatically. If the restore is planned to be started by scheduler, enter the corresponding task name.

Drive

The drive which SEP sesam will use for restore.

Interface

The name of the server from which the files are being restored. This is either a Remote Device Server (RDS) or SEP sesam Server.

Target node

The name of the server where the files are being restored to. Only computers with the same platform (Windows or UNIX) are available. If you need to perform a cross-platform restore, return to the task selection step of the wizard and choose Mount saveset.

Preferred media pool

If the data was migrated or replicated and different media pools were used for the process, the source media pool to restore from can be selected from the drop-down list of available media pools.

Used media | Barcode

If the data was migrated, the migrated copy is stored to another media. Here the source media to restore from can be selected from the drop-down list of available media.

Target path settings

Restore to original target path

This option is selected by default. It restores the data to the same location from which it was backed up. Note that this only applies if the target node is the same server from which the data was backed up, i.e. when source and target server are the same.

Original tree structure

This check box at the right is enabled by default when restoring to original location. The directory structure of the restored files is the same as the original directory structure of the backed up data. If this option is disabled, the directory structure is not recreated and only the files are restored (flat structure).

New restore target

This option enables you to restore data to some other location. The path to the directory to which the data should be restored can be entered manually or by using the Browser button to open the file explorer.

Execution options

If the files with the same name in the target directory already exist, the following selection can be made:

do not overwrite existing files

Selected by default. Files will be restored only if they are not already present on the target system.The original data will not be overwritten.

overwrite existing files

Files on the target system will be overwritten and replaced with their restored version.

create new version

Data from backup is restored as a new version by appending a tilde to the original file name. The original data remains intact. For example:

README.TXT -> ~README.TXT

The restore is started by clicking the Start button. If the restore configuration should be started manually at a later time or by a scheduled task, use the Save button to save the task under the assigned name in the Name field. All, started and scheduled restores are saved in SEP sesam under Main selection -> Tasks -> Tasks by clients/Tasks by groups with the current timestamp. A restore can be restarted by using the menu item Activities -> Restore or from Main selection -> Job state -> Restore -> right-click selected restore -> Immediate start.

Expert Options

Clicking the button Expert options will open a new window, where more specific options and actions can be defined.

Options

Restore options text box allows user to provide additional specific options for restore. This is helpful for special options of the sbc command. For details on commands, see SBC CLI.

Verbose level allows user to change the verbosity of the main log to display more information than the default logging mode. Verbose levels from 0 to 6 are available. The higher the number, the more trace information will be logged during restore.

Tip

If required, you can get more information on options from SEP sesam support or search for them in additional documentation for special SBC clients (e.g., SBC for MS Exchange).

Restore the complete saveset

Restores all files from the saveset.

Restore according to the composed list

Restores previously selected directories and files.

Disk_info disaster recovery

This option is available when restoring from DISK_INFO backup of a Linux host. It is required when recovering a Linux server for restoring the backed up file partition information. A special BSR license (Bare System Recovery) is required. For details, see List of Licenses.

Relocation

By default, no relocation is selected: files are restored to original path with the original tree structure.

The with relocation option allows to specify a new target location for restored files. Individual files can be restored to separate paths. For example, the files from C:\Program Files\Java are going to be saved as a new restore target in the directory C:\Java, where all sub-directories are recreated (see screenshot).

Filter

The Filter tab allows to restore only data that matches the filter criteria. Regular wildcards should be used (* and ?). For example, *.doc would result in restoring only files that have the extension ".doc".

The filtering is first applied to the client, i.e. all data will be sent over the network. Filtering is especially useful if no LIS file is available, thus enabling selective restore.

Task type

By default, the task type according to which the data is backed up is selected (default is path; other task types are, for example, Hyper-V, SAP Hana, Exchange Server, Lotus Notes, MySQL, VMware vSphere etc.).

When you have backed up data with task type other than default path, for example Hyper-V, you can still use the option As path backup. This option allows you to restore your data directly to the file system without any additional action, for example, files from a Hyper-V backup, rather than restoring according to your special task type, for example, restoring (and importing) Hyper-V data to the Hyper-V manager.

The option Write saveset into file allows you to restore the entire save set into a single file.

Pre/Post

Under the Pre/Post tab you can specify whether any pre- or post-script should be applied for this restore task.

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.

If the restore did not finished successfully, you can force the execution of post commands by enabling this option (e.g., booting a database).

EOL

Specifies for how long (in days) this restore task will be kept and can be accessed using GUI. Default is 7 days. If you want to use a restore task after a longer period of time or use it as a template, it is recommended to set a longer retention time. Setting the value to 0 (zero) means unlimited lifetime.

Start time

Instead of starting your restore immediately, you can specify the Start time by entering the desired date and hour.

In the Delay start for up to, the maximum allowed startup time (the amount of time an event can be in the queue) can be specified in days and/or hours. The actual event startup depends on the processor load of the system. At the starting time of the event, every event is forwarded into the queue, where it might wait until jobs with a higher priority are finished. For jobs with the same priority, the FIFO rule (first in first out) applies. If the event cannot be executed within this specified time frame, it will not be executed at all.

Stop task if it runs longer than can be defined by setting the amount of time (days and/or hours) after the event's scheduled start time at which the event will be cancelled.

Additionally, Stop task at can be used to define the exact date and time when the task should be stopped.

A Follow Up event can be specified to trigger the predefined event on the SEP sesam Server once the restore is completed. For details, see Follow-up Events.

Clicking Ok will save all adjustments made in the Expert options window.

Immediate Start -> Backup

Special backup parameters, applicable only for Citrix XenServer backup.

Media pool

Selection of a media pool that will be used for this backup.

Drive group

This inactive field displays the name of the drive group, which is defined for the specified media pool. The backup is executed automatically on a drive from the assigned drive group.

Drive

You can define which drive handles the backup job for drive groups with several drives. If no drive is selected, SEP sesam selects the available drive based on criteria for load sharing.

Interface

If multiple network connections are available, the hostname for the backup source (if necessary, the network interface) is defined.

Execution

Start time

Instead of starting your backup immediately, you can specify the startup time by entering the desired date and hour.

Delay start for up to

You can define the maximum allowed startup time (the amount of time an event can be in the queue) in days and/or hours. The actual event startup depends on the processor load of the system. At the starting time of the event, every event is forwarded into the queue, where it might wait until jobs with a higher priority are finished. For jobs with the same priority, the FIFO rule (first in first out) applies. If the event cannot be executed within this specified time frame, it will not be executed at all.

Stop task if it runs longer than

You can set the amount of time (days and/or hours) after the event's scheduled start time at which the event will be cancelled.

By clicking the Start button, the backup process is picked up by SEPuler that initiates the execution of the event immediately or (if the time is specified) at the desired start time.

Immediate Start -> Restore

From the list of the restored tasks select the desired task.

Once you have selected the task, the final step of the restore wizard is displayed. It provides an overview of the restore task. For details, see Restore – Save and Start.

Immediate Start -> Migration

In the migration task window, the tab Execution Parameter is displayed.

Select the desired migration task from the Task Name drop-down list. The selected migration task is displayed with its parameters. You can modify the migration destination and filter settings. By clicking the Start migration button, the changes of the migration task are saved and the migration is started. For details on migration options, see Migration tasks. For step-by-step procedure, see Configuring Migration.

Immediate Start -> Media Action

Media events can be activated by SEPuler (timetable) as user-defined events, overflow of media (EOM) or backup itself. For details on media event configuration, see Creating a Media Event.

You can choose from four different 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, the structure of tape is checked and recorded.

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

Archive adjustment

An archive adjustment makes a comparison between media in the loader carousel or magazine and the SEP sesam media archive database.

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 Prioritization of events.

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.

Parameter

Media Pool

Defines the media pool that is used for the media event.

Drive

Optionally, you can define a specific drive for the event execution. If a drive is not selected, SEP sesam Server automatically selects one of the available drives.

Drive group

Displays the name of the drive group that belong to the media pool.

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.

Start time

Optionally, you can delay the immediate start by modifying the start time.

Immediate Start -> Command

Starts a preconfigured command event by inserting it with the actual time into the calendar. Events initiated with the Immediate start command from the GUI or command line are listed in the calendar as non-recurring events. For details on command event configuration, see Creating a Command Event.

Name

Use the Choose button to select a command from the drop-down list of already configured commands. Select the command and click OK.

Client

Select hostname of the computer on which the command is going to be executed.

User

Specify a user with rights to execute the command on the client. This is only valid for Unix systems, on Windows the command is executed with the rights required to run SEP sesam service. For information on access restrictions for command events, see section Access limitation of command events.

Command

The selected command is displayed.

Start time

Instead of starting your command event immediately, you can specify the startup time by entering the desired date and hour.

Delay start for up to

You can define the maximum allowed startup time (the amount of time an event can be in the queue) in days and/or hours. The actual event startup depends on the processor load of the system. At the starting time of the event, every event is forwarded into the queue, where it might wait until jobs with a higher priority are finished. For jobs with the same priority, the FIFO rule (first in first out) applies. If the event cannot be executed within this specified time frame, it will not be executed at all.

Stop task if it runs longer than

You can set the amount of time (days and/or hours) after the event's scheduled start time at which the event will be canceled.

Access limitation of command events

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

ping

only command ping

Restart backups

You can restart all defective or aborted backups of a SEP sesam backup day.

Clicking [+] button marks all selections for the job, while clicking [-] clears the selections. By enabling and disabling the check box in front of each backup you activate or deactivate individual backups.

All restarted backups are put into the queue with priority 0 (zero; the highest priority that overrides all other priorities) and are executed unconditionally. If you need to adjust the priority, select it by using the Prio option.

Cancel current running activities

Allows you to stop all running activities in your SEP sesam environment. If you respond to the confirmation dialog with OK, SEP sesam stops all running tasks. This is useful for resetting your backup environment or for maintenance operation.

GUI Configuration Options

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

Defaults

Under Defaults, you can define the access to SEP sesam online help, define some extra settings, set retention periods for logs and restore tasks, change UI mode, customise the GUI font and tables, check the settings and set the date format. Note that the last tab differs depending on SEP sesam version, however most of the options basically remain the same.

Help

By default, the option Use Web help in the GUI is set. The online help is set to the user manual on the SEP sesam Wiki, thus providing the latest updated version of help topics online. Unless your GUI client has internet connection problems, it is recommended to use the latest Web help.

For a GUI client without an internet connection, copy the user manual to local storage and set a link to the local help file by using the option Use local help in the GUI.

Use the search button to select the local HTML site.

Use the test it button to check the access to help files.

Extras

The following settings can be activated in Extras:

Switch off the scrolling for warning "30 Days remaining for update authorisation"You can switch off the scrolling for notification about the pending expiration of updates. If there is no update permission, the notification never appears. After installing update, this option is reset.

Provide selection of "broken backups" in the Restore WizardIf this option is checked, you are allowed to perform a restore from incomplete, broken, or interrupted backups. By default, this selection is not provided.

Number of tracelog lines to displayThe default value for tracelog lines is 60. Click the arrows to increase or decrease the number of lines.

User specific default interfaces for drive groupYou can set a user specific interface for each disk drive group (Default Interface). This setting overrides the default interface specified via the drive group.

Compress LIS filesBy default, the LIS files are compressed after 14 days. You can change the number of days after which the LIS files are compressed or deactivate the check box to prevent compression of LIS files.

In the Expert mode some additional options are available. By double-clicking Backups or Restores by state you can review trace log information, displayed in the new Trace Log tab.

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

Font Style: The predefined GUI font is plain. Check the Bold Font option to change the font-weight property of the entire GUI.

Table Striping: You can change the appearance of GUI tables by selecting one of the zebra striping tables from the drop-down list.

Table Row Spacing: Click the arrows to adjust the spacing between table rows in the entire GUI.

Font used in tables (available for v. ≥ 4.4.3 Grolar): You can change the default font (proportional) to non-proportional (monospaced).

Settings

The Settings tab displays an overview of all internal GUI settings.

Display Format | Data displays | Default Date Format

The name of the last tab differs depending on SEP sesam version, however all options remain the same.

SEP sesam version 4.4.3

Under the last tab Default Date Format, you can change default setting for the date format.

SEP sesam version 4.4.3 Tigon

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

Media types

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

Media type

Sesam internal identification of the media type

Drive type

Sesam internal drive types

Capacity

Storage capacity of allowed combination media / drive

Command

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

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

Name: Enter a name for the new event.

Client: Select a client, on which the command will be executed.

User: Enter the username of a user with sufficient access to execute the command on the client.

User Permissions

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

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

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

Permission Management

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

Policy-based authentication is enabled by default. You can switch to database-based authentication by using the Activate Authentication button in the Permission Management window. If you choose not to activate the database-based authentication, policy-based authentication stays enabled. Policy-based authentication is configured in User Permissions (see previous menu option). For details, see Configuring Policy-Based Authentication.

When you turn on database-based authentication by using the Activate Authentication button, upon the restart of a GUI and SEP sesam client, you can use any of the 3 available tabs: Users, Groups and Activation. You can create users, modify their settings, such as adding a user to the group or removing it from the group, and delete users. You can also deactivate the database-based authentication.

E-Mail Settings

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

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

Interfaces

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

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

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

SEP sesam allows the use of Pre-, Post-, Alarm-, Notify-, and Disaster interfaces to be combined into scripts. A detailed description of these interfaces with all parameters and settings can be found in the Administration Manual.

PRE interface

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

POST interface

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

Alarm interface

The SEP sesam system needs no administration after complete set-up of all clients and backup tasks during normal operation (except for the restore). If any functional errors occur, e.g., failure of a certain backup, this event is automatically passed on to the alarm interface. This interface is programmable to filter desired messages and their conveyance to the authorized personnel.

Note

Do not use commands which require input from the user, such as OK buttons. Commands that require user interaction may cause interruption of backups during the night.

Notify interface

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

Disaster interface

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

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

Linux: <SESAM_BIN>/skel/templates/sm_disaster

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

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

User view

Available for v. ≤ 4.4.3. Based on the user permissions, certain SEP sesam GUI elements (Components, Tasks and Scheduling) are disabled when the user view is changed from Admin to Operator.
There are two types of user views: Admin and Operator. Only the Admin has full control over the SEP sesam, while Operator is only allowed to monitor SEP sesam events and logs on GUI client.

Window

The SEP sesam GUI can be rearranged almost without limitation. Clicking Window in the menu bar displays the following options:

In Manage layouts you can save and manage layouts.

Arranging and docking windows:The first time the GUI is started, the docking functionality is disabled by default. You can activate it by selecting the Docking Mode check box in the Manage layouts window. If the option is deactivated, all window positions are fixed.

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

The layout comprises the following settings:

Windows and frames: Windows that are open and the position of the windows and frames.

Current messages: Default settings, such as refresh interval, cyclic view on/off and the selection of the displayed drives.

Object selection: Expand status of the selection tree.

Toolbars: The arrangement and looks (e.g., buttons with or without a label) of the toolbar.

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

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

License information

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

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

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

SEP sesam version information

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

Components

Topology

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. By marking (clicking on one of the tree components and clicking the switch properties), the user opens the entry screen for the components.

Such grouping enables large organizations at different locations to be managed and represented as a group with separate, centrally-managed units (using a tree-like structure). Locations can be hierarchically organized - multiple sub-locations can be summarized under one Location. In our example, we will create a new location HOME.

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.

To create a new location independent of another location, start at Topology and click the button New Location.

A client is always assigned to and created within a location.

Location Properties

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

New locations can be configured 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.

Name

Name of the location

in

Superordinated location (not editable)

Description

More exact description of the location

Contact

Contact person at this location

Note

Additional information

Client Properties

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

The following screenshot shows the input fields and functions of clients.

Note

The client properties are slightly different if the client is already added and configured and you edit its properties, or if you are configuring a new client. The Platform and additional tabs for entering access options are only available when configuring a new client.

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

Location

Predefined location. A client always has to be assigned to a location.

Platform

Select the relevant platform of the client: Windows, UNIX, VMS or NETWARE. Depending on the platform, tabs for special access parameters are displayed. The Platform option is only available when configuring a new client.

PROXY: Use this option if there is no direct remote access to this backup client. The data transfer is executed via vendor specific protocols, the client is accessed via the mandatory DataMover. The following protocols are supported: vSphere (vCenter Server), Citrix Xen Server, NetApp and Novell SMS for NetWare 5.1/6.0/6.5.

SSH: The communication method SSH is based on a key-pair operation of the SSH implementation of the used operation system.

RSH: Remote Shell: It is a historic old option and is rarely used.

Last Sesam Message

The most recent system status message for the existing client.

Notes

Optional comment by the user.

Interfaces

Only edit this field if the client is the SEP sesam Server or a Remote Device Server (RDS). If there is an additional network for backups, 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 back to the SEP sesam Server will fail. The network protocols for the data transfer can be set by using the common prefixes ftp://server (default), http://server:11000 or https://server:11443. In the backup tasks the defined interfaces may be chosen for the data transfer.Note If several interfaces are enter, separate them with a return or a blank.

Sesam Version

This field shows the SBC (SEP sesam Backup Client) version of the installation.

Locked for backups

Option is used only in special cases, when you want to exclude a client from backup for technical or other reasons. Checking this option will deactivate your client from all scheduled backups until this option is set.Note: If this switch is set the client can no longer be backed up until the setting is removed.

Client is virtual machine

It should only be selected if you are adding a virtual machine.

Firewalls

By default SEP sesam uses ports that are assigned randomly by the operating system for its data connections. If clients that are behind a firewall are to be saved these ports can be defined.

Access Options

The default communication port at a backup client is 11301. If a port other than 11301 are used, then SEP sesam is to configure the service on the client sm.ini to this port. In this field you have tell the SEP sesam Server over which port 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 parralel 2 ports of a client are needed.

Listen Port

The default STPD-port for Remote Device Servers (incl. SEP sesam Server) is 11001.Note: For more information about firewalls please check the Administrator Manual.

In future versions, this values will be used to define the affiliation of a backup client to a VM in a virtual environment.

Additional Properties

Note

A third tab is available for the following task types: Micro Focus Open Enterprise Server (formerly Novell OES), VMware, Citrix XEN, MySQL, PostgreSQL, NetApp, RHEV.

The following example shows the options for the OES-Netware client. If you are trying to back up an OES-NetWare or an OES-Linux client, the SEP sesam data mover connects to the TSA provided by Micro Focus (formerly Novell). To communicate with the various TSA's you need the following information.

Account

User name authorized for communicating with the TSA's.

NetWare Password

NetWare user's password, that is communication with the TSA's.

Repeat Password

Enter the password again to make sure it is correct.

Data Mover

The data mover is the host where the SEP sesam Micro Focus (formerly Novell) Client with the normal base software patches is installed. SEP sesam Micro Focus Client is needed to start the communication between the SEP sesam Server and the running TSA. SEP sesam Micro Focus Client can be installed on any Linux machine running Micro Focus Storage Management Services (SMS). The only requirement is that either the SEP sesam Client or the SEP sesam Server software is installed correctly. The resolved DNS SEP sesam Client or SEP sesam Server is then entered as the data mover. If special backup methods are used, the settings must be entered in the tabs within the masks and must be visible to the SysAdm.

Clients

The item Clients provides a list of all interconnected, in SEP sesam configured computers – SEP sesam clients and their properties (assigned location, operating system, access mode, SBC version, etc.). Right-clicking a client opens its properties where you can edit the client's settings.

Right-clicking in the clients list opens the shortcut menu, from which you can choose 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 delete a client by right-clicking it and selecting Delete.

Further client properties can be displayed in the list by right-clicking the table header and selecting additional columns. By selecting the Save view option, these properties are also displayed when the clients list is called up again.

Data stores

A data store is a device type used for writing the save sets directly on one or several configured storage locations – into the file system. Data store configuration consists of specifying data store capacity and watermarks: HWM and LWM.

The default data store type is Path. This data store type is relevant for configuring all storage locations, except for SEP sesam additional archiving and deduplication module that uses a dedicated SEP Si3 deduplication store. As of SEP sesam version 4.4.3, SEP EasyArchive data store and FDS deduplication store are no longer supported.

SEP sesam uses a data store instead of a conventional media pool to define storage repository. The data is still primarily backed up to a media pool, however a data store is used underneath to save data to dynamically managed data areas, including disk backups.

Depending on the SEP sesam version, the data store window might be slightly different, but the configuration remains the same across various SEP sesam versions. As of version 4.4.3 Grolar, a few additional options are available: new data store type NetApp Snap Store, S3 credentials, Si3 State, Si3 Repair Area. For details, see How to manage a DataStore .

Data store concept

The difference beween a conventional media pool, typically used for backing up directly to tapes, and a data store is in defining the storage space directory directly in the drive by using the operating system's partition functions. Therefore the data store space is managed at partition level.

Another difference is that when a data store becomes full during backup, the save set will not be split up. Instead, the backup will be aborted. You should consider this when specifying the data store capacity. For details, see Data store calculation recommendations below.

Note

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

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

Data store capacity

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

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

Watermarks and purge

A watermark is a parameter used for data store configuration (managing disk space usage).

A high watermark (HWM) is the upper value for the used disk space on the data store. It defines the available storage space for backup and migration. When this value is reached, a data store purge process is started to remove all obsolete (EOL-free) save sets. For details, see Managing EOL.

The oldest free save sets are deleted first. Purging is done until the low watermark is reached. When setting the HWM parameter, you should ensure that sufficient space is allocated between data store capacity and HWM for a complete full backup. Otherwise the backup will be canceled (file system full). For details, see Data store calculation recommendations below.

A low watermark (LWM) is the lower value for the used disk space on the data store. It defines how much storage space is available for save sets with expired EOL and how many EOL-free files can be deleted (purged) from the data store. If LWM is set to 0 (default value), all EOL-free save sets are removed from the data store, regardless the filler loading. If both watermarks, HWM and LWM are used, all EOL-free save sets will only be purged, when the HWM is exceeded.

The manual execution of the data store purge process deletes obsolete (EOL-free) save sets. Another option is to clean up a data store (≥ 4.4.3. Tigon V2), as described below.

Clean up orphaned save sets

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

Steps

In the Main selection -> Components, click Data stores to display the data store contents frame.

In the content pane menu, click Clean up and select the data store (and the relevant drive number) for which you want to free up space by removing orphaned save sets.Click Clean Up.

You can check the status of the clean up action in the data store properties under the Actions tab.

Data store calculation recommendations

Data store volume sizing and capacity usage should be managed at partition level. It is recommended that only SEP sesam data is stored on the respective volume.

The data store should be at least three times (3x) the maximum full backup size of the planned backup to allow the watermarks to work automatically and dynamically.

It may be necessary to scale up the data store to beyond 3x the maximum size when a longer hold-back time is stipulated or very big save sets are to be stored. To do this, sufficient space should be allocated:

between capacity and HWM for a complete full backup

between HWM and LWM for another full backup

inside the LWM area for a third full backup

A virtual drive can handle up to 124 simultaneous backups (channels) for storing data to a SEP sesam data store (depending on the SEP sesam version). Only when it becomes necessary to back up more than 124 channels (SEP sesam server Premium Edition) should another drive be added to the data store.

Because a backup is terminated rather than split up when a data store becomes full, the correlation between the size of the data store and the size of the biggest backup task must be determined carefully. Take the example of a data store defined at 3 TB, whereas the biggest save set is 2 TB. With an EOL=1, a data store three times (3x) the maximum full backup size may be too small to allow the watermarks to work properly. In such a case, it is recommended to scale up the data store size.

Limitations

When a media pool requires more than one data store, all the data stores must be connected to the same SEP sesam Device Server (IP host). SEP sesam does not currently support network-distributed data stores being served by a single media pool.

When using more than one data store, only negative OR positive values can be used for capacity and HWM/LWM. SEP sesam does not support the use of negative AND positive values at the same time.

Data store properties

HWM treshold – the upper value (in GB) for the used disk space. When this value is reached, a purge process is triggered for all EOL-free save sets thus freeing up data store capacity.

Low Water Mark

LWM treshold – the value (in GB) for how much storage space is available for files with expired EOL in the data store. If LWM is set to 0 (default value), all EOL-free savesets are removed. For the deduplication store the LWM is not editable. It is set to 0 by default.

Total

Maximum available space (in GB) on the partition as reported by the operating system.

Used

Total used space (in GB) on the partition.

Free

Available disk space (in GB) for SEP sesam.

Save sets properties

Selecting a data store and clicking the tab Savesets opens a list of all save sets with their details. You can change EOL of individual save set, adjust backup-related EOL, and lock or unlock individual save set.

Saveset EOL

The column Saveset EOL enables you to change EOL for each individual save set, stored on the respective data store. You can extend or reduce its retention time. If the adjusted save set is a part of a backup chain, the whole chain is affected. See EOL-related backup chain dependencies.

Backup EOL

The column Backup EOL enables you to adjust EOL for all save sets containing the same data. This backup-related EOL is applied to all save sets with the same data, including migrated and replicated save sets. For example, adjusting EOL of a migrated save set from 2.12.2016 to 12.12.2017 results in changed EOL for all related backup data, i.e., original backup, replicated backup, as well as for all backups in a backup chain, if a save set with adjusted EOL is a part of it.

EOL-related backup chain dependencies

You can extend or reduce the retention period for an individual save set or backup-related save set, as described above. Keep in mind that increasing EOL of a DIFF or INCR save set will result in increased EOL of all dependent backups (FULL and other DIFF and INCR) in order to retain the backup data. This keeps the backup chain readily available for restore. On the other hand, decreasing EOL of a DIFF or INCR save set to a date in the past will result in a warning message prompting you to confirm your decision to set the whole backup chain to already passed time. By setting EOL for DIFF or INCR save sets to expired time results in purging and overwriting the complete backup chain.

Note

Each save set can be deleted when the following conditions are met:

Its EOL has expired.

Typically, there must be no other save sets that depend on this save set. You can override this condition by explicitly allowing the EOL for the whole backup chain to be set to expired, thus deleting backup data on all related save sets.

Loaders

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

Identifying storage devices and their configuration

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

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

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.

Loader properties

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

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.

Device Server refers to the server where the loader is connected. In small environments the loader or disk array is usually installed directly on the SEP sesam Server. However, more complex backup environments use RDS instead. RDS receives data during backup and writes it to the attached tape device.

Type

The device type.

Ctrl

The loader type – there are different types of loaders available:

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.

Slots

Number of slots in the loader.

When inserting a cleaning tape, use the last slot in the loader and reduce the number of slots in the loader by one (or by the number of cleaning tapes loaded). Additionally, configure the auto-clean option in the tape library setup.

Ports

Number of mailslots 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 updated and always shows the current status.

Default view

Changed view with bigger icons

The left part represents the tapes in slots. In the right corner at the top 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 a 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. Direct verification of the media label is possible.

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

Legend

The following table lists the icons used for displaying various media and loader status.

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. For details, see Setting up Archive Adjustment.

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.

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

Drive Group

The drive group is automatically defined by the media pool.

Drive (opt.)

Optional input of a single drive.

First Slot, Last Slot

Offers the possibility to limit the synchronization to the selected segment of the autoloader.

Automatic Introduction

If unknown media (without SEP sesam label) are found within the loader, they will be added to the specified media pool.

Tape Type

Selected media type for automatic new media entry.

Handling of unknown SEP sesam media

Accept without initialization: Foreign SEP sesam media, e.g., from another SEP sesam Server, will be entered into the new media pool without initialization.

Overwrite:

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 read again and verified. Bar code information is ignored.

Adjustment by barcode only

SEP sesam does not unload the tapes from the drives and checks only the barcodes of tapes within the slots.

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 media within the library. The use of port slots depends on the hardware installed.

Action

Import

Transport of tape cartridge through the input/output port into the magazine.

Export

Transport of tape cartridge from the magazine through the input/output port – exit from loader.

Load from slot

Move tape cartridge from the specified magazine slot into the specified drive.

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.

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 List of Licenses.

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

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

New Group

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

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.

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

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

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.

Path: Applicable only for data store and removable media; specifies the path for connecting the device, e.g., /dev/media/USB or simply F:.

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. For details, see Licensing: SEP sesam Server comparison.

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.

Note

With some drive types, such as DISK_CHNG, the name is automatically assigned based on disk + drive number.

Here is an example of an already configured drive.

Manage multiple drives

As of v. 4.4.3 Grolar, new Manage multiple drives option is introduced to enable 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 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.

Drive action

In the Drives content window selecting a specific drive and then Drive action from the menu, allows to manage the specific drive and media in the drive.

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.

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 lower, cyclically updated information window.

Configure all drives

As of v. 4.4.3 Grolar, 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 may have different kind of media pools for different types of backup data, backup sources (e.g., file backup, DB backup) or drive types. SEP sesam requires that media pools are configured and media are added to it.

SEP sesam automatically labels each medium with a unique media label during initialization. Media labels are stored in the SEP sesam database. The media label is a combination of the name of the pool (e.g., DAY_, WEEK_, MONTH_) and a 5-digit number. For example, if the name of the pool is LTO_month, the media label for media in this pool consists of a prefix LTO_month, followed by an incrementing number, e.g., 00001 – first media label would be LTO_month00001. The next medium would have a media label LTO_month00002, and so on.

While media pools represent a conventional way of organizing data storage and are typically used for backing up directly to tapes, SEP sesam uses a data store for backing up to disks. Even though the data is still primarily backed up to a media pool, a data store is used underneath to save data directly on one or several configured storage locations – into the file system. The data store space is managed at partition level. For details, see Data Stores.

Media pools are the base for building a backup strategy. Each media pool stands for a set of media, foreseen for a specific purpose. For example, media pools can be created and managed for work days, weekends, certain locations, certain types, databases and more.

Properties

You can create a new media pool from Main Selection -> Media Pools -> New Media Pool. You specify media pool characteristics when configuring a media pool. Some of the properties can subsequently be modified. For details, see Configuring a Media Pool.

Media Pool

Name

The user-defined name of a media pool. The name may not end with five numbers because this form is used for media labeling.

Description

Optional user comment.

Drive Group

Selection of a drive group to which the media pool is attached.

Retention time [Days]

The time period for which all media in the respective media pool are protected after data is written to the medium, thus preserving the save sets and keeping them available for restore. The retention time period starts with the date a save set is written to the media and lasts for the period defined by media pool's EOL (in days).

Readability Check

This is a process that checks the backup data readability. During the check the data on medium is read in blocks, and the structure of tape is checked and recorded. It also checks whether all determined backup sets on the tape are recorded in the database and vice versa. The results are shown in the log.

By default, the value is 0 (zero) and the readability check is switched off. If a number > 0 is set, a medium is checked after the specified number of days and marked by status Read check required. Readability check can only be applied if a medium EOL has not expired and is not applicable for EOL-free media. For details on EOL, see Media Strategy.

Expiration of read check overdue [days]

The number of days a readability test is overdue. It is calculated based on the readability check limit and the value of expiration overdue.

Repeat rate for readability check [times]

If Unlimited is selected, the medium is checked according to the specified frequency. If Execute is selected, the check will be repeated as many times as specified.

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 special set of options to allow sharing of media across media pools.

may use empty, foreign media

If there is no available media in the respective pool and this option is selected, SEP sesam will use unknown or blank media for backup.

may use EOL free media

If selected, media with expired EOL from the same media pool can be used for backup. If not, the use of the specific medium can be forced.

may use SPARE media

If there is no available media in the respective pool, but the media pool SPARE_ is configured and this option is selected, SEP sesam allocates media from the spare pool – the spare medium is removed from the spare pool and added to the target pool.

may use media from another pool

If selected, it allows the respective media pool to use available tapes of other media pools in case it run out of its own.

another media pool may use media from this pool

If selected, another media pool that run out of its own tapes can use the available tapes of this media pool.

Note

Media sharing strategies are based on the acquisition of 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 be aware of this when planning your media strategy.

Media

The term medium describes a data carrier on which backed up data is stored and preserved in case of an emergency. It contains tapes in tape devices, hard disks as changeable at USB connection or virtual media as directories, which are located on permanently connected hard disks. SEP sesam uses only media that are registered in media archives. The first window shows the media-archive containing all media prepared for use with SEP sesam.

The media table columns can be arranged in a particular order by dragging & dropping with the left-mouse button on the column header. You can select which columns should be displayed. These settings will be stored in the users local Java profile. If you right click on a column header the following options are shown:

Label

SEP sesam label of the medium. Always "pool name + 5-digit number".

Barcode

Barcode-number of the media, if available.

Write Protection

Switchable between On/Off; as long as On is selected, SEP sesam does not use this media for backups.

First Init

Date of the first initialization of the medium.

Last Init

Date of the last initialization of the medium.

Sesam Day

The date when the medium was last used for backup.

Media EOL

The media is not available up to this time (EOL = End-Of-Lifetime = Backup day + Lockdays of the media pool).If the EOL (delay time) has elapsed of the medium (lock symbol = gray), then the medium will be "overwritten". If the EOL of the medium has not yet expired, but the medium is currently in use on this drive for that media pool yet (lock symbol = blue), then further backups are appended. If the lock icon = red, then this medium is locked until the displayed date.

Occupancy

Occupancy in proportion to the total storage capacity of the media (sometimes more than 100).

Loader

Represents the numeric value of the loader, which handles the media pool. The field is empty if no loader is used.

Slot

Slot within the loader where the medium was located before it was loaded into a drive. With this information, it is possible to put the medium back to the source slot by a simple unload command, without explicitly specifying the target.

Cartridge Type

Cartridge type of the medium.

Comment

Displayed the last SEP sesam system message.

Pool

To which the medium belongs to.

Storage Pool

On which Storage Pool is the medium configured.

Readability Test

Date of the last readability check.

Read Check Message

Result of the last readability check.

User Comment

Further information.

Encrypted

The Encrypted field states whether the medium is encrypted or not (Yes/No).

EOL changed by

Close Tape

Encryption Capable

Contains Encrypted Blocks

Unique Cartridge Identity

Cartridge ID of the medium.

UUID

Universal Unique IDentifier is a 128-bit unique identification value.

Dupl Flag

In Drive

If a medium is loaded into the drive, the SEP sesam label will be displayed.

Properties 1

Note

As of v. ≥ 4.4.3 Grolar the media properties view is slightly changed.

Media Pool

Name of the media pool containing this media (uneditable).

Storage Pool

Name of the used storage pool (uneditable).

Write Protection

This switch is set by SEP sesam itself, and can only be changed manually. When toggled to "On", the medium is not used for backups even if EOL (End-Of-Lifetime) is expired.

Backup Day

Date of the backup day (uneditable).

Locked until

It is automatically set with values from the media pool while the backup procedure is running. It can be adjusted individually.

Drive

Drive in which the media was last used (uneditable).

Next Media

In a big backup session, more than one medium can be used. This value indicates in what position this medium was used during the backup (uneditable).

Media Type

Media type of the medium (uneditable).

Loader

Numeric value of the loader, which handles the media pool.

Slot

Number of the slot in the loader. It is better to use an archive adjustment.

Encrypted

States if the medium is encrypted or not.

Ok

Save the changed media parameters in the database and return to the start screen.

Delete Media

Removes the data set from the archive and closes the entry mask.

Apply

Save of the changed media parameters in the database. Entry mask can be used for further changes.

Cancel

No action and return to the start screen.

Properties 2

Label

SEP sesam label of the medium, used for media identification.

Barcode

Barcode information of the medium.

Occupancy

Shows the current occupancy of the medium in percentage (uneditable).

EOM

End Of Medium states if there is still space left on the medium.

Error Count

Accumulated count of errors of the medium on the drive.

Error Delta

Displays the difference of errors compared to the last usage.

Use Count

Counts the initialisation of the tape (uneditable).

Comment

The last SEP sesam system message.

User Comment

Make additional notes.

Savesets and Media Actions properties

The Savesets lists all currently saved backups of the medium. You can show or hide columns by clicking a right-mouse button on the column title.

The Media Actions lists all media events, such as the introduction in the SEP sesam environment, initialization for backup, readability check, etc.

Adding a new medium

From Media -> Introduction you can insert new medium into the media-archive.

Media Pool

Name of the media pool to which the medium is added. Select one of the configured media pools.

Drive

Selection of drive in which the media must be initialized (depends on the selected media pool).

Type, Device, Client, Loader

(uneditable)

Media Type

Selection of media type (pre-selection depends on the drive type).

Note

Utilzation of unknown SEP sesam Media alerts the user that a SEP sesam tape or medium has been entered, but is not entered in the SEP sesam database. This can happen when a tape was erased or if a tape was entered from another SEP sesam installation. Empty tapes or tapes from other programs/applications will always be overwritten. Media found in the SEP sesam database will never be overwritten.

Handling of unknown SEP sesam Media

It affects SEP sesam's bahavior, if a SEP sesam tape label is recognized on the medium, but it is not found in the database. This is the case, when a tape was removed or there is tape from another SEP sesam installation. Empty media or media written by other applications are always re-labeled. However, media, which are already in the database, will never be re-labeled.

Accept without initialization

Takes over the medium with the given label in the SEP sesam database. If te related media pool does not exist, it will automatically be created.

Label Number

Treats the media as empty and writes a new label on the tape.

Automatically assign next number

SEP sesam automatically assigns the label number for the media that should be added. By this process, the highest existing numeric value within that media pool is increased by one.

Take label from media

Creates the last five digits according to the editable text box.

Start

Start insertion of new media

Cancel

Close screen, no insertion.

Tasks

The tasks tab allows the user to set events for backups, restores, data migration and replication.

Tasks By Clients

The status of a backup task is shown as a colored, rectangular icon.

Icon without additional rectangle: The backup has not started, or the last backup log has been erased from the tape.

Icon with a green rectangle: Last backup task status 'successful without warnings' or 'successful with warnings'.

Icon with red rectangle: Last backup task 'unsuccessful/failed'.

Icon with purple rectangle: Backup task stopped.

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

Immediate start: Allows you to initiate a process manually, see Immediate start.

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.

Create a new backup task

The default task type is Path backup (files, directories). By selecting the source, the task type is set automatically.

Client

Name of the host that should be backed up.

Source

Specify disks, directories, files to be backed up. When specifying more than one source, use commas to separate them. By selecting the source, the task type and task name are set automatically.

Note

When using a Netware NSS Filesystems on Linux OES the NSS Volumes are normally found below the Linux path /media/nss.

Exclude List

With the exclude list certain directories and files can be excluded from a backup. The selection is made with regular expressions except for NetWare file systems where file the patterns '*' and '?' are used. For details on various exclude options, see Creating Exclude List.

Note

If you want to suppress a specific directory, you should enter the complete path name. Multiple excludes are delimited with commas.

The selections in the upper right of the window next to the input fields Source and Exclude List open the Client browser.

The client browser is kind of cross-platform file explorer. It does not only show files and directories in the tree view, but also databases, pipes, sockets, character or block devices if they are relevant for data backup. The extended functions can be accessed by right-clicking. A progression 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

Additional information about the backup.

Create New

You can create more than one task of that client at a time. Additional backup options can be defined in the Save options field:

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

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.

Backup with VSS

Actives the using of Microsoft Volume Shadowcopy Service. It works only on Windows operating systems with installed VSS services.

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.

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.

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.

Backup:

Execute pre

Execute pre script before actual backup.

Ignore pre error

Forces a backup job to start even if the pre-commands were not properly executed.

Execute post

Commands written in the post-interface will be initiated.

Ignore backup error

Switches on/of if the post script is executed after a faulty backup.

Restore:

Execute pre

Commands written in the pre-interface will be initiated.

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

Commands written in the post-interface will be initiated.

Start post in spite of restore error

Forces a restore to complete even if the post-command script failed to completely execute, e.g., a paused database will be restored even though the backup task failed.

Additional Call Arguments (Expert Options)

Save options

Further parameters which depart from the standard backup procedure can be added (e.g., -v 3 for higher log level).

Restore options

Same as backup options, but only in the event of a restore.

Encrypt & Compression

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

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 he has to carry the (processor) load. Additionally, the encryption slows down the data transfer considerably. You can decide if the password hash should be stored in the SEP sesam database or not. If it should not be stored in the database, the SEP sesam will ask for the password at every restore event of that task.

Info

Information regarding the setting/selection of a encryption key.

Define new keyword

If any of the encryption options is selected, new button appears. Clicking Define new keyword opens the following fields:

new keyword

Specify your encryption password.

repeat keyword

Re-enter your encryption password - type it manually, do not cut and paste.

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 a software compression can be activated here.

Compression

options yes or no

Task Groups

By using the tabs Task Group or Schedules the task can be directly assigned to a task group or schedule.

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 of the already configured task groups, click the checkmark next to the target task group. Organizing related tasks into groups can simplify your backup scheduling. For details, see Grouping of SEP sesam Components 4.4.

Schedules

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 on scheduling, see The SEPuler - an event calendar.

Novell SMS

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

Tasks by Groups

From Main Selection -> Tasks -> By Groups it is possible to enter multiple tasks in one or more groups. You can also see all of the tasks that have been assigned to a particular group.

A single event will activate all the collected tasks within the task group. The tasks will then be executed depending on the number of sms channels available. The remaining tasks will be retained in the execution queue and will be started chronologically.

Tasks by groups properties

Tasks bundled to tasks groups can be executed on a single appointed time. If possible, tasks are performed simultaneously on the drives. The other tasks are dynamically assigned to the backup devices by SEP sesam. The last backup state of the whole task group is also displayed.

Group Name

Task group name.

Comment

Additional information.

The > selector assigns a single task to the selected group and >> selector allocates all available tasks. Selector < removes single- and << removes all tasks. The order in which SEP sesam starts tasks can be modified with ↓ and ↑ arrows.

Backup Plans

The menu item Backup Plans offers an overview of all configured tasks, task groups, and migrations, which are assigned to a schedule. By default, the displayed backup plans also include unscheduled tasks. To suppress the unscheduled tasks from being displayed, use the Hide unscheduled tasks button.

Migration Tasks

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

This allows for the duplication of save sets. To optimise migration performance, only successfully backed-up save sets or save sets with warnings (status successful or with warnings) can be selected for migration, whilst save sets with errors or partially restorable save sets (containing data from canceled backups) are not migrated.

Provided that the media in the source and target media pools are available after migration, the save set is duplicated; however, a save set is considered to have been migrated if it is deleted from the source media pool. Both, source and target data sets can be accessed with the restore wizard. If only the migrated save set exists, it will be required in the event of a restore.

Migration tasks are managed under Main selection -> Tasks -> Migration tasks menu. The source and target media pool must be defined in a new migration dialog. Additionally, a number of filter options are available (including by task, task group or backup client). You can also migrate backups from a specific medium to a different pool.

You can start a configured migration task from the GUI immediately or attach it to a scheduled migration event so that it starts automatically at a predefined time. For details, see Configuring Migration.

Here is a description of all the fields and the functions assigned to them:

Name

A name for the migration task like for example 'EasyDisk1-to-Xtra_FDI' (max. 50 characters).

Parameters

Media pool Specification of the source media pool.

Pool Media pool name (e.g. 'EasyDisk1') from which the backups are to be copied (migrated). (mandatory field)

Drive Drive number of the drive that is used to read the data (mandatory field).

Destination Specification of the target.

Pool Media pool name (e.g. 'Xtra') to which the backups are to be copied (migrated). (mandatory field)

Drive Drive number of the drive that is used for writing the data (mandatory field).

Interface Optional specification of the network interface through which the data transfer is executed.

Date The time frame of the backups that are to be migrated is defined.

Sesam day Allows for the the definition of an absolute time frame for the selection of the backups that are to be migrated. The entered date always refers to the Sesam day.

Relative Backup Date From/to as a relative specification of the number of passed days. As an example, the relative time frame from -6 to 0 copies all datasets from the last 6 Sesam days including the current Sesam day.

Filter

Using the filter options the number of backups to migrate can be limited.

Backup State This allows to choose to only migrate certain backups with certain states (successful, with warnings or partially restorable). Default is migrating all successful backups and backups with warnings.

Backup Level Choice according to CFDI-level (Copy, Full, Diff Inc): C, F, D, I and G. The CFDI-level 'G' means generation-migration. This means that, in addition to the incremental backups of the past days, all connected backups from the past, up until and including the last associated full backup, are included in the migration. Among other things, this makes sure that all relevant backups for a possible disaster recovery are available on the created media set for removal scenarios.

Copy migrated savesets again Already migrated save sets will be used as source for migration in addition to original backup save sets. This allows the so called migration-of-migration.

Object

Task Default = "*" for all tasks in the defined time frame. Here, a particular task can be chosen for migration.

Task group Default = "*" for all tasks in the defined time frame. If a task group is selected only the tasks within the defined time frame of this task group are migrated.

Client Default = "*" for all backup clients in the defined time frame. If a backup client is chosen only the backups from this client are migrated.

Number of copies Default = 0 (zero) means that backups can be migrated as often as you want. Entering a number > 0 means that a backup can only be migrated that many times.

Special Filter

Start Media Standard = "*" for all media. With this the save sets of a particular medium of the media pool can be migrated. Depending on media size, a backup can range over several media. Only backups that begin on this medium are migrated!

Saveset Standard = "*" for all save sets. It is possible to only migrate a particular backup.The selection is made according to the save set ID.

Comment

Text field for additional input. To expand the comment field place the mouse pointer in the field and click F1.

Buttons

Make A Copy And Save

If the migration task was given a different name in the field Name all changed options can be saved under a new name.

Save

Saves the current changes.

Delete

Migration task is deleted.

Cancel

Editing of the migration task is closed, the changes are discarded.

Si3 Replications

Replication was introduced with SEP sesam version 4.4.2. Replication tasks are managed under Main selection -> Tasks -> Si3 Replications menu. For detailed explanation on how to configure replication, its advantages and limitations, see Replication.

Here is a description of all the fields and the functions assigned to them:

Name

Enter a meaningful name for the replication task, e.g., rep-source_mediapool-to-target_mediapool.

Parameters

Media pool Specification of the source media pool

PoolEnter the name of 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.

Destination Specification of the target

Pool Enter the name of the target media pool to which the data will be replicated, e.g., target_mediapool.

Note

With v. 4.4.2, the EOL (end-of-life) of the target media pool will be ignored. If a save set is deleted from the source media pool, it will also be deleted from the target media pool. It is recommended to upgrade to the latest version, which solves this issue.

Drive Select the drive number of the drive that will be used to write the data.

Interface Specify the network interface of the RDS through which the data transfer will be executed, e.g. the name of the RDS.

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

Note

Only the save sets with status successful and with warnings are selected for replication, whilst save sets with errors and only partially restorable save sets (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.

Buttons

Make a copy and save

If the replication task was given a different name in the Name field, all modified settings can be saved under a new name

Save

Saves the current changes

Delete

Replication task is deleted

Cancel

Editing of the replication task is closed, the changes are discarded

Tasks as List

The context menu Tasks as List shows a list of all configured tasks.

By clicking Properties you can see the information of a selected task and also make changes to it. Alternatively you can double-click the backup task to open it.

Right-click menu

Right-clicking a backup task in the table shows a Context Menu with the following options:

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.

Copy

Copies the selected backup task.

Delete

Right-click on the backup task, which you want to delete and select Delete. Answer the following security question with Yes.

New task properties can be added to the list by a right-click on the table header and selecting the additional columns. The new columns will only be applied if the Save view button was activated.

The list can be printed using the Print button.

Scheduling

The chapter SEPuler describes Time Management within SEP sesam. Here is a discussion of the user interface for backup schedules, events and calendar attributes with in SEP sesam.

Schedules overview

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

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

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

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.

As of 4.4.3 Grolar, a new option Without Schedule is available under the Schedules.

This option is available, if you set the value for enable_gui_events_without_schedule in the Defaults window (Configuration -> Defaults -> Settings tab) to 1 manually.

It shows all backup events which are not assigned to a schedule 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.

Note

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

Create new schedule (schedule properties)

The options for creating a SEP sesam schedule differ slightly depending on your SEP sesam version. Refer to the relevant version-specific information below. Version 4.4.3 provides a few additional options such as user-defined dates (custom calendar). For details on its usage, see Creating Custom Calendar.

Schedule v.4.4.2

Name

The name of the schedule.

Execution

Enabled by default. Use this option to activate or disable the schedule. If set to No (disabled), the schedule will still be displayed as shaded in the list of schedules, but the related jobs will not run.

Cycle

Configure the intervals for scheduled jobs. Jobs can occur once or recur from every day to every year.

The time range of the schedule. Clicking the arrow displays a calendar.

Begin

Start time of the repetition cycle. The schedule is only valid from the specified date. There can be no execution prior to this date.

End

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 End checkbox and enter the date of its suspension. By default, this option is disabled and the schedule will be repeated in perpetuity.

Start time frame

The start time of the events linked to the schedule.

Start

Designated start time of the event. The actual start time depends on the processor load of the system. See below option Duration.

Duration

The time frame for the allowed actual start specified in days and/or hours (the amount of time an event can be in the queue). Actual start of event depends on the processor load and event priority. At schedule's designated start (see above option), every event is forwarded into the queue where it waits to be processed according to its priority. If execution is not possible within the specified duration time, the event will not be started.

Schedule v. 4.4.3

Execution

Enabled by default. Use this option to activate or disable the schedule. If you deselect the execution option, 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 or yearly.

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 (available on SEP sesam v. 4.4.3 or higher, see creating custom calendar for details)

Advanced settings

Allows you to further refine your schedule.

Start time frame

Select the check box if you want to specify maximum allowed actual startup time for your event (the amount of time an event can be in the queue). Specify the startup time in days and/or hours. The actual start time depends on the processor load of the system. At the starting time of the event, every event is forwarded to the queue, where it may have to wait until jobs with higher priorities are completed. For jobs with the same priority, the FIFO rule (first in first out) applies. If this option is set and the event cannot be executed within the specified time frame, it will not be executed at all.

Repeat task

Select the check box if you want to repeat the event. Choose how often (in hours or minutes) the task should be repeated.

For a duration of

Available if the Repeat task check box is selected. You can specify for how long should the event be repeated in days and/or hours.

Stop task if it runs longer than

Select the check box if you want to set the amount of time (days and/or hours) following the event's scheduled start time after which the event will be cancelled.

New backup event

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

The button New Backup Event opens the following window:

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

The event only works within the prioritization concept as a block for other backups with the same name when schedules are overlapping. See Blocking events

(non-editable parameter) The drive group which is specified in the media pool. This field changes depending on the media pool selection

Drive (opt.)

Selection of a drive from the drive group mentioned above

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 (≥4.4.3)

Specification of events that are started on the SEP sesam Server once the initial event has completed. For details, see Follow-up Events.

Object

Task

Selection of the backup task related to this event

Task Group

Selection of the backup task group related to this event

New restore event

The button New Restore Event opens the New restore event window with the Source tab selected. The first tab is Schedule. For more details, see Scheduling Restore.

New restore event – Source

Restore Task

Selection of the restore task for which the event is going to be configured.

Fix Restore

The restore will be executed exactly as defined by the restore task parameters using the same backup save set.

Selection

The restore task can be adjusted, for example to use the most recent backup save set. The following parameters can be set.

Parameters

Saveset Limitation

indication of the time frame:

View: oldest selection: first, second, third, and so on

View: recent selection: last, penultimate, antepenultimate, and so on

backup day

set a time frame for the exact backup day: from date ... to date

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.

Example : 2 weeks ago until now: from date = -14 to date = 0

FDI-Type

Only save sets with the specified backup level will be used for restore: C (copy backup), F (full backup), D (differential backup), I (incremental backup).

Selection

Provides the criteria according to which the backup save set 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.

Media Preference

Option to limit the media that are used as the restore source.

No limitation >> ' '

Regular medium before clone >> 'media'

Clone before regular medium >> 'clone'. If no clone is available this selection is ignored.

Tolerance

Option to limit the media that are used for the restore.

Error if medium is not available (Default) >>

Only select available media >> 'available'

Only select available media that are eol-protected >> 'eol-protected'

Pool Restriction

Option to define that a save set must come from the specified media pool.

State

Option to 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)

New restore event – Destination parameters

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.

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.

The name of the already configured migration task for which you want to create a migration job.

Priority

The priority of your migration 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.

The name of the source media pool from which the data will be migrated, e.g., source_mediapool.

Drive

The drive number of the drive that will be used to read the data.

Destination

Pool

The name of the target media pool to which the data will be migrated, e.g., target_mediapool.

Drive

The drive number of the drive that will be used to write the data.

Interface (opt.)

The network interface of the server through which the data transfer will be executed.

Time frame

The time frame of the backups that will be migrated specified by exact date or by relative backup date.

Filter

Backup state

The backup completion status of the save sets you want to migrate: successfully or with warnings (default) or only successful. You cannot migrate the erroneous or only partially restorable save sets (containing data from cancelled backups).

Object

Select one of the following objects as a migration source.

Task

Only this task within the defined time frame is migrated.

Task group

Only the tasks of this task group within the defined time frame are migrated.

Client

Only the backups for this client within the defined time frame are migrated.

Backup level

The backup level relevant for migration (COPY, FULL, DIFF, INC).

Number of copies

How many times may the backed up data be migrated. Default is 0, meaning that data migration is unlimited.

Copy migrated save set again

A save set that has already been migrated can be migrated again.

Special filter

Start media

Select only one medium from the source media pool to be migrated.

Save set

Select only one save set to be migrated according to its ID.

Parallel migration

The data can be migrated concurrently using multiple streams, thus improving the migration speed.

New media event

Succession Parameters

Priority

The priority of your media 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

The event is only in effect to block other media events for the pool when schedules overlap. See Blocking events.

Execution Parameters

Media Pool

Grouping of media by certain criteria (e.g., by types of media etc.)

Media Strategy

Indication of strategy OLD defined in the media pool

Drive Group

Selection of a drive group. Advantage: Sesam uses the drives belonging to a specific group independently

Drive

Selection of a certain drive

Tape Label

Selection of a pre-set tape label (tape identification) from the media pool

Spare Label

Selection of a pre-set spare label from the media pool

A media event from the point of its activation defines a specific media of a pool onto which the backups write their data.
The contents of the media are deleted by the event.

If the expected media is unavailable at the start of a backup or end of media is reached during data-transfer then SEP sesam creates an internal media event which provides the next media for the backup. If no media event is configured in the calendar only the internal one is in effect at the EOM.

New command event

As of SEP sesam version 4.4.2, a new command event can be scheduled to run automatically. In the Main Selection -> Scheduling -> Schedules, select the schedule to which you would like to add a command event. Right-click it and select New command event.

Under the Sequence Control, the following options are available:

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

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.

Under the Parameter, define the following:

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 Choose button, and delete an existing command event.

Client: Select a client, on which the command will be executed.

User: Enter the username of a user with sufficient access to execute the command on the client.

You can also access the configured commands from the menu bar -> Configuration -> Command.

Access restriction 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 only executed when the username and the command are entered into the file /etc/sesam_cmdusers.allow on the client computer.

Format: 'user command|* ( * = all commands is started with su - user)

Windows

External commands are only executed when the user and the command are entered in the registry on the client computer, in key text HKEY_LOCAL_MACHINE/SOFTWARE/SEP Elektronik GmbH/sesam/CommandEvents/user/command.

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.

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.

Events

Shows an overview of configured backup-, media-, command- and NEWDAY events. Those are the events which SEPuler permanently checks and (if starting time is reached) executes in chronological order.

Events as List

The context menu Events as List shows a list of all configured events. The events overview displays details for each listed event, including event level, ID, related task, related schedule, event priority, target media pool, drive number, interface, follow-up events and the time of the next execution.

By right-clicking an event or by clicking the Properties button, the properties of an event are displayed. For details on different event types and their properties, see Schedules.

Use the Print button to print the events list, or select Export to export the list as Excel or CSV file format.

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.

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

In the calendar window an additional icon appears in the toolbar. A mouse-click on the icon activates the automatic update function. This means that the calendar window is refreshed (updated) every 10 seconds.

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

Job State

Backups are an integral part of the SEP sesam information system.
Only "completed" backups are displayed with a multitude of selection and filtering options.

All Results by State

All Results window provides details of all jobs. You can open it from the Main Selection -> Job State -> All Results.

Note

As of v. 4.4.3 Grolar 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.

It shows the following information:

Job ID

Event Type: backup type, command, media, etc.

State: successful, active, error

Object (the name of the object being processed)

Task (the name of the task)

Start and end time of a 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)

Drive (the number of the drive used by a job)

Data size

Throughput

Duration

Session ID

Pool (the name of the used media pool)

Message (record of the performed action, such as Backup completed successfully)

User comment

You can filter the results you want to display by clicking the Filter button on the far right side of the window.

Backups by State

From Main Selection -> Job State -> Backups backup operations can be viewed historically.

Note

As of v. 4.4.3 Grolar 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.

The order of the columns can be changed as needed by dragging-and-dropping selected columns.
By selecting a task and clicking the button Properties or by simply double-clicking the task you can view the details of a specific task. An active task can be canceled by selecting it and clicking the button Cancel.

By clicking a column header, e.g. "State" or "Start Time", the column will be sorted accordingly. If you right-click a column header a pop-up menu appears:

You can set which columns are shown by adjusting the Column Visibility.

These settings are stored in the local Java-profile of the GUI client by default. The jobs (if already implemented) are shown grouped in treetable view (see Tasks by Groups). The button Table View can be used to switch to a simple flat view. After switching this button turns into Treetable View so you can go back to the previous view.

Toggle Grouping

As of 4.4.3. Tigon V2, you can use additional Toggle Grouping button to group the same backup task states in one item and display its current status. Grouping allows you to quickly scan the success of backup jobs (useful for backups which are running several times a day and generate a huge backup tasks count on one day, such as SAP HANA or Oracle). Note that you can identify the state of a grouped task by the color of the state column. If the grouping contains backup jobs with different states, the icon is also 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 one ended with errors.

State Filter

The Filter can be found on the top right side of the window. The filter window divides into four areas (Data Range and Clients, State, Type and Task Name).

Note

The control window all servers is only visible for the SEP sesam Master GUI. Using this option the system administrator can select specific SEP sesam Servers for display and action.

Date Range and Clients

With Data Range and Clients you can restrict the display by time or by client.

Date (Sesam Date)

The date range specification from/to controls the display of running backups in the table.

Filter

Client

Filters the backups specified by the client during the period

All servers

The switch is only relevant in a Master GUI environment and then used to display the backups of all servers that are managed with the Master GUI.

State

With the filter State you can display or hide particular backup states. It can be helpful in more complex backup environments for job analysis.

In Progress

In Queue

This task is in the queue, i.e., appointment started by SEPuler, however, must wait until the tape drive is available for the selected media pool.

Active

This task is in process.

Not restorable

Canceled

The task was aborted during data transmission.

Error

Fatal error during completion of that task.

Restorable

Successful

Backup is successful.

Info

Some system-related files could not be backed up, i.e., opened files under Windows.

All states

On

Can be turned on/off.

Type

This area allows you a specified view off different task types.

Events

Newday

Can be turned on/off.

Backups

Can be turned on/off.

Migrations

Can be turned on/off. Therefore backups in line with a migration are also displayed here and not only in Job State -> Migration. This can be useful if periodic dependencies should be compared.

Startup

Start up events are running after restarting SEP sesam Server. These events are not running regularly; they are triggered automatically by the server start up.

Commands

Shows command events.

Groups

Are placeholders for grouping of single tasks and can be turned on/off.

Task Name

A search string can be entered in the input box by which the task names are filtered. They are displayed in the list underneath. There you can select one or more tasks by holding down the CTRL-key and clicking the name(s).

Filter Settings

In the Filter Settings the automatic refresh of the result table can be activated or deactivated.

Properties of a finished backup

More details about tasks can be accessed by selecting a task and double-clicking it (or by clicking the Properties button).

Info 2

Information about drives and time.

Info 3

Shows status of encryption and compression.

Main Log

Main log records the events that occur during a backup process (startup/shutdown information, errors, etc.). As of v. 4.4.3 Grolar, every time the EOL is modified, corresponding information is shown in main log.

Pre Log

Post Log

Savesets

The Savesets lists all currently saved backups. For details on how to check backup chain dependencies, see Managing EOL.

Restores by State

This window displays restores that have been performed using the same Filter- and Selection Options just like they are displayed for backup tasks. However, the columns in the result tables are somewhat different.

Note

As of v. 4.4.3 Grolar 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.

By selecting an active restore task from the table and by clicking the button Cancel a running restore can be stopped. Any data transferred before the Cancel command stays on the target system.

Properties of a finished restore

Info 1

Saveset

Name of the backup job

User

Name of the user

Size[KB]

Size of the restore in bytes

Restore Type

Complete restore or selective restore

Tree type

Hierarchical or flat

Mode

Overwrite, not rename

Used Labels

List of used media

Message

Detailed status report e.g., Restore completed successfully

Info 2

State

Latest status e.g., Successful

Backup Task

Name of the backup task

Interfaces

System interface that was/were used

Location

Location of the target computer

Client

Name of the target system

Drive

Number of the used disk drive

Backup count

Number of the used backup task

Start time

Start of the backup

Stop time

End of the backup

Target

Path of the restore

Comment

Additional information

Info 3

The expert options that were entered in the restore wizard are displayed here.

Options

Passed options e.g., higher log level "-v 3".

Reduction Path

Passed reduction path e.g., "/usr/opt".

File Filter

Repeat of the optional file filter e.g., "*.c".

Protocol

You will find reports and logs regarding the restore in the restore protocol/log files.

Pre Log

Reports for the restore Pre- interface, run before the restore began.

Post Log

Reports for the restore Post- interface, started after the restore finished.

Migrations by State

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 state of your migration or replication job from Main selection -> Job State -> Migrations and Replications. Migration and replication use the same filters and selections as does SEP sesam backup system, for details see Backups by State. The columns provide details on status, start and end time, and media pools used for the task.

As of SEP sesam version 4.4.3. Tigon V2, 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.

Note

As of v. 4.4.3 Grolar 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.

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 the overview by date range and/or media action status. Filter settings remain in effect even if you switch to another tab and are dismissed when the Media actions tab is closed.

Note

As of v. 4.4.3 Grolar 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.

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.

EOM (end of media): EOM specifies whether there is still free space left on the medium or tape. If there is no free space left, the medium or tape is full and can no longer be used for storing data.

inventory: A process that scans media in the device and updates SEP sesam information about the media in the tape library.

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 save sets. The oldest free save sets are deleted first. Purging is done until the LWM (low watermark) is reached.

Properties

You can view the details of each listed media action by double-clicking the desired table item (or by selecting a table row and clicking the button Properties). The following tabs are available.

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

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

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 save sets on the medium.

Display all segment marks of the tape.

State of the readability check at the end of the protocol.

Monitoring

Monitoring provides several features, including a dashboard (displays the state and other details of your backups and restores), last backup state (shows the last status of each configured backup job), shows all running processes/daemons, and the status of all used disk drives (information on queue).

As of SEP sesam v. 4.4.3.33, SEP sesam dashboard is available in the GUI. The dashboard is also available online at the following address: http://[servername]:11401/sep/ui or https://[servername]:11401/sep/ui. For example, if the name of the server is localhost, the following link will open the SEP sesam dashboard: http://localhost:11401/sep/ui.

SEP sesam dashboard is an easy-to-use monitoring tool that constantly tracks SEP sesam operations and their state and provides key metrics of your backup environment. You can check whether all your backups and restores have been completed successfully and review other various useful information, such as daily, weekly, monthly or custom statistics on SEP sesam events, on total size of backed up and restored data and on data store utilization. You are able to filter the reports by events, clients, tasks and state; check backups and restores per client or application over time; get an overview of up-coming events and data store utilization.

You can export the dashboard data into CSV, JPG and PNG formats. For all details on dashboard features, see SEP sesam Dashboard.

Last Backup State

In this view you can see jobs which have never been backed up. Furthermore, you can check previously executed jobs with their last backup state.

Note

As of v. ≥ 4.4.3 Grolar you can additionally filter the results by date range (previously only by states and event types).

This window quickly shows how the last run of a backup went in order to find possible errors and fix them.

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

Processes

Shows the state of SEP sesam processes on the SEP sesam Server.

The command line allows the user to display all processes and daemons with the command:

If for example the rmi demon is not available the following would be displayed:

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

If a process/daemon is off-line, it can be restarted by using the command line. Example for rmi:

sm_main reload rmi

Drives

Monitoring drives shows the drive queue. By selecting all (*) or selecting the desired drive number from the drop-down list, followed by clicking the Refresh button, the information about the queue is displayed. A queue is managed by a queue manager (QM). SEPuler and some other internal processes send their tasks as jobs to the queue manager which coordinates the execution. The jobs are processed according to their priority. The required queues are created by SEP sesam during the configuration of drives.

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

Logging

SEP sesam creates two protocols or log files for each backup day: the status file and the day log. This information is stored as files in <SESAM ROOT>/var/prot. It can be utilized for other tasks and can be transmitted in print, email or web forms if desired by using post commands to transmit data for reporting and control if desired.

The selection of time interval enables restrictions to output. Start this by clicking the Show button.

State

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

Functions

From - to

The time selection allows filtering of the output.

Note

A backup day is defined by two newday events.

Today, Yesterday

Shows logs from today or yesterday.

Help

Online help.

Send

E-mails the log to your support service or any other predefined address.

Print

Prints the log using the default printer.

Day Log

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

Time selection allows to filter the day log output. Day log protocols are the first and most important starting point for problem analysis. The user can find detailed help for problems and error messages in the SEP Sesam Admin Manual. These errors and a PuTTy copy of the log file can be sent to SEP sesam support to provide detailed information on SEP sesam operations.

Error Log

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

Time selection allows to filter the error log output. Error log can be sent to SEP sesam support to provide detailed information on failures.

Sesam Interface Logs

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

Notification

Notification center

Notification center is used to dynamically send different types of messages – notifications from the SEP sesam Server to all open GUIs. These messages inform the user about license violations, not configured interfaces and include other important information, such as announcement of a new release or alert about an error, send via RSS feeds.

Notifications can be accessed from the upper right corner of the SEP sesam by clicking the Notification Center or from the menu bar -> Window -> Show Notification Center.

All messages which are visible in the notification center need a response:

All dismissed messages will disappear from the Pending messages list.

If a message is accepted or postponed, it stays in the Pending messages list until they have been resolved (in case of accepted messages) or accepted+resolved or dismissed (in case of postponed messages).

Tip

To view the messages that were already resolved (accepted or dismissed), click the Show resolved messages button. The Resolved messages list is displayed under the Pending messages. This list contains all messages that have already been completed with details, such as the name of the user who resolved the message, optional comment, etc.

Subscribe to SEP Sesam RSS Feeds

SEP sesam RSS feeds are used to inform about new releases and new features, version specifically. To subscribe to a SEP sesam RSS Feed go to the following homepage: