Archive:User Manual 3.4 - 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 2009 by SEP AG. All rights reserved.

Any form of reproduction of the contents, in part or in total, is restricted by copyright. Any use hereof must be granted by SEP AG in writing. During compilation of this documentation SEP AG and its employees used their best effort and diligence to illustrate the functionality of SEP sesam backup software, its utilities and its interaction with other third party software products. However, SEP AG does not guarantee that all information contained herein is free of errors or omissions.

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 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 (5) data streams with our Standard Server offering up to 64 data streams with the Advance 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 mail restore.

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 (Klient 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, ie. 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

The SEP sesam principle takes into account the interaction of each component of a data backup, server, client, data store (local attached disk, NAS, SAN, USB disk drives, tapes drives, networks, firewalls, etc. After the installation of a SEP sesam server the System Administrator has full control to set up the software to fit the backup environment. This user must setup of the storage hardware, the configuration of the drive groups and drives and the initialization of media pools with the corresponding physical and/or virtual media has to be accomplished. This overriding design principle gives the administrator the ability to create a backup environment uniquely applicable to the user environment. Flexibility, Performance, Data Availability and Security are the foundations that set the framework for SEP sesam.

The SEP philosophy: Backup all the data required in the shortest possible time, secure it in the safest manner possible, restore it in the shortest window of time. Allow for recovery from an inadvertent file deletion to a full system disaster. One tool for all environments. A tall order - SEP delivers.


Sesam-Philosophy en.png


The red arrows from the media pool to the right (see figure above) shows the direct relationship of the media pools to a drive group. To that drive group, 1-N drives are assigned. Next the storage media (tapes, virtual disk media, removable media etc.) can be assigned to the appropriate media pool. The media pool is used to assign the BACKUP LOCATION. The data source is directly related to a task. By specifying the data source you determine WHAT should be backed up, nothing more. The SEP sesam SEPuler or scheduler connects the media pool to the data. This scheduled timetable specifies WHEN something should be backed up, where the data will be stored and for how long. The final choice is the type of backup to be performed. Let's call it HOW we will backup (e.g. Full, Diff, Inc backups) and we define WHERETO (Media Pool) the backup should take place. All reside in the SEPuler, the heart of the backup environment.

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 required.
  2. Define tasks (WHAT should be backed up).
  3. Define timetables (WHEN the backup takes place).
  4. Link the timetable 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.

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.

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


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

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.

<<<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 media 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 canceled
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 coincide with the actual location of the media. 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 is 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).

For this reason there is no entry for EOM, 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 mediapool should be used.

When using a single tape drive the media event is not required. By daily inserting a tape without an EOL entry SEP sesam will automatically complete the prior day's backup and (set the data protection) and will initialize the new tape. This method has the advantage that in the event of a holiday, new data will be continually written 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. In 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 Sesam or the backup will be blocked.

The GET_OLDEST strategy selects the media

  • 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 the 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 Sesam media archive database. An archive adjustment is mandatory whenever the contents of a loader carousel has been altered. This is especially true after inserting new media or used media which has not yet been registered (initialized) by SEP sesam.

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

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.

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.

<<<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 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 SEPuler finds a backup/restore task the execution of the corresponding program is initiated. Once the backup task has started, 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 to the calendar as non-recurring events.

All events in 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

System level backups are cyclical in nature. Sesam backup uses the SEPuler to create a cogent and easily maintained backup cycle.

A schedule describes the recurrence of an event and may be executed in minutes, hours, days, months or years. A schedule also allows for repetitive scheduling and absolute one-time execution.

A modification of a task may have an effect on all events within a schedule.

A schedule or task can be deactivated using either the GUI or command line.

A schedule can be used for any number of events; a particular task (Backup, Restore, etc.) can have events in several schedules. Sesam has implemented a system of priorities to prevent multiple tasks from conflicting with the execution of another task. If a daily backup is to take place at 11 p.m. on Saturday, and the weekly or monthly task is scheduled to begin at the same time, the highest priority precludes the lesser. In this case, the monthly task is flagged priority '3' and will override the weekly backup flagged '2' and the daily backup flagged '1'.

Setting Event Priorities

SEP sesam allows for complex backup event strategies by setting priorities from 1 the lowest priority to 10 the highest priority.

Within each Sesam -day the system determines if there is a similar event with a higher priority setting that has already executed or is scheduled for execution. If there is a job or task waiting to execute with a lower priority than one in the queue it is suppressed.

For certain backup tasks several schedules can be created which may overlap on certain days. An example would be a daily backup '1' set to run at 11 p.m. while a weekly backup '2' is set to run at 12 midnight. The jobs with lower priorities will be suppressed.

Schedules with priority=0 are always executed.

Similar events are arranged by the particular type:

  • BACKUP-events are similar when their tasks are equal
  • MEDIA-events are similar when their drive number or drive group are equal
  • COMMAND-events are similar when their names are equal
Schedule  Time   Prio  
DAILY     20:00   1    daily incremental
WEEKEND   18:00   2    on weekend differential
MONTHEND  21:00   3    on month end full
  • at week end WEEKEND overrides DAILY
  • at month end MONTHEND overrides DAILY
  • at coinciding weekend with month end MONTHEND overrides WEEKEND

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 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 requisite 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 Schedule).
  • A Blocking Event works only on similar/similarly named events (Switch Blocked Event within the event).


Attention

  • switching off a schedule blocks the execution of all events using this schedule (select Execute in

Schedule).

  • a blocking event has an effect on similar events only ( select blocking event in Events).

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

Example A backup event executing the task CSRC executes daily with priority 2. A second backup event has also been created for CSRC, however, it is set to run only once a year on December 24th. It is set up as a 'blocking' event, since it has been set with a priority of '9'. Hence, the daily backup with priority '2' will be suppressed.

On December 12 the priority check within SEPuler recognizes that a higher prioritized backup CSRC exists (namely the blocking event) and blocks the execution of the backup of the daily event. Upon completion, the blocking event, set to run on Dec. 12, sends a message that it was activated.

The SEP sesam backup day - NEWDAY

SEP 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. 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, which 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. 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 backup exceed the time allotment between 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 Sesam status and daily log files
  • reorganizes the Sesam database
  • Advances the calendar (SEPuler) 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 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.

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.

<<<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 backup are copied to saveset on the pre-selected media.

To speed up and simplify the restore of desired data 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

A full backup copies all source files precisely as they are. During a restore this version of the files is easily copied back from the media. Note: However, in some cases it represents a large amount of data. And may require an extended period to restore all files.

A differential backup copies only those files that have been changed or altered after the latest full backup. Since a smaller amount of files must be transferred, the backup time is shorter. In order to restore the whole data source, one must first copy back the files from the full backup before copying those of the differential one. This is a two-step process which is automatically scheduled and started by the Generation Restore mode of Sesam.

The incremental backup copies files changed since the previous backup regardless of type. This generates the smallest amount of data on the backup media. To restore the whole data source it is necessary to first copy back the saveset of the last full backup, and then all intermediate savesets. Therefore, depending on the administrator's backup strategy, the restore can contain several steps.

A copy backup is a full backup, however, without a change to the archive bits. A copy backup does not alter diff/incr backups of external backup systems.


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 snapshots 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 since the saveset has stored original paths.

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 of the VSS Shadow Backup

Establish a new backup task or modify an existing one for the client. Add option -o vss in field Save options in the task properties under tab Options 1. The task source is unchanged.

Vssoption en.JPG


Note

For a system_state backup the option -o vss is already set, and should not be added again under Options 1!

Parallel Backups

Sesam supports parallel i.e. simultaneous backup for several data sources onto one drive. This is denoted as 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 = End Of Media ).


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 (underline, 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.

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.

<<<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 configured with the restore manager 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.


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.

<<<Back
The Restore
User Manual
Next>>>
Storage Time Limit, Media Cycle


Duplication and Migration

During migration, backed up data is moved from one media pool (disk) to another media pool (tape or disk). Typically data is backed up to disk (faster) and is then migrated to tape. The previously backed up data are stored in backup savesets. These savesets are transferred 1:1 from the source mediapool (disk) to the target mediapool (tape). This allows the completion of the D2D2T migration.

If you leave the media in both the source and target mediapools the saveset is duplicated. Deleting the savesets from the source mediapool (disk) defines the data as migrated. Data can be restored from either source using the SEP Restore Wizard. If only the migrated saveset still exists this will be used should a restore take place.


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.

<<<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 how to configure SEP sesam to perform a simple data backup using the components described above. The detailed description of the interface elements can be found 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 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 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

Strategy


The IT department and SysAdm should decide on a backup strategy. How many computers will be secured or backed up? How many gigabytes of data will be needed today, in six months, in two years? Where are the computers? When will the computers be backed up? How long will data be stored? How will the data be stored, hard disk, raid array, single tape, tape library? Where will tape media or external disks be stored? Fireproof vault, off-site? What is the budget allowed by the organization to secure business critical data?

This information should be gathered and then the hard data discussed below should be assembled for easy and seamless configuration and maintenance of the daily production and backup cycle.

Once the initial strategy is decided upon. (This should be a flexible plan, especially if this is the first time the company has implemented a backup strategy.) Data gathering can now begin for the real information to implement the plan. After the strategy has determined which computers should be backed up by SEP sesam the names, IP addresses and access to these systems is required.

In GUI->Components->Topology->New Location, freely selected location names and their descriptions are inserted since each server or client must be related to a specific location. Location LOCAL is entered as the default.

Main en.jpg

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

New-Client 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 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 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 Sesam is installed!


Lader Konfig 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 initially selected. The SysAdm can accept this setting or enter a new location.


Laufwerksgruppen en.jpg


In the event in the field 'Loader', in the drive characteristics you find "No Loader" yet it should be serviced by an Autoloader, the drive was not configured properly, i.e. not properly recognized. 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 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 organization 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.


Neuer Medienpool 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 a 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. 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


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 Clients, the button New Task opens an input-window where the description of each backup must to be entered. The task name is arbitrary but it should be a recognizable task name, e.g. "Dly bkp Gndlf 1 = Daily Backup Gandalf" (max. 15 letters). Specify in the input fields which client disks, directories and files are to be included in the backup.

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

Neuesicherung01 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

Zeitplaene en.jpg


The SEP sesam SEPuler is the event calendar scheduler - it is really the heart of the software. Everything that occurs with SEP sesam is registered and logged within the SEPuler. An event is a task set by the SysAdm to occur at a specific time. It consists of a description of the event to take place; a start time; a priority selection (0-9); as well as its recurrence, i.e. every minute, hourly, daily, weekly, monthly, annually.

In GUI->Scheduling->Schedules a default schedule was established during installation. SysAdm can edit, adjust or update the scheduler at any time. SEP NEWDAY, the day change mechanism within the scheduler, has been pre-set to 8:30 a.m. of the following day. ( NEWDAY-event ). This means that all backups from the prior day will either be completed or terminated by 8:30 a.m. Again, 8:30 is the arbitrary starting time for the next day's business activities - the SysAdm user can change this.

The SEPuler determines the frequency or the recurrence of backup tasks to be performed by SEP sesam. The initial installation sets this event to 'Daily'.

At this point the SysAdm must verify that an initialized medium is available for sesam to perform a backup operation. This is done via GUI->Activities->Immediate Start->Media Action .

At the beginning of the next backup event the SEPuler will carry out the instructions as entered in the backup task established earlier. The bottom display window will show messages regarding the requests for a media. This may be automated via the autoloader or it may generate a request for tape in the event a single drive is used.

{{:Step 7: Starting a Backup 3.4|Step 7: Starting a Backup}

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>>>
Components: Topology


The SEP sesam Graphical User Interface (GUI)

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


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

In the toolbar , buttons (shortcuts) for a quick start of the most important functions such as backup, restore , display backups by state , calendar sheet , and ? = about SEP sesam are present.

The drop down menu for different servers is only visible in the Master GUI.

In the Component window on the left, components of the Sesam system are shown. With additional mouse clicks sub-menus can be opened displaying more detailed information. Various activities are initialized from this drop down sequence or menu.

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

The picture of the actual serer (upper right) is only visible as Master Sesam screen in the top layer. Implementing the server as the Master Sesam you can administer other sesam systems from a central location. The working window of the GUI shows all the object trees for the available sesam servers, their objects and their locations. This is also true for the Display of the "Job Status" components (Filters).

The "Media" Display as well as the "Calendar" and the sub-components to "Monitoring" and "Protocol" are also used in the field "Server" of the chosen Sesam Server. The Display in "Output Window" also shows the data of the chosen Server.

Components

In the Component Window (Left) you see a listing of the components of the Sesam System. By clicking further down the tree where you can find more detailed information. By choosing a component in the Work Window for the related Object you can select either tree structure or List for display.

Main Window

In the working window the corresponding Object Class for the required Function is displayed, e.g. Components->Topology Location and clients can be configured.

Section Output

The output window (below) displays three Registers for " für "Ongoing Notifications", "Performance" und "Protocol or Log Files".

Current Messages

Last Notification shows the result of the last activity. In the event the field cyclic is set, a cyclical actualization 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" flag of desired drives from the Drop Down menu.

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 re-display the communication activity between the GUI clients and the SEP sesam Server GUI according to the settings selected in Configuration->Support->Protocol Mask.

Features of the Graphical User Interface (GUI)

All windows can be adjusted using either the edges or corners to the desired size. The settings or sizes of the windows will be stored, from the size of the main window to the daughter windows, and the restored to the same size when the GUI is restarted.

The input of improper (not allowed) values will generally be suppressed by the User Interface, i.e. only specific values are permitted. For example, the task name does not permit spaces, \, /, ? or *. Additionally, in certain fields the 'name length' is limited.

The visual appearance of the output can be set interactively to the personal preference of the user. This includes the Column order, Column width and Sorting criteria.

Adjusting the SEP sesam GUI

Under Window ->Customize you will see the following window:

Anpassen en.jpg


Save positional data:

Off
All adjustments (window size, window position, slider position) which are made during the GUI-session will be reset to system defaults after restarting the GUI.
Local storage
If record position is chosen under Position setting all window positions and slide bar positions will be saved in a profile. After restarting the GUI all customizations will be preserved, the window will usually reopen in the same position it was in when it was closed.
AngepassteGUI en.jpg


The size of a window can also be adapted albeit only windows with minimize and maximize buttons.

Fensteranpassen en.jpg


Remote storage
It’s possible to choose a customized profile with the option „Use positions from profile“ which is stored in the SEPsesam server database. By doing so the SysAdm or other users can create a specific profile to perform work from any location.
Anpassenremote en.jpg


Actions
With Delete all recorded positions the profile is set back to the default status.
With Load profile positions for current session all adjustments from the stored profile will take effect and all adjustments done so far will be rejected.
With Save recorded positions to profile all adjustments will be stored in the SEPsesam database.


Useful Tips:

Invalid entries are generally prevented by the interface, i.e. only acceptable characters can be entered (e.g. the task name cannot contain blanks, backslash \, forward slash /, ? or *). The input length is also restricted.

Components

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


Topology

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

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

The menu item Topology shows all 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 related 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 usual Sesam computers. With a mouse click their individual data can be viewed.

A 'usual' Sesam server shows one node only, namely itself.


GUITopologie en.jpg


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

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


Server Properties

Remoteserverneu en.jpg


Server Name        Name of the servers in the network
Connection         On (green) /  Off (grey) / Broken (red)
Operating System   of the Server
DB-Port            Port of the socket connection to the remote DB
DB-Name            Name of database on the server
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

Location is 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 Sesam server or from an existing location (sub-location). Sesam sets up a tree-structure for all locations(e.g. USA-Colorado-Boulder-SEP Software) offering greater visibility.


Location window en.jpg


Name
denotes the 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 defined as computers in the network from which data are to be saved. The computer on which Sesam is installed is called the server .

If a client is not available for backups (e.g. because of a shutdown), the SysAdm can select the check box locked for backups and prevent unnecessary access (locked clients are marked with off under Topology). If an unavailable client is not locked, the SEPuler will continue to look for it to perform the scheduled backup.

Warning: Once selected locked for backups the client will no longer be backed up, even if on the event calendar. The SysAdm must remove the check to reestablish the backup schedule.


Neuer Klient en.jpg


Name               A DNS recognizable name for the client. IP Addresses cannot be used.
Location           selection of pre-defined locations. A Client must be assigned to a Location
Operating System   selection of an Operating system (WNT, Linux or Unix) for the Client
Access Mode        selection of access method. Default is CTRL. SSH and RSH  can be selected, too
Notes              additional information
Interfaces         additional TCP/IP-Names of the client in case there are more network cards installed, these 
                   are accessed by their respective names. This should allow a fast, smooth data transfer without  
                   blocking other network activities over separate fast networks.

Note If several interfaces are entered, separate them with a Return or a Blank.

In this field the SBC (Sesam Backup Client) client software version is shown.
Locked from backup 
If a client needs to be excluded from the backup plan for technical or other reasons you can deactivate it here.
Note:

If the switch is set from this time forward the client can no longer be backed up, until the setting is removed. Even if the client is part of the pre-established backup schedule.

Firewalls

Klienteigenschaften en.jpg


Normally when initiating backups of clients Sesam uses the ports randomly provided by the operating system. However, this is not allowed if the client is located behind a firewall.

If there is a firewall in place a port range can be pre-determined by using the command sm_ctrlc for communication with the clients:

Access Options input -o port=firstport-lastport

Another method to connect through the firewall is to configure a Singleport connection ( -s ), where Sesam uses only one port (by default 11301).

Note: This must not be done for Remote Tape Servers.

The return ports from client to the Sesam server are placed in STPD Options , e.g. 11003-11005. The data can now be transferred over these ports. Each parallel backup requires two separate ports. For each additional parallel running backup from a client you will need to assign a further 2 ports, e.g. 11003-11007).

Listen Port

   When using a Remote Device Server (incl. Sesam Server) the standard setting is the STPD Port 11001. 

Note: Further information regarding Firewalls can be found in the Admin Handbook.

Additional Properties

In the event 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  
Re-enter Password to insure 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 Sesam Server and the running TSA. That means that the sesam-Novell client can be installed on any Linux computer/server. The only requirement is that it have either sesam client or server software properly installed. The resolved DNS sesam client or server will then be entered as the data mover. In the event 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>>>
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.


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


Ladereigenschaften en.jpg


Attention

Windows requires the Device Label of the SCSI ID. Linux, however, requires the Device File or Data, e.g. /dev/sg2.


Device  
SCSI Device Description of the Loader
  • Windows:

The SCSI ID can be entered using the "sesam loader utility" (slu) as long as the Drivers have been properly installed. 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 (Changer)

The displayed ID must now be entered under "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, in addition to the SCSI ID, you will need to enter the data file into "Device (SCSI-ID)".


Tape Server  
Remote Device (Server) where the Loader is installed

The Remote Device or the Remote Device Server refer to the server where the Auto Tape Loader is connected. In smaller environments you would normally install the Auto Loader or Disk array directly to the SEP sesam Server. You will use the Remote Device (Server) in more complex data centers and data backup designs. The backup stream will flow to the Remote Device (Server) instead of to the SEP sesam server (Master Server).

Type  
Manufacturer
Ctrl  
Loader Control with sesam Loader Utility SLU
Fächer  
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, as the case maybe, if 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, allows 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, where 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 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 


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

Button 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 will be 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 or regions. If the media have bar code labels, it will be noted and taken into account for the backup process. A 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 within the load, without regard to which Pool (Storage Pool) they have been assigned/reassigned.

Functions
Legend  
key for the VTL color coding
Laderlegende en.jpg


Change Views  
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 or (Media Archive)

Select Archive Adjustment

Archivabgleich en.jpg


Mediapool  
Select a Mediapool where you want to perform the Library Sync - All media will be shown regardless of the pool selected
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 New Media
In the event unknown media (without sesam Label) are found within the loader, these unidentified media will be added to the specified mediapool
Media Type  
Entry of Media Type for Automatic New Media entry
Handling of unrecognized SEP sesam Media
  • Enter without initialization - foreign sesam Media, e.g. from another SEP sesam server will be entered into the new Mediapool

- 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 
Every tape label will be newly read, and verified. The bar code information will be ignored.

Select 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 within the SEP GUI, as well as the sorting from media within the library. The use of Port Slots will be dependent upon 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)
Slot
defines the number of the slot receiving the tape cartridge, or from which it must be loaded
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 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.


Laufwerksgruppen02 en.jpg

Button Properties

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

Select New Drive Group

New Drive Group is used to configure a new group.

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

Select 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

In Sesam media are grouped into media-pools . The identification of a particular medium is always "`pool-name + 5-digit number"', this is the reason why a pool-name is never allowed to end with 5 digits.

Media pools provide the main base for building up backup strategies. The user can set up and manage media pools for working days, weekends, specific locations, specific types, databases and more. The virtual DISK-Media are also configured by means of media pools since the pool inherits the directory and capacity information.

Properties

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

Select New Media Pool

Neuer Medienpool en.jpg


Name
identification of the new pool
Description
User comment
Drive Group
selection of a drive group


The sequence for a backup is Task -> Mediapool -> Disk Drive Group


Media Strategy
GET_OLDEST strategy, i.e. the oldest, unlocked, type-compatible, EOL-free (EndOfLifetime) media of the pool is used
Change Strategy
TIME (avoiding tape winding times) pre-set
Locked [Days]
number of days for which the media must be write protected after an initialization
EOL = EndOfLife is Initialization date + Lock days
opt.Directory
for DISK_HARD only: specifies the directory on the disk in which the virtual media should be created
opt.Capacity
for DISK_HARD only: specifies the maximum available capacity on the disk for this media pool
This determines the maximum possible number of DISK-media within this pool
The maximum size of a Media Pool is influenced by SEP licensing!


Medienpoolmitstorage en.jpg


opt. Use Storage Pools
only with DISK_HARD. Distribute the DISK Media pools to different backup locations.


Storage Pools

(From Sesam Version 3.4)
We have added an additional check box under Components->Mediapool with Use Storage Pools. If this option is selected you will be asked if Storage Pool mechanisms should be activated. A detailed description on how to configure Storage Pools can be found under Using Storagepools.


Medienpoolmitstorage en.jpg


After accepting this option a dialog box appears to create the Storage Pools.


Storagepoolalegen en.jpg


After selection of at least one Storage Pool, click OK and return to the Media Pool Dialog which now has a new flag Storage Pool.


Storagepoolszuweisen en.jpg


Now with this Media Pool a subset of the defined Storage Pools can be selected, e.g. 1 to n)

After saving the Media Pools the Storage Pool is activated.


new Media Event 
links to Scheduling


new Media 
links to 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 Sesam.


Medien 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
Locked until
The media is not available up to this time
EOL = EndOfLifetime = Backup day + Lockdays of the media pool
Occupancy
occupancy in proportion to the total storage capacity of the media (sometimes more than 100)
Error Delta  
change in number of errors compared with the previous day
Pool
to which the medium belongs to
Slot
in loader, in which the current medium resides
Media Type
shows the media type
Storage Pool
the memory area which is/will be used
Comment
further information


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


Button Properties Media

Medieneigenschaften en.jpg


Media Pool
name of the media pool containing this media (uneditable)
ID
identification number of the media (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 Number
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


Medieneigenschaften02 en.jpg


Label
used for media identification
Barcode
bar code on the media
Occupancy Level
shows the current occupancy of the medium in percentage (uneditable)
Error Count
absolute number
Error Delta
change in number of errors compared with the previous day
Use Count
counts the initializations of the tape (uneditable)
Duplication
has this media been duplicated (yes/no, uneditable)
Comment
additional information


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


In the view Savesets all savesets stored on the media are listed.


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

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.

<<<Back
Tasks
User Manual
Next>>>
Tasks by groups


Tasks by clients

Under Tasks you find three different types of backup tasks: Backup, Restore and Migration. To make administration easier three views are possible: View of the client, View of the Groups, and a view of the Backup Plan.

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


The selection Properties shows the information for the chosen Task and allows changes therein. Alternatively you can double-click the backup task to open it.

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

Neuesicherung01 en.jpg


Task Name
user selected identification of a backup task (use digits, letters and underscore (_) 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
selection of 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


OK
Saves the changed task parameters in the database and returns to the start screen
Apply
Saves the changed task parameters in the database. The entry mask can be used for further changes
Delete
removes the dataset from the database and closes the entry mask
Cancel
no action and return to the start screen


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 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, however, 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
Neuesicherung02 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:

run Pre  
Commands written in the Pre- interface will be initiated
Backup if Pre- start command fails 
Forces the a backup job to start in the event the Pre- commands were not executed properly.
run Post  
Commands written the Post- interface will be performed
start Post even if Post commands fail
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
Backup if Pre- start command fails 
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 even if Post commands fail
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) 
Backup 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
Neuesicherung03 en.jpg


Option 2 allows the selection of Encryption and Compression.

Cryptogrophy
Encoding  
none, bf64 or aes256
Info  
Information regarding the setting/selection of a encryption key
Set new Key Word 
This button is activated when either (bf64 or aes256) has been selected. A mouse click (if permissions are in place) combines the next two input fields
New Keyword 
Enter new keyword
Re-enter 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
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 System where file pattern '*' 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

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, Online Backups for databases, are supported by 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 Event Command_Event.

For all online 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 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

Neuermigrationsauftrag en.jpg


Name  
a fitting name or label for this task could be e.g. 'DISK2TAPE'
Pool  
Media_pool_name, e.g. 'DISK', from the source where data will be taken (migrated)
Drive 
Drive Number from where the data will be read (Source)
Remote Device Server  
Selected Tape Server where the data will be written to complete migration. As a general rule, it will be the Client or Remote Device Server (RDS) where the relevant tape or backup device is connected.
Count  
If the value is greater than >0, multiple duplication is possible. This is valid for targeted media for backup archiving and 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.

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.

<<<Back
Tasks By Clients
User Manual
Next>>>
Scheduling


Tasks by Groups

For the menu location ->GUI->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

Auftragsgruppeeigen en.jpg


Group Name 
Task Group Name (Use relevant and easily recognizable Names, e.g. File Backup, Database Backup,...
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 an moving it up or down with the respective arrows ↓ and ↑. The uppermost Task will performed first. If you are using a 'Standard' server license the first five (5) 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

<translate>


Schedules overview

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

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

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

Schedules overview 4.4.png

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

Create new schedule (schedule properties)

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

Schedule v.4.4.2
Schedule 4 4 2.png
</translate>


<translate>

Name 
The name of the schedule.
Execution 
Enabled by default. Use this option to activate or disable the schedule. If set to No (disabled), the schedule will still be displayed as shaded in the list of schedules, but the related jobs will not run.
Cycle 
Configure the intervals for scheduled jobs. Jobs can occur once or recur from every day to every year.</translate>

<translate>

once 
no repetition, single run
daily 
repetition in days, hours or minutes
weekly
repetition in weeks or weekdays
monthly 
repetition on absolute or relative dates: 1st, 2nd, ... or Mon, Tue, ... </translate>

<translate>

yearly 
repetition on absolute or relative dates
Period of validity 
The time range of the schedule. Clicking the arrow displays a calendar.</translate>

<translate>

Begin 
Start time of the repetition cycle. The schedule is only valid from the specified date. There can be no execution prior to this date.
End 
Set the validity of the schedule. If the schedule should only be valid for a limited period of time, e.g., until the end of the year, select the End checkbox and enter the date of its suspension. By default, this option is disabled and the schedule will be repeated in perpetuity.
Start time frame
The start time of the events linked to the schedule.</translate>

<translate>

Start 
Designated start time of the event. The actual start time depends on the processor load of the system. See below option Duration.
Duration 
The time frame for the allowed actual start specified in days and/or hours (the amount of time an event can be in the queue). Actual start of event depends on the processor load and event priority. At schedule's designated start (see above option), every event is forwarded into the queue where it waits to be processed according to its priority. If execution is not possible within the specified duration time, the event will not be started.
Schedule v. 4.4.3
Schedule-4 4 3.png
</translate>


<translate>

Execution 
Enabled by default. Use this option to activate or disable the schedule. If you deselect the execution option, all events that are linked to this schedule will be deactivated. The schedule will still be displayed as shaded in the list of schedules, but the related jobs will not run.
Name 
The name of the schedule.</translate>

<translate>

Start 
The start date and time for the schedule. By default, the current date is already entered in the first (date) field. In the next (hour) field, specify the start time <hh:mm> for a job to begin. The schedule will be activated on the specified date and time.
Expiration date
Set the validity of the schedule. If the schedule should only be valid for a limited period of time, e.g., until the end of the year, select the check box and enter the date of its suspension. Clicking the arrow displays a calendar. The schedule will be deleted after the Expiration date criterium is met.
By default, this option is disabled and the schedule will be repeated in perpetuity.</translate>

<translate>

Table with time intervals
Configure the time intervals for scheduled jobs. Jobs can occur once or recur daily or yearly.
once 
no repetition, single run
daily 
repetition in days, hours or minutes
weekly
repetition in weeks or weekdays
monthly 
repetition on absolute or relative dates: 1st/2nd... or Mon/Tue... </translate>

<translate>

yearly 
repetition on absolute or relative dates
user defined 
option for setting up a custom calendar (available on SEP sesam v. 4.4.3 or higher, see creating custom calendar for details)
Advanced settings
Allows you to further refine your schedule.</translate>

<translate>

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

<translate>

Repeat task 
Select the check box if you want to repeat the event. Choose how often (in hours or minutes) the task should be repeated.
For a duration of 
Available if the Repeat task check box is selected. You can specify for how long should the event be repeated in days and/or hours.
Stop task if it runs longer than 
Select the check box if you want to set the amount of time (days and/or hours) following the event's scheduled start time after which the event will be cancelled.

New backup event

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

The button New Backup Event opens the following window:

Backup task SSDD follow-up.png
</translate>


<translate>

Sequence Control 
Priority
The priority of your backup event. Default priority level is 1, which is the lowest priority (the highest is 99). The only exceptions are schedules with priority 0, which override all other priorities and are always executed. See Setting event priorities.
Blocking Date
The event only works within the prioritization concept as a block for other backups with the same name when schedules are overlapping. See Blocking events
Execution parameter 
Backup Type
Select between the backup types FULL, DIFF, INC, COPY
Hot/Cold backup
Execution parameter, e.g., for database backups</translate>

<translate>

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)
Source Side Deduplication (≥4.4.3)
Introduced in SEP sesam version 4.4.3. Source-side deduplication (Si3S) requires a special license and a configured Si3 deduplication store. If the specified target media pool is combined with an Si3 deduplication store backend, the option Source Side Deduplication is shown and can be enabled
Drive Group 
(non-editable parameter) The drive group which is specified in the media pool. This field changes depending on the media pool selection
Drive (opt.)
Selection of a drive from the drive group mentioned above</translate>

<translate>

Interface (opt.)
Selection of an alternate (configured) name of the TCP/IP-name of the client. This can be used to direct the data flow over a particular network connection in order to enable smooth execution of backups or restores without blocking another network activities.
Follow up (≥4.4.3)
Specification of events that are started on the SEP sesam Server once the initial event has completed. For details, see Follow-up Events.</translate>

<translate>

Object 
Task 
Selection of the backup task related to this event
Task Group 
Selection of the backup task group related to this event

New restore event

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

New restore event – Source
Schedules 4.4 new restore event.png
Restore Task 
Selection of the restore task for which the event is going to be configured.
Fix Restore 
The restore will be executed exactly as defined by the restore task parameters using the same backup save set.
Selection
The restore task can be adjusted, for example to use the most recent backup save set. The following parameters can be set.
Parameters 
Saveset Limitation
indication of the time frame:
  • View: oldest selection: first, second, third, and so on
  • View: recent selection: last, penultimate, antepenultimate, and so on
backup day 
set a time frame for the exact backup day: from date ... to date
relative backup day 
from - to as a relative indication of the number of days that have passed since the backup. Negative numbers specify days in the past, while positive numbers specify days in the future.
Example : 2 weeks ago until now: from date = -14 to date = 0
FDI-Type 
Only save sets with the specified backup type will be used for restore: C (copy backup), F (full backup), D (differential backup), I (incremental backup).
Selection 
Provides the criteria according to which the backup save set to be restored is defined:
  • youngest: The most recent backup in the range of the relative backup day will be used for restore.
  • oldest: The eldest backup in the range of the relative backup day will be used for restore.
Media Preference 
Option to limit the media that are used as the restore source. </translate>

<translate>

  • No limitation >> ' '
  • Regular medium before clone >> 'media'
  • Clone before regular medium >> 'clone'. If no clone is available this selection is ignored.
Tolerance 
Option to limit the media that are used for the restore.
  • Error if medium is not available (Default) >>
  • Only select available media >> 'available'
  • Only select available media that are eol-protected >> 'eol-protected'
Pool Restriction
Option to define that a save set must come from the specified media pool.
State 
Option to select the condition of the backup that will be used for restore:
  • successful or with warnings (default)
  • only successful
  • only with warnings
  • partially restorable (canceled backups)
New restore event – Destination parameters
Schedule dest param tab.png


Sequence control 
Priority
The priority of your restore event. Default priority level is 1, which is the lowest priority (the highest is 99). The only exceptions are schedules with priority 0, which override all other priorities and are always executed. See Setting event priorities.
Blocking date
Used together with high priority for special events. See Blocking events.
Execution parameter 
Backup Type 
Optionally, the backup type of the save set can be overridden. The restore is then executed with a different backup type (usually tape backup).
On/Offline
Execution as Online/Offline restore.
Media Pool 
Not selectable.</translate>

<translate>

Drive Group 
(non-editable parameter) The drive group which is specified in the media pool. This field changes depending on the media pool selection:;Drive (opt.): Selection of a drive from the drive group mentioned above.</translate>

<translate>

Interface (opt.)
Selection of an alternate (configured) name of the TCP/IP-name of the client. This can be used to direct the data flow over a particular network connection in order to enable smooth execution of backups or restores without blocking another network activities.
Follow up (≥4.4.3)
Specification of events that are started on the SEP sesam Server once the initial event has completed. For details, see Follow-up Events.

New migration event

As of SEP sesam v. 4.4.1, the procedure for configuring migration is changed (including GUI options). If you are using SEP sesam version < 4.4.1, see Configuring a migration job in SEP sesam versions lower than 4.4.1.

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

Creating a migration event consists of reviewing migration task parameters and (optionally) setting event priority.

Migration event.png
Name
The name of the already configured migration task for which you want to create a migration job.
Priority
The priority of your migration event. Default priority level is 1, which is the lowest priority (the highest is 99). The only exceptions are schedules with priority 0, which override all other priorities and are always executed. See Setting event priorities.
Blocking date
Used together with high priority for special events. See Blocking events.
Parameter 
Media pool 
Pool
The name of the source media pool from which the data will be migrated, e.g., source_mediapool.
Drive
The drive number of the drive that will be used to read the data.</translate>

<translate>

Destination 
Pool
The name of the target media pool to which the data will be migrated, e.g., target_mediapool.
Drive
The drive number of the drive that will be used to write the data.
Interface (opt.)
The network interface of the server through which the data transfer will be executed.
Time frame
The time frame of the backups that will be migrated specified by exact date or by relative backup date.
Filter 
Backup state
The backup completion status of the save sets you want to migrate: successfully or with warnings (default) or only successful. You cannot migrate the erroneous or only partially restorable save sets (containing data from canceled backups).
Object
Select one of the following objects as a migration source.
Task
Only this task within the defined time frame is migrated.</translate>

<translate>

Task group
Only the tasks of this task group within the defined time frame are migrated.
Client
Only the backups for this client within the defined time frame are migrated.
Backup type
The backup type relevant for migration (COPY, FULL, DIFF, INC).
Number of copies
How many times may the backed up data be migrated. Default is 0, meaning that data migration is unlimited.
Copy migrated save set again
A save set that has already been migrated can be migrated again.</translate>

<translate>

Special filter
Start media
Select only one medium from the source media pool to be migrated.
Save set
Select only one save set to be migrated according to its ID.
Parallel migration 
The data can be migrated concurrently using multiple streams, thus improving the migration speed.

New media event

New media event.png
Succession Parameters  
Priority
The priority of your media event. Default priority level is 1, which is the lowest priority (the highest is 99). The only exceptions are schedules with priority 0, which override all other priorities and are always executed. See Setting event priorities.
Blocking date
The event is only in effect to block other media events for the pool when schedules overlap. See Blocking events.
Execution Parameters
Media Pool
Grouping of media by certain criteria (e.g., by types of media etc.)
Media Strategy
Indication of strategy OLD defined in the media pool
Drive Group
Selection of a drive group. Advantage: Sesam uses the drives belonging to a specific group independently
Drive
Selection of a certain drive
Tape Label
Selection of a pre-set tape label (tape identification) from the media pool
Spare Label
Selection of a pre-set spare label from the media pool

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

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

New command event

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

New command event.png
</translate>


<translate> Under the Sequence Control, the following options are available:

  • Priority: Define a priority of your command event. SEPuler always executes the schedules with higher priority first. Default priority level is 1, which is the lowest priority (the highest is 99). The only exception are the schedules with priority 0, which override all other priorities and are always executed. For details, see SEPuler.</translate>

<translate>

  • Blocking date: This should be used together with high priority for special events. If checked, the blocking event will block events of the same type of a lower priority, ensuring the command event to be processed in case other command events are scheduled at the same time. See Blocking events.

Under the Parameter, define the following:

  • Name: Enter a name for the new event or search for and select an already existing command event. Searching for command opens a new window, where you can add a new command event, copy an already existing command event, select which existing command event you want to use again by clicking the Choose button, and delete an existing command event.
Select command.png
</translate>


<translate>

  • Client: Select a client, on which the command will be executed.
  • User: Enter the username of a user with sufficient access to execute the command on the client.
  • Command: Enter the complete command and parameters if necessary, e.g., eventlog.ps.
SEP Tip.png Tip

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

Access restriction of command events

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

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

UNIX

External commands are only executed when the username and the command are entered into the file /etc/sesam_cmdusers.allow on the client computer.

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

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

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


<translate>

command</translate>|| <translate> Run</translate>

* <translate>

all Commands</translate>

<translate>

Specific Commands</translate> || <translate> only these</translate>

cmd /c <translate>

all DOS Commands ( dir, etc. )</translate>

<translate>

DOS-Commands</translate> || <translate> only these</translate>


{{<translate> Note</translate>|

<translate> Many errors are made when setting up the desired user permissions and allowed commands:

  • The necessary entries are not entered in the target client directories, not entered in the server or are entered incorrectly.
  • Instead of entering the command as a key it is entered as a character string.</translate>

}}

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

Zeitplaene en.jpg

The window shows an overview of the configured schedules and the related events. Using the tools lists the switches may be set to control the time and events for all activities within SEP sesam. You will either create a new schedule or activate a previously established schedule. Within the schedule you set an event and specify the tasks for the event. The Task will then be executed in the specified time range,and depending on the action the task will be rescheduled automatically by the SEPuler to be performed during the next cycle.

Properties Schedule - New Schedule

Neuerzeitplan en.jpg


Name
Identification of the schedule
Execute
(De-)Activation of all events using this schedule by the user
Duration
Time interval for the execution of a schedule

: the date can be entered through a graphical calendar appearing at mouseclick.

Begin
Start time for the repetition cycle. The schedule is valid only after the day for which Begin is

: specified. The first execution can be performed no earlier than the start time Begin

End
If the check box End is activated then the repetition cycle is ended after the selected date.

: After the day End no further executions occur. If the check box End is not set, the : repetition cycle is unlimited.

Starting Range
Backup task can be started only in this defined period of time
Start
Desired Start of the event. The actual start time of the event depends on system load.

: Each event is inserted at start time into a waiting queue at start time. Depending on : workload and job limit of this waiting queue and the schedule priority, execution must wait until : all current tasks are completed and there are no tasks of higher priority pending. For tasks of : equal priority the rule FIFO (first in first out) is valid .

Duration
The user can set up a Starting Range by defining the duration. If execution cannot start in the

: duration interval, the job is not started.

A variety of settings is offered for the cyclic behavior of a schedule:

  • one-time the desired time in the starting range is set
  • daily specific days or hours or minutes
  • weekly specific weeks and weekdays
  • monthly specific months at specific month date
  • monthly at 1., 2.,3.,4., last day, weekday, weekend day, Mo,Tu,We,Th,Fr,Sa,Su of month (optionally a daily offset here is possible) these specifications are denoted as relative
  • yearly similar to monthly; absolute and relative specifications allowed


User-defined Schedules

User Defined Schedules exhibit a list of absolute and relative Date Inputs, that cylce annually. In the field Name enter a descriptive Name for each List Entry. In the field Date/Offset you enter, depending on the switch setting, a date in the format Month-Day (mm-dd) or Offset. The Offset is a number between -50 and +50 and designated the number of days before or after a specific date, e.g. Easter, ( Offset=0 is Easter Sunday). This allows the setting or creation of backup tasks for holidays that change from year to year. By selecting Assume Task the entry will be made to the List. Further, displayed lists as well as elements from other lists can be copied or deleted. To take this action double click the right mouse button and select the desired choice. The user defined schedule is normally used for exception scheduling for typically stringent schedules during concurrent schedules for blocking events that may occur during vacations or holidays.

New Backup Event

Sicherungsparameter en.jpg


Succession Parameters
Priority
Priority
Blocking event
The event is in effect only to block other Backups with the same name if schedules overlap
Execution Parameters
Backup Type
Selection of the Backup type FULL, DIFF, INC, COPY
On/Offline
Execution Parameter, e.g. for Database Backup Task
Media Pool
Target for the Backup data. The exact label of the target media is determined by the previously executed media event
Drive Group
Specified in the media pool drive group (not editable) changes at media pool selection
Drive (opt.)
Selection of a drive from the pre-set drive group
Interface (opt.)
Selection of additional configured TCP/IP-Name of the client. So the data stream can be directed over a specific network connection permitting undisturbed backup or restore
execution without blocking other network activities


Object 
The backup object or Task Group
Task 
Selection of a single backup task
Task Group 
Selection of a single Backup Task Group


New Restore Task Event

The switch New Restore Event opens the following window where the 2nd register is selected. The 1st Register is the mask Schedule and is already correctly pre-set.


Note

Some of the described functionality/fields displayed are unavailable in the current version but will be added in later revisisons.

New Restore Task Event - Source
Neuerruecksicher en.jpg
Restore Task 
Select a previously set Restore Task
Set Restore 
With a fixer Restore the restore will be performed as it has been set previously in the Restore Wizard. The pre-defined backup source for the specified criteria will be used to perform the restore.
Select
The Restore Task will be used as a template. The Backup Task, and the Restore Task (Full, -Selective) will be set. The exact backup will be determined using the following parameters:
Selection Parameters 
Saveset Limitaion 
Enter the time constraints:
  • View: oldest selection: first, second, third, etc.
  • View: newest selection: last, next to last, etc.,
Backup (Sesam) Day 
Limiting selection to a specific time period: from Date - to Date.
relative Backup Day 
from - to as a relative input the count of days past
Example: 2 weeks to today: from date = -14, to Date = 0.
FDI Type 
Only backup volumes with the following FDI Types may be selected (Copy, Full, Diff, Inc): C, F, D, I.
Selection 
You can dynamically select the backup volumes for restore. Selecting the option newest or oldest either the most current or the oldest volume will be restored, i.e. in accordance with the relative Backup Day and other possible limited factors.
Media Preference 
The limiting selection for the Restore Source should a Migrated/Cloned medium be required.
  • No Restrictions >> ' '
  • Regular Media before Clone >> 'media'
  • Clone before Regular Medium >> 'clone', in the event there is replicated data (a Clone of the previous dataset) it will be restored, if one is is not available the latest media source will be restored.
Media Availability 
Limiting Selection can restrict restore to media/data currently in the Autoloader.
  • Error if Medium is unavailable (Default) >>
  • Select only available media >> 'available'
  • Select only available media with EOL Protection >> 'eol-protected'
Pool Limitation 
Permits Source selection to specific Media Pools.
Status 
Limitations based on Backup Result - Possible choices are:
  • Successful or Successfully with Warnings (Default)
  • Only Successful
  • Only with Warnings
  • Partly Restorable - Interrupted or failed backups
New Restore Task Event - Destination Parameter
Zielparameter en.jpg


Sequence of Events 
Priority 
see Setting Event Priorities
Blocking Events 
see Blocking Events
Execution Parameters 
Backup Type 
this option can overwrite the Backup Type of a Backup Task and perform the restoration of another backup type, usually a Path Restore.
On/Offline
Perform a Restore Online/Offline.
Media Pool 
Not selectable.
Disk Drive Group 
Shows the chosen Media Pool for the Disk Drive Group.
Drive 
Selection field for the desired drive from the Disk Drive Group.
Interface 
optional specification of the interface where the data transfer to Target Node occurs.

New Migration Task Event

As with the executonn of other sesam tasks you must first establish a new schedule Scheduling -> New Schedule. Using this new Schedule you can now create a new Migration Event Task Schedulng -> New Migration Event. The Task window mask is only slightly different from that for a Restore Event.


Note

The following functionality for some of the described fields will only be available in later versions of SEP sesam.


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 Division:
  • View: Oldest selection: first, second, third, etc.
  • View: most recent selection: last, next to last, previous to next to last, etc.
Backup Day 
Limiting choices for a fixed time period : from date x ... to date y.
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 Sesam Day for the selected Media Pool.
FDI Type 
Selection possibilities in relation to CFDI Type (Copy, Full, Diff, Inc): C, F, D, I und G

A difference to previous Restore Tasks now exists. The new selection to the standard CFDI Task selection is now available - type 'G' for 'Generation' Migration. This means that next to the incremental backup from the last days and all relevant past backups up to and including the last Full Backup will be included in the Migration Task. With this you can accomplish a Disaster Recovery of a failed server. By using the combination of available Full- Incremental- and Backups stored off-site, a restore can offer the most relevant and complete backup as desired.

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, by selecting a check box, the backup Source to be limited to specific Mediapools.
Status 
Limitation according to Backup Results: are Possible
  • 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

Neuermedientermin en.jpg


Succession Parameters
Priority
Priority (see Chapter 4 - Prioritizing)
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 Sesam creates an internal media event, which provides the next media for the backup. If no media event is configured in the calendar, then always only the internal one is in effect at EOM.

New Command Event

The switch New Command Event opens following window:


New-Task-Event en.jpg


Parameter
Description
Priority
Priority
Blocking event : The event is in effect (Prioritizing concept) only to block other command events with exactly the same command when schedules overlap
Selection
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 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.

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


Kalenderblatt en.jpg



When calling the Calendar Page an additional icon with two pointers is merged in the toolbar. A mouse click on the icon activatres the automatic Update Function, this means that the Calendar Page will be cycled (updated) every 10 seconds.


Calendar sheet auto update en.jpg


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

Job State

Jobstatus en.jpg


Backups are an integral part of the Sesam Information System. Only "completed" backups are displayed, along with a multitude of display, information and filtering possibilities are offered.


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

Overview of all Tasks using the following Filters:

  • Time_Filter
  • Client_Filter
  • Status_Filter
Sicherungsstatus en.jpg

Once you've changed a filter selection, it will be activated when you click the "Show" switch.

You can halt a Task by selecting an active task in the Table and clicking the Switch Abort.

Clicking the column label, e.g. column Status or column 'Start_Time, will display the data either alphabetically or by execution time.

Note

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


State Filter

Working
in Queue
The task has been queued for execution, i.e. the SEPuler has started this job but it has to wait until resources

(e.g. Tape Drive for a Media Pool) are available.

Active
the task is being processed.
Not Restorable
Interrupted
The backup Task was interrupted during data transfer
errors exist
Fatal errors were detected during the completion of the backup task.


Restorable
Successful
Backup Successful
Info
System dependent - some files/data could not be backed up, e.g. open files in Windows.

By clicking a task in the table and selecting the switch Properties or with a double click on the task line you can see other information for the backup task. You can store preferred settings for these tasks, see User Settings for State Filters

Properties of a finished backup

Info 1
Auftragstatus en.jpg


Saveset 
Name of the Backup Task
Type 
Backup Type (F=Full, C=Copy, I=Incremental, D=Differential)
Media Count 
Media used for the backup
Size 
of the backup in Bytes
Used Labels 
List of used Media
Status 
Detailed status reports
Info 2
Auftragstatus02 en.jpg
Info 3

Shows status of Encryption and Compression.

Auftragstatus03 en.jpg
Protocol

The Backup Log or Protocol 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.

Statistics

Presentation of the above table for selected Backup Tasks/Jobs displayed in a pie chart, the graph can be rotated with mouse clicks. You can switch between table output and graphical output with the button in 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
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. The columns in the Result Tables are, however, somewhat different.


Ruecksicherungstatus en.jpg

By selecting an active Restore Task from the Table and by clicking the switch Abort a running Restore can be halted. Any data transferred before the Abort command stay on the target system.


Properties of a finished restore

Info 1
Ruecksich01 en.jpg


Saveset 
Name of the Backup Job
User 
Name of the User
Restore Type
Full Restore or Selective Restore
Tree Type 
Hierarchical or flat
Mode  
Overwrite, not rename
Used Labels
List of used Media
Report 
Detailed status report, e.g. Restore was successful
Info 2
Ruecksich02 en.jpg


Status 
Latest Status, e.g. successful
Backup Task 
Name of the Backup Task
Interface 
used System Interface
Location 
Location of Target Computer
Client 
Name of the target System
Disk Drive 
Number of the used Disk Drive
Backup Number 
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
Ruecksich03 en.jpg


The following Expert Options can be selected in the Restore Wizard and the setting propagated.

Options
Passed Options, e.g. "-v 4".
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>>>
Monitoring


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.


Migstatus en.jpg


Properties of a finished migration

The detail mask for a Migration Task is a Subset from Restore by state.

You can select either "Info 1", "Info 2" and "Protocol" for viewing.

Info 1
Migstatus01 en.jpg


Pool 
Shows the used Media Pools
Size[Bytes] 
Shows the resulting size
Used Labels
Shows the used tapes
Reports 
detailed status, e.g. Migration was successful


Info 2
Migstatus02 en.jpg


Status 
Latest Status, e.g. successful
Backup Task 
Name of the Backup Task
Interface 
used System Interface
Location 
Location of Target Computer
Client 
Name of the target System
Disk Drive 
Number of the used Disk Drive
Backup Number 
Number of the used backup task
Start Time 
Start of the backup
End Time 
End of the backup
Target 
Path of the restore
Protocol

Reports regarding the Migration are found in the Migration Log.


Monitoring

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


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


Processes

Shows the status Processes/Daemons of SEP sesam.


Monitorinproz 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 affirm the selection with the switch Show and all the information for the queue will be displayed. The queue is overseen by the 'Queue Manger'. The 'Queue Manger' can initialize the queues, where jobs are set (submitted). However, the 'Queue Manager' sets a job 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.

Monitoringlw en.jpg

Logging

Protokolle en.jpg


Sesam creates two protocols or log files for each backup day, the status file and the day protocol. 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>>>
Daily Protocol


State

Statusprotokoll en.jpg


Sesam creates a status protocol. One row is written for each backup started in chronological order .


Function of the buttons:

Server    only MasterSesam : view protocol of other Sesam servers
Show      shows selected interval
Help      Online-Help
Send      sending the protocol-file via an email to SEP AG 
          (have to be configured and released 
Print     printing the protocol-file to 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>>>
Menu Bar and Tool Bar


Daily Protocol

Tagesprotokoll en.jpg


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.

Menu Bar and Tool Bar

Menueleiste en.jpg


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

In addtion, other buttons can be added dynamically, e.g.

  • cyclical Show-Updates for "Job Status" Working Window (e.g. "Job Status->Backups").


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 a new GUI version from the SEP sesam server if one is available. 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, backed up files can be restored from backup media (tape, disk etc.) onto the desired computer (client).

Rücksicherungsassistent-Filter en.jpg

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


Searching by task name

To search for a certain task intended for restore, the selection fields task and Saved in period represented by 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 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 as well.

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
data 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
original files are not overwritten.
overwrite existing files
original 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 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 as well. The higher the number the more trace information is logged during the Restore. The SEP Sesam support can offer more options to you as well as the additional documentation 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 globally 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 database)

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.

Sofortstart einer Sicherung en.jpg


Task
Selection of a configured task
Task Group
Selection of a configured task group
Backup Type
Selection of backup type (Full, Diff, Inc, Copy)
Media Pool
Selection of a media pool the backup data should be copied to
Drive Group
the backup is executed on a drive, automatically selected by Sesam from the drive group, specified in the media pool (not editable)
Drive (opt.)
Selection of a specific drive from the selected drive group
Interface (opt.)
additional TCP/IP-Name of the source-client


Start time
Entry in the event calendar - can be modified ( Delay, etc. )
OK
insert into the event calendar
Cancel
No action and return to the start screen
Immediate Start Restore

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

Immediate Start Media Action

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

Immediate Start Command

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

Additional hints for appropriate command events can be found in the Administration Manual ( access restrictions of command events ).


Sofortstart Befehl en.jpg


Name
Run without Names
in Schedule
Run without Schedule ( one_time)
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 
opens a Window for selection of previously established Task or Order.


Sofortbefehlauswahl en.jpg

Restart of Backups

All failed backups of a Sesam backup day can be restarted within this window.


Sicherungennachstarten en.jpg


Sesam day
select a Sesam backup day
Client
select a client from which information is to be shown
Table
Restart
activates restart of backup
Server
on MasterSesam only shows information from other Sesam Servers as well
Status
reason of error
Task
name of backup task
Start time
of 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 deselect all tasks
Graph
progress bar
start time
execution time
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.

Konfiguration1 en.jpg


Defaults

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

State Filter

In State Filter categories are defined, which are shown in Backups by Status and Restores by Status.


Konfigurationvorbelegung en.jpg


Current Messages

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


Konfigurationlaufende en.jpg


Online Help

In Online Help ,the browser and reader installed on the administrators computer are assigned. These will work with the HTM- and PDF-files containing SEP sesam's online help. After entering the appropriate data the button search changes to test it, immediately allowing a check of online help.


Konfigurationonline en.jpg


Extras


Konfigurationextras en.jpg


In Extras the warning scroll text, providing broken backups and separate selection of the media filter box can be activated.


Starting with Version 3.4 the following Extras settings can be activated:

Turn off Warning Ticker for 30 Day Test or Upgrade expiration

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

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

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

Open a separate Window for Filter Settings for Media

This will display a Window for Filter criteria in s separate window to the Media Overview.

User Selection of Disk Group Interfaces


Konfigurationdefault en.jpg


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


Settings The Guide Settings will normally not be 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_ Media in directory specific storage devices ( HDD, diskette, also virtual etc. )
DAT 4mm Technique ( Digital Audio Tapes )
DLT 1/2 Zoll Technique
EXA Exabyte 8mm Technique
LTO LTO-Technique
SLR QIC-Technique
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


Neuermedientyp en.jpg


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


Media Management

Medienmanagement en.jpg


Settings for emergency strategies for single tape drives are possible. If the improper media is inserted in the tape drive you can still over-write the tape on permitted media as long as it is not locked.

Remote Server

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


Note

Ths Menu Option is only available in the Sesam Version Master Sesam.


Remoteserver en.jpg


Server Name
Name of additional Sesam server in the network
Connection
Server is on the network (green = ON, red = Broken, gray = OFF)
DB-Version
Database-Version
Type
Connection type between GUI and Kernel
Operating System
of the Sesam Server

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


Remoteserverneu en.jpg


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

DB-Name 
Name of the Sesam internal database
DB-Port 
Port number for the database connection
RMI-Port 
Port number for Client-Server connection
Comment  
optional notation

Interfaces

User interfaces are small procedures of the operating system interpreter which can be programmed by the user. 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 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.

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. Sesam allows the use of Pre-, Post-, Alarm-, Notify-, and Disaster Interface to be combined into scripts. A detailed description of these interfaces with all parameters and settings can be found in 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 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 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 Sesam backup-server data is used to recover the system to a working state. To recover from this catastrophic event, Sesam provides a disaster interface.

The concept is as follows:

  • During the normal backup procedure the 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 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 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 Sesam are stored.

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

  • Reinstall Sesam from the distribution kit
  • Identify the defined location containing the last disaster backup of 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

After an unlock process triggered by the responsible support authority settings for sending emails can be configured.

Email-accounts02 en.jpg
  • Account: sesam (it's a mandatory argument here)
  • Customer: Name of the customer
  • SMTP Email Address: Mail Sender (Customer)
  • SMTP Server: Address of the Outgoing Mail Server at the customer ( also TCP/IP-Address possible )
  • E-mail user name: Account name of the Outgoing Mail Server of the customer
  • Password: Password of the Incoming Mail Server at the customer (optional) masked

input only necessary on smtp-Servers performing authentication if needed interactively

  • Recipient: Address of the responsible support pre-set at installation - not editable
  • CC: Address for copy of the email
  • BCC: Address for copy of the email - not shown to recipient



If no account name is specified it is assumed that no authorization is necessary at the SMTP-Server. The storage of the password is also optional. If it should not be saved, then it is queried when necessary in a dialog box and is used for the current session only without saving.

Protocols
Protokollierung en.jpg


Here the scope of the protocoling can be set in the lower window. Under normal conditions 'user level' is set. For support reasons, 'db level can temporarily be set' creating a more detailed output. 'develop level' is set by SEP AG support.



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

The points at this Menu relate to Window positioning in the working area to the right of the Selection - File Tree. You can show and use up to eight (8) daughter windows simultaneously. The settings are only effective if more than one window is used for work space.

For direct switching for placement use the selections Tile vertical,Tile horizontal and Cascade.

The entry Auto controls how Newly Opened windows are displayed, i.e. in the same manner as before - Underlay, Overlay and Side-by-Side.

The number of visible windows can be selected in a sub-menu - Windows.

  • 1 Window
  • 2 Windows
  • 4 Windows
  • 8 Windows
Auto Close
When the number of allowed windows has been exceeded the oldest window will be closed automatically.
Auto Scale
When opening another Window the system will recalculate the required workspace and adjust the window size accordingly.
Close
Closes the active window.
Close All
Closes all open windows.

Reuse of Window Positions

By selecting the menu choice Customize... all settings for Repeat Usage from Window Positioning as described in Adjusting the SEP sesam GUI.

Anpassen 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
Window
User Manual
Next>>>
Appendix


Help

Help can be found within the GUI under Online User Guide.


Onlinehilfe en.jpg


By using Online Support the user can register and may send listings, log files or protocols and comments via email to the support staff. Response times vary depending on the type of support contract in place and the nature of the support request.


Mailsenden en.jpg


The selection of Listings and Log Files (Protocols) occurs in the lower Dialog Window, you can view this by clicking the Protocol Switch:

Listingsundprot en.jpg


In License Info the local computer name and TCP/IP Address are shown as they are listed in the licensing module.


Lizenzinfo en.jpg

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

Notes:

  • In case of Windows setting the task's exclude_type to 'regexp' will use the PCRE matching instead of the default file 'pattern'. A path must end with '/$' to indicate a full match, e.g. 'C:/Temp/$'
  • In case of UNIX/Linux the exclude items are set according to "emacs regex mode". A path must end with '$' to indicate a full match, e.g. '/var/opt/sesam$'
  • The Metacharacters must be 'escaped' if they should match to file name characters, e.g. use '\.' to match a '.' 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

In case of Windows backup tasks the default task's exclude_type is set to 'pattern' (file pattern).

The special characters used in File Patterns matching are:

Pattern Meaning
* matches everything
 ? matches any single character
[seq] matches any character in seq
[!seq] matches any character not in seq

Notes:

  • The file pattern match is done according to FNMATCH(3) Linux Programmer's Manual with flags FNM_FILE_NAME | FNM_LEADING_DIR | FNM_CASEFOLD | FNM_PERIOD | FNM_NOESCAPE.
  • An exclude with File Patterns for NetWare File System backup only allows the use of joker '*' (some characters) and '?' (one 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 entire path in the exclude list. Several excludes require a separation by commas.