Source:SEP sesam Processes

Overview

The following list introduces SEP sesam processes that are required for uninterrupted operation of the SEP sesam Server. You can use different commands to check the functionality of the individual processes. For example, you can use the command sm_main status to see if all daemons are running. You can also check the status of the SEP sesam processes in the GUI (Main Selection -> Monitoring -> Processes).

Note that antivirus programs may disrupt network communication and cause SEP sesam processes, such as backup and replication, to fail. One program that is known to cause SEP sesam processes to terminate is Sophos Firewall with IPS (Intrusion Prevention System) enabled. Make sure that there are no antivirus, firewall, IDS or IPS programs preventing interaction with SEP sesam.

Daemon summary

Use the command sm_main status to quickly check if all relevant daemons are running on a computer where SEP sesam is installed or if one is missing. As an additional information you can see the current version of the installed SEP sesam (incl. service pack) and when the individual subprocesses were (re)started.

Windows

C:\Program Files\SEPsesam\bin\sesam>sm_main status
2023-06-21 14:42:41: $Id: 957650feda (HEAD, origin/v5_1_0) 2023-06-12 10:19:55 +0200 $ (Python version: 3.8.10 (tags/v3.8.10:3d8993a, May  3 2021, 11:48:03) [MSC v.1928 64 bit (AMD64)])
2023-06-21 14:42:41: VERSION='server,5.1.0.6,20230613141801'
2023-06-21 14:42:41: SP=
2023-06-21 14:42:41: sm_main[33700]
2023-06-21 14:42:41: Arguments: C:\Program Files\SEPsesam\bin\sesam\sm_main.exe status
2023-06-21 14:42:41: Found SDS configuration file: "D:\ProgramData\SEPsesam\var\ini\stpd_conf\Si3-NG_4.ini"
2023-06-21 14:42:41: Java options for SDS set in sm.ini to: -Xmx8192M
2023-06-21 14:42:41: Found SDS configuration file: "D:\ProgramData\SEPsesam\var\ini\stpd_conf\Si3-supportnix_15.ini"
2023-06-21 14:42:41: Java options for SDS set in sm.ini to: -Xmx8192M
2023-06-21 14:42:41: Daemons: ['qm', 'db', 'rmi', 'passd', 'sms', 'stpd', 'ctrl', 'sshd', 'sepuler', 'sds-4', 'sds-15']
2023-06-21 14:42:41: qm         [ 11860]: online
2023-06-21 14:42:41: Found job:   1    db                    0     32924 2023-06-13 14:18:50
2023-06-21 14:42:41: Check DB service. "C:\Program Files\SEPsesam\bin\sesam\sm_db" "select * from pg_user" -o noerr Retry: 1
2023-06-21 14:42:41: db         [ 32924]: online
2023-06-21 14:42:41: Found job:   2    rmi                   0     73888 2023-06-13 14:18:56
2023-06-21 14:42:41: Check UI server. Retry: 1
2023-06-21 14:42:41: UI server is up and running
2023-06-21 14:42:41: rmi        [ 73888]: online
2023-06-21 14:42:41: Found job:   3    passd                 0     60524 2023-06-13 14:19:03
2023-06-21 14:42:41: passd      [ 60524]: online
2023-06-21 14:42:41: Found job: 926    sms                   0    108992 2023-06-20 16:29:36
2023-06-21 14:42:41: sms        [108992]: online
2023-06-21 14:42:41: Found job: 927    stpd                  0      7892 2023-06-20 16:29:37
2023-06-21 14:42:41: stpd       [  7892]: online
2023-06-21 14:42:41: Found job:   6    ctrl                  0     25608 2023-06-13 14:19:04
2023-06-21 14:42:41: ctrl       [ 25608]: online
2023-06-21 14:42:41: Found job:   7    sshd                  0     58820 2023-06-13 14:19:04
2023-06-21 14:42:41: sshd       [ 58820]: online
2023-06-21 14:42:41: Found job:   8    sepuler               0    103036 2023-06-13 14:19:05
2023-06-21 14:42:41: sepuler    [103036]: online
2023-06-21 14:42:41: Found job: 930    sds-4                 0     90272 2023-06-20 16:29:39
2023-06-21 14:42:41: sds-4      [ 90272]: online
2023-06-21 14:42:41: Found job: 931    sds-15                0     49484 2023-06-20 16:29:40
2023-06-21 14:42:41: sds-15     [ 49484]: online
STATUS=SUCCESS MSG=All daemons online

Linux/Unix

sm_main status
2023-06-21 14:43:45: $Id: 957650feda (HEAD, origin/v5_1_0) 2023-06-12 10:19:55 +0200 rev:65459 (Python version: 3.8.5 (default, Jun 12 2023, 19:29:55)  [GCC 7.3.1 20180323 [gcc-7-branch revision 258812]])
2023-06-21 14:43:45: VERSION='server,5.1.0.6,20230607152230'
2023-06-21 14:43:45: SP=
2023-06-21 14:43:45: sm_main[26435]
2023-06-21 14:43:45: Parent process: 27866 27765 -bash
2023-06-21 14:43:45: Arguments: sm_main status
2023-06-21 14:43:45: Found SDS configuration file: "/var/opt/sesam/var/ini/stpd_conf/Dedupe_29.ini"
2023-06-21 14:43:45: Found SDS configuration file: "/var/opt/sesam/var/ini/stpd_conf/Si3-NG-b11_3.ini"
2023-06-21 14:43:45: Daemons: ['qm', 'db', 'rmi', 'passd', 'sms', 'stpd', 'ctrl', 'sshd', 'sepuler', 'ui', 'sds-29', 'sds-3']
2023-06-21 14:43:45: qm         [  2859]: online
2023-06-21 14:43:45: Found job:   1    db                    0      2872 2023-06-13 14:17:58
2023-06-21 14:43:45: Check DB service. "/opt/sesam/bin/sesam/sm_db" "select * from pg_user" -o noerr Retry: 1
2023-06-21 14:43:46: db         [  2872]: online
2023-06-21 14:43:46: Found job:  65    rmi                   0     10222 2023-06-13 14:20:08
2023-06-21 14:43:46: Check UI server. Retry: 1
2023-06-21 14:43:46: UI server is up and running
2023-06-21 14:43:46: rmi        [ 10222]: online
2023-06-21 14:43:46: Found job:   3    passd                 0      3612 2023-06-13 14:18:19
2023-06-21 14:43:46: passd      [  3612]: online
2023-06-21 14:43:46: Found job:  15    sms                   0      5290 2023-06-13 14:18:47
2023-06-21 14:43:46: sms        [  5290]: online
2023-06-21 14:43:46: Found job:  16    stpd                  0      5846 2023-06-13 14:18:53
2023-06-21 14:43:46: stpd       [  5846]: online
2023-06-21 14:43:46: Found job:   6    ctrl                  0      4069 2023-06-13 14:18:19
2023-06-21 14:43:46: ctrl       [  4069]: online
2023-06-21 14:43:46: Found job:   7    sshd                  0      4076 2023-06-13 14:18:20
2023-06-21 14:43:46: sshd       [  4076]: online
2023-06-21 14:43:46: Found job: 114    sepuler               0      8563 2023-06-13 14:44:40
2023-06-21 14:43:46: sepuler    [  8563]: online
2023-06-21 14:43:46: ui                 : unused
2023-06-21 14:43:46: Found job:  20    sds-29                0      6096 2023-06-13 14:18:56
2023-06-21 14:43:46: sds-29     [  6096]: online 
2023-06-21 14:43:46: Found job:  21    sds-3                  0      6231 2023-06-13 14:18:57
2023-06-21 14:43:46: sds-3      [  6231]: online
STATUS=SUCCESS MSG=All daemons online

Description of the SEP sesam processes

sm_qm_main

This is the main process of the SEP sesam process structure. All other SEP sesam processes derive from it. The queue manager follows all individual drive queues. This process has to run on SEP sesam Server, SEP sesam RDS and SEP sesam Client.

Windows

The sm_qm_main process is associated with the service SEP Sesam visible in the Windows services list.

On Windows, all processes can be found in the Task Manager or on the command line as a tree view.

C:\Program Files\SEPsesam\bin\sesam>sm_list -t | findstr sm_
   sm_qm_main.exe (2884)
     sm_passd.exe (4076)
     sm_stpd_main.exe (4016)
     sm_ctrld_main.exe (2420)
     sm_sshd.exe (2260)
     sm_sepuler.exe (3676)
     sm_java.exe (7976)
     sm_sms_watch.exe (4556)
     sm_sms_watch.exe (4740)
     sm_sms_watch.exe (5464)
     sm_sms_watch.exe (4408)
     sm_sms_watch.exe (7024)
     sm_sms_main.exe (7692)
       sm_data_server.exe (2432)
       sm_data_server.exe (1320)
 sm_javaw.exe (3700)
 sm_list.exe (3832)

C:\Program Files\SEPsesam\bin\sesam>sm_kill list | findstr sm_
2884  (0x0B44)    "C:\Program Files\SEPsesam\bin\sesam\sm_qm_main.exe"
4076  (0x0FEC)    "C:\Program Files\SEPsesam\bin\sms\sm_passd.exe" -D
4016  (0x0FB0)    "C:\Program Files\SEPsesam\bin\sms\sm_stpd_main.exe" -D
2420  (0x0974)    "C:\Program Files\SEPsesam\bin\sesam\sm_ctrld_main.exe" -D
2260  (0x08D4)    "C:\Program Files\SEPsesam\bin\sesam\sm_sshd.exe" -D
3676  (0x0E5C)    "C:\Program Files\SEPsesam\bin\sesam\sm_sepuler.exe" -D
7976  (0x1F28)    "C:\Program Files\SEPsesam\bin\sesam\sm_java.exe" server -ren
6140  (0x17FC)    "C:\Program Files\Java\jre1.8.0_111\bin\java" -classpath "C:\Program Files\SEPsesam\bin\gui\sm_ui.jar" -Djava.rmi.server.hostname=backupsrv -Dsep.sesam.config="C:\ProgramData\SEPsesam\var\ini\sm.ini" -Djava.security.policy="C:\ProgramData\SEPsesam\var\ini\sm_java.policy" de.sep.sesam.gui.server.GUIServer -ren
4556  (0x11CC)    "C:\Program Files\SEPsesam\bin\sesam\sm_sms_watch.exe" 0
4740  (0x1284)    "C:\Program Files\SEPsesam\bin\sesam\sm_sms_watch.exe" 4
5464  (0x1558)    "C:\Program Files\SEPsesam\bin\sesam\sm_sms_watch.exe" 11
4408  (0x1138)    "C:\Program Files\SEPsesam\bin\sesam\sm_sms_watch.exe" 13
7024  (0x1B70)    "C:\Program Files\SEPsesam\bin\sesam\sm_sms_watch.exe" 14
3700  (0x0E74)    "C:\Program Files\SEPsesam\bin\sesam\sm_javaw.exe" client -uAdministrator -Sbackupsrv -lwindows -p11401 -P local -v2 -ren
4832  (0x12E0)    "C:\Program Files\Java\jre1.8.0_111\bin\javaw.exe" -Djava.io.tmpdir="C:\Users\ADMINI~1\AppData\Local\Temp\2" "-splash:C:\Program Files\SEPsesam\bin\gui\splash\splash.png" -classpath "C:\Program Files\SEPsesam\bin\gui\sm_ui.jar" de.sep.sesam.gui.client.Frame -uAdministrator -Sbackupsrv -lwindows -p11401 -P local -v2 -ren
7692  (0x1E0C)    "C:\Program Files\SEPsesam\bin\sms\sm_sms_main.exe" -D
2432  (0x0980)    sm_data_server.exe 2
1320  (0x0528)    sm_data_server.exe 3
3776  (0x0EC0)    C:\Windows\system32\cmd.exe  /K "C:\ProgramData\SEPsesam\var\ini\sm_prof.bat"
5624  (0x15F8)    sm_kill  list

PostgreSQL on Windows

If you are using PostgreSQL on Windows, first list the processes:

C:\Program Files\SEPsesam\bin\sesam>sm_list -t 
    sm_qm_main.exe (11860)
     conhost.exe (30736)
     postgres.exe (32924)
       postgres.exe (66196)
       postgres.exe (1400)
       postgres.exe (46040)
       postgres.exe (62120)
       postgres.exe (79320)
       postgres.exe (76900)
       postgres.exe (81904)
       postgres.exe (44932)
       postgres.exe (84808)
       postgres.exe (72432)
       postgres.exe (87012)
       postgres.exe (45824)

When you have the list of processes, manually search for sm_qm_main.exe and check all sub processes.

To list PostgreSQL service on Windows, execute:

sm_kill list | findstr postgres.exe 
32924  (0x809C)    "C:\Program Files\SEPsesam\bin\db\pgsql\bin\postgres.exe" -D D:\ProgramData\SEPsesam\var\db_pg
66196  (0x10294)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forklog" "5416" "5420" "0"
1400  (0x0578)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forkboot" "5284" "-x4"
46040  (0xB3D8)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forkboot" "5272" "-x3"
62120  (0xF2A8)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forkboot" "5256" "-x5"
79320  (0x135D8)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forkavlauncher" "5240"
76900  (0x12C64)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forkcol" "5224"
81904  (0x13FF0)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forkbgworker=0" "5204"
44932  (0xAF84)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forkbackend" "5604"
84808  (0x14B48)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forkbackend" "1944"
72432  (0x11AF0)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forkbackend" "3928"
87012  (0x153E4)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forkbackend" "2292"
45824  (0xB300)    "C:/Program Files/SEPsesam/bin/db/pgsql/bin/postgres.exe" "--forkbackend" "1524"

Linux/Unix

On modern Linux this process is associated with systemd unit "sepsesam.service". On systems with SysV-style init this process gets called by the init script /etc/init.d/sesam.
Use the commands pstree and ps to search for it's sub-processes.

backupsrv:/opt/sesam/bin/sesam # pstree | grep sm_
     |-sm_qm_main-+-java---98*[{java}]
     |            |-sm_ctrld_main
     |            |-sm_passd
     |            |-sm_postgres---su---postmaster---10*[postmaster]
     |            |-sm_restore
     |            |-sm_rmi_main---java---91*[{java}]
     |            |-sm_sepuler
     |            |-sm_sms_main
     |            |-4*[sm_sms_watch]
     |            `-sm_stpd_main-+-sm_stpd_utl_mai
     |                           `-4*[{sm_stpd_main}]
backupsrv:/opt/sesam/bin/sesam # ps -ef | grep sm_
root      4126     1  0 Jan14 ?        02:09:17 /opt/sesam/bin/sesam/sm_qm_main
root      4137  4126  0 Jan14 ?        00:00:00 /bin/sh /opt/sesam/bin/sesam/sm_postgres
root      4316  4126  0 Jan14 ?        00:00:00 /opt/sesam/bin/sms/sm_passd
root      4332  4126  0 Jan14 ?        17:22:30 /opt/sesam/bin/sms/sm_stpd_main
root      4339  4126  0 Jan14 ?        00:00:00 /opt/sesam/bin/sesam/sm_ctrld_main
root      4348  4332  0 Jan14 ?        00:05:51 /opt/sesam/bin/sms//sm_stpd_utl_main 0
root      4647  4126  0 Jan14 ?        00:06:00 /opt/sesam/bin/sesam/sm_sms_watch 0
root      5849  4126  0 Mar27 ?        00:21:02 /opt/sesam/bin/sesam/sm_sepuler -d
root      6102  4126  0 Jan14 ?        00:00:00 /opt/sesam/bin/sms/sm_sms_main
root      6253  4126  0 Jan14 ?        16:09:58 /opt/sesam/bin/sesam/sm_sms_watch 2
root      6404  4126  0 Jan14 ?        00:56:51 /opt/sesam/bin/sesam/sm_sms_watch 3
root     13106  4126  0 Jan18 ?        00:33:41 /opt/sesam/bin/sesam/sm_sms_watch 1
root     15092 22052  0 18:25 pts/0    00:00:00 grep --color=auto sm_
root     18503  4126  0 Apr26 ?        00:00:00 /bin/sh /opt/sesam/bin/sesam/sm_rmi_main
root     18618  4126 24 Apr26 ?        23:04:29 /opt/sesam/bin/sesam/java -Xmx5004M -XX:MaxDirectMemorySize=5204M -Xms10080M -Xmx10080M -classpath /opt/sesam/bin/sds/i2dedup-server.jar -Dlogback.configurationFile=/var/opt/sesam/var/ini/sm_sdslog.xml -Dgv_rw_stpd=/var/opt/sesam/var/log/sms -Ddrive_num=2 -Dconfig.inifile=/var/opt/sesam/var/ini/stpd_conf/Si3-Store_2.ini i2.dedup.streaming.BinaryProtocolServer start
root     18759 18503  8 Apr26 ?        07:46:53 java -classpath /opt/sesam/bin/gui//sm_ui.jar -Dsep.sesam.config=/var/opt/sesam/var/ini/sm.ini -Djava.rmi.server.hostname=backupsrv.sep.de -Dfile.encoding=UTF-8 -Djava.security.policy=/var/opt/sesam/var/ini//sm_java.policy de.sep.sesam.gui.server.GUIServer -p11401 -ren
root     29964  4126  5 17:06 ?        00:04:31 /opt/sesam/bin/sesam/sm_restore -I 20190430170610436@3Hc_4aCsINJ -r backupsrv_all-20190430_170610 -S backupsrv.sep.de -d 3

sm_ctrld_main

Via control daemon it is possible to execute SEP sesam commands on the SEP sesam Client. This daemon listens on TCP port 11301. For example, if the SEP sesam Server sends the command sm_ctrlc -l root <backup_client> sbc -b -s @/tmp/test.sav /etc, then a backup job of the /etc directory is started on the client. Backed up data is saved in the file test.sav in the client's local /tmp directory. This process has to run on the SEP sesam RDS and SEP sesam Clients.

Note that from version 5.0.0 Jaglion V2 this process is by deafult disabled.

sm_sshd

SEP sesam provides an SSH tunnel for secure control communication. If a new backup client gets installed, the SM_SSH daemon will be automatically listen on TCP port 11322. Over time, the encrypted SSH communication replaces the old unencrypted control communication. You can start a test backup on a Linux client with the following command:

sm_ssh <backup_client> sbc -b -s @/tmp/test.sav /etc

This process has to run on the SEP sesam RDS and SEP sesam Clients.

postmaster

This is a database server which administers SEP sesam database. This process has to run on SEP sesam Server.

Note that from version 5.0.0 Jaglion V2 this process is also available on Windows.

sm_passd

This is an authentication daemon for the Sesam Transfer Protocol Daemon (STPD – a service that requests the backup data from the SMS Server and manages the data flow between the SEP sesam Server and a client) via name resolution. This process has to run on SEP sesam Server and RDS. If source-side deduplication should be used this process also has to run on SEP sesam Client.

sm_rmi_main

This is the GUI server which is the interface between a GUI client and SEP sesam kernel module (like database, logfiles, etc.). It listens on TCP port 11401. This process has to run on the SEP sesam Server in order to access its database.

sm_sepuler

SEPuler is a permanently active background routine (daemon), constantly searching for events to be executed. When SEPuler finds a scheduled task or manually triggered event, the execution of the corresponding program is initiated. This process has to run on SEP sesam Server. For details, see SEPuler - an event calendar.

sm_sms_main

This is the main process of SMS (Sesam multiplex stream service) and it's the parent process for all sm_data_server processes. This process has to run on SEP sesam Server and RDS.

sm_data_server

The data server processes receive the individual data streams of the backup tasks and then transfer them multiplexed to the storage device (tape or disk). This process has to run on SEP sesam Server and RDS.

sm_stpd_main

The Sesam Transfer Protocol Daemon (STPD) waits for the data which is delivered via network from clients during a backup. It listens on TCP ports 11000 (HTTP), 11001 (FTP) and 11443 (HTTPS) for transfer of backup data. This process has to run on SEP sesam Server and RDS. If source-side deduplication should be used this process also has to run on SEP sesam Client.

sds

This is the SEP sesam deduplication engine. It depends on Java for the execution.

Copyright © SEP AG 1999-2024. 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.