User Manual 4.2 - printable version

From SEPsesam
Jump to: navigation, search
Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.

Copyright © SEP AG 1999-2017. All rights reserved.

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.


Contents

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.

SEP sesam supports all standard backup devices, disk, tape, tape autoloaders, tape libraries. SEP sesam delivers Virtual Tape Libraries (VTL) as a standard component of the base product. Using economical, high-performance disk drives SEP sesam delivers a lasting, sustainable solution for the backup and recovery of enterprise critical data. Disk-to-Disk-to-Tape (D2D2T) functionality delivers further enduring security for maximum performance by backup and restore.

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.

Drive
Local or remote storage device
Loader
Robot loading the media from/to the drive
Client
Computer from which the data is backed up
Media
Repository for the saved Data
Task
Description of a Backup or Restore
Event
Start time of different activities

Additional Features:

  • Backup Server on Linux (including Novell OES), Windows, FreeBSD und Unix
  • Clients for Linux, Windows, many UNIX derivatives, NetWare (Client free support) and VMS
  • Fast and easy installation on standard O/S configurations. Less than one minute on SUSE and RedHat!
  • SEP sesam creates a test backup and restore upon installation to verify system is running
  • JAVA based graphical user interface. (GUI)Master GUI design provides full access to clients and servers
  • Support for all automated tape drives or autoloaders
  • Full, Differential, Incremental and Copy (for off-site storage) backups are possible
  • Scheduled backups using user/administrator selected events
  • Media administration and setup via GUI or Master GUI. Allows flexible media strategy and easy task selection.
  • Powerful scheduling tool
  • SEP NEWDAY allows backups to record on the same calendar day, i.e. backups started on Friday and finishing on Monday before 8 am can have the same backup day
  • event control can be used for any external applications
  • Scheduler allows development of flexible media strategies to avoid delays and missed backups
  • Selection of optimal data paths throughout the network
  • User configurable Command Line interfaces (Alarm, Pre/Post, Notify, Disaster, etc.)
  • Fast data restore via effective administration of the backup savesets and implementation of well-designed search algorithms
  • Full and selective restore to the original paths or in newly-created directories with or without preserving the original path structure
  • On-line modules for database backup DB2, Informix, MS SQL, MySQL, ORACLE, SAP R/3 and others are available, i.e. backup performed without stopping the database
  • Optimized tape backup using parallel backup streams for multiple clients; Sesam Multiplex Streaming allows up to 64 continuous backup data streams
  • Migrate from savesets on disk to tape; DISK-to-DISK-to-TAPE

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.


Sesam-Philosophy en.png

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:

  1. Create the clients. Install client software on target computers to be backed up along with any online modules that are required.
  2. Define tasks (WHAT should be backed up).
  3. Define schedules (WHEN the backup takes place).
  4. Link the schedule with an event (WHAT will be backed up WHERETO and HOW).


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


<<<Back
Principle of SEP sesam
User Manual
Next>>>
Media Strategy


Grouping of SEP sesam Components

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


Sesam GUI 4.2 en.jpg


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 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 currently free drive. 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. Sesam requires the configuration of media pools.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Grouping of SEP sesam Components
User Manual
Next>>>
The SEPuler - an event calendar


Media Strategy

The 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 pool name may never end with five (5) digits. In the GUI a new media pool is created under GUI->Components->Media Pools->New Media Pool . An important parameter set in the media pool is Locked Days , i.e. how many days a tape from this pool cannot be used, preserving the backup data. This is a number of days and is called End of Life = EOL.

For each medium the following information is stored in media archive:

Label  
Identification of the media
Media Pool  
Name of the pool where the media belongs
ID  
Number within the pool
Write Protection 
Can be set up by the user; blocks the media against overwrite until the write protection is cancelled
Backup Day  
Date of backup day, SEPsesam uses the date the backup started, e.g. a backup starts at 11 p.m. on January 1, but finishes at 2 a.m. on January 2, a Jan 1 backup
Locked until 
Date from which it can be used again = backup day + Pool_EOL
Drive Number  
of the drive used for backup
Media Type  
is compatible only with certain drive types
Loader  
in whose magazine the media are currently loaded
Slot  
of the magazine
Occupancy  
in MB, GB, etc.
Error Count  
accumulated count of potential error messages of the drive for this medium


The fields Write Protection, Loader and Slot can be changed directly by the user.

Write protecting media precludes it being overwritten during backup, preventing data loss. The write protection setting is preserved until the user cancels it manually.

EOL write-protection, however, is automatically controlled by SEP sesam.

Loader and slot numbers must always match with the actual location of the medium. This is especially valid when using smaller autoloaders that do not have bar code readers. It is physically and technically impossible to recognize manual changes to tapes in the autoloader magazine. If media are removed from the autoloader or entered at random the program will not recognize these changes. It is absolutely necessary to either start an archive adjustment via the GUI or to enter the correct data (loader and slot numbers) directly into the archive.

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

Media change using the media event

Entered media should be fully utilized and written on until the end of media (EOM).

No entry for EOM is necessary. SEP sesam will request a new medium from the corresponding mediapool automatically when the medium or tape is full.


Every day a new cassette from the media pool should be used.

When using a single tape drive the media event is not required. By inserting a tape without an EOL entry every day SEP sesam will automatically complete the prior day's backup (set the data protection) and initialize the new tape. This method has the advantage that in the event of a holiday, new data will be written continually on the tape in the drive from the end of the last backup (write) until the tape is full.

When using an autoloader a daily media event must be set. Doing so assures that a new medium is used from the loader. The prior days media will be locked using the EOL command set by the administrator.

When using either a single tape or autoloader it is possible to pre-define a medium for a specific purpose. This is useful when certain media are used for month-end, year-end, or for copy purposes.


It is generally recommended to set the media event during regular working hours, for example 10 am, and after SEP NewDay. This way the request for a new tape, requiring manual change, doesn't occur in the evening or at night when the backup is scheduled to take place.

GET_OLDEST strategy

If there is only one media pool connected 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 and load it into a drive.

The user must be sure the autoloader magazine is accessible by SEP sesam or the backup will be blocked.

The GET_OLDEST strategy selects the medium

  • with the oldest 'locked until' date in the media pool (= the oldest one)
  • with no set write-protection
  • with already exceeded locked until date

to be used next.

Spare Pools

Blocked backups can be prevented by using SPARE POOLS.

The name of spare pools start with SPARE_. In this situation, initially unused media are inserted and kept for later use. For each type of drive an adequate spare pool should be generated and filled with compatible media.

These spare pools are used by media events in case 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. Here the spare media migrate from spare pools to the working pools resulting in a dynamic increase of media pool size depending on the amount of data being backed up.

SPARE pools can be used for automatic insertion of new media into working media pools. For big loaders the media are pre-initialized with labels of SPARE pools at SEP AG saving time during the installation phase. The media then migrate as needed to the working pools on the production system.

Media utilization can be influenced in following ways:

  • locking time-limits of media pools
  • set/unset write-protection in media archive
  • media events in SEPuler
  • modify the locking date of a media in archive to an already exceeded date and execute a media event

Archive Adjustment

An Archive Adjustment makes a comparison between media in the loader carousel or magazine and the SEP sesam media archive database. An archive adjustment is mandatory whenever the contents of a loader carousel have been altered. This is especially true after inserting new media or used media which have not yet been registered (initialized) by SEP sesam.

Once new media have been inserted in the autoloader it is necessary to execute an archive adjustment. The option Automatic new Entry is selected to enter the new media automatically.

The adjustment is started using the GUI->Components->Loader->Content->Archive Adjustment.

When selecting Archive Adjustment be certain that the autoloader being realigned is selected in the GUI Window, i.e. make sure 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.


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


<<<Back
Media Strategy
User Manual
Next>>>
The Backup


The SEPuler - an event calendar

The scheduling of SEP sesam backup and restore tasks is controlled by the SEPuler, which acts as an electronic calendar and assistant performing all stored backup and restore events. The SEPuler is a permanently active background routine (daemon) constantly checking for events to be executed. When the SEPuler finds a backup/restore task the execution of the corresponding program is initiated. Once the backup task has started, the SEPuler will determine the next execution event for a cyclical backup/restore task and rewrite the event to the backup calendar. For example, if the SEPuler starts a weekly backup on Saturday, January 1, it will schedule a new weekly backup to occur on January 8.

Possible types of SEPuler events are backup, media, arbitrary command and newday.

Backups 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, one-time tasks.

The schedule provides a normalized view of the event calendar showing completed, executing and future events. It can be viewed under GUI->Scheduling->Calendar Sheet.

Detailed information regarding completed backups, restores, etc. can be obtained here.

Schedules

The cyclical behaviour of SEP sesam is realized through the above mentioned schedules. A schedule is a table that describes the cyclic behaviour of an event, i.e. when the event is supposed to happen and in which periods to repeat it. The mere 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 will entries be made in the schedule which are then picked up by the SEPuler. Potential changes in the schedule naturally affect all events that are assigned to that schedule. The following functions can be done with a schedule:

  • A schedule's execution can be deactivated in the GUI.
  • A schedule can be used for an arbitrary number of events as long as the type of event is the same.
  • A task (backup, migration, media action, restore and command event) may have events in several schedules.

Setting Event Priorities

For more complex event strategies schedules can be given priorities. Starting with the lowest priority 1 (up to 99) the SEPuler checks if, within a sesam day, an event with the same type (e.g. backup) and the same task name but with a higher priority has already run or is still scheduled to run. It then supresses the execution of events with lower priorities. This way, for example, several schedules are created that overlap on certain days. According to their priorities they prevent each others execution. Schedules with prio=0 get special treatment. This means that no dependencies are accounted for and they are always executed.

The equality of events is managed differently for the different types:

  • Backup events are equal if their task name is the same
  • Media events are equal if their drive number or drive group number is the same
  • Command events are equal if their name is equal
Example
the 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 done instead of the the daily event (prio 2 overrides prio 1).
  • At the end of the month the end of month event is done 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 overrides the weekend event (prio 3 overrides prio 2)

Blocking Events

A blocking event is an event of any type with a higher priority which inhibits another event 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).

Important Information
  • Event blocking is accomplished by checking the according field during the configuration of a task.
  • Turning off a set event schedule can prevent the completion of all events used by this event Schedule (Switch Execute in the schedule).
  • A blocking event only works on similar/similarly named events (Switch Blocked event in the event).


Attention

  • switching off a schedule blocks the execution of all events using this schedule (select Execute in the schedule).
  • a blocking event has an effect on similar events only ( select blocking event in the events).

A blocking event is created by marking the corresponding priority field during the configuration of an event.

Example A backup event that executes the task stratu1_etc runs continually with priority 2. A second backup event, also for the 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 a backup stratum1_etc with higher priority and overrides the execution of the daily backup. The blocking event itself doeen't create an entry in the job status but only gives out the message that it was activated.

The SEP sesam backup day - NEWDAY

SEP sesam NEWDAY event resets the backup calendar. A NEWDAY switch set to Monday, 8 am, will cancel all pending jobs from the weekend and reset the SEPuler to begin looking at the current day's calendar settings. SEP sesam defines the time interval between two NEWDAY-events as a backup day. Since there is only one event for NEWDAY, it is set after the installation and only its schedule can be modified or deactivated.

Having set a daily NEWDAY-event at 08:00, the backup day extends until the morning of next day at 08:00. Backups that run after midnight - the actual date change - are 'time stamped' with the previous day's date. The reason is quite simple, yet elegant. The data was created on day one, but not backed up until day 2. To do otherwise would create two backups for the same date, with a portion on backup day 1 and the remainder on backup day 2. With SEPsesam NEWDAY all media backed up from one day have the same date. SEP sesam NEWDAY gives system managers the flexibility to extend backup routines to run after midnight and retain the backup date of the prior day. This is very useful when the computers requiring backups exceed the time allotment between the end of day and midnight.

Weekends are often used for full-backups. When this is the case, it is advisable to interrupt the NEWDAY event on the weekend. Define the execution as a weekly event but without execution since a full backup is performed instead.

Note: SEP sesam protocol or log files are all created with the date of the backup day.

Example: Backup day from 10.SEP.2007 08:00 until 11.SEP.2007 08:00 A backup starting on 11.SEP.2007 00:40 will be assigned to backup day 10.SEP.2007, it will appear in the daily protocol as 20070910.

Backups can be arranged in shifts.

A NEWDAY-event also executes the following tasks:

  • aborts all executing backups (data created after NEWDAY belong to the next backup sequence) This is also useful in complex network environments, when alerts are not transmitted to the backup server. These backup tasks would otherwise remain suspended but are terminated by the NEWDAY event.
  • deletes files and database entries for savesets which no longer exist
  • finalizes the SEP sesam status and daily log files
  • reorganizes the SEP sesam database
  • advances the calendar (SEPuler) by one day
  • restart of the SMS- and STPD-processes


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


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
The SEPuler - an event calendar
User Manual
Next>>>
The Restore


The Backup

Automatic backups are monitored and initiated by the SEPuler. Data specified in task for backups are copied to saveset on the pre-selected media.

To speed up and simplify the restore of desired data SEP sesam creates additional listings and media segmentation data. Doing so shortens recovery time.

The SysAdm user defines which data in his network should be backed up and sets the backup event schedule. Decisions must be made during the task configuration regarding media, media pools and backup type (full, differential, incremental). The SysAdm uses this pre-determined configuration to select and organize backup tasks, schedules and events. If desired PRE- and POST-interface commands must be configured at this juncture, as well.

Full-, Diff-, Inc-, Copy-Backup

The Full-Backup copies all the files of the source defined in the task. When doing a restore this version of the files can be restored easily by copying it back from the medium but this may in come cases be a very large amount of data to. The archive bits are not deleted on Windows systems. Information about the status of that backup for diff- and inc-backups that are based on it is stored in the SEP sesam database. If you want to force-reset of the archive bits you can do so via the backup options by entering -o clear_archive.

A Diff-Backup (differential) saves only those files that were altered since the last full backup (of the same task). This can drastically shorten the backup time. To restore the whole data source, the saveset of the full backup has to be copied back first before the saveset of the diff-backup can be copied. This means that two steps are necessary. This however is detected and performed by SEP sesam's generation restore.

An Inc-Backup (incremental) saves only those fields that were altered since the last backup of the same task. This way generally creates the smallest amount of data. In order to restore the whole data source, first the saveset of the last full backup as well as all inc-backups have to be copied back. Therefore, depending on your backup strategy, several steps are necessary which are however performed by SEP sesam automatically. A combination of full backups onto tape drives and diff- or inc-backups onto virtual disk media is a common method.

A Copy-Backup is a full backup that has no influence on following diff- and inc-backups. For the treatment of archive bit see full backup above. This type is usually used for additional full backups, e.g. monthly backups, or backups for archiving, i.e. removal from storage.

In case no initial FULL-Backup exists, DIFF- or INC-Backups are automatically performed as FULL-Backups!


Backup with VSS (Volume Shadow Service) on Windows

With the Volume Shadow Copy Service (VSS) opened files can be consistently backed up under Windows. Thereto by Windows a non-persistent snapshot (shadow) is taken of the volumes and then backed up.

In the saveset the data is stored with original location, e.g. "C:\".

The total amount of VSS snaphosts is restricted to oper systems:

  • under XP only one set (with some volumes) is allowed,
  • other oper systems allow up to 64 sets.


Attention

If the restricted total amount of created volumes will be exceeded then a VSS backup fails. The total amount includes VSS snapshots which may be created otherwise!

As VSS uses the Copy-on-Write method only the amount of space for data which is changed during backup is needed as additional space during backup. The non-persistent snapshot disappears after the backup and does not occupy a volume identifier. Differential and incremental back ups are processed on the shadow. The restore is unchanged due to saveset has stored original pathes.

See:

A description using SEPsesam Pre-/Post-Interface for SEPsesam Version 3.0 is located under SEP sesam Volume Shadow Copy Service (VSS) for Windows via Pre/Post.

System Requirements

  • Client operating system: Windows XP, 2003, 2008
  • Sesam Server from version 3.4.1.64
  • Sesam Client from version 3.4.1.64


Activation/Deactivation of the VSS Shadow Backup

When creating a new backup task you will see the option Backup with VSS. This box is checked by default and can be unchecked if necessary.

Newbackuptask 4.0 en.jpg

Parallel Backups

Sesam supports parallel i.e. simultaneous backup for several data sources onto one drive. This is called Sesam Multiplex Stream (SMS).

Modern tape drive manufacturers have continued to dramatically increase 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 64 channels on a single drive; each channel can serve one backup source.

Data of the different streams are distributed into packets, each packet is supplied with an identification mark and is copied onto the media. The data of a certain stream are not contiguously positioned on the media, but are 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 savesets across several media ( EOM = EndOfMedia ).

Encryption

Supported encryption algorithms are the Advanced Encryption Standard (AES) 256-bit encryption and the Blowfish encryption. You can select the type of backup encryption under the Encryption and compression tab of the backup task properties. For every encryption you must create and store an encryption key. Data can be encrypted and compressed at the same time only if it is stored on tape, thus using the manufacturer's compression algorithms. If the data is stored to disk, it can either be encrypted or compressed, but not both.

Important

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

Storing the encryption key during encryption

When a backup encryption is selected the encryption key is also encrypted in the Sesam database. This occurs and is backed up in the Task Table as well as being stored in - Table Results.

In the event the encryption key is changed the following tasks are undertaken with the new key and the new key is stored with the resulting backup. A restore of required data takes place with the use of the relevant key and the key is stored accordingly. A restore requires the entry of the key word.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
The Backup
User Manual
Next>>>
Duplication and Migration


The Restore

SEP Sesam offers full restore ( all files of a saveset ), selective restore ( selected files ) or generation restore. From the Sesam interface the Restore Wizard - an assistant program - is launched. The Restore Wizard guides you through the various steps for data recovery.

Restores can be performed as so called automatically scheduled restores to check the stored data. For that purpose a restore is configurated with the restoremanager and saved. This saved restore (contains all the parameters for implementation) is started in continuous intervals from the SEPuler. With that procedure the data integrity can be controlled and logged.

Selective Restore

During selective restore only a subset of files of a saveset 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 generation view , the selection list displays not only the files from the selected differential or incremental backup but all files since the last full backup - so all generations of files are presented.

In the Sesam GUI a specific view can be chosen, either the view for single backups or the generations view. Using the single backups view the user 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 possible using Sesam and creating an event or task. The restores will then be performed at the set time. It is even 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

The restore wizard can be started from the toolbar Configuration -> Restore


Restore wiz p1.png

Datasets can be searched for by task name in the saveset or by filename or path. The specific tasks can be selected from the task drop down. Or a search regular expression can be entered into the search pattern field. The saved in period allows for the user to search a range of dates of stored backups. The show external results check box will search for results of the search on other clients’ savesets.


Restore wiz p2.png


The results of the search will appear on the next page. Check boxes on the bottom allow for options.

Complete restore of selected task – check this box to restore everything in the task. Hide Migrated – if checked , savesets that have been moved with a migration task will not appear in the results. Generation Restore- restoring an Incremental or Differential backup will require this box to be checked. Sesam handles this automatically.

Disaster Restore- check if restoring a server from a disaster scenario. Please see SEP sesam Server Disaster Recovery for Sesam disaster recovery instructions. If a client server is being recovered simply select the server’s disaster recovery back up task.

   Restore wiz p3.png

The next screen allows for a selective restore of individual files. Simply navigate the file explorer and select the files needing to be restored. The Search button allows for files to be searched by regular expressions.


Restore wiz p4.png


The final screen of the restore wizard provides an overview of the restore job. The saveset chosen to restore is listed on top, followed by the editable name of the restore task.

Other options:

Drive: The drive the backup is on. This is more relevant to tape backups without a loader.

Interface: The server with the attached storage the backup saveset is on. This is either a remote device server or the sesam server directly. In other words the server where the files are being restored FROM

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

Target Path settings:

Restore to original path: if check the files will be restored to original locations on the server. This only works if the target node is the server the backup was taken from. New restore target: select if the files need to be restored to some other location besides the original path. The text field to the right can be edited to the new path on the server. Or the browser button will launch the file explorer and the location can be selected graphically. Original Tree structure: if checked all folders in the tree to the restored files will be created in the new target path. If not checked only the files themselves will be restored.

Execution options: this is a dropdown menu with three options:

Do Not OVERWRITE Existing Files : This is the default option. When selected, files will be restored only if they are not currently on the target system. Overwite Existing Files: This selection will overwrite files w2ith their restored version. Create a New Version: this selection will restore files already at the target location is a modified name.

Expert options button: this button opens a popup window to the expert restore options.


Verbose level : this allows user to change the verbosity of the main log from 1 to 6. 0 print only standard and error messages together with summary 1 add a line for every item when processing starts for it: 'sbc-3008: Info: Processing item: [xxx]...' 2 add a line when processing for item 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


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

The radio buttons: Restore the complete saveset , restore according to composed list and disk_info disaster recovery will be selected according to selection made during the restore wizard. Changes here will override the selection made during the wizard. Restore the Complete saveset will restore all files from the saveset. Restore According to the composed list will create a selective restore according to the regular experessions entered into filter tab. Disk_info disaster recovery will restore disk info like the Master boot record and registry during a disaster recovery restore.

The Relocation tab describes files being restored to a new target. The radio button selects whether files are being restored to original path or new paths. Individual files can be restored to separate paths.

The Filter tab filters files for a selective restore using regular expressions.

The backup type tab allows for the option to restore the entire save set into a single file.

the Pre/post tab selects if the user would like the pre or post script to run for this restore task.

EOL tab selects how long the restore will remain in the GUI. Default is 7 days.

Scheduling Restore Tasks

Once a restore task has been created. It can be started immediately from the wizard or saved and scheduled like any other task.

Scheduling p1.png


In the Schedules tab of the main gui simply right click the schedule where you wish the restore task to run the select “new restore task.” This will open a popup window with three tabs. The schedule will show the schedule parameters the restore task is being added to.

Schedule source tab.png


The Source tab provides parameters of the specific restore task


In the Restore Task dropdown select the name of the created task.

the Fix Restore radio button sets the schedule to run the restore exactly as it is defined in the task parameters using the same backup saveset .

The Selection radio button will run the restore task using adjusted parameters in the schedule. For example, restoring the most recent backup saveset.

Saveset limitation is currently not active.

backup day is currently not active

relative backup day selects the backup saveset to restore that falls within the range specified. Negative numbers are days in the past while positive numbers are days in the future. Therefore, a range of -7 to 0 will select a backup saveset to restore that is less than a week old when the restore task runs.

FDI Type is the type of backup saveset that the restore will use C stands for copy backup, F is for full backup D is for differential backup I is for incremental backup

The selection dropdown determines the specific backup saveset the restore will use. youngest: the restore will us the most recent backup that falls in the range of the relative backup day. Oldest: the restore will use the least recent backup in the range.

Media preference is not active Tolerance is not active

Pool restriction will limit the backup saveset to come from a specific media pool. The State dropdown will define the condition of the backup used to restore. successfully or with warnings: the backup used must have either completed with a successful stat or with warnings in the main log. only successful: the backup saveset must have completed successfully without warnings. Only with warnings: only backup that completed with warnings Partially restorable: backups that failed but are listed as partially restorable in the main log.

Schedule dest param tab.png


The Destination Parameter tab allows for the option to select the priority of the job and the drive:


The priority field adjusts the priority of the job in the queue higher prority jobs go first. Blocking date: will prevent the restore event from running if timetables overlap. If checked the restore will block events of the same type of a lower priority. Enforce FULL: used for scheduling backup tasks. Drive: allows for the selection of the drive that will be the source of the restore.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
The Restore
User Manual
Next>>>
Storage Time Limit, Media Cycle

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.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Duplication and Migration
User Manual
Next>>>
Basic Configuration


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.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Basic Configuration
User Manual
Next>>>
Step 2: Clients


Step 1: Locations

First decide which servers you want to be backed up by SEP Sesam. To accomplish this you will need the names and permissions to access the relevant systems.

Using GUI->Components->Topology->new Location you can create the location names and descriptions for the client. Every client must be clearly assigned to a location. As a default the location on the server is set to 'LOCAL'. In the following illustration several 'locations' have been created. location names are freely selectable, they should be unambiguous and they should be easy to remember.

GUITopologie 4.0 en.jpg


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Step 1: Locations
User Manual
Next>>>
Step 3: Storage Hardware - Drives and Loaders


Step 2: Clients

Within the location, a new client is configured in GUI:Components->Topology->New Client. According to the operating system of that computer, either Windows, UNIX, VMS or NetWare platform is selected.

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, Sesam automatically selects the TCP/IP address. Otherwise it must be entered in the etc/hosts file.

For Operating System insert O/S installed on that computer.

If the client has several network cards, their TCP/IP names can be entered in Interfaces .

During configuration an attempt to contact the remote computer is executed (Sesam software must be installed on the target client).

Newclient 4.0 en.jpg


Setup of the Secure Shell (SSH)-Client

To use ssh for client access mode, you must configure automatic login from Sesam server to the client by using the public key.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Step 2: Clients
User Manual
Next>>>
Step 4: Media - Data Carriers


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 use the SEP sesam GUI function GUI->Components->Loader. To perform this operation open the referenced GUI window where the previously configured loaders are located. Each loader is marked and its properties are entered. With OK, the device is finally 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 in the Device Manager (e.g. not as "unknown Media Changer") before SEP sesam is installed!


Loader 4.0 en.jpg


For drives, an analog procedure is applied. Properties of each drive are selected via GUI->Components->Drives->Drive Groups. By default, the drive group Tape_Drives is selected initially. The SysAdm can accept this setting or enter a new location.


Laufwerksgruppen en 3.8.jpg


If the drive characteristics in the field 'Loader' state "No Loader" yet it is supposed to be serviced by an autoloader, the drive was not configured properly, i.e. not recognized properly. You can enter this drive into the configuration location simply by selecting OK.


Note

The first drive in the loader is Drive 0. In the event there are more drives in the loader they will simply be numbered sequentially.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Step 3: Storage Hardware - Drives and Loaders
User Manual
Next>>>
Step 5: Tasks - Select what you want to backup


Step 4: Media - Data Carriers

To prepare media (tape cartridges, removable drives, etc.) for SEP sesam, they must be initialized. The initialization process writes unique identification information to the media which is used by SEP sesam to perform backup and restore operations. The identification label is placed at the beginning of media during physical initialization.

SEP sesam creates labels of the format <Poolname>nnnnn. From the beginning SEP sesam requires the organisation of media into media pools. Within the pool the media are numbered sequentially. After installation a media pool with the name of SEP sesam server is created. A "test pool" can be created under GUI->Components-> Media Pools->New Media Pool.

The media strategy GET_OLDEST and the change strategy TIME are set as default.

For 'Drive Group' choose the one where the new media will be mounted.


Newmediapool 4.0 en.jpg

Now the media have to be included in the media archive (library), which is done under GUI->Components->Media->Initialization.


Medienneuaufnahme en.jpg


The window Adding new media appears. After choosing a drive the specific drive properties are listed below. After that choose the pre-configured entries as desired under Media Pool and Media Type. Now choose Automatic assign of next number and start. SEP sesam determines a sequential number for the label, initializes the cartridge and adds the media into the database. When adding a large number of media at one time to a loader use the automated method. To accomplish this fill the magazine with "raw-media" and then select archive adjustment from the GUI.

The newly created media and media pools are listed under GUI->Components->Media Pools e.g.->Media


Archiveadjustment 4.0 en.jpg


First, select the according media pool, then define the number of media from 0 to n (e.g. for 6 media 0 to 5). Now activate Automatic Introduction, select the according tape type and click Start


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Step 4: Media - Data Carriers
User Manual
Next>>>
Step 6: Schedules


Step 5: Tasks - Select what you want to backup

In GUI->Tasks->by Client choose the according location and then the client of which you want to backup data. Once the client is selected click new backup task at the top or by right clicking it.

A window is opened in which the details of a single backup can be entered. The task name can be chosen freely (max. 32 characters). In the field Source enter which drives, directories and/or files you want to backup.

The line Exclude List allows you to enter file names or patterns of files which should not be backed up.

Newbackuptask 4.0 en.jpg


Individual or single tasks can be consolidated under a specific group name in task groups .


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Step 5: Tasks - Select what you want to backup
User Manual
Next>>>
Step 7: Starting a Backup


Step 6: Schedules

Zeitpläne 4.0 en.jpg


This window shows an overview of the configured schedules and the events that are connected to them. Using the buttons in the toolbar you can configure the scheduling of all processes in SEP sesam. Now, either a new schedule is created or an already existing one is used. In the schedule a new event is created and its job is defined. The job is then done at the set time and, if necessary, forwarded to the next execution time in the calendar.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Step 6: Schedules
User Manual
Next>>>
Directory structure of SEP sesam software


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.


Button Sofortstart Sicherung en.jpg


To configure a normal, periodic backup first select the desired recurrence of the backup. Next, create a new event using the scheduler. 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 GUI->Scheduling->Calender Sheet' or GUI->Backups->Status. This saveset also appears in the restore wizard. It can also be accessed from the command line under backups > Status.

Directory structure of SEP sesam software

A detailed description of the different Sesam directories can be found in the Sesam Administration Guide.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Directory structure of SEP sesam software
User Manual
Next>>>
Menu Bar and Tool Bar


The SEP sesam Graphical User Interface (GUI)

After starting SEP sesam, the connection to the SEP sesam database is first created. Upon completion the main GUI screen opens. This screen controls all SEP sesam procedures and operations.


SEPsesamGUI 4.0 en.jpg


The main screen consists of title-, menu- and tool-bars (top) as well as the component window (left); display window (right); and activities display window (below). The menu bar displays the menu titles File, Activities, Configuration and Help.

By clicking with your mouse or activating Alt + the key of the underlined letter, a drop-down menu opens with several sub-items (functions, actions, commands).

These sub-items can also be activated in the same way (with a mouse click or via Alt + key of the underlined letter) and input masks for further or more precise definition of an action can be opened as well.

The main toolbar offers the buttons Immediate Start: Backup, Restore Wizard, Backups by State, Calendar Sheet, About SEP sesam and Start Disaster Recovery.


In the Main Selection window on the left components of the SEP sesam system are shown. By clicking them sub-menus can be opened displaying more detailed information.

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

Last View in the lower right hand corner of the window indicates the time of latest update of the information. If the check box cyclic (lower right) is checked, the messages will be updated at pre-set intervals.


Master Sesam

Mastersesam1 4.0 en.jpg

The so-called Master Sesam GUI mode can be used to administer several SEP sesam servers with one GUI. This mode can be activated by adding more SEP sesam server in 'Configuration > Remote Server' ad setting their connection to 'On'. If a server is not accessible this is shown in the table view. The GUI client has to be authorized on the according SEP sesam server.

Remoteserverlist 4.0 en.jpg

Once at least one additional SEP sesan server is configured and the connection works a "server" selection window with the reachable servers appears in the upper right corner. The server that's selected in this window affects the "media" shown, the "calendar" sheet, the sub-components of "monitoring" and "logs" as well as the "current messages".

The object trees that are shown in the work windows of a master sesam show all available SEP sesam servers and their objects. This includes the view of the "Job State" components (filters) that can be set to the server selected in the upper right corner or all servers.

Mastersesam2 4.0 en.jpg

Windows

Windows can be pulled out of the main window of the GUI via Drag&Drop and positioned and scaled to your needs. Using the so-called Docking-funtion the layout can be adjusted freely. Even toolbars can be moved to wherever you like.

Dockable en l1.jpgDockable en r.jpg

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.

Main Window

In the work window the corresponding object class for the required function is displayed, e.g. Components->Topology locations and clients can be configured.

Section Output

The output window (below) displays three registers for Current Messages, Performance" and "GUI Logging".

Current Messages

Last Notification shows the result of the last activity. In the event the field cyclic is set, 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 of the running backups and restores can be observed in the graphical display. You can see the amount of data being backed up, the transfer rate in the individual SMS channels for each of the selected drives.


Performance en.jpg


Logging

The log files display the communication activity between the GUI clients and the SEP sesam server GUI according to the settings selected in Configuation->Support->Logging.

Features of the Graphical User Interface (GUI)

The GUI of SEP sesam 4.2 can be adjusted almost without limitations. For more information on this feature see Window

Menu Bar and Tool Bar

Menueleiste 4.0 en.jpg


In the menu bar you can find the menus File, Activities, Configuration, Window and Help. Below the menu bar you will find a toolbar for easy access to these important elements:

By activating the Docking Mode this toolbar can be moved freely and even be detached from the window.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Menu Bar and Tool Bar
User Manual
Next>>>
Activities


File

File->GUI Update gets the most recent GUI Version from the SEP sesam-Server if the current one is outdated. In this case the user name, server name and port for the RMI connection must be entered or confirmed.

GUI Update en.jpg


File->End closes open windows and returns the system to previous status. Running processes like backup and restore are not affected.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
File
User Manual
Next>>>
Configuration


Activities

Restore

With this function backup files can be restored from backup media (tape, disk etc.) onto the desired computer (client).

Rücksicherungsassistent-Filter en 3.8.jpg

In the Introduction section of this manual the administrator can find a short description of the restore procedure.


Searching by task name

Search for a certain task intended for restore by using the selection fields Task and Saved in period. If you use the wild card [*] all tasks are selected. After activating the Next button all the savesets created within the given period are shown in tabular format.


Searching by File or Path Name

This function supports the search for files or directories. Using this method backups containing these files or file patterns are detected and listed.

There is an input-field Search Pattern for filename or path as well as selection fields Task and Saved in period to narrow the search requirements. Selecting the wild card [*], selects all tasks. After activating Next button, the savesets created within the given period and matching the file patterns are shown in tabular format.


Selection of the backup
Rücksicherungsassistent-Auftraege en.jpg


Task 
Task Name (from user )
Start 
Start Time for the backup
Number 
Running number from the Backup task on the backup day
Type 
Type of backup (C = Copy, D = Differential, F = Full, I =Incremental
Media Count 
Number of used Media
Size 
Size of the Backup
Client 
Target Client
Backup Day
Date of the backup
Status 
Status of the backup

If the selection completely restore selected Task is marked, the final mask will change to Start Restore.

Otherwise the File Selector Selective Restore will be switched on.


If the backup type Diff or Incr is selected then a Generation Restore is started. This means that SEP sesam calculates all the required steps for a proper data Restore from the last full backup up until the last desired backup (Diff-, Incr-) and guides this process including media loading and recall automatically.

If the switch is deactivated then only selected backup jobs will be restored. After selecting a specific task for restore the switch Continue is selected and a window is opened Select Files to continue the Restore Process for the desired files.

Selection of the files
Rücksicherungsassistent-Dateien en.jpg

The previously selected task is visible in the upper part of this window. Below are all the directories and files of the backup task in the usual tree structure. By clicking the symbol [+] to left of the folder the symbol changes to [-] and all the folders and files inside are displayed. By clicking [-] once more the folder is closed again. You can select files or folders for the Restore by clicking the box in front of it. While doing so the absolute path of the selected folder or files is shown above in the line Position.

Note If a folder is selected all the folders and files inside it are selected aswell.

The button search opens a search function in which you can enter the names of folders/files or parts thereof as search criteria.

Ruecksicherung-Suchen en.jpg

The found folders and/or files are displayed as a list directly below. By selecting (clicking the box) folders/files and confirming with the button OK they are included in the tree structure of the above window. The button Reset can be used to reset the selection. After clicking the button Next the Start screen to start the Restore is shown.

Rücksicherungsassistent-Start en.jpg
Restore Options
Choices for the Restore
Complete Restore
All files will be restored
Restore according to the List
Selected Files will be restored.
Name
In the event the restore should be started by the scheduler. A relevant name should be entered here.
Note

As soon as a previously selected task name is changed, the system assumes that it is dealing with a planned or Scheduled Restore and will not automatically delete this task.


Drive
The drive that is used for the Restore.
Interface
Network interface through which the Restore data is sent.
Target Node
Computer on which data is to be restored. Only computers with the same platform (WNT or UNIX) are available.
Used Media
Labels of the media which contain the data to be restored.
Target
restore to original target path
datat is restored at its original location.
new Restore target
data is restored below the shown folder.
Execution options
In case that there are already files with the same name in the target directory following directions can be given:
do not overwrite existing files
orginal files are not overwritten.
overwrite existing files
orginal files are overwritten.
create new version
The file from the Backup is saved under its original name with a ~ in front of it. The original file is untouched by this. For example:

README.TXT -> ~README.TXT

Back
return to the preceding register.
Start
immediate start of the Restore.
Save
Saves the Restore task so it can be started at a later point in time.
Cancel
Cancels the entire action. The Restore Wizard is closed.

Once the Restore is started it's saved as a Restore task with the current timestamp in SEP sesam (Components->Tasks) and can be repeated though Activities->Immediate Start->Restore

Expert Options
Ruecksicherung-Expertopt en.jpg


The window Expert Options offers the option of giving the Restore additional arguments. This is helpful for special options of the SBC command. The Verbose level can be entered to adjust the trace output. Verbose levels from 0 to 6 are available and "none" can be entered aswell. The higher the number the more trace information is logged during the Restore. The SEP Sesam support can offer more options to you aswell as the additional dokumentation for special SBC clients (e.g. SBC for MS Exchange)


Register Reduction


Ruecksicherung-reduktion en.jpg


Without reduction the whole original path to every file is created when restoring with the original tree structure. With reduction the contents of the path selected with files in this path are restored in the path below it. Example (according to the screenshot above) The files from C:\Program Files\Java are to be saved as a new Restore target in the directory C:\Java. The subdirectories are also created in C:\Java.

Register Filter

Ruecksicherung-filter en.jpg


The register Filter can be used to only restore data that fits the filter criteria. The filter uses the regular wildcards ('*' and '?') for this, e.g. *.doc only restores files with the ending *.doc.

Warning
the filtering is performed at the client i.e. all the files are sent over the network first. This function is especially useful if no LIS file is available to run a selective Restore.

Register Pre/Post

Ruecksicherung-prepost en.jpg

The pre- and post-actions can be switched on and off globaly with the register 'Pre/Post'. Following four options can be used:

Execute pre
the commands from the pre interface are performed.
Start Restore in spite of pre error
usually, the following Restore is not started if the pre commands don't work properly. This can be forced here.
Execute post
the commands from the post interface are performed.
Start Restore in spite of post error
if the Restore did not run properly the execution of post commands can be forced here (e.g. booting of a databank)

Register EOL

Ruecksicherung-eol en.jpg

Restore tasks are kept for a certain time after they've been executed (e.g. for later reuse). If a task is to be created as a template this time should be set high accordingly. Setting it to '0' means infinite i.e. unlimited lifetime.

The button Apply saved all your adjustments. By comfirming with the Ok button all the adjustments are saved and the window is closed. Cancel closes the 'Expert" window.

Immediate Start

Immediate Start Backup

Immediately starts a backup process by inserting it into the event calendar at the current time.

Immediate Start Restore

Immediately restarts a restore task already configured through the restore wizard.

Immediate Start Migration

Shows the configuration dialog to select an existing migration task. It is possible to change a migration task and execute the task immediately by pressing the button Start. You can also create a new migration task and store it under a different name. The configuration of a migration task is described in the chapter Migration tasks.

Immediate Start Media Action

Immediately starts a media event by inserting it into the event calendar at the current time.

MedienInitNew en 3.8.jpg


You can choose from four different media actions:

Initializing
A medium is initialized for backup. This means that the tape label will be overwritten. Existing information on that tape will be deleted. A media event prepares that medium of the selected pool to be used for the backup. Exisiting data on that tape will be deleted during the new initialization.
Readability check
The readability check allows frequent tests of used media. This feature is under license.
Close tape
This will close the tape which means the tape is blocked until the defined EOL (End-Of-Lifetime) is reached. The tape is then blocked no matter if the tape is full or not.
Archive adjustment


Sequence Control
Priority 
see at Prioritization of events
Blocking date 
this event just works as a block for other media events in the same media pool, see Blocking events


Execution parameter 
Media Pool 
Used media pool
Drive 
You can define optionally if a specific drive should execute this event. If you don't make a selection the SEP sesam server decides what drive will be used.
Drive group 
A view box that shows which drive group belongs to the media pool.
Media 
If selected this medium will be used. If you leave the field empty the next medium with the oldest EOL is used.
Immediate Start Command

Immediately starts a command event by inserting it into the event calendar at the current time.

Additional guidelines for appropriate command events can be found in the Administration Manual.


Immediatestartcommand 4.0 en.jpg


Name
Run without Names
Command
Command to be executed
Prio
Run without priority, therefore always
User  
User name on the client under which this task will be recorded.
Client
Server/Workstation where the command should be executed
Start_Time
Entry in the calendar. This can be changed ( Delays, etc. )
Command Selection Commandselection 4.0.jpg 
opens a window for selection of previously established task.


Sofortbefehlauswahl en.jpg

Restart of Backups

All failed backups of a SEP sesam backup day can be restarted in this window.


Sicherungennachstarten en.jpg


Sesam day
select a SEP sesam backup day
Client
select the client you wish to see
Table
Restart
activates restart of a backup
Server
on MasterSesam only. This shows information from other SEP sesam servers
Status
reason of error
Task
name of the backup task
Start time
Start time of the failed backup
Type
backup type (F=Full, D=Differential, I=Incremental, C=Copy)
Count
number of executions of this task during backup day
Button +
to select all tasks
Button -
to deselct all tasks
Graph
progress bar
start time
New start time for the backup
Button Start
starts selected backup tasks at the specified time
Button Cancel
no action and return to the start screen

Next to the Buttons + and - the user can select Tasks in other ways: With a Mouse_click the choice of a Table column can be reversed. Also, with more mouse clicks using Ctrl + Mouse_Click a selection and with Space_Bar (Space) redirect is possible. Multiple lines can be selected using Shift + Key Up or Down .


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Activities
User Manual
Next>>>
Window


Configuration

The following functions are available by clicking the Configuration button.

Konfiguration 4.0 en.jpg


Defaults

Default values for status filters, the current messages window and online help can be set here.

Current Messages

In Current Messages, defaults for the bottom information window are set.


CurrMessages 36en.jpg


Help

In the register Help you can see that the online help is set to the user manual on the SEP AG Wiki. If the GUI client has no internet access you can copy the user manual to local storage and set a link to the local help file by using the option above. With the button search you can select the local HTML site and check the access by using the button test it.


ConfigHelp 36en.jpg


Extras


ConfigExtras 38en.jpg


The following settings can be activated in Extras:

Turn off Warning Ticker for 30 Day Test or Update expiration

Switches the ticker notifying the user of pending expiration of updates off. Permissions appear off. This will be reset when a new update is installed. If there is no update permission this Ticker never appears.

Allow the selection of stopped/interrupted Backups for the Restore Wizared

Makes it possible to select incomplete, broken, interrupted backups for the Restore Wizard. The default is not to allow this selection.


User Selection of Disk Group Interfaces


Konfigurationdefault en.jpg


Here a user specific interface can be set for each disk drive group (Default Interface). A selection here will override any setting previously established.

Retention periods


ConfigKeepTime 36en.jpg


Sesam Logs
The SEP sesam log files are kept for 7 days by default. You can adjust this retention time as you need.
Readability Check Logs
Retention time for readability check log files (standard: 3.999 days)
Calendar sheet entries
The default retention time for old calendar sheet entries is 35 days.


Settings

The register Settings is usually not shown, only when the trace (de-bug) level is increased should it be displayed. You will see internal GUI settings in a table.


Konfigurationeinstellungen en.jpg

Media Types

Listing of all media-types defined in 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)- can be neither erased nor changed.


Medientypen en.jpg


Media-type
Sesam internal identification of the media type
Drive-type
Sesam internal drive types
Capacity
Storage capacity of an allowed combination media / drive


Allowed Media-types
Media-type Description
DISK_ Medien auf verzeichnisorientierten Speichergeräten ( Festplatte, Diskette, auch virtuell etc. )
DAT 4mm Technik ( Digital Audio Tapes )
DLT 1/2 Zoll Technik
EXA Exabyte 8mm Technik
LTO LTO-Technik
SLR QIC-Technik
Drive-type
Drive-type Generic Drive-type
DISK_CHNG DISK
DISK_HARD DISK
AIT AIT
DLT DLT
SDLT DLT
DAT DAT
DDS DAT
EXA EXA1
QIC QIC
SLR QIC
LTO LTO
VXA EXA2


Newmediatype 4.0 en.jpg


New type designations for media and drives can be created or new combinations can be derived from existing ones.


Media Management

There are no general settings for media handling available anymore. You can set up the Mediapool behaviour directly at each Mediapool ( see Tab Options at mediapool).

Remote Server

This option is used for the server administration of the Master GUI. It is possible to both configure or remove SEP sesam servers or add new servers to the backup tree.


Note

The menu option is only available in the SEP sesam version Master Sesam.


Remoteserver en.jpg


Server Name
Name of additional SEP sesam server in the network
Connection
Server is on the network (green = ON, red = Broken, gray = OFF)
Operating System  
OS of the server
GUI Build
GUI-Version
Type
Connection type between GUI and kernel
Operating System
OS of the SEP sesam server

The Master GUI allows the administrator control of all SEP sesam servers and clients.


Newremoteserver 4.0 en.jpg


When entering a new server into the SEP sesam backup scheduler there are additional parameters which must be set. The values are preset with default settings.

Server name 
Name of the SEP sesam
Connection 
Switch ON or OFF
DB-Name 
Name of the SEP sesam internal database
DB-Port 
Port number for the database connection
RMI-Port 
Port number for client-server connecton
Comment  
Optional comment by the user


User Permissions

Userpermissions 4.0 en.jpg

In User Permissions you can configure the user authorization. Options are 'Admin', 'Operator' and 'Restore'. 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.

Newuserpermission 4.0 en.jpg

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

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

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

Interfaces

User interfaces are small procedures of the operating system interpreter which can be programmed by the user. SEP sesam starts these procedures with certain parameters on certain events but is not concerned with what these procedures do. Only the PRE/POST-interface can have an effect on the execution of backups. These programs should not run for too long since they can delay the backup.

Templates for these procedures are delivered during the installation in the SEP sesam directory <SESAM_ROOT>/skel/templates. To activate such an interface its corresponding template file must be copied to the directory <SESAM_ROOT>/bin/sesam - it is only active there (at the client). Having selected a client the user can modify the templates to his needs within a text editor window.

As default, the Sesam interfaces send messages by Email if the Email configuration is set.

Sesam offers the following interfaces: Pre-, Post-, Alarm-, Notify-, and the Disaster interface.


Editpre en.jpg


After selecting the target client the administrator can use a text editor window to create a master for other clients. This can be used to set up other clients in a similar manner. 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


Editpre02 en.jpg


PRE- Interface

Before a backup begins the user can specify several special actions that will be executed before and during the backup activity. For example, the system can generate messages notifying the user that the backup has or has not been completed successfully. You can enter end/start programs commands or you can have the system execute preparatory actions in the databases (i.e. Stop Database) you plan to backup. These actions can be programmed within the PRE-interface.

POST- Interface

Having finished the backup data transfer some special actions might also be needed (e.g. 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 authorised personnel.

Hint Do not use commands which require input from the user (OK-buttons etc.). Such commands may cause interruption of backups during the night.

Notify- Interface

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

Disaster- Interface

A disaster is described as a system failure, disk drive failure or other severe action that has occurred and makes the access to current data impossible. In this event the SEP sesam backup-server data is used to recover the system to a working state. To recover from this catastrophic event, SEP sesam provides a disaster interface.

The concept is as follows:

  • During the normal backup procedure the SEP sesam backup server also saves its own data.
  • Meta data relating to the various backups are copied to another system and are available for restore via SEP sesam in the event of a system failure or major data loss.

The last known 'good' copy of data is selected and set to the Restore Wizard.

After the installation of SEP sesam the file ID /var/skel/templates/sm_disaster (sm_disaster.cmd in Windows) can be copied by the user to ID /bin/sesam/sm_disaster ( sm_disaster.cmd ) and modified in any way.


This procedure is executed by using all backups containing DISASTER or SESAM delivering 2 arguments:

  • the label of the currently used media
  • the complete restore command, with which the data can be restored from the saveset.

The Disaster Strategy is implemented as follows:

  • The user sets up at least one backup with the name SESAM_BACKUP. This will back up the var-directory of Sesam which includes all listings, log files, database, and INI-files.
  • Run this backup daily in either COPY or FULL mode.
  • The user programs sm_disaster(.cmd) so that the contents of both input arguments are copied from the Sesam computer to pre-defined locations on another computer (Emails, copies of files, Diskettes, etc.) Along with this the information about the last disaster backup of SEP sesam are stored.

In case of emergency the following steps must be executed after the computer is restored:

  • Reinstall SEP sesam from the distribution kit
  • Identify the defined location containing the last disaster backup of SEP sesam and copy the restore command in a procedure file e.g. sm_disas.cmd
  • Load the specific media into the drive and start sm_disas.cmd


Example: The metadata of the disaster interface will appear as follows: SESAM_00003 d:/su/var NULL sbc -r -l full -o over -S softnt6:11001 -d SMS:Tape0 -t SESAM_00003:3 -s SC20020710200512 -n 5 -R /

SESAM_00003 is the media SC20020710200512 is the saveset on the media sbc -r ... is the restore command

Disaster-Recovery for Windows

Pre-conditions:

  • Windows 2000 Installation with active net connection
  • Active SEP sesam
  • SBC from version 2.2 A3

Windows 2000 Server / Windows 2000 Server with Active Directory

  • Backup
  1. Create an All backup-task (e.g. DISASTER_ALL with source all)
  2. Create a Registry backup-task (e.g. DISASTER_REG with source registry)
  3. Create a System State backup-task (e.g. DISASTER_SYS with source system_state)
  • Restore
  1. Boot in directory services restore mode
  2. Restore of the All backup
  3. Restore of the Registry backup
  4. Reboot in directory services restore mode
  5. Restore of the System State backup
  6. Reboot


Windows 2000 Professional

  • Backup


  1. Create an All backup-task ( e.g. DISASTER_ALL with source all )
  2. Create a System State backup-task ( e.g. DISASTER_SYS with source system_state )


  • Restore


  1. Restore of the All backup
  2. Restore of the System State backup
  3. Reboot

Support

E-Mail Settings
Email 4.0 en.jpg


By clicking Create New the following window is opened:

Emailaccount 4.0 en.jpg
  • Account: Name of account (mandatory)
  • Customer: Name of customer
  • E-mail Address: Mail Sender
  • SMTP Server: Name or IP-address of the outgoing mail server.
  • SMTP user: User name for SMTP server
  • Password: Password for the Mail Server. Necessary if SMTP Server requires authentication
  • SMTP port:
  • Recipient: Address of recipient
  • CC: Address for copy of the email
  • BCC: Address for copy of the email


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

Protocols
Logging 36en.jpg


Here the scope of the protocolling can be set in the lower window. Under normal conditions 'Info' level is set. For support reasons 'Debug' level can temporarily be set creating a more detailed output.



Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Configuration
User Manual
Next>>>
Help


Window

By clicking Window in the menu bar you get the following options:

Fenster 4.0 en.jpg


In Manage Layouts you can find the Window manager:

Fenstermanager 4.0 en.jpg


Here you can save and manage layouts. You can also activate/deactivate the Docking Mode here. Once the option is deactivated all window positions are fixed.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Window
User Manual
Next>>>
Components


Help

When clicking Online Manual SEP sesam tries to open the online version of the SEP sesam wiki homepage. For this the client has to be connected to the internet and a web browser has to be installed.

Under Online Support the user can get in contact with support via email, i.e. send selected listings and protocols. It's important that a valid email account is configured under Configuration->Support->E-Mail Settings which can be chosen in the dialog shown below.


Emailsenden 4.0 en.jpg


The selection of the listings and protocols is managed in a sub-dialog which appears by clicking the button Loggings.


ListingsProts 36en.jpg

Under License Info the local name of the computer and the TCP/IP adress are shown as determined by the licencing-module. This information is used to build a SEP sesam license. In addition, the expiration dates (timeout) with respect to license and upgrade validity and all licensed components are shown. Also the license info shows the amount of licensed components which are currently in use.


LizenzInfo en 3.8.jpg


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


AboutSesam en 3.8.jpg

Components

Selection Components 4.2 en.jpg


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Components
User Manual
Next>>>
DataStores


Topology

The SEP sesam backup environment including the hardware, computers, backup devices, etc is referred to as Topology .

These interconnected computers (clients and servers) can be grouped into locations and sub-locations as well as the storage devices (loaders, drives ) that are available for SEP sesam locally or attached to clients (Remote Device).

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.

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.


GUITopologie 4.0 en.jpg


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.


Server Properties

Remoteserver 4.0 en.jpg


Server Name  
Name of the server in the network
Connection  
On (green) / Off (grey) / Broken (red)
Operating System  
of the server
DB name  
Name of database on the server
DB port  
Port of the socket connection to the remote DB
RMI port  
Port of the socket connection to the remote GUI
Comment  
User comment

Note The parameters of the server cannot be edited here.

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.


Newlocation 4.0 en.jpg


Name
Name of the location
in
Superordinated location (not editable)
Description
More exact description of the location
Contact
Contact person at this location
Notes
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 screen shot shows the input fields and functions of clients. Note: these options are different when the client is created and when the client is selected and edited. Once a client is added its name cannot be edited. If its name is incorrect or not resolvable in the network the cilent has to be deleted and added again.


Clientproperties 4.2 en.jpg


Location  
Predefined location. A client always has to be assigned to a location.
Operating System 
Enter the operating system of the client you want to backup. If the right one isn't on the list choose a similar one.
Access Mode  
Select the access mode for the server-client communication.
  • CTRL: It is the default setting
  • SMSSH: The SEP sesam brings its own SSH based control communication with the new version (NEW in version 4.2.2.x) on Linux and Windows. See also here
  • PROXY: Es besteht kein direkter Remote-Zugriff auf diesen Backup Client. Der Datentransfer erfolgt über die Protokolle des jeweiligen Software Anbieters, die Sicherung erfolgt über den anzugebenden DataMover. Unterstützte DataMover Protokolle: vSphere (vCenter Server), Citrix Xen Server, NetApp und Novell SMS für NetWare 5.1/6.0/6.5.
  • 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 Message 
The most recent system state (e.g. communication error during client creation).
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 because otherwise the connection back to the SEP sesam server fails. The network protocols for the data transfer can be set by using the common prefixes ftp:// (default), http:// or https://. In the backup tasks the defined interfaces may be chosen for the data transfer.
Note If several interfaces are entered separate them with a return or a blank.
SBC Version 
This field shows the SBC (SEP sesam Backup Client) version of the installation.
Locked for backups
If a client needs to be excluded from the backup plan for technical or other reasons you can deactivate it here.
Note: If this switch is set the client can no longer be backed up until the setting is removed.
Client is a vCenter Server
At a Windows client there is a possibility, that this host work also as VMware vCenter Server. Then the check box has to be activated and insert the correct values in the fields of the additional page.

Firewalls

Client-Options 4.2 en.jpg

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 Sesam is to configure the service on the client sm.ini to this port. In this field you have tell the 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.
Wake on LAN
For more information see the HowTo
VM Parameter
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

If you are trying to backup an OES-NetWare or a OES-Linux client the SEP sesam data mover connects to the TSA provided by Novell. To communicate with the various TSA's you will need the following information.


Netwareaccess en.jpg


User  
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 sesam/Novell client with the normal base software patches is installed. The sesam-Novell client is needed to start the communication between the SEP sesam Server and the running TSA. This means that the sesam-Novell client can be installed on any Linux computer with Novell Storage Management Services (SMS). The only requirement is that it has either the SEP sesam client or server software installed properly. The resolved DNS sesam client or server will then be entered as the data mover. In the event that specialized backup methods are used the settings will be required to be entered in the tabs within the masks and they must be visible to the SysAdm.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Topology
User Manual
Next>>>
Loader


DataStores

Until now media types for disk backups (DiskHard and DiskChange) were based on the historic media concept of tape backups. This means a media pool based on these media types has to be separated into logical media.

From Sesam version 4.0.3.x disk backups should be save to the Sesam DataStore. With it the defined disks (partitions) are managed as a whole. Using Sesam DataStore provide several new functions and features.

DataStore features

  • SEP sesam still backs primary up to a mediapool. Now Backup to disk based on one or several Sesam DataStores.
  • A DataStore doesn't have a traditional media structure. Data will be written in dynamically managed data areas.
  • When a backup writes a DataStore full the saveset will not splitted. In this case the backup breaks. This behaviour you have to regard during the planning of DataStore dimensioning (see Using recommendations).
  • The lock time (EOL) will still defined on the mediapool. On backup onto a DataStore these lock times are valid on the backup saveset directly not on a medium or data area anymore. This means only the space for the saveset will be locked on disk.
  • DataStore space will be managed on partition level, means the determination of the fill rate on filesystem level is too time-consuming and on big partition not useful presentable.
  • During DataStore configuration all values (capacity and watermarks) will specified by negative values. These values define the space which should be free on DataStore (partition).
  • When you set up the low watermark (LWM) less than zero (LWM<0) a saveset hold-back time longer than the requested off-time (EOL) can be reached. For that the DataStore has to calculate big enough.
  • A DataStore purge process will be triggered by different events.
  • On using a mediapool with more than one DataStores the backups will dynamically and evenly distributed by Sesam queue manager (balancing).
  • With the high watermark (HWM) and low watermark (LWM) the DataStore saturation can be optimized.
  • If HWM cannot be undershot during a purge process an event will be triggered by SEP sesam alarm interface. By default an email will be sent when the Sesam alarm interface is activated and email notification on SEP sesam server is configured.

Using recommendations

  • DataStore volume sizing and occupancy will be managed on partition level. You shouldn't store no other data than the Sesam backup data.
  • The DataStore should have the triple maximum full backup size of the planned backups hence the watermarks can work automatically and dynamically.
  • It could be possibly necessary to scale the DataStore bigger than three times of the max size when a longer hold-back time is stipulated or very big saveset will be stored.
  • The design should run in the direction, that ...
    • ... between Capacity and HWM a complete full backup should have enough space.
    • ... an another full backup should have space between HWM and LWM.
    • ... a third full inside the LWM area.
  • A virtual drive can handle up to 64 simultaneously backups (channels) to store the data onto a Sesam DataStore (depends on SEP sesam version). When it's necessary to backup more than these channels (possible from SEP sesam server premium edition) only then you should add an another drive to the DataStore.
  • Because a backup which filled the DataStore completely won't be split but the backup will break you make sure how the propotion between the DataStore size and the size of the biggest backup task. E.g. a DataStore will defined with 3 TB whereas the biggest saveset is already 2 TB, then with an EOL=1 a triple DataStore size can even to small to allow the watermarks work properly. In this case it could recommended that the DataStore size should designed bigger.

Restrictions

  • When a mediapool should use more than one Datastore, all DataStores have to connect to the same Sesam Device Server (IP host). An operation with one mediapool serves network ditributed DataStores will currently not sopprted.

Function

In a classic media pool based on DiskHard the directory of the storage space is defined in the media pool.


DataStore Principle 403b.jpg


With DataStore this definition happens on the drive. As shown in the illustration, a media pool still points to a drive group. Only now one or more DataStores are set in between as an additional level. The connection of a DataStore to the drive is static.

Several DataStores are only needed in a media pool if a media pool is supposed to use the data of several disk partitions. In this case all drives of the DataStores of a mediapool must be part of the same drive group. This ensures that the SEP sesam queue manager can distribute the backups on this media pool on all DataStores (Balancing).

The disk space usage management of the DataStore only uses operating system functions of partitions. This means that several DataStores can be set up on a partition, however every DataStore sees the values of the other partitions when checking the partition allocation. This means that the DataStores obstruct each other. It is therefore recommended that you only use one DataStore for each hard disk partition.

Watermarks and Purge

So-called watermarks are available for managing the disk space usage. The High Watermark (HWM) defines how full a DataStore can get until a Purge deletes obsolete files (EOL free). The Low Watermark (LWM) defines how much of the EOL-free files can be deleted from the DataStore. If a LWM=0 is set, all EOL-free savesets are physically removed from the DataStore regardless the filler loading. This value can be used to control how much storage space is made available for files with expired EOLs in the DataStore. This way a data history that exceeds a necessary minimum can be provided on disk. SEP sesam always deletes the oldest savesets first.


DataStore Watermarks-Purge 403b.jpg


Events that lead to a Purge in a DataStore:

  • New day
  • After sharing the drive of the DataStore after a backup
  • Manual Purge in the GUI

Instructions

I. How to set up a DataStore

II. How to use a DataStore

III. How to administer a DataStore

IV. How to maintain a DataStore

V. How to delete a DataStore


DataStore GUI-View 403en.jpg


The column value of the Sesam DataStore table contain following values:

Capacity
The partition size added this value the sesam use the result size of the partition for backups.
Filled
How much data the Sesam has already written.
High Water Mark
High watermark treshold
Low Water Mark
Low watermark treshold
Total
Partition capacity where the Sesam DataStore stores its data. This Size is the result of a operating system request.
Used
So much data occupy space on that partition. (Not only the Sesam data - what the Sesam stored, see the column filled).
Free
Free size of the partition on which the Sesam DataStore is configured.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
DataStores
User Manual
Next>>>
Drives


Loader

Loaders are devices composed of drive(s), a magazine with slots for media and a robotic mechanism that moves media between the slots, drives and a potentially available insert-eject port. In most cases, this insert-eject port is a conveyor belt moving the cassettes into/out of the loader. There is no dependency in SEP sesam to use any manufacturers devices or device types. A list of supported hardware is available at Supported Storage Hardware.

Loading of media is defined as the movement of a cassette from the magazine into a drive, unloading is the opposite. Loaders enable a fully automated backup system during night or weekends.

The menu item Loaders shows the configured loaders and the drives within them and offers the respective tools you will need to configure your loader.


Lader 4.0 en.jpg


Properties Loader and New Loader

The configuration (addition) of storage hardware is automatic (local) so long as the newly added hardware is supported and recognized by the operating system (listed in the O/S device driver directory). Adding other loaders (e.g. for remote devices) is possible at any time.


Loader 4.0 en.jpg


Attention

On Windows use the device name like Changer0. On Linux also use the device file or data, e.g. /dev/sg2.


Device  
SCSI device description of the loader
  • Windows:

The device name can be entered using the "sesam loader utility" (slu) as long as the drivers have been installed properly. Use the following command:

<SESAM_BIN>\sesam\slu.exe scan


Now, all attached SCSI devices will be listed.

Example output:

ID=0000 other:  WDC WD3000JD-55KLB0 (HardDisk)
ID=3000 other:  TSSTcorp DVD-ROM SH-D162C (CdRom0)
ID=4030 Tape:   Quantum DLT4000         D67E (Tape0)
ID=4031 Loader: Quantum 1x8             E456 (Changer0)

The displayed device name must now be entered at "Device (SCSI-ID)".

  • Linux:

The required data file for Linux can also be determined using the command:

<SESAM_BIN>/sesam/slu scan 

Example output:

ID=0000 other:   ATA      ST380013AS
ID=1000 other:   TOSHIBA  ODD-DVD SD-M1802
ID=7040 Tape:    Quantum  DLT4000          D67E (/dev/nst0)
ID=7050 Tape:    Quantum  DLT4000          D67E (/dev/nst1)
ID=7060 Loader:  HP       C1194F           1.04 (/dev/sg4)
STATUS=SUCCESS MSG="OK"

When using Linux you will need to enter the data file at "Device (SCSI-ID)".


Device Server  
Remote Device (Server) where the loader is installed

The Remote Device or the Remote Device Server refers to the server where the Auto-Tape-Loader is connected. In smaller environments you would normally install the Auto-Loader or Disk array directly on the SEP sesam Server. You would use the Remote Device (Server) in more complex dbackup environment. The backup stream follows to the Remote Device (Server) instead of to the SEP sesam server (Master Server).

Type  
Manufacturer
Ctrl  
Loader control with sesam loader utility SLU
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).


Barcode  
Select yes/no depending on whether the loader has a barcode reader or not
Automat. Unload Function
Select yes/no

Almost all autoloaders and libraries allow explicit commands to transport tapes to and from the loader mechanism. Therefore you will most often select 'no' in the SEP sesam GUI and allow the manufacturer's drive settings to perform as designed.


Virtual Loader (VTL)

Backup designs and concepts from DISK to DISK or from DISK to DISK to TAPE necessitate a disk based storage area. This storage area is handled by SEP sesam as a Virtual Tape Libary (VTL). The VTL controls all DISK-HARD Drives. DISK drives on Remote Device Servers are controlled using Loader 0.

A VTL can be created in different storage areas using the available data systems ( NFS, NTFS, ext3, ...). Special hardware is not required when displaying multiple virtual drives, and can therefore allow the installation and use of more lesser cost devices.

Device         SCSI device identification of loader (./bin/sesam/sm_slu scan shows the descriptions to use)
Tape Server    Client to which the loader is SCSI-connected
Type           Manufacturer identification
Ctrl           Loader-control using Sesam Loader Utility SLU
Slots          number of slots in the magazine
Barcode        select yes/no depending on whether the loader has a bar code reader
Autom.Unload   The drives of the loader unload automatically when the robot moves the media.
               If not then the drive must be opened with a special command (depends on the loader type) before   
               the robot's movement 


Loader 0 has a special designation. It is the so-called virtual loader, i.e. it does not exist physically but is used exclusively for the "'movement"' of virtual DISK-media. Since DISK_HARD-media are virtual (directories on disks) they do need a virtual loader.

Contents

Loader-content en.jpg


This view shows a symbolic representation of the loader. It is updated with every cycle so that it always shows the current status. On the left you see the cassette with slots, next to it is the arm or selecting device (changer), above is the drive (s), and finally at the bottom is the exit port. Most often only a portion of the autoloader media is changed, i.e. for very large tape libraries only a portion of the media will be reserved for SEP sesam. The user/administrator has the option to limit the archive adjustment (Cassette Adjustment, Library Sync) to specific loader areas. If the media have bar code labels this is taken into account for the backup process. Direct verification of the media label is possible.

The archive adjustment (Cassette Adjustment, Library Sync) can also occur at the same time an inventory of the loader's tapes is initiated. The user thus obtains an overview of the tapes in the loader without regard to which pool (Storage Pool) they have been assigned/reassigned.

Functions
Legend  
explains the VTL color coding
Laderlegende en.jpg


Change view  
changes icon size for the selected cassettes in the slots


Laderinhaltgross en.jpg


Barcode as label 
Instead of the cassette written label the bar code label is used (if available).
Archive Adjustment  
Cassette adjustment; Library sync between a loader magazine and the SEP sesam database (Media Archive)

Archive Adjustment

Archivabgleich en 3.8.jpg


Media Pool  
Select a media pool where you want to perform the archive adjustment - All media is shown regardless of the pool selected
Storagepool  
if the selected media pool has storagepools pools assigned to it you can select them here.
Drive Group  
The drive group is automatically defined via the media pool
Drive (opt.)  
optional input of a single drive
First Slot, Last Slot
Offers the possibility to limit the synchronization to a portion of the autoloader
Automatic Introduction
If unknown media (without sesam label) are found within the loader these unidentified media will be added to the specified media pool
Tape Type  
Entry of media type for automatic new media entry
Handling of unknown SEP sesam media
  • Accept without initialization - foreign sesam media, e.g. from another SEP sesam server will be entered into the new media pool

- Note: any media from a competitive manufacturer will be entered into the target mediapool 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 is written to the tape.

Check label on tape 
Every tape label is read again and verified. Bar code information is ignored.

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

Laderaktion en.jpg


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
Load via label
move tape cartridge with certain ID (e.g. S00001) into the specified drive
Unload
move tape cartridge from the specified drive back into its slot
Loader Number
selection of a defined loader
Drive Number
selection of a defined drive (within that loader)
Label
In case of "'Load via label"' instead of slot number
Start
of the corresponding action
Cancel
closes the entry mask without an action


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Loader
User Manual
Next>>>
Media pools


Drives

Drives are devices saving data onto media within, i.e. Disk - Platter, Tape - Tape cartridge. They can be connected either to a SEP sesam computer (local drive) or to other computers that can be accessed through the network (remote drive). These are normally tape devices, with removable tape cartridges. It is also possible to back up data to disk or other directory oriented devices.

According to the grouping principle of Sesam the organization in drive groups is required here as well. Even standalone drives must belong to a group.

Large auto loaders can have several internal drives which are loaded from one magazine. It is recommended that these drives are organised into one group. A backup is delegated only to this group. Sesam searches for the particular drive to be used for the backup.


Virtual Drives

In addition to offering backup to standard tape drives, SEP sesam allows the full utilization of high capacity disk drives to fully complement and support growing bandwidth availability. These are noted as Virtual Drives. SEP sesam simulates media on these drives to fully utilize the directory and file structure to enhance backup performance. For the user there is no difference, except during configuration and setup, between virtual and physical tape loaders.

Shared Drives

By using the Shared Drives option drives are designated for sharing to fully utilize newer Network technologies, e.g. SAN's, which allows the disks to be available to multiple servers at any time. A physical drive can be seen by any number of servers and can likewise be used by the relevant systems to store data. In this example, Shared Drives can only be written to by one client at a time as opposed to standard drive configurations. Parallel backups from separate clients are not possible. SEP sesam Shared Drives uses specific drive identifiers to monitor and track the drives and the attached servers. This means that multiple drives will be labeled similarly and various backup clients will be apportioned to them. The SEPuler will perform sequential backups from the outstanding event list.


Most often large Tape Loaders and Libraries have multiple drives installed to operate media cassettes. It is recommended to organize these multiple drives into a single group. A backup will then be delegated to only this Group. SEP sesam will select which drive to use for the backup task. Scheduled backup tasks will thus be distributed to the available drives within the Drive Group. These allow the optimal resource management in the event of a drive failure. In this case SEP sesam moves the backup tasks to the remaining drives within the Group.


Laufwerke 4.0 en.jpg

Button Properties

Here the parameters of the selected element are shown and changed if necessary (Group or Drive).

New Group

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

Newdrivegroup 4.0 en.jpg
Name
An arbitrary name of the drive group
  • Please select a description/name that is easily recognizable by all administrators, support personnel and users. This can and 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

Here the new drives are configured. Each drive must be assigned to a drive group; the drive group must have been previously created.


Neueslaufwerk en 3.8.jpg


The Sesam-internal number of the drive drive-number is pre-set.

Field Loader specifies whether the drive is served by a loader or not. The loaders configured and accepted in Sesam appear in a drop down menu. When selecting "'no Loader"' sesam configures a manually operated standalone drive.

In the drop down Drive Type the type of the drive is set ( DISK-Types see below ).

In the field Device Server the client to which the drive is connected is entered. The drop down shows all clients configured in SEP sesam. The selection of the local computer creates a local connection, a remote device can also be specified.

   Configuration Example


Drive 1 and 2 are local drives

Drive 11 through 21 are remote Devices at various locations

Drive 1:

 08:00:18  I001-START   Start on Drive 1 finished
 08:00:18  Retrieves BACKUP Tasks from the SEPuler Event Calender

Drive 2:

 09:08:58  Automatic Backup TEST_BACKUP finished
 09:10:39   

Drive 11:

 09:05:57  Automatic Backup TEST_BACKUP finished
 09:07:37   

Drive 21:

 10:32:47  Automatic Backup elektrik_orcl finished
 10:34:54   

In the event an expansion of one drive at location 1, Drive 12 will entered into the backup scheme.

Drive Name

   Freely selected or specified and if it is a shared drive within a SAN it must be the same for all client shared drives
   e.g. SAN-Drive-LUN-0. 

Loader

   This specifies whether the drive is controlled by a a loader or not. 
   Loaders configured allowed as devices within SEP sesam appear in the drop-down menu. 
   'No Loader' simply means that it is a single drive and must be handled manually. 

Drive Type

   Choice of drive technology (e.g. DISK, DISK_HARD, DLT, LTO,...).
   You can specify DISK_HARD und DISK_CHNG for hard disk drives. 
   Hard drives in NAS or DAS architecture are treated as DISK_HARD. 
   DISK_CHNG is used for all backups to USP hard drives removable drives. 
   Using this configuration, e.g. a daily update is made and a new, initiated drive is used for backup. 
   (This is similar to a tape drive with daily inserted tape). 

Attention

The utilization of Removable Devices requires the insertion of the device path (Direct Option)!


Tape Server

   In the field Tape Server you need to enter the backup server or remote device server where the drive is located/connected.
   The Drop down Menu shows everything on the configured clients.
   The selection of the local/remote server either creates a local or remote device. 

Drive Group

   Every drive must be assigned to a drive group;
   the assignment of multiple drives to a similar Drive Type is possible,
   e.g. in the same auto loader with multiple drives.

Drive Number in Loader

   shows the sequence within in the Loader how drives will be used.
   The order is dependent upon the hardware vendor's numbering scheme for all installed drives.
   If the order is entered improperly SEP will not be able to access the correct drive or cassette.
   If there is only one drive in the Loader, '0' is automatically entered. 

Device (non-rewinding)

   Device Label, where the device has been configured.
   For Tape Drives the Operating System specific SCSI designation is selected, e.g. /dev/nst0 or Tape0 (see the description below) 

Info

   Status log for the drive. e.g. Read/Write Error 


Operating System Specific Designation

   * Windows: 

If the drive has been installed properly you can determine (output) the SCSI ID using the "sesam loader utility" (slu).

<SESAM_BIN>\sesam\slu.exe scan

You will now see a list all SCSI connected devices.

Example output:

ID=0000 other: WDC WD3000JD-55KLB0 (HardDisk) ID=3000 other: TSSTcorp DVD-ROM SH-D162C (CdRom0) ID=4030 Tape: Quantum DLT4000 D67E (Tape0) ID=4031 Loader: Quantum 1x8 E456 (Changer)

The visible ID must now be entered under "Device (SCSI-ID)".

   * Linux: 

You can use the same command to determine the necessary device files:

<SESAM_BIN>/sesam/slu scan


Example output:

ID=0000 other: ATA ST380013AS ID=1000 other: TOSHIBA ODD-DVD SD-M1802 ID=7040 Tape: Quantum DLT4000 D67E (/dev/nst0) ID=7050 Tape: Quantum DLT4000 D67E (/dev/nst1) ID=7060 Loader: HP C1194F 1.04 (/dev/sg4) STATUS=SUCCESS MSG="OK"

In addition to the SCSI-ID the Device File used will also be entered under "Device (SCSI-ID)" (you can test this wit the mt command).

Disk Type are automatically entered with the disk{Drive Number} (see below).


Properties - Options

   Path for Removable media 
       for Type DISK_CHNG you just enter the Device Description/Label, e.g. /dev/media/USB or F: 
   Block Size  
       for Type DISK_CHNG you need to enter the Block Size
   SMS Number  
       Shows the internally assiged SMS Number 
   SMS Channel  
       Sets the maximum number of parallel streams that can be used during backup to the backup drive

The number of data streams available for backup have also been assigned pre-determined limits based on the type of Server License in use, e.g ONE (1), Standard (5) or Advanced (unlim.)

Example of SMS Stream Limitation

   SEP sesam ONE Server License

The system has a drive and a tape drive connected. Multiple backup tasks will be started simultaneously for execution after the close of business.

   Result: The backups one after another to either the disk or tape drive, whichever has been specified.
   Only one backup stream is active.
   SEP sesam Standard Server License

The system has one disk drive and two tape drives attached. The SMS channels are connected to all drives. Multiple jobs (e.g. 10) have been set to start in one Backup Series.

   Result: Backups run parallel to either one of the drives or to both using 5 data streams depending on the desired backup path scheme.
   Either one or both tape drives can be used simultaneously but only 5 data streams are open for data transfer. 


   SEP sesam Advanced Server License

The system has one disk drive and three tape drives available for backup. The SMS channel is set to 8 datastreams per tape drive. Multiple tasks (e.g.) are started after close of business and within multiple Task Groups.

   Result: The backups run in parallel on all three drives.
   There is no limitation to the number of data streams that may be used or the SMS channels.
   The configuration and number of streams used for backup is dependent upon the system capability and throughput (pipe) available. 


In Device the operating system specific SCSI-identification of the storage device is inserted. With the command ID/bin/sesam/sm_slu scan a list of the connected SCSI-devices can be created.

On Windows-Systems the identification to be entered is displayed in brackets at the end of the row - Tape\Number\ ( from the registry ). On UNIX- and LINUX-Systems the device representation is /dev/n ( test with the mt-command suggested ).

DISK-Types are automatically entered with disk{Drive Nr} ( see below ).

New-Drive en.jpg


Drive Number
number automatically assigned by Sesam for a new drive can be changed
Loader
selection of loader which serves this drive (it is possible without loader)
Drive Type
selection of type (e.g. DISK, DISK_HARD or Types of tape devices )
Tape Server
configured Sesam client the drive is connected to
Drive Group
selection of drive group (since every drive must be assigned to a drive group)
Device
SCSI-Identification, under which the device is configured at system level
SMS-Channels
max. number of parallel backups on Sesam Multiplex Stream Tape (0 = no SMS-Drive)
Options
for type DISK_CHNG, the device directory and the block size must be entered
Saveset
statistics about backups and restores on that drive

A special case are the virtual drives already mentioned above where no physical drives and moveable media (tapes) exist.

Type DISK_HARD Configuration by selection of drive type DISK_HARD and loader 0 . The device is not editable, it is automatically disk + drive-number.

The assignment of directories to virtual media is performed through the media-pool which also specifies the maximum capacity (in KB) for this pool. This later prevents the unsupervised writing to the disk.

Type DISK_CHNG Configuration by selection of drive type DISK_CHNG and no loader or physical loader if available. The device is not editable, it is automatically named "'disk"' + drive number. In Options the path for the virtual media is defined.

Drive Action

Selecting this option from the drive-group window shows following screen.

Laufwerksaktion en.jpg


From the GUI, the following 7 actions may be taken for the selected drive. The execution and progress of the activity is shown in the lower, cyclically updated information window.


Get label
shows the label of media, currently in the drive
Mount media
the MOUNT Status is reserved for the tape media to prevent unnecessary spooling.
Dismount media
cancels the MOUNT Status.
Unload media
cancels the MOUNT Status and ejects the cassette

CAUTION After manual changes to the drive ( tapes removal or insertion), the drive must be dismounted.

Unload Media should not be confused with unloading from an Auto Loader. It means, in this case, that the tape in the drive should be released and ejected. The loader can re-acquire the tape and re-enter it into its cassette ( = Unload via Loader ).

Release Drive

   All activities will be halted 

Reconfigure Drive

   Used after a change in the drive parameters 

Release Drive Group

   All jobs running on the Drive Group are canceled.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Drives
User Manual
Next>>>
Media


Media pools

SEP sesam media are managed with distinct labels in media pools. The label consists of the pool name (e.g. DAY_, WEEK_, MONTH_) and a five-digit number that is automatically assigned to the respective media of the selected pool by SEP sesam.

Media pools are always the base for building a backup strategy. This way media pools can be created and managed for work days, weekends, certain locations, certain types, databases and more. In the GUI, go to Components->Media Pools->New Media Pool to create a new media pool.

Properties

Components-Mediapools 4.2 en.jpg


Displays the properties of the lower tree of marked objects. Depending on the marking selected you can see the properties of a server, a media pool or a media event or a media. The media pools for backup-to-disk and backup-to-tape are identified here by different symbols.


Mediapool Tab1 4.2 en.jpg


Name
Name of the new pool
Description
User comment
Drive Group
Selection of a drive group
Retention time [Days]  
Number of days for which the media are locked after initialization or last backup - from when reusable = Backup time + Pool_EOL

Readability Check

When readability test the media in blocks read, it determines the structure of the volume, ie which backups are on it, etc. Finally, the contents of the tape compared with the Sesam database. The results are shown in the log.

The readability test is started using a normal schedule with an attached media event.


Mediapool Tab2 4.2 en.jpg


Readability check limit [days]
If the value = 0, for that media pool no tests may be required. Otherwise every N days is reported readability test.
Expiration of read check overdue [days]
This is an extra status, which signals a readability test for a medium overdues. Here counts [review period] + [overdue] for the calculation status.
Repeat rate for readability check [times]

unlimited=Readability is carried out cyclically unlimited times
Execution= N x times.

Optionen

Here are more options for media management are provided. Generally, the most centrally defined in Sesam (see Media management). These settings can be set specifically for each media pool.


Mediapool Tab3 4.2 en.jpg


may use empty, foreign media
When enabled, unknown or blank media are used for backup, in case of no further medium in the certain media pool is available.
may use SPARE media
Is there a media pool that with the prefix SPARE_ in the name starts and this also includes available media. In case of no further medium in the certain media pool is available, the first medium in this pool will be used. In this case, the medium is transferred to the target pool, ie the spare pool will empty over time. Here the availability of media, check and refill if necessary, the media pool.
may use EOL free media
When activated, other media from the same media pool can also be used (general setting). By deactivation, the use of specifically defined medium can be forced.

Is no medium is available in the specific media pool, may also media from other media pools are used, provided they are EOL free and is available in the corresponding Tape Libary for the used drive. Adjustments must be made separately for each media pool:

may use media from another pool
This option specifies that the media pool may use the media of other media pools, if they were released for it.
another mediapool may use media from this pool
When activated, the media of this media pool will be released and can be used in case of failover through other media pools.

ATTENTION: For all media failover strategies is important to know that with the acquisition of a medium of a different pool, the medium is transferred in each case in the target pool and receives a name from there. Thus, it is gone in the source pool.

Storage pools

Storage pools are configured on a historic way backup-to-disk with multiple disk areas. A detailed introduction to the topic of storage pools can be found at HowTo using storagepools.
Today, the DataStore should be generally used for backup-to-disk (see Using Sesam DataStore)


new Media Event 
see Scheduling


new Media 
see Media Creation


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Media pools
User Manual
Next>>>
Tasks


Media

Media are information carriers used for backup (tapes, disks etc.). The first window shows the media-archive containing all media prepared for use with SEP sesam.


Medien 4.0 en.jpg

If you right click on a column header the following options are shown:

Mediacolumns 4.0 en.jpg


Label
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, Sesam does not use this media for backups
Backup Day
Date of the Sesam Backup day
Last Init  
Date of the last initialization of the medium
Locked until
The media is not available up to this time
(EOL = EndOfLifetime = 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 mediapool 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  
Loader that the medium is in
Slot
in loader, in which the current medium resides
Cartridge Type  
Crtridge Type of the medium
Comment
further information
Pool
to which the medium belongs to
Storage Pool
the memory area which is/will be used
Readability Test  
Date of the last readability check
Read Check Message  
Result of the last readability check
User Comment
Here you can makes notes to individual media

The Write Protection on a medium prevents the tape from being reused and helps prevent data loss. Write Protection stays in effect until it is removed manually by the user.
The EOL Write Protection however is automatically controlled by SEP sesam.


Properties Media

Mediaproperties1 4.0 en.jpg


Media Pool
Name of the media pool containing this media (uneditable)
Storage Pool  
Name of the storage pool that's being used (uneditable)
Write Protection
Selection between On/Off, the media can be overwritten or not
Backup Day
Date of the backup day (uneditable)
Locked until
The media is not available up to this time Caution: Editing possible
Drive
Drive in which the media was last used (uneditable)
Next Media
Number of next cartridge (uneditable)
Media Type
Manufacturer identification of the media (uneditable)
Loader
Number of the loader in whose magazine the media is at present (uneditable)
Slot
Number of the slot in the loader. Attention: It's better to use an archive adjustment


Ok
save the changed media parameters in the database and return to the start screen
Apply
save of the changed media parameters in the database. Entry mask can be used for further changes
Delete
removes the dataset from the archive and closes the entry mask
Cancel
no action and return to the start screen


Mediaproperties2 4.0 en.jpg


Label
Used for media identification
Barcode
Bar code on the media
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
Absolute number
Error Delta
Change in number of errors compared with the previous day
Use Count
Counts the initialisations of the tape (uneditable)
Duplication
Has this media been duplicated (yes/no, uneditable)
Comment
Additional information
User Comment  
Make additional notes


In the view Savesets all savesets stored on the media are listed. There are all columns viewable which you can see on the backup status. You can show or hide columns by press the right mouse button on the column title and select columns you like to show or hide.


MediaPropsSavesets en 3.8.jpg


Task
Task name
Date
Start time of the backup run
Count
Count of the backup executions per backup-day
Saveset
Identification of the saveset
Split
Is the saveset located on one media (no) or distributed on several media (number of parts)

Select Initialization

Here a new medium is inserted into the media-archive.


Medienneuaufnahme en.jpg


Media Pool
Select one of the configured pools
Drive
Selection of drive in which the media must be initialized (depends on the selected pool)
Media Type
selection of media type (pre-selection depends on drive type)
Get label from media
use already existing label on media
Automatically assign next number
Sesam automatically counts up label numbers for the initialized media.


The warning Utilzation of unknown SEP sesam Media alerts the user to the fact a SEP sesam tape or medium has been entered but is not entered in the 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.

Accept without initialization
Enters the media with the existing label in the sesam database. If a relevant Media Pools is not available, it will automatically create one.
Overwrite
Treats the media as empty and writes a new label on the tape.
Start
Start insertion of new media
Cancel
close screen, no insertion

Tasks

The tasks tab allows the user to set events for backups, restores and migration of data. For administration there are three tiers of operators: by Client, By Group and Backup Plan (Tree structure is on the left side).

Auftraege 4.0 en.jpg


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Tasks
User Manual
Next>>>
Tasks by groups


Tasks by Clients

Nachclients 4.0 en.jpg


The status of a backup task is shown as a colored, rectangular Icon in the right, lower corner:

  1. Icon without additional rectangle: The backup has not started, or the last backup log has been erased from the tape.
  2. Icon with a green rectangle: Last backup task status 'successful without warnings' or 'successful with warnings'.
  3. Icon with red rectangle: Last backup task 'unsuccessful/failed'.
  4. Icon with purple rectangle: Backup task stopped.


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.


TaskRightMouseMenu 36en.jpg


Right mouse menu
Clicking a backup task in the tree with the right mouse shows a 'Context Menu' with the following optons:
  • Results (only for Backup Tasks) Show the last backup for this Task, see Properties of a finished backup),
  • Immediate Start, see here
  • Properties, Shows the properties of the related Backup Task,
  • Copy (only with Backup Task),
  • Delete, see here


Select New backup task

Newbackuptask 4.0 en.jpg


Task Name
User selected identification of a backup task (use numbers, letters and underscores (_) only)
Backup Type
Type of backup (Path-Backup Standard)
Path-Backup - Files, Directories (pre-set)
Registry ( WNT )
System state ( Win2000 )
Lotus Notes
MS Exchange Server
Informix
MS SQL Server
ORACLE
ORACLE7
SAP/R3
Client
Select a computer from which the backup is to be executed
Additional TCP/IP names related to a special network route can be specified (Client interface )
Source
Disk, directory, files, which should be backed up
Multisourcing - additional sources are separated by commas


Note

When using a Netware NSS Filesystems on Linux OES the NSS Volumes are normally found below the Linux path /media/nss. You can enter multiple paths as 'Source' (Multi-Source) by separating them with a comma.


Exclude List
Excludes certain files from the backup
Comment
Additional information


Unix:

over file system limits
When this option is not selected only the data of a file system will be backed up.
Example: By selecting / as a backup source /usr will not be backed up, if /usr is on its own partition.  
Currently, this setting is only applicable to UNIX clients.
if over NFS mounted files
even if the option over file system limits is selected, NFS Mounts will not be backed up. If a backup is desired you must set this option.


Windows:

with SEP sesam Bare Metal Recover (SBMR). sometimes referred to as Bare System Recovery
setting this option field provides three further choices for SEP with SBMR. Further information regarding the configuration of SEP sesam disaster recovery can be found in SEP sesam BSR 2.1.

The selections in the upper right of the window next to the Input Fields Source and Exclude List open the Client Browser, so that the desired files and directories can be combined with a mouse click.

Apply New
'Apply New' allows the user to select further tasks, in regard to currently selected jobs.


The tab "'Options 1"' enables to select from pre-defined Pre/Post-Options for backups and restores.

For a backup/restore a selection can be made in Change Profile from pre-defined profiles and if necessary a modification can be made by clicking the checkbox.


Options 1
Newbackuptaskoptions1 4.0 en.jpg


Register Option 1 allows the choice of performing a pre-defined Pre/Post operation for backup and restore. Using this Register 'Pre/Post' actions for backup and/or recovery/restore globally can be set on or off. There are four possible choices.

Backup:

Execute pre  
Commands written in the Pre- interface will be initiated
Ignore pre error 
Forces the backup job to start in the event the Pre- commands were not executed properly.
Execute post  
Commands written the Post- interface will be performed
Ignore backup error 
Forces the Post- command to complete even if there were errors in the backup job, (e.g. this will restore a paused database even though the backup task failed).

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 though the Pre- command script was not properly executed.
Execute post  
Commands written the Post- interface will be performed
Start post in spite of post error 
Forces the completion of a restore task even though the Post- command script failed to completely execute, (e.g. this will restore a paused database even though the backup task failed)
Additional Call Arguments (Expert Options) 
Save Options  
Dependent on selected backup type and O/S platorm
Example: -v1 to set the verbose level in Protocol log
Restore Options  
same as backup options, but only in the event of a 'Restore'
Options 2
Newbackuptaskoptions2 4.0 en.jpg


Option 2 allows the selection of Encryption and Compression.

Cryptography
Encryption  
none, bf64 or aes256
Info  
Information regarding the setting/selection of a encryption key
Define new keyword 
This button is activated when either (bf64 or aes256) is selected. A mouse click (if permissions are in place) combines the next two input fields
New keyword 
Enter new keyword
Repeat new keyword
enter the new keyword manually, do not cut and paste!
Important

The password/keyword must be at least one (1) character and maximum 27 characters in length. It cannot have any special characters or spaces.


Compression (only available for Windows)
Compression  
yes or no
Novell SMS

This tab is only shown on linux clients that can work as a datamover for Novell OES clients. Since SEP sesam version 3.6 it is possible to grant every task a different logon to the eDirectory.

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.


Important
  • In Windows und Unix regular expressions are used, in NetWare file patterns are used. If you wish to suppress a specific directory you should enter the complete path name.
  • Multiple Excludes are delimited with commas.

Examples may be found in the attachment..


Backup Types

SEP sesam differentiates between path backups and special backup types.

For path backups you can use the following entries:

  • Backup of the Windows System_State is accomplished with the entry system_state as the only source of a path backup.
  • Backup of the Linux partition schema is accomplished with the entry disk_info as the only source for the path backup.
  • Windows SBMR/BSR backups also take place by selecting a path backup with corresponding activation of Backup -> SBMR/Bare Systems Recovery

Many special backup types, for example, hot backups for databases, are supported by SEP sesam. Many of the backup jobs will be initiated from within the database. In this case the jobs cannot be started from the SEPuler. These backups require command events.

For all hot backups for supported databases required the relevant online module license. The support of new special backup types is constantly under development and is continually extended to include new products. A complete description of supported applications and the requirements for them can be found in the product documentation.

Client Browser

Clientbrowser en.jpg


The client browser is an O/S independent file search engine. In the client tree structure you will see not only files and directories, but also databases, pipes, sockets, character or block devices as long as they are relevant to the backup environment. The added functionality is accessed with a right mouse click. Additionally, the overview for the resulting character string helps to prevent the overflow of lists or exclude lists.

Note

The entire character string for the selected path, starting with SEP sesam version 3.4 cannot exceed 1,000 characters. If this limit is exceeded you must switch to a manually edited backup list. Information regarding the creation of such a text file as backup source can be found in the SEP sesam FAQ.

Menu  
Appears when the right mouse button is pressed.
Expand  
The tree for this location is dynamically expanded and opened.
Show Legend  
Shows the abbreviation list in the lower window.
Restore Previous List 
Deletes the complete input string.
Accept  
Enters the chosen selection (Folder, Files) to the selected Source.

Legend


Clientlegende en.jpg


Note

When browsing a NetWare NSS in the current file system you may only select one source per task. Using a Linux path /media/nss/Full.. it may appear that you can enter multiple selections but, in fact, only the initial path will be backed up.

Delete Task

You select this tree to delete a task. Click the right mouse button and select 'delete'. Answer the following security question with 'Yes'.

New Restore Task

To create a new restore task see Restore. If you select the restore from this location certain parameters will be pre-set. A task name will also be automatically assigned.

New Migration Task

A migration is the process of copying already backed up data from one media pool (e.g. disk) to a different media pool (e.g. tape). The previously backed up files are organized in the form of savesets. These are copied identically from the source media pool to the target media pool. This way a duplication of savesets is possible. Typically these are realized in the sequence Disk-To-Disk-To-Tape (D2D2T).

As long as both media are available after the migration (in the source- or target- media pool) the saveset is duplicated. After the saveset is deleted from the source-media pool it is considered migrated. Optionally, both datasets can be accessed with the restore wizard. If only the migrated saveset exists it will be required in case of a restore.

The migration tasks are managed in a seperate menu item. In order to make SEP sesam more flexible regarding various requirements the tradition of the SEP sesam-Principle of only defining the source for tasks is broken with. Now source and target have to be defined in the new migration dialog. This enables you to immediately start a configured migration task from the GUI or attach it to a Migration Event over a schedule to start it automatically at a certein point in time.


Additionally a number of filter options were added(by task, task group or backup client, only to name a few). It is now also possible to migrate backups from a particular medium to a different pool.


MigrationTask en 3.8.jpg


Here is a descrition 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)
    • starting on medium
      Standard = "*" for all media. With this the savesets of a particular medium of the media pool can be migrated. Depending on media size a backup can range over several media. Here only backups that begin on this medium are migrated!
    • Drive
      Drive number of the drive that is used to read the data (Mandatory field)
    • Saveset
      Standard = "*" for all savesets. With this it is possible to only migrate a particular backup. The selection is made according to the saveset-ID.
  • Target
    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
    Here the timeframe of the backups that are to be migrated is defined.
    • Sesam day
      allows for the the definition of an absolute timeframe for the selection of the backups that are to be migrated. The entered date always referrs to the Sesam day.
    • relative Backup day
      from/to as a relative specification of the number of passed days. As an example, the relative timeframe 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 status
    This allows to choose to only migrate certain backups with certain statuses (successful, with warnings or partially restorable). Default is migrating all successful backups and backups with warnings.
  • Backup type
    Choice according to CFDI-Type (Copy, Full, Diff Inc): C, F, D, I and G. The CFDI-Type '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 thing, this makes sure that all relevant backups for a possible disaster recovery are available on the created media set for removal scenarios.
  • Object
    • Task
      Default = "*" for all tasks in the defined timeframe. Here, a particular task can be chosen for migration.
    • Task group
      Default = "*" for all taskt in the defined timeframe. If a task group is selected only the tasks within the defined timeframe of this task group are migrated.
    • Client
      Default = "*" for all backup clients in the defined timeframe. 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.
Notes
text field with max. 255 characters for additional input.


Buttons

Start
After activating immediate start of the migration task
create 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


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Tasks By Clients
User Manual
Next>>>
Backup Plans


Tasks by Groups

For the menu location Tasks->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 with this view. 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.


Auftraegenachgruppen en.jpg


With a right mouse click on the task group you will open a menu with the following options:

Properties Task Group

Taskgroup 4.0 en.jpg


Group Name 
Task group name
Comment  
Additional information.
Tab Assign Tasks


Auftraegezuweisen en.jpg


With the arrow > selector you can add a single and with the double-arrow >> selector you can add all available tasks to the chosen task group. You can remove tasks using the arrow selectors < und <<. The task execution sequence can be altered by selecting a task and moving it up or down with the respective arrows ↓ and ↑. The uppermost task is performed first. If you are using a 'Standard' server license the first five tasks will be be performed when the backup starts and the rest will be queued for execution as the first tasks finish.

Note

If you want to delete a task group you must first remove all tasks from the group.

Properties Task

For a description of this field see New Backup Task

New Task Group

When creating a new task group use the same dialog box as with properties. In this case the fields group name, comments and assigned tasks are empty.

New Task

When creating a new backup task use the same dialog box as with "Client Tasks", see here.

Delete Task Group

To delete a backup Group you need to select it in the backup tree, open the property window and select "Delete". Finally, click 'Yes' to complete the selection.

You can only delete "Empty" groups. If there are still tasks associated with the group, you will see the following window and the remaining tasks. These will need to be removed, reassigned or deleted before you can fully delete the task group.


Auftragsgrploeschen en.jpg


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Tasks by groups
User Manual
Next>>>
Migration Tasks


Backup Plans

The Menu item Backup Plans offers an overview of all configured tasks and their respective tasks, task groups and their connected backup events. It also offers a starting point for configuring backup events wchich branches out to Scheduling.


Sicherungsplaene 4.0 en.jpg


Properties 
shows information about the selected object
  • for single tasks see here
  • for task groups see here
  • for events see here


new backup event 
links to new Backup Event

However the beginning is adjusted to the task view: instead of new backup event in schedule ... here it says new backup event for task ... which means the task is set but the schedule can be chosen freely.

Help 
opens online help
Right Click Menu 
Context sensitive menu with the same options as for properties


Properties Event

EventProps 36en.jpg


The parameters correspond to the input lines described under new backup event.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Backup Plans
User Manual
Next>>>
Scheduling

Migration Tasks

Migrationsauftraege 4.0 en.jpg


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. For details, see How to create a migration job.

MigrationTask en 3.8.jpg


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
    Here the timeframe of the backups that are to be migrated is defined.
    • Sesam day
      allows for the the definition of an absolute timeframe for the selection of the backups that are to be migrated. The entered date always referrs to the Sesam day.
    • relative Backup day
      from/to as a relative specification of the number of passed days. As an example, the relative timeframe 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 status
    This allows to choose to only migrate certain backups with certain statuses (successful, with warnings or partially restorable). Default is migrating all successful backups and backups with warnings.
  • Backup type
    Choice according to CFDI-Type (Copy, Full, Diff Inc): C, F, D, I and G. The CFDI-Type '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 thing, this makes sure that all relevant backups for a possible disaster recovery are available on the created media set for removal scenarios.
  • Object
    • Task
      Default = "*" for all tasks in the defined timeframe. Here, a particular task can be chosen for migration.
    • Task group
      Default = "*" for all taskt in the defined timeframe. If a task group is selected only the tasks within the defined timeframe of this task group are migrated.
    • Client
      Default = "*" for all backup clients in the defined timeframe.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
  • starting on medium
    Standard = "*" for all media. With this the savesets of a particular medium of the media pool can be migrated. Depending on media size a backup can range over several media. Here only backups that begin on this medium are migrated!
  • Saveset
    Standard = "*" for all savesets. With this it is possible to only migrate a particular backup.The selection is made according to the saveset-ID.
User Comment
text field with max. 255 characters for additional input.


Buttons

Start
After activating immediate start of the migration task
create 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

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.


Zeitplanung 4.0 en.jpg


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Scheduling
User Manual
Next>>>
Events


Schedules

Zeitpläne 4.0 en.jpg

This window shows an overview of the configured schedules and the events that are connected to them. Using the buttons in the toolbar you can configure the chronology of all processes in SEP sesam. Either create a new schedule or edit an existing one. In this schedule create a new event and define its job. The job is then done at the desired time and, if needed, forwarded to the next time of execution in the calendar.

Schedule properties - create new schedule

Newschedule 4.0 en.jpg
Name 
Name of the schedule
Execution 
(De-)Activate all events that are connected to this schedule
Cycle 
Options for cyclical behaviour of a schedule
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, 3rd, 4th, last day, weekday, weekendday, Mon, Tue, Wed, Thu, Fri, Sat, Sun of the month. Optionally a positive and negative day offset is possible.
yearly 
Same as monthly; absolute and relative dates are possible
user specified (Option)
List of absolute and relative dates
Period of validity 
Range of time for the execution of a schedule. The date can be entered with a graphical calendar which pops up when clicked.
Begin 
Start time of the repetition cycle. The schedule is only valid after the day that's entered in this field. There can be no execution prior to this date.
End 
If the checkbox next to End is selected the schedule will not be executed after the date that's specified in the field. If this field isn't activated the schedule is repeated indefinitely
Start time frame
the event can only be started within this defined time frame
Start 
Designated start time of the event. The actual start time depends on the processor load of the system. Every event is forwarded into the queue at its starting time. Depending on the workload and job limit of this queue and the schedule priority the execution has to wait until jobs with higher priority are finished. For jobs with the same priority there is the FIFO rule (first in first out).
Duration 
The user can define a start time frame by setting its duration. If the execution isn't possible within this time frame the job won't be started. This is entered in days, months, and minutes.

New Backup Event

The button 'New Backup Event opens the following window:


Newbackupevent 4.0 en.jpg


Sequence Control 
Priority
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
Execution parameter 
Backup Type
Select between the backup types FULL, DIFF, INC, COPY
On/Offline
Execution parameter e.g. for database backups
Media Pool
Target for the backup files. The exact label of the target medium is determined by the last prior media event or by the end of media (EOM)
Drive Group 
the drive group that's specified in the media pool (not editable). 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.
Object 
the backup task or task group
Task 
Selection of the backup task
Task Group 
Selection of the backup task group

New Restore Task Event

The button New Restore Task Event opens the following window with the second resister selected. The first register is the same as New Schedule and is already predefined correctly.

New Restore Task Event - Source
Newrestoretaskevent 4.0 en.jpg
Restore Task 
Selection of a restore task
fix Restore 
When selecting Fix Restore the restore is executed exactly as defined in the task. The selected saveset is restored according to the set criteria and the selected files.
Selection
The restore task is used as a template. This way the backup task and the restore type (full, selective) are preset. The exact saveset however is selected dynamically by using the following entries.
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 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
Example : 2 weeks ago until now: from date = -14, to date = 0
FDI-Type 
Only savesets with the according FDI-Type are selected (Copy, Full, Diff, Inc):C, F, D, I.
Selection 
A dynamic selection of the according saveset is done for the restore. Using the options youngest or oldest the youngest or oldest saveset within the selected time frame (as per the relative backup day and other limitations).
Media Preference 
Option to limit the media that are used as the restore source (should cloned media be used?)
  • 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 limit the possible sources to specific media pools in a selection box.
Status 
Possible limitations in regard to the backup result are:
  • Successful or with warnings (Default)
  • Only successful
  • Only with warnings
  • partially restorable (cancelled backups)
New Restore Task Event - Destination parameters
Newrestoretaskeventdestination 4.0 en.jpg


Sequence control 
Priority 
see Setting Event Priorities
Blocking Date 
see Blocking Events
Execution parameter 
Backup Type 
Optionally, the backup type of the saveset can be overridden. The restore is then executed with a different backup type (usually tape backup).
On/Offline
Execution as Online/Offline restore.
Medienpool 
Not selectable.
Drive Group 
Display of the drive group that's assigned to the selected media pool.
Drive 
Selection of the target drive that's to be used. Only drives that are assigned to the drive group are selectable.
Interface 
optional indication of the interface that's to be used for the data transfer on the target node.

Migration Task Event

New Migration Task Event

As with executing the other SEP sesam tasks first you need to create a new schedule in Scheduling -> Schedules.

Then, create a new migration task event in this schedule by clicking New Migration Task Event. Select the desired migration task from the drop-down-menu in the field Name and click OK.

Migrationstermin 36de.jpg


Alter a Migration Task Event
Migrationstermin en.jpg


Migration Task 
Select a previously created Migration Task
Source
Set the parameters as in New Restore Task Event - Source
Select Parameter 
Saveset Limits 
Input for the time management:
  • View: Oldest selection: first, second, third, etc.
  • View: most recent selection: last, next to last, second next to last, etc.
Backup Day 
Limiting choices for a fixed time period : from date, to date.
Relative Backup Day 
from - to as relative input for the number of past days. Example of relative backup day: from -1 to +1 copied as a dataset, set to the previous SEP sesam day for the selected media pool.
FDI Type 
Selection possibilities in relation to CFDI type (Copy, Full, Diff, Inc): C, F, D, I and G


Selection 
Instead of the saveset selected in the restore task a dynamic selection of the saveset to be restored from the time of the restore is made. Selections are newest or oldest', i.e. the newest/oldest saveset out of the selected interval (according to the relative backup day) is selected.
Media Preference 
Limiting selection of the media to use as the restore source / Should a cloned medium be used
  • No limitation >> ' '
  • Regular medium before clone >> 'media'
  • Clone before regular medium >> 'clone'

If no clone is available the selection is ignored.

Media availability 
Limiting selection of the media to use as the restore source taking their availability inside the loader into account
  • Errors if media not available (Default) >>
  • Selection of available media >> 'available'
  • Selection of available media with EOL-block only >> 'eol-protected'
Pool Limitation 
Enables the backup source to be limited to specific mediapools by selecting a check box.
State 
Limitation according to backup results.
  • Successful or successful with warnings (Default)
  • Only successful
  • Only with warnings
  • Partially restorable (broken/stopped backup)
Destination Parameter
Essentially as in New Restore Task Event - Destination Parameter
Migrationsterminziel en.jpg


Sequence Control 
Priority 
see Setting Event Priorities
Blocking_Events 
see Blocking Events
Performance Parameter 
Backup Type 
Not Selectable.
On/Offline
Not Selectable.
Media Pool 
Enter the target Media Pool, e.g. "LTO4".
Drive Group 
Shows the chosen Media Pool from the delegated Drive Group
Drive 
Selection field for the target Drive from the Drive Group.
Interface 
optional Input of the Interface where the data transfer should occur.

New Media Event

Newmediaevent 4.0 en.jpg


Succession Parameters
Priority
Priority
Blocking event
The event is only in effect to block other media events for the pool when schedules overlap


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

The switch New Command Event opens following window:


New-Task-Event en.jpg


Parameter
Sequence Control  
Priority
Blocking event : The event is in effect (Prioritizing concept) only to block other command events with exactly the same command when schedules overlap
Execution parameter
select already defined command events
Name
Identification of the command event
Command
complete command
Client
Selection of computer, on which the command should be executed
User
pre-defined user name at the client (access restriction), which may execute this command



The switch List opens the following window:


Befehle en.jpg


New 
Set new command schedule
Change 
Change existing schedule
Copy 
Copy existing schedule
Delete 
Delete existing schedule
Save
Saves new schedule
Access restriction of command events

An 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 tasks, this must be entered/permitted at the target client.

UNIX External commands are only executed when the user name and the command are entered into the file /etc/sesam_cmdusers.allow at 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 of the client computer, in key text: HKEY_LOCAL_MACHINE/SOFTWARE/SEP Elektronik GmbH/sesam/ HKEY_LOCAL_MACHINE/SOFTWARE/SEP Elektronik GmbH/sesam/CommandEvents/user/command

command           execution
*                 all commands
specific command  this command only
cmd /c            all DOS commands ( dir, etc. )
DOS-Command       this command only


Additionally on the client computer the entry

CTRLD_Path=ID/bin/sesam;ID/bin/sms in the file

ID/var/ini/sm.ini in section [CTRLD_Server] must be extended with the directories where the desired programs reside.

Registryentry.JPG


command Run
* all Commands
Specific Commands only these
cmd /c all DOS Commands ( dir, etc. )
DOS-Commands only these


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 entered incorrectly.
  • Instead of entering the command as a key it is entered as a character string.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Schedules
User Manual
Next>>>
Calendar Sheet


Events

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


Termine 4.0 en.jpg


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Events
User Manual
Next>>>
Job State


Calendar Sheet

The calendar sheet provides an overview of all events and their current states in an hourly grid. It also provides a convenient and fast overview of what was executed on the system and what is about to run. With a mouseclick on the entries detailed information can be displayed; it corresponds to GUI->Backups->by Status.

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.


Kalenderblatt 4.0 en.jpg



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.


Kalenderblattautoupdate 4.0 en.jpg


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

Job State

Jobstatus 4.0 en.jpg


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


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Job State
User Manual
Next>>>
Restores by State


Backups by State

under Job State->Backups backup operations can be viewed historically.


Sicherungen 4.0 en.jpg

The order of the columns can be changed as needed via Drag&Drop. 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 is sorted alphabetically/chronologically. If you right-click a column header a pop-up menu appears:

Sicherungenspaltenoptionen 4.0 en.jpg


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

Sicherungenspaltenauswahl 4.0 en.jpg


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 Task 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 other view.

Note

The Control Window all Server is only visible for the SEP sesam Master Sesam. Using this option the System Administrator can select specific Sesam Servers for display and action.


State Filter

The Filter can be found on the right side of the window.

Date Range and Clients
BackupStatusFilter-Time en 3.8.jpg


Date (Sesam Date)
The definition of a daterange from / to limits the visibility of the backup history field
Filter
Client
Filters the backups specified by the client during the period
all servers
The switch is only relevant in a master environment and then used to display the backups of all servers that are managed with the master GUI.
State
BackupStatusFilter-Status en 3.8.jpg


In progress
in Queue
This task is in the queue, ie appointment started by SEPuler, however must wait until the tapedrive is available for the choosen mediapool.
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 successful
Info
System-related some files could not be backed up, ie opened files under Windows
Type
Filter Typ 4.0 en.jpg


The display of...

  • Newday can be turned on/off
  • Backups can be turned on/off
  • Media - media inits can be turned on/off
  • Migrations can be turned on/off. Therefore backups in line with a migration are displayed also here and not only in the field JobStatus/Migration. This can be useful if periodic dependencys should be compared.
  • Startup shows Sesam newdays
  • Commands shows command events
  • Groups are placeholders for grouping of single tasks and can be turned on/off
Task Name
Filter Auftrag 4.0 en.jpg


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

Properties of a finished backup

Info 1
Taskproperties1 4.0 en.jpg


Saveset 
Name of the Backup Task
Type 
Backup Type (F=Full, C=Copy, I=Incremental, D=Differential)
Media Pool 
Name of the media pool that was used for the backup
Size 
of the backup in bytes
Used Labels 
List of used media
Message 
Detailed status reports
Info 2
Taskproperties2 4.0 en.jpg
Info 3

Shows status of encryption and compression.

Taskproperties3 4.0 en.jpg
Protocol

The backup logo displays and stores the reports regarding the process of the backup.

Auftragsprotokoll en.jpg
PRE-Log
Report regarding the Pre- interface activated before the backup task started.
POST-Log
Report for the Post- interface, after the backup was finished.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Backups by State
User Manual
Next>>>
Migrations by State


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.


Ruecksicherungen 4.0 en.jpg


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
Restoreproperties1 4.0 en.jpg


Saveset 
Name of the backup job
User 
Name of the user
Size[Bytes] 
Size of the restore in bytes
Restore Type
Full 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 was successful
Info 2
Restoreproperties2 4.0 en.jpg


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
Disk Drive 
Number of the used disk drive
Backup Count 
Number of the used backup task
Start Time 
Start of the backup
End Time 
End of the backup
Target 
Path of the restore
Info 3
Restoreproperties3 4.0 en.jpg


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

Options
Passed options, e.g. higher loglevel "-v 3".
Reduction Path
Passed reduction path. e.g. "/usr/opt".
File Filter
Repeat of the optional file filter, e.g. z.B. "*.c".
Protocol

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


Ruecksichprot en.jpg


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.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Restores by State
User Manual
Next>>>
Media Actions by State


Migrations by State

Migration uses the same filters and selections as does SEP sesam backup system Filter- and Selections. The columns are similar to Restore by state.


Migrationen 4.0 en.jpg


In the true sense a migration is a grouped task to copy savesets.

Properties of a Migration

Info
MigStatusInfo 36en.jpg


Migration Task
Name of the migration job
ID
UniqueID of the task
Sesam Date
Sesam date of execution
Start Time
Start of migration
Stopzeit
End of migration
State
Displays the success of the migration

Size and Throughput are currently not displayed. On the right side information is displayed about the involved media pools, drives and filters.

Main Log
MigStatusProt 36en.jpg


The principal elements necessary for an analysis can also be seen in the migration log. At the top the select row shows the SQL-statement which selects the appropriate individual backups to copy them. In case of an error, it is useful to query the SEP sesam-database with that SQL-string. Furthermore it is logged from which media pool to which media pool a migration is done per single job which tapes are involved for every job and the size of each saveset.

Properties of a single Copy-Job to Migration

Info
MigCopyJobInfo 36en.jpg


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


Main Log
MigCopyJobProt 36en.jpg


The log of a migration copy-job is a subset of Restores by State.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Migrations by State
User Manual
Next>>>
Monitoring


Media Actions

Since SEP sesam version 3.6 there is beside the option to initialize the readability check option and the explicit close tape option (block by EOL) of a medium. Hence there is a separate view to these media actions.


Medienaktionen 4.0 en.jpg


Adjust a new medium

The status values of a new adjusted medium can beside of the table view show separately. Select the desired table item and click the button Properties.

Info 1

Mediaactionproperties1 4.0 en.jpg


Saveset
Type
Media Pool
Media Number
Size
Throughput
used labels
Message

Info2

Mediaactionproperties2 4.0 en.jpg


State
Current state of the media action
Task
Name of the task that was performed
Location
Client
Name of the device server that operated the adjustment process
Drive
The drive has operated the adjustment
Cycle Number
Start time
Adjustment has been started
Stop time
Adjustment has been finished
Source
Exclude List
Items that were excluded
Comment
Make additional notes

Readability check of a medium

You can view the details of individual media by double-clicking or selecting the medium and clicking the button.

Info 1

Readcheck 4.0 en.jpg


Action
readcheck means readability check of this medium
State
shows the state of the operation
Label
Name of the medium that was checked
Client
The device server on which the readability test took place
Start time
When did the readability check start?
Stop time
When did it end?
Message
Additional information about the state of the operation

Info 2

Readcheck2 4.0 en.jpg


ID
SEP sesam unique ID of the action
Planned for
date on which the medium was checked
Run
Total number of read checks that were performed on this medium
Prio
Priority of the action
Pool
Media pool that contains the medium
Drive
the drive that added the medium
Device
On physical drives the device ID of the operating system is diplayed. On virtual drives the SEP sesam logical drive no. is shown
Throughput
The average throughput of the entire check process
Session ID
Size
Number of the read 64kByte blocks

Protocol

ReadableTestProt 36en.jpg


The readability test protocol of a medium contains the following information:

  • When the readability check was executed
  • On which device the medium was checked
  • The SEP sesam label of the medium
  • The last time the medium was initialized
  • The read throughput every minute
  • Information of the stored savesets on the medium
  • Display all segment marks of the tape
  • State of the readability check at the end of the protocol

Monitoring

Monitoring shows all running processes/daemons as well as the status of all running disk drives.


Monitoring 4.0 en.jpg


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Monitoring
User Manual
Next>>>
Processes


Last Backup State

Letzterbackupsstatus 4.0 en.jpg

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

By right-clicking on a canceled or failed backup you get these options:

Letzterbackupstatus rechtsklick1 4.0 en.jpg

The same thing for successful backups:

Letzterbackupstatus rechtsklick2 4.0 en.jpg


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Last Backup State
User Manual
Next>>>
Monitoring Drives


Processes

Shows the status Processes/Daemons of SEP sesam.


Monitoring Prozesse 4.0 en.jpg


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

sm_main status 	

The following output appears:

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

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, using the command line, it can be restarted. In this example the rmi:

sm_main reload rmi


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Processes
User Manual
Next>>>
Logging


Drives

This shows the disk drive queue. Use the selection all (*) or one drive (select the desired drive) and conffirm the selection with the button Show. All the information for the queue is then displayed. The queue is overseen by the Queue Manger. The Queue Manger can initialize the queues in which jobs are set (submitted). However, the Queue Manager sets a Job Limit. Tasks that have reached their start times but cannot be loaded into the queue due to the Job Limit are held with status Pending.

The queues are established during the configuration of the disk drives. The SEPuler and other internal processes send their responsibilities and functions to the Queue Manager for coordination.

Monitoringlaufwerke 4.0 en.jpg

Logging

Logging 4.2 en.jpg


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.


Caution: A backup day is framed by two NEWDAY events.

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


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Logging
User Manual
Next>>>
Day Log


State

Statusprotokoll 4.0 en.jpg


Sesam creates a state log. One line is written for each backup in chronological order .

Functions:
From - To
Space of time of the log
Today, Yesterday
Shows today's i.e. yesterday's log
Help
Online help
Send
E-mails the log to your support service or any other predefined adress.
Print
Prints the log using the default printer.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
State
User Manual
Next>>>
Interface Logs


Day Log

Tagesprotokoll 4.0 en.jpg


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.

These 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 SysAdm Guide. These errors and a PuTTy copy of the log file can be sent to support@sep.de to provide detailed information.

Error Log

The error log is the subset of the entire day log. Only error messages will be printed out here.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
State
User Manual
Next>>>
Interface Logs


Day Log

Tagesprotokoll 4.0 en.jpg


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.

These 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 SysAdm Guide. These errors and a PuTTy copy of the log file can be sent to support@sep.de to provide detailed information.

Error Log

The error log is the subset of the entire day log. Only error messages will be printed out here.


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
State
User Manual
Next>>>
Appendix


Sesam Interface Logs

In this area you can check the log information of the SEP sesam server interfaces (sm_notify, sm_alarm and sm_disaster).

Notification

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

The notification center is used to dynamically send messages from the Sesam server to all open GUIs. Thereby different types of messages, so-called notifications, are send. These messages inform the user about License violations, not configured interfaces, as well as important information send via RSS Feeds.

Notification Center

Notifications can be found in our notification center either in the lower right corner of the "Current Messages Window" or by selecting "Window"->"Show Notification Center" in the Task bar.


Notification center gui 4 2 1.jpg


All messages which are visible in the notification center (see below) need a response of some kind. All "dismissed" messages will disappear from the Pending Messages list. If a message is "accepted" or "postponed", the message stays in the Pending Messages list until, in case of accepted messages, they have been "resolved", or in case of a postponed message, they have been "accepted"+"resolved" or "dismissed".

To view "accepted"+"resolved" or "dismissed" messages hit the "Show Resolved Messages" button. A second list appears showing the Resolved Messages. This list contains all messages that have already been completed. In the Resolved Messages list you can see the user who resolved the message with an optional comment that was inserted.


Notification center4 2 1.jpg

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

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:

http://notification.sepsoftware.com/

Then click on the RSS feed you are interested in:

SubscribeRSS1.png

You can either choose an application or use one of the given ones.

SubscribeRSS2 en.png

To subscribe to the RSS Feed click on Subscribe Now. In the given example the RSS Feed is subscribed to Microsoft Outlook

SubscribeRSS3 en.png

Now, if you open your Microsoft Outlook you can find the RSS Feed under RSS-Feeds

SubscribeRSS3 Outlook en.png

Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Activities
User Manual
Next>>>
Window


Configuration

The following functions are available by clicking the Configuration button.

Konfiguration 4.0 en.jpg


Defaults

Default values for status filters, the current messages window and online help can be set here.

Current Messages

In Current Messages, defaults for the bottom information window are set.


CurrMessages 36en.jpg


Help

In the register Help you can see that the online help is set to the user manual on the SEP AG Wiki. If the GUI client has no internet access you can copy the user manual to local storage and set a link to the local help file by using the option above. With the button search you can select the local HTML site and check the access by using the button test it.


ConfigHelp 36en.jpg


Extras


ConfigExtras 38en.jpg


The following settings can be activated in Extras:

Turn off Warning Ticker for 30 Day Test or Update expiration

Switches the ticker notifying the user of pending expiration of updates off. Permissions appear off. This will be reset when a new update is installed. If there is no update permission this Ticker never appears.

Allow the selection of stopped/interrupted Backups for the Restore Wizared

Makes it possible to select incomplete, broken, interrupted backups for the Restore Wizard. The default is not to allow this selection.


User Selection of Disk Group Interfaces


Konfigurationdefault en.jpg


Here a user specific interface can be set for each disk drive group (Default Interface). A selection here will override any setting previously established.

Retention periods


ConfigKeepTime 36en.jpg


Sesam Logs
The SEP sesam log files are kept for 7 days by default. You can adjust this retention time as you need.
Readability Check Logs
Retention time for readability check log files (standard: 3.999 days)
Calendar sheet entries
The default retention time for old calendar sheet entries is 35 days.


Settings

The register Settings is usually not shown, only when the trace (de-bug) level is increased should it be displayed. You will see internal GUI settings in a table.


Konfigurationeinstellungen en.jpg

Media Types

Listing of all media-types defined in 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)- can be neither erased nor changed.


Medientypen en.jpg


Media-type
Sesam internal identification of the media type
Drive-type
Sesam internal drive types
Capacity
Storage capacity of an allowed combination media / drive


Allowed Media-types
Media-type Description
DISK_ Medien auf verzeichnisorientierten Speichergeräten ( Festplatte, Diskette, auch virtuell etc. )
DAT 4mm Technik ( Digital Audio Tapes )
DLT 1/2 Zoll Technik
EXA Exabyte 8mm Technik
LTO LTO-Technik
SLR QIC-Technik
Drive-type
Drive-type Generic Drive-type
DISK_CHNG DISK
DISK_HARD DISK
AIT AIT
DLT DLT
SDLT DLT
DAT DAT
DDS DAT
EXA EXA1
QIC QIC
SLR QIC
LTO LTO
VXA EXA2


Newmediatype 4.0 en.jpg


New type designations for media and drives can be created or new combinations can be derived from existing ones.


Media Management

There are no general settings for media handling available anymore. You can set up the Mediapool behaviour directly at each Mediapool ( see Tab Options at mediapool).

Remote Server

This option is used for the server administration of the Master GUI. It is possible to both configure or remove SEP sesam servers or add new servers to the backup tree.


Note

The menu option is only available in the SEP sesam version Master Sesam.


Remoteserver en.jpg


Server Name
Name of additional SEP sesam server in the network
Connection
Server is on the network (green = ON, red = Broken, gray = OFF)
Operating System  
OS of the server
GUI Build
GUI-Version
Type
Connection type between GUI and kernel
Operating System
OS of the SEP sesam server

The Master GUI allows the administrator control of all SEP sesam servers and clients.


Newremoteserver 4.0 en.jpg


When entering a new server into the SEP sesam backup scheduler there are additional parameters which must be set. The values are preset with default settings.

Server name 
Name of the SEP sesam
Connection 
Switch ON or OFF
DB-Name 
Name of the SEP sesam internal database
DB-Port 
Port number for the database connection
RMI-Port 
Port number for client-server connecton
Comment  
Optional comment by the user


User Permissions

Userpermissions 4.0 en.jpg

In User Permissions you can configure the user authorization. Options are 'Admin', 'Operator' and 'Restore'. 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.

Newuserpermission 4.0 en.jpg

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

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

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

Interfaces

User interfaces are small procedures of the operating system interpreter which can be programmed by the user. SEP sesam starts these procedures with certain parameters on certain events but is not concerned with what these procedures do. Only the PRE/POST-interface can have an effect on the execution of backups. These programs should not run for too long since they can delay the backup.

Templates for these procedures are delivered during the installation in the SEP sesam directory <SESAM_ROOT>/skel/templates. To activate such an interface its corresponding template file must be copied to the directory <SESAM_ROOT>/bin/sesam - it is only active there (at the client). Having selected a client the user can modify the templates to his needs within a text editor window.

As default, the Sesam interfaces send messages by Email if the Email configuration is set.

Sesam offers the following interfaces: Pre-, Post-, Alarm-, Notify-, and the Disaster interface.


Editpre en.jpg


After selecting the target client the administrator can use a text editor window to create a master for other clients. This can be used to set up other clients in a similar manner. 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


Editpre02 en.jpg


PRE- Interface

Before a backup begins the user can specify several special actions that will be executed before and during the backup activity. For example, the system can generate messages notifying the user that the backup has or has not been completed successfully. You can enter end/start programs commands or you can have the system execute preparatory actions in the databases (i.e. Stop Database) you plan to backup. These actions can be programmed within the PRE-interface.

POST- Interface

Having finished the backup data transfer some special actions might also be needed (e.g. 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 authorised personnel.

Hint Do not use commands which require input from the user (OK-buttons etc.). Such commands may cause interruption of backups during the night.

Notify- Interface

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

Disaster- Interface

A disaster is described as a system failure, disk drive failure or other severe action that has occurred and makes the access to current data impossible. In this event the SEP sesam backup-server data is used to recover the system to a working state. To recover from this catastrophic event, SEP sesam provides a disaster interface.

The concept is as follows:

  • During the normal backup procedure the SEP sesam backup server also saves its own data.
  • Meta data relating to the various backups are copied to another system and are available for restore via SEP sesam in the event of a system failure or major data loss.

The last known 'good' copy of data is selected and set to the Restore Wizard.

After the installation of SEP sesam the file ID /var/skel/templates/sm_disaster (sm_disaster.cmd in Windows) can be copied by the user to ID /bin/sesam/sm_disaster ( sm_disaster.cmd ) and modified in any way.


This procedure is executed by using all backups containing DISASTER or SESAM delivering 2 arguments:

  • the label of the currently used media
  • the complete restore command, with which the data can be restored from the saveset.

The Disaster Strategy is implemented as follows:

  • The user sets up at least one backup with the name SESAM_BACKUP. This will back up the var-directory of Sesam which includes all listings, log files, database, and INI-files.
  • Run this backup daily in either COPY or FULL mode.
  • The user programs sm_disaster(.cmd) so that the contents of both input arguments are copied from the Sesam computer to pre-defined locations on another computer (Emails, copies of files, Diskettes, etc.) Along with this the information about the last disaster backup of SEP sesam are stored.

In case of emergency the following steps must be executed after the computer is restored:

  • Reinstall SEP sesam from the distribution kit
  • Identify the defined location containing the last disaster backup of SEP sesam and copy the restore command in a procedure file e.g. sm_disas.cmd
  • Load the specific media into the drive and start sm_disas.cmd


Example: The metadata of the disaster interface will appear as follows: SESAM_00003 d:/su/var NULL sbc -r -l full -o over -S softnt6:11001 -d SMS:Tape0 -t SESAM_00003:3 -s SC20020710200512 -n 5 -R /

SESAM_00003 is the media SC20020710200512 is the saveset on the media sbc -r ... is the restore command

Disaster-Recovery for Windows

Pre-conditions:

  • Windows 2000 Installation with active net connection
  • Active SEP sesam
  • SBC from version 2.2 A3

Windows 2000 Server / Windows 2000 Server with Active Directory

  • Backup
  1. Create an All backup-task (e.g. DISASTER_ALL with source all)
  2. Create a Registry backup-task (e.g. DISASTER_REG with source registry)
  3. Create a System State backup-task (e.g. DISASTER_SYS with source system_state)
  • Restore
  1. Boot in directory services restore mode
  2. Restore of the All backup
  3. Restore of the Registry backup
  4. Reboot in directory services restore mode
  5. Restore of the System State backup
  6. Reboot


Windows 2000 Professional

  • Backup


  1. Create an All backup-task ( e.g. DISASTER_ALL with source all )
  2. Create a System State backup-task ( e.g. DISASTER_SYS with source system_state )


  • Restore


  1. Restore of the All backup
  2. Restore of the System State backup
  3. Reboot

Support

E-Mail Settings
Email 4.0 en.jpg


By clicking Create New the following window is opened:

Emailaccount 4.0 en.jpg
  • Account: Name of account (mandatory)
  • Customer: Name of customer
  • E-mail Address: Mail Sender
  • SMTP Server: Name or IP-address of the outgoing mail server.
  • SMTP user: User name for SMTP server
  • Password: Password for the Mail Server. Necessary if SMTP Server requires authentication
  • SMTP port:
  • Recipient: Address of recipient
  • CC: Address for copy of the email
  • BCC: Address for copy of the email


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

Protocols
Logging 36en.jpg


Here the scope of the protocolling can be set in the lower window. Under normal conditions 'Info' level is set. For support reasons 'Debug' level can temporarily be set creating a more detailed output.


Appendix

Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Appendix
User Manual
Next>>>
Exclude with File Patterns


Exclude with Regular Expressions

Examples for exclude list:

  • Backing up '/var' without '/var/tmp' but with directory '/var/tmp1':
 \./var/tmp$
  • Backing up '/var' without any directory '*/tmp*':
 /tmp
  • Backing up source '/usr' avoiding '*.o', '*.tmp', 'a.out' and 'old*.c' files and all 'old*' directories:
 \.o$, \.tmp$, /a\.out$, /old.*\.c$, /old.*/$

  • Backing up '/usr' without '/usr/var/spool' and '/usr/var/log':
 \./usr/var/spool$, \./usr/var/log$
  • Avoid all 'syslog####.log' files:
 /syslog[0-9]*.log$


Icon archived docs.png THE CONTENT OF THIS PAGE IS OUTDATED
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
<<<Back
Exclude with Regular Expressions
User Manual


Exclude with File Patterns

An exclude with File Patterns for NetWare File System backup only allows the use of '*' (any character string) and '?' (single arbitrary character).

Examples for exclude list with file patterns:

  • Backing up '/var' without '/var/tmp' but with directory '/var/tmp1':
 ./var/tmp
  • Backing up '/var' without any directory '*/tmp*':
 /tmp*
  • Backing up source '/usr' avoiding '*.o', '*.tmp', 'a.out' and 'old*.c' files and all 'old*' directories:
 *.o, *.tmp, a.out, old*.c, /old*

  • Backing up '/usr' without '/usr/var/spool' and '/usr/var/log':
 /usr/var/spool, /usr/var/log
  • Avoid all 'syslog####.log' files:
 /syslog*.log
  • Backing up NetWare NSS Volume 'VOL1:' without 'VOL1:tmp':
 VOL1:tmp
Attention

If you want to exclude a specific path then put the entire path in the exclude list. Several excludes require a separation by commas.