Archive:Configuration 3.6

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.

Configuration

The following functions are available by clicking the Configuration button.

Defaults

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

Current Messages

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

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

Extras

Following Extras settings can be activated:

Turn off Warning Ticker for 30 Day Test or Update expiration

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

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

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

Animated sidebar filter windows

On activation filterbox sidebars in the jobstatus views appear or hide floating. The float speed depends on the GUI clients performance.

User Selection of Disk Group Interfaces

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.

Retention periods

Sesam Logs

The SEP sesam log files will keep for 7 days normally. You can adjust this retention time as your needs.

Readable Checks Logs

Retention time for Readable check log files (standard: 2190 days)

Calendar sheet entries

The retention time for old calendar sheet entries is 35 days normally.

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.

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.

Media-type

Sesam internal identification of the media type

Drive-type

Sesam internal drive types

Capacity

Storage capacity of an allowed combination media / drive

Allowed Media-types

Media-type	Description
DISK_	Medien auf verzeichnisorientierten Speichergeräten ( Festplatte, Diskette, auch virtuell etc. )
DAT	4mm Technik ( Digital Audio Tapes )
DLT	1/2 Zoll Technik
EXA	Exabyte 8mm Technik
LTO	LTO-Technik
SLR	QIC-Technik

Drive-type

Drive-type	Generic Drive-type
DISK_CHNG	DISK
DISK_HARD	DISK
AIT	AIT
DLT	DLT
SDLT	DLT
DAT	DAT
DDS	DAT
EXA	EXA1
QIC	QIC
SLR	QIC
LTO	LTO
VXA	EXA2

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

Media Management

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.

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.

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 connecton

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.

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

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.

• 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 authentification 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 dialogue box and is used for the current session only without saving.

Protocols

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