Source:SEP sesam Processes
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.
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.
Description of the SEP sesam processes
sm_main status
- Windows
You can use this command on Windows to display all running processes.
C:\Program Files\SEPsesam\bin\sesam>sm_main status 2018-02-20 11:03:31: $Id: d22ec68 (HEAD, tag: v4_4_3_3_build, origin/v4_4_3_3, v 4_4_3_3) 2017-11-21 17:22:50 +0100 $ 2018-02-20 11:03:31: VERSION='server,4.4.3.48,20171205121022' 2018-02-20 11:03:31: sm_main[3664] 2018-02-20 11:03:31: Arguments: sm_main status 2018-02-20 11:03:31: Found SDS configuration file: "C:\ProgramData\SEPsesam\var\ini\stpd_conf\DDS-SESAM-SERVER12_4.ini" 2018-02-20 11:03:31: Daemons: ['qm', 'passd', 'sms', 'stpd', 'ctrl', 'sshd', 'sepuler', 'rmi', 'sds-4'] 2018-02-20 11:03:31: qm [ 4884]: online 2018-02-20 11:03:31: Found job: 2 passd 0 4932 2017-12-05 12:10:36 2018-02-20 11:03:31: passd [ 4932]: online 2018-02-20 11:03:31: Found job: 1000 sms 0 5616 2018-02-20 08:00:16 2018-02-20 11:03:31: sms [ 5616]: online 2018-02-20 11:03:31: Found job: 4 stpd 0 4012 2017-12-05 12:10:37 2018-02-20 11:03:31: stpd [ 4012]: online 2018-02-20 11:03:31: Found job: 5 ctrl 0 3420 2017-12-05 12:10:37 2018-02-20 11:03:31: ctrl [ 3420]: online 2018-02-20 11:03:31: Found job: 6 sshd 0 2776 2017-12-05 12:10:38 2018-02-20 11:03:31: sshd [ 2776]: online 2018-02-20 11:03:31: Found job: 7 sepuler 0 4828 2017-12-05 12:10:38 2018-02-20 11:03:31: sepuler [ 4828]: online 2018-02-20 11:03:31: Found job: 29 rmi 0 4484 2017-12-05 15:16:21 2018-02-20 11:03:31: rmi [ 4484]: online 2018-02-20 11:03:31: Found job: 58 sds-4 0 3036 2017-12-05 15:51:11 2018-02-20 11:03:31: sds-4 [ 3036]: online STATUS=SUCCESS MSG=All daemons online
- Linux
backup:/opt/sesam/bin/sesam # ./sm_main status 2018-02-20 11:07:39: $Id: d22ec68 (HEAD, tag: v4_4_3_3_build, origin/v4_4_3_3, v4_4_3_3) 2017-11-21 17:22:50 +0100 rev:46479 2018-02-20 11:07:39: VERSION='server,4.4.3.48,20171121173703' 2018-02-20 11:07:39: sm_main[12966] 2018-02-20 11:07:39: Arguments: ./sm_main status 2018-02-20 11:07:39: Found SDS configuration file: "/var/opt/sesam/var/ini/stpd_conf/DDS-SEPSRV-01_1.ini" 2018-02-20 11:07:39: Daemons: ['qm', 'db', 'passd', 'sms', 'stpd', 'ctrl', 'sshd', 'sepuler', 'rmi', 'ui', 'sds-1'] 2018-02-20 11:07:39: qm [ 2646]: online 2018-02-20 11:07:39: Found job: 2 db 0 2966 2018-02-09 11:54:59 2018-02-20 11:07:39: Check DB service. Retry: 1 2018-02-20 11:07:39: db [ 2966]: online 2018-02-20 11:07:39: Found job: 1139 passd 0 26921 2018-02-20 08:00:28 2018-02-20 11:07:39: passd [ 26921]: online 2018-02-20 11:07:39: Found job: 1140 sms 0 27140 2018-02-20 08:00:35 2018-02-20 11:07:39: sms [ 27140]: online 2018-02-20 11:07:39: Found job: 1138 stpd 0 26901 2018-02-20 08:00:27 2018-02-20 11:07:39: stpd [ 26901]: online 2018-02-20 11:07:39: Found job: 6 ctrl 0 5536 2018-02-09 11:55:09 2018-02-20 11:07:39: ctrl [ 5536]: online 2018-02-20 11:07:39: Found job: 7 sshd 0 5552 2018-02-09 11:55:09 2018-02-20 11:07:39: sshd [ 5552]: online 2018-02-20 11:07:39: Found job: 8 sepuler 0 5560 2018-02-09 11:55:10 2018-02-20 11:07:39: sepuler [ 5560]: online 2018-02-20 11:07:39: Found job: 9 rmi 0 5567 2018-02-09 11:55:10 2018-02-20 11:07:39: rmi [ 5567]: online 2018-02-20 11:07:39: ui : unused 2018-02-20 11:07:39: Found job: 394 sds-1 0 10289 2018-02-12 22:41:15 2018-02-20 11:07:39: sds-1 [ 10289]: online STATUS=SUCCESS MSG=All daemons online backup:/opt/sesam/bin/sesam ##
sm_main (Windows)
This is the main process of the SEP sesam structure on Windows. All other SEP sesam processes derive from it. It follows all sub-processes and possibly restarts them when they are completed. On Windows, all processes are listed in the Task Manager or in the command line as a tree view.
C:\Program Files\SEPsesam\bin\sesam>sm_list -t For process 3944 [System Process] (0) System (4) smss.exe (332) csrss.exe (440) with PPID: 432 csrss.exe (504) with PPID: 496 wininit.exe (512) with PPID: 432 services.exe (600) svchost.exe (680) vdsldr.exe (1352) WmiPrvSE.exe (3432) svchost.exe (712) svchost.exe (832) svchost.exe (856) taskhostex.exe (1420) svchost.exe (912) svchost.exe (984) svchost.exe (696) spoolsv.exe (1088) svchost.exe (1132) svchost.exe (1176) ScvmmGuestServiceV5.exe (1256) svchost.exe (1692) rdpclip.exe (928) rdpinput.exe (1376) svchost.exe (1768) svchost.exe (1804) VSSVC.exe (1920) msdtc.exe (2800) svchost.exe (2152) sm_qm_main.exe (4884) conhost.exe (2452) sm_passd.exe (4932) sm_stpd_main.exe (4012) sm_ctrld_main.exe (3420) sm_sshd.exe (2776) sm_sepuler.exe (4828) sm_sms_watch.exe (1524) sm_java.exe (4484) java.exe (1988) sm_sms_watch.exe (3692) sm_sms_watch.exe (2232) sm_sms_watch.exe (2480) sm_sms_watch.exe (4904) sm_java.exe (3036) java.exe (4700) sm_sms_watch.exe (1516) sm_sms_watch.exe (1780) sm_sms_watch.exe (5312) sm_sms_watch.exe (5952) sm_sms_watch.exe (5304) sm_sms_main.exe (5616) oodiag.exe (2292) vds.exe (5064) armsvc.exe (5776) lsass.exe (608) winlogon.exe (540) with PPID: 496 LogonUI.exe (808) dwm.exe (816) csrss.exe (3944) with PPID: 3512 winlogon.exe (2004) with PPID: 3512 dwm.exe (3996) explorer.exe (2132) with PPID: 3100 notepad.exe (948) putty.exe (2988) AcroRd32.exe (2896) AcroRd32.exe (2604) RdrCEF.exe (2204) RdrCEF.exe (5352) RdrCEF.exe (2808) powershell.exe (2516) conhost.exe (2624) notepad.exe (4224) iexplore.exe (792) iexplore.exe (3288) iexplore.exe (4896) sm_javaw.exe (2648) javaw.exe (3404) notepad.exe (3056) with PPID: 4964 cmd.exe (2384) with PPID: 4100 conhost.exe (3244) sm_list.exe (5756) AdobeARM.exe (3076) with PPID: 5544
C:\Program Files\SEPsesam\bin\sesam>
sm_qm_main
This is the main process of the SEP sesam structure on Linux/Unix. All other SEP sesam processes derive from it. It follows all sub-processes and possibly restarts them when they are completed. This process has to run on SEP sesam Server and in Linux/Unix also on RDS. The queue manager follows all individual drive queues.
backup:/opt/sesam/bin/sesam # ps -ef | grep sm root 2646 1 0 Feb09 ? 00:22:40 /opt/sesam/bin/sesam/sm_qm_main root 2966 2646 0 Feb09 ? 00:00:00 /bin/sh /opt/sesam/bin/sesam/sm_postgres root 5536 2646 0 Feb09 ? 00:00:00 /opt/sesam/bin/sesam/sm_ctrld_main root 5552 2646 0 Feb09 ? 00:04:39 /opt/sesam/bin/sesam/sm_sshd root 5553 11847 0 12:26 pts/0 00:00:00 grep --color=auto sm root 5560 2646 0 Feb09 ? 00:22:11 /opt/sesam/bin/sesam/sm_sepuler 0:00 /bin/sh /opt/sesam/bin/sesam/sm_rmi_main root 5781 5567 1 Feb09 ? 03:24:37 java -classpath /opt/sesam/bin/gui//sm_ui.jar -Dsep.sesam.config=/var/opt/sesam/var/ini/sm.ini - Djava.rmi.server.hostname=backup.local -Dfile.encoding=UTF-8 -Djava.security.policy=/var/opt/sesam/var/ini//sm_java.policy de.sep.sesam.gui.server.GUIServer -p11401 -ren root 7140 2646 0 Feb09 ? 00:02:46 /opt/sesam/bin/sesam/sm_sms_watch 0 root 9987 2646 0 Feb12 ? 00:25:32 /opt/sesam/bin/sesam/sm_sms_watch 1 root 10289 2646 19 Feb12 ? 1-11:57:15 /opt/sesam/bin/sesam/java -Xmx2855M -XX:MaxDirectMemorySize=2380M -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=1 -Dconfig.inifile=/var/opt/sesam/var/ini/stpd_conf/DDS-SEPSRV-01_1.ini i2.dedup.streaming.BinaryProtocolServer start root 10333 2646 0 Feb12 ? 00:02:48 /opt/sesam/bin/sesam/sm_sms_watch 2 root 10428 2646 0 Feb12 ? 00:03:27 /opt/sesam/bin/sesam/sm_sms_watch 3 root 10513 2646 0 Feb12 ? 00:04:04 /opt/sesam/bin/sesam/sm_sms_watch 4 root 10599 2646 0 Feb12 ? 00:02:33 /opt/sesam/bin/sesam/sm_sms_watch 5 root 26901 2646 0 08:00 ? 00:00:08 /opt/sesam/bin/sms/sm_stpd_main root 26909 26901 0 08:00 ? 00:00:00 /opt/sesam/bin/sms//sm_stpd_utl_main 0 root 26921 2646 0 08:00 ? 00:00:00 /opt/sesam/bin/sms/sm_passd root 27140 2646 0 08:00 ? 00:00:00 /opt/sesam/bin/sms/sm_sms_main root 28341 2646 0 08:00 ? 00:00:00 /opt/sesam/bin/sesam/sm_start 5 root 28497 28341 0 08:00 ? 00:00:00 sm_data_store purge -d 5 root 28622 28497 0 08:00 ? 00:00:00 sm_rexec -P prot -v 0 -L /dev/stdout backup.local sm_client dir /mnt/s3/AWS-S3/AWS-S3/AWS-S300001 root 28657 28622 0 08:00 ? 00:00:00 sm_rexec -P prot -v 0 -L /dev/stdout backup.local sm_client dir /mnt/s3/AWS-S3/AWS-S3/AWS-S300001 root 28662 28657 0 08:00 ? 00:00:00 sm_client dir /mnt/s3/AWS-S3/AWS-S3/AWS-S300001 backup:/opt/sesam/bin/sesam #
sm_ctrld_main
Via control daemon it is possible to execute SEP sesam commands on the SEP sesam Client. 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 Server, SEP sesam Client and RDS.
sm_sshd
SEP sesam provides an SSH tunnel for secure control communication. If a new backup client gets installed, the SSH daemon will be automatically started on 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
postmaster (Linux only)
This is a database server which administers SEP sesam database. This process has to run on SEP sesam Server.
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.). 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 The 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 ports 11000 (for HTTP transfer), 11001 (for FTP transfer) and 11443 (for HTTPS transfer). 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.