Source:SEP sesam Processes: Difference between revisions
(Fixing transclusion.) |
(moving translation markers (fix for <span>)) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 27: | Line 27: | ||
<!--T:8--> | <!--T:8--> | ||
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. | 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.</translate> | ||
==== {{anchor|status}}Daemon summary ==== < | ==== {{anchor|status}}<translate>Daemon summary</translate> ==== | ||
<translate><!--T:10--> | |||
<!--T:10--> | |||
Use the command <tt>sm_main status</tt> 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 general version of SEP sesam and when the individual sub processes were (re)started.</translate> | Use the command <tt>sm_main status</tt> 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 general version of SEP sesam and when the individual sub processes were (re)started.</translate> | ||
Line 91: | Line 90: | ||
STATUS=SUCCESS MSG=All daemons online | STATUS=SUCCESS MSG=All daemons online | ||
=== {{anchor|description}}<translate> Description of the SEP sesam processes</translate> === | |||
==== <tt>sm_qm_main</tt>==== | ==== <tt>sm_qm_main</tt>==== | ||
Line 180: | Line 179: | ||
==== <tt>sm_ctrld_main</tt> ==== | ==== <tt>sm_ctrld_main</tt> ==== | ||
<translate><!--T:17--> 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 {{path|sm_ctrlc -l root <backup_client> sbc -b -s @/tmp/test.sav /etc}}, then a backup job of the <tt>/etc</tt> directory is started on the client. Backed up data is saved in the file <tt>test.sav</tt> in the client's local <tt>/tmp</tt> directory. This process has to run on the SEP sesam RDS and SEP sesam Clients.</translate> | <translate><!--T:17--> | ||
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 {{path|sm_ctrlc -l root <backup_client> sbc -b -s @/tmp/test.sav /etc}}, then a backup job of the <tt>/etc</tt> directory is started on the client. Backed up data is saved in the file <tt>test.sav</tt> in the client's local <tt>/tmp</tt> directory. This process has to run on the SEP sesam RDS and SEP sesam Clients. | |||
<!--T:29--> | |||
Note that from version 5.0.0 ''Jaglion V2'' this process is by deafult disabled.</translate> | |||
==== <tt>sm_sshd</tt> ==== | ==== <tt>sm_sshd</tt> ==== | ||
Line 189: | Line 192: | ||
This process has to run on the SEP sesam RDS and SEP sesam Clients.</translate> | This process has to run on the SEP sesam RDS and SEP sesam Clients.</translate> | ||
==== <tt>postmaster</tt> | ==== <tt>postmaster</tt> ==== | ||
<translate><!--T:20--> | |||
This is a database server which administers SEP sesam database. This process has to run on SEP sesam Server. | |||
<!--T:30--> | |||
Note that from version 5.0.0 ''Jaglion V2'' this process is also available on Windows.</translate> | |||
==== <tt>sm_passd</tt> ==== | ==== <tt>sm_passd</tt> ==== |
Revision as of 13:02, 29 November 2022
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.
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 general version of SEP sesam and when the individual sub processes were (re)started.
Windows
C:\Program Files\SEPsesam\bin\sesam>sm_main status 2019-04-30 19:01:34: $Id: 30e8e5a23e (HEAD -> v4_4_3_4, tag: v_4_4_3_64, tag: v4_4_3_4_build, origin/v4_4_3_4) 2018-10-22 10:30:29 +0200 $ 2019-04-30 19:01:34: VERSION='server,4.4.3.64,20190319141846' 2019-04-30 19:01:34: sm_main[5588] 2019-04-30 19:01:34: Arguments: sm_main status 2019-04-30 19:01:34: Daemons: ['qm', 'passd', 'sms', 'stpd', 'ctrl', 'sshd', 'sepuler', 'rmi'] 2019-04-30 19:01:34: qm [ 2884]: online 2019-04-30 19:01:34: Found job: 2 passd 0 4076 2019-03-19 14:27:37 2019-04-30 19:01:34: passd [ 4076]: online 2019-04-30 19:01:34: Found job: 1788 sms 0 7692 2019-04-30 08:00:18 2019-04-30 19:01:34: sms [ 7692]: online 2019-04-30 19:01:34: Found job: 4 stpd 0 4016 2019-03-19 14:27:37 2019-04-30 19:01:34: stpd [ 4016]: online 2019-04-30 19:01:34: Found job: 5 ctrl 0 2420 2019-03-19 14:27:38 2019-04-30 19:01:34: ctrl [ 2420]: online 2019-04-30 19:01:34: Found job: 6 sshd 0 2260 2019-03-19 14:27:38 2019-04-30 19:01:34: sshd [ 2260]: online 2019-04-30 19:01:34: Found job: 7 sepuler 0 3676 2019-03-19 14:27:39 2019-04-30 19:01:34: sepuler [ 3676]: online 2019-04-30 19:01:34: Found job: 8 rmi 0 7976 2019-03-19 14:27:39 2019-04-30 19:01:34: rmi [ 7976]: online 2019-04-30 19:01:34: Found job: 39 sds-11 0 6796 2019-04-30 11:42:17 2019-04-30 19:01:34: sds-11 [ 6796]: online STATUS=SUCCESS MSG=All daemons online
Linux/Unix
backupsrv:/opt/sesam/bin/sesam # ./sm_main status 2019-04-30 18:58:06: $Id: 30e8e5a (HEAD, tag: v_4_4_3_64, tag: v4_4_3_4_build, origin/v4_4_3_4, v4_4_3_4) 2018-10-22 10:30:29 +0200 rev:48355 2019-04-30 18:58:06: VERSION='server,4.4.3.64,20181024102619' 2019-04-30 18:58:06: sm_main[21443] 2019-04-30 18:58:06: Arguments: ./sm_main status 2019-04-30 18:58:06: Found SDS configuration file: "/var/opt/sesam/var/ini/stpd_conf/Si3-Store_2.ini" 2019-04-30 18:58:06: ATTENTION: Java options for SDS set in sm.ini to: -Xms10080M -Xmx10080M 2019-04-30 18:58:06: Daemons: ['qm', 'db', 'passd', 'sms', 'stpd', 'ctrl', 'sshd', 'sepuler', 'rmi', 'ui', 'sds-2'] 2019-04-30 18:58:06: qm [ 4126]: online 2019-04-30 18:58:06: Found job: 2 db 0 4137 2019-01-14 20:21:08 2019-04-30 18:58:06: Check DB service. Retry: 1 2019-04-30 18:58:06: db [ 4137]: online 2019-04-30 18:58:06: Found job: 3 passd 0 4316 2019-01-14 20:21:15 2019-04-30 18:58:06: passd [ 4316]: online 2019-04-30 18:58:06: Found job: 15 sms 0 6102 2019-01-14 20:21:37 2019-04-30 18:58:06: sms [ 6102]: online 2019-04-30 18:58:06: Found job: 5 stpd 0 4332 2019-01-14 20:21:15 2019-04-30 18:58:06: stpd [ 4332]: online 2019-04-30 18:58:06: Found job: 6 ctrl 0 4339 2019-01-14 20:21:16 2019-04-30 18:58:06: ctrl [ 4339]: online 2019-04-30 18:58:06: sshd : unused 2019-04-30 18:58:07: Found job: 25068 sepuler 0 5849 2019-03-27 17:13:23 2019-04-30 18:58:07: sepuler [ 5849]: online 2019-04-30 18:58:07: Found job: 29267 rmi 0 18503 2019-04-26 18:23:24 2019-04-30 18:58:07: rmi [ 18503]: online 2019-04-30 18:58:07: ui : unused 2019-04-30 18:58:07: Found job: 29268 sds-2 0 18618 2019-04-26 18:23:25 2019-04-30 18:58:07: sds-2 [ 18618]: 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
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.