Admin Manual
From SEPsesam
Contents |
Sesam directory structure
During installation Sesam creates two directory structures, one for static data and one for variable data. Both directory structures can be located in the same main directory but it is not a requirement.
Using Unix you will find the install directory in the file: /etc/sesam2000.ini.
SESAM_BIN Directory
In this directory you will find all uneditable Files including programs, templates, etc. During installation the following directory structures are created:
| Template-Files including the raw database for the initial installation | SESAM_BIN/skel
|
| Preparation files for the User Programable Interface | SESAM_BIN/skel/templates
|
| Sesam Server-components | SESAM_BIN/bin/sesam
|
| sms- and stpd-components | SESAM_BIN/bin/sms
|
| Sesam Server Gui-components | SESAM_BIN/bin/gui
|
| Sesam Server Database-components | SESAM_BIN/bin/db
|
SESAM_VAR Directory
Here you will find all data that can be changed or updated, e.g. the Sesam database, protocol and log files. During Setup the following directory structure will be created:
| Initialization Files | IV /var/ini |
| Database | IV /var/db |
| Log-Top Directory | IV /var/log |
| Temporary "Shortlived" Files | IV /var/tmp |
| Temporary Working "Medium Life" Files | IV /var/work |
Example
C:\Programme\SEPsesam
Example
A typical Sesam direcory structure after an RPM install on Linux will appear like the following list. The programs are located under: /opt/sesam, the data under /var/opt/sesam,
barometrix:~ # find /opt/sesam/ /var/opt/sesam/ -type d /opt/sesam/ /opt/sesam/bin /opt/sesam/bin/db /opt/sesam/bin/gui /opt/sesam/bin/gui/html /opt/sesam/bin/sesam /opt/sesam/bin/sms /opt/sesam/skel /opt/sesam/skel/db /opt/sesam/skel/templates ### /var/opt/sesam/ /var/opt/sesam/var /var/opt/sesam/var/ini /var/opt/sesam/var/ini/root /var/opt/sesam/var/log /var/opt/sesam/var/log/db /var/opt/sesam/var/log/lgc /var/opt/sesam/var/log/sms /var/opt/sesam/var/tmp /var/opt/sesam/var/work /var/opt/sesam/var/work/smslis /var/opt/sesam/var/work/info /var/opt/sesam/var/work/ctl /var/opt/sesam/var/work/sem /var/opt/sesam/var/times /var/opt/sesam/var/lis /var/opt/sesam/var/not /var/opt/sesam/var/qm /var/opt/sesam/var/glbv /var/opt/sesam/var/prepost /var/opt/sesam/var/prot /var/opt/sesam/var/sel /var/opt/sesam/var/db barometrix:~ #
/opt/sesam/bin /var/opt/sesam
In /var/ini the following installation files are created with relevant information and program files:
sm.ini sm_java.policy sms.ini odbc.ini debug.ini sm_lic.ini stpd.ini
Administration
Start and Stop the Sesam Server
SEPsesam has a simple interface to start and stop the server. Using sm_startup the system starts, any jobs in the queue will begin. After the startup command is entered all daemons and other services, especially the global "qu_all" are initialized and running. The command sm_startup checks the "SEPsesam" environment and initializes the disk drives by running the "sm_config_drives"
When using the sm_startup command to start the SEPsesam Server the software can now check if all Daemons and services are active by using the sm_main status command.
If some processes are not active use the command sm_main start to stop sm_startup to abort the initial startup and restart the system.
To halt the SEPsesam Server use the command sm_shutdown which calls sm_os_startup stop. This command calls sm_main stop to stop services and daemons.
Reboot Configuration (Autostart after Reboot)
SEPsesam is configured in such a way that whenever the system is rebooted it will automatically self-restart.
To turn-off the automatic restart of SEPsesam take the following action:
Unix Systems
Enter sm_setup unset_reboot. To reactivate the service for auto restart use sm_setup set_reboot.
Windows Systems
In Computer Management under Services and Applications deactivate the service for SEPsesam Server.
Master GUI
The Master GUI is used to control and monitor multiple SEP sesam server environments from a single location. The location can be local or remote, and the location does not have to have an instance of sesam server running locally. In this case we refer to a server as a Location, whereby each sesam server monitors multiple clients (servers, desktops, laptops, remote tape or disk devices).
The "Sesam Master" has an embedded second control layer which includes switches and settings to allow the control and access to the multiple server farms to be controlled by the Master GUI. All local GUI's for each sesam Server location are still available to the local administrator.
Conditions and Requirements
- all Sesam servers attached to the Master GUI must have the same main revision (e.g. 3.0.x or 3.1.x or 3.2.x)
After that the Master GUI administrator can add all of the sesam server locations (server and GUI subset locations) to the Master GUI topology with GUI-> Configuration->Remoteserver.
- Note: There is no limit to the number of Sesam server, that can be added to a single Master GUI. However, experience has shown that adding more than 10-15 locations to the Master GUI becomes extremely difficult to administer.
Description
- the GUI Client connects to a sesam server
- the names of available servers can be found in the sesam database
- the connection to the relevant servers is performed by the Master GUI
This results in the following situation:
- When the connection to the Master GUI is lost, all other connections are closed.
- Permissions must be set to allow the GUI Client connection to each monitored server (Routing, Firewalls, etc.)
Problem Description and Solution
If there is a problem connecting to a Remote Server, try to make a direct connection to the device or computer.
/opt/sesam/bin/sesam/sesam_gui -S remotesesam1
Licensing
After installing SEP sesam the customer/user has unrestricted access to the entire SEP sesam product set including all options, database modules, etc. for a period of 30 days. Seven (7) days before the end of the trial period the user will be notified that the test period is approaching its end. After the 30 day period the software's ability to backup is set to 'off'. However, the restore of any of the data stored during the period is still possible.
License requirements
To issue a license the following information for the SEP sesam server is required:
- Server name
- IP Address
- Operating System
After installation the information for the sesam server name can be found under the sesam GUI menu:
Help -> License Info or by typing ALT + L
- Packing List Number
- Hardware Platform (i386, x86, ppc, ia64, ...)
This information is found:
- for Linux console with uname -i
- for Windows use command line with set (using Windows 2003 with systeminfo)
If requested please forward this information to: sales@sepsepsoftware.com or by calling +1-303-499-0205 or +1-303-570-9358.
If you have questions during the 30 Day Installation Support period please send an email to: support@sep.de (support@sepsoftware.com) or by calling +303-499-0205. (+ 49 700 SEPSUPPORT)
License- and service documents
On top of the license file which is sent digitally (via email in most cases) license certificates for the acquired modules, update- and/or support contracts and an update-/support card are sent aswell. All the relevant information (IP-adress, server name, license details, period of validity and reaction times) is summarized clearly in these documents. These documents are sent by regular mail or if you preferr as a PDF file via email.
Changing an Existing License
In the event the Server Name or IP Address for the SEP sesam Backup Server must be changed a license transfer must be requested from SEP.
A change of server name or IP address requires that the original license has to be reissued with the new information. The relevant information regarding the current license and new information to be included on the reissued license must be sent via email asking for a "request for change" to sales@sepsoftware.com or sales@sep.de.
To avoid typographic or other errors the request submission must be made via email or in text form.
The license transfer will be performed and transmitted via email within the guaranteed reaction time of your Support or Update Agreement. All existing licenses and service contracts will be reissued and updated at the customer center. For customers with existing Support and Update Contracts there is no charge for this service.
|
In the event you are overwriting a current, existing license it is advised to make a backup copy of the current license file. In the event of errors or permisssions on the new license the previous license can be reentered to avoid downtime. |
Entering a License Key
License Keys are generally transmitted via email as an attachment "License File". After receipt of the attachment it must be loaded into the SEP sesam Server. To do so, please use the following commands:
- unzip the file sm_lic.zip on the target computer/server
- copy the file sm_lic.ini to <sesamroot>/var/ini
After copying the file the license can be verified using the sesam GUI or from the command line:
- For UNIX/Linux
#> source <SESAM_ROOT>/var/ini/sesam2000.profile #> sm_info c
- For Windows
> <SESAM_ROOT>\var\ini\sm_prof > sm_info c
The commands above allow the system administrator to verify that the license has been entered correctly.
Sesam interfaces
Sesam offers several user configurable interface programs. They can be adopted by the system administrator to perform specific activities and functions. Templates of these programs can be found in <SESAM_ROOT>/skel/templates. To activate them, all you need to do is copy them into <SESAM_ROOT>/bin/sesam.
Once copied to the proper directory they can be adopted by any texteditor.
The following interfaces are available:
| Name | Command | will be executed on |
| PRE | sbc_pre | Client |
| POST | sbc_post | Client |
| DISASTER | sm_disaster | Server |
| NOTIFY | sm_notify | Server |
| ALARM | sm_alarm | Server |
- On Windows computers all commands have the extension .cmd.
- Because the Sesam server is always a Sesam client, the PRE/POST will be executed here too.
PRE Interface
Before a backup starts, a special action can be performed on the client. Some examples are:
- notifications to various individuals or administrators
- shutdown a running application, e.g. one or multiple databases
- export a database
These activities can be accomplished with the help of the PRE command line tools.
The following example uses 10 arguments from an actual SEPsesam backup event.
| Arg.Nr | Meaning |
| 1 | Backup source |
| 2 | Device server name |
| 3 | Task name |
| 4 | Drive number |
| 5 | Backup type: copy, full, differential, incremental |
| 6 | Number of backups of this task on one sesam day |
| 7 | Saveset name |
| 8 | Medialabel |
| 9 | Mediapool |
| 10 | Schedule, which starts the task |
Return Value: Before the end of the procedure there must be either written back to Standard Output STATUS:OK or STATUS:ERROR {text}
SEPsesam checks this output for the PRE activity and proceeds with the scheduled backup task according to the setting 'Backup even if Pre fails'.
POST Interface
After a backup task has been completed the administrator can select to perform special tasks, for example:
- Start one or more Database(s)
- Send a notification that a backup has completed or finished
- Erase or clear an Export File.
These actions can be freely programmed using the Post- Interface.
SEPsesam recognizes that a backup has failed. In this even the Post- command will not be completed.
The Post command follows with 12 Arguments from the actual SEPsesam backup task.
| Arg.Nr | Meaning / Definition |
| 1 | Backup source |
| 2 | Name of the backup Server or (Tape server interface) |
| 3 | SESAM task name |
| 4 | Disk Drive Number |
| 5 | Backup Type: C_opy, F_ull, D_ifferential, I_ncremental |
| 6 | Backup Status ( 1 = ok, 0 = error ) |
| 7 | Notification Text from Backup |
| 8 | Count of Completed Jobs for the Backup Day (= Number on the LIS File) |
| 9 | Saveset name |
| 10 | Label on the used Media |
| 11 | Media pool of the used Media |
| 12 | Schedule Time when Backup began (started) |
Before the end of the procedure either
STATUS:OK
or
STATUS:ERROR {text} must be written in Standard Output.
In the even the Post task ends with an error, the backup will be written with a "Warning" Status.
Notify
sm_notify may be called in the following examples:
- Backup was halted
- Restore was halted
- Next Media is required
As opposed to sm_alarm a call can be made after a successful action This 'call' always must follow with two parameters:
- Module name
- Message
The following module names are used
BACKUP
Called at the end of a backup.
- Message
- taskname and result of the backup
Example:
sm_notify BACKUP "kbx11_etc: successful without warnings"
BACKUP_GROUP
As soon as the last backup for a backup group is finished, the interface provides a complete status report for the backup group.
- Message
- group name and status of the backup group.
Example:
sm_notify BACKUP "Oracle_Server: 7, Error: 0, Cancelled: 0, Warning: 0, Success: 7"
ALL_JOBS_DONE
As soon as all scheduled backups for a specific backup day 'Sesam Day' have ended, the administrator can enter a command to issue an eMail with the backup status, or direct the system to unmount a tape or tape drive.
- Message
- Report status of the backup for this 'Sesam Day'
Beispiel:
sm_notify ALL_JOBS_DONE "102 Sicherungen beendet mit 23 fehlerhaften, \ 17 mit Warnungen und 62 erfolgreichen."
Example of sm_notify:
- Send an e-Mail with complete backup status
- Unload of tape drive with drivenumber 2
read_sm_ini()
{
. `grep -i '^sm_ini=' /etc/sesam2000.ini|cut -d"=" -f2` 2>/dev/null
}
read_sm_ini
source ${gv_rw_ini}/sesam2000.profile
#
echo $0 $*
myjob=$1
mymessage="$*"
#
# send mail:
#
echo "$mymessage" >> ${gv_rw_lgc}/sm_notify.lgc
#
if [ "$myjob" = "ALL_JOBS_DONE" ]
then
sm_smtp -A sesam -s "Sesam backup status: $1 $2" -M gv_dayfile: -a gv_prot:
sm_drive dismount 2 unload
fi
#
exit
GET_VOLUME
Is issued as soon as sesam requires a different media or tape which sesam cannot load automatically. For example in the case of a single tape drive where the mounted tape media has reached capacity, and another tape is required to finish the backup.
- Message
- Label for the media is required.
INIT
Is issued when a new tape or new backup device is initialized.
- Message
- Label for the initialized Media and the tape or drive used.
sm_notify INIT "I001-MEDIA INIT_1 successful initialization of the Media in Drive 1 \
with Label DISK00004 (Selecting media according to GETOLDEST)"
Alarm
sm_alarm is always called when a sesam action is unsuccessful. The module names are the same as by sm_notify
When using a single tape drive an alarm is sent after 15 minutes: sm_alarm SM_GET_VOLUME. This period of time allows the system administrator while performing a Data Recovery operation to insert the required tape media, without sending out a system alarm.
Disaster
sm_disaster is always called after the action SESAM_BACKUP. All information regarding the completed backup is passed to the program. This allows the restore of the data in the event of a complete system failure.
|
This interface should always be configured! |
Settings without GUI
Certain settings can not yet be configured by GUI.
Compressing Sesam Listing files
To save space you can compress all LIS files older than n days, in this example 3 days:
sm_db "insert into defaults (key,user_name,value) values ('compress_lis','sesam','3')"
Backup without using archive bit on Windows
Instead of using the archive bit Sesam can also use an internal timestamp. This is especially useful, if other programs also use and reset the archive bit.
sm_db "insert into defaults values ('with_archive_bit','sesam','no')"
For Unix Systems
Switch off the use of the timestamp file for UNIX backup, instead select the timestamp from the Sesam DB.
sm_db "insert into defaults values ('with_timestamp_file','sesam','no')"
Environment for sesam processes
Especially for database backups it is necessary that specific environment variables are set. This can be done through entries in the 'sm.ini under the section '[ENVIRONMENT].
... [ENVIRONMENT] LD_LIBRARY_PATH=/opt/sesam/bin/sesam:/opt/lotus/notes/latest/linux ORACLE_HOME=/opt/oracle
This settings will be read/set during sesam startup. All processes started by sesam will inherit this settings.
Disable the Alivetest
The sesame Alive test, during a backup periodically checks to see if the backup client is still online. It can be switched off with the following command:
sm_glbv w gv_ctrlc_no_alive ON
Re-activated with:
sm_glbv R gv_ctrlc_no_alive
Loader specific settings
Initialize element status
Some loaders need an additional Initialize element status command after changing media manually. To switch this on in Sesam:
sm_glbv w gv_initialize_loader_1 yes
Allow medium removal
Sometimes unload of medium from a drive is locked by prevent medium removal.
To allow media removal again:
sm_glbv w gv_scsi_<drive_num>
Sends command
slu {SCSI_ID-von-gv_scsi_{drive_num}} -a
SCSI Id of drive has to set before by
sm_glbv w gv_scsi_2 4050
Drive number 2 with SCSI Id 4050
Remote access
Configuration of a SSH client
To access a client from a Sesam server using ssh, instead of the unencrypted ctrl-connection, Sesam server has to be able to logon to the client without a password. This can be archived by public/private authentication. The configuration is described in the man pages of ssh und sshd. Using the Sesam GUI the access mode has to be changed to SSH.
Note: Browsing of the filesystem is not possible with ssh in the current version.
Command calls
Start a Backup from the Command Line
The easiest way to start a single backup task is using the program sbc_com_interface:
sbc_com_interface -b openjob:none -I backup -C <Sesam Server> -j <task> \
-m <mediapool> -l <Level (C|F|D|I)>
Example:
sbc_com_interface -b openjob:none -I backup -C buildfix -j TEST_BACKUP -m DISK -l F
starting the GUI
sesam_gui -S <Sesam Server>[<:port>] -M [0|1|2]
- -M N
- shut down the Master GUI (N=0), connect directly with several Sesam servers (N=2)
Treatment of the archive bit
Windows OS use the archive bit (A-Bit) in the data properties to manage data changes. The A-Bit is set to 1 if the file is altered. Generally Sesam does not use the archive bit although it can be forced in options with -o clear_archive if needed. Normally the time information for FULL, DIFF or INC Backups is saved in the Sesam Databank because the archive bit can be changed by other programs.
Influence on the A-Bit by the Backup type:
- Full backs up all files and sets the A-Bit to 0
- Diff only backs up files with A-Bit = 1 and leaves the A-Bit unchanged
- Inc only backs up files with A-Bit = 1 and sets the A-Bit to 0
- Copy backs up all files and leaves the A-Bit unchanged
Administrative data for the savesets
The names of the savesets are calculated unambiguously by Sesam from the time of the Backup. For the Restore an index is created for every saveset that lists, creates and administeres the Backup names and dates of the backed up files (listing). Additionally, there is the Backup protocol which contains messages about the backup and a list of files that could not be backed up due to the OS.
Following administrative data is saved with every completed Backup:
- Name from the timestamp as a definite identification of the saveset
- Task name
- Date of the Backup day
- Execution counter of the task per Backup day
- CFDI-Type Copy, Full, Diff, Inc
- Media counter - Distribution of the saveset to media
- Label of the media in use
- Drive number
- Client from which the data is backed up
- Backup source
- Start and end time
- Success state
- Size of backed up data
- Password if backed up with encryption
The success state of a Backup is visible in the column State in Backup by State.
This information can be shown throught various filters in the Sesam GUI (Backup by state, calendar sheet, etc.).
