https://wiki.sep.de/wiki/api.php?action=feedcontributions&user=Fho&feedformat=atomSEPsesam - User contributions [en]2024-03-28T10:31:10ZUser contributionsMediaWiki 1.38.4https://wiki.sep.de/wiki/index.php?title=4_4_3:Citrix_XenServer_Requirements_and_Configuration/de&diff=1768624 4 3:Citrix XenServer Requirements and Configuration/de2021-02-11T11:25:22Z<p>Fho: Created page with "Weitere Informationen finden Sie in der [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Dokumentation]."</p>
<hr />
<div><div class="noprint"><languages /><br />
<br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]]}}</div><br />
<br />
<br />
=={{anchor|overview}}Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Weitere Quellen</b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=4_4_3_Grolar:Citrix_XenServer_Backup]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#Citrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Wenn Sie ein Problem mit Ihrem ''Citrix XenServer'' haben, überprüfen Sie bitte das [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Citrix XenServer Troubleshooting]].<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Falls Sie eine ältere SEP sesam Version verwenden, schauen Sie bitte ins [[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]].<br />
|}</div><br />
Dieser Artikel beschreibt Anforderungen und Konfigurationsschritte für die SEP sesam Integration im Zusammenhang mit dem Citrix XenServer. Beachten Sie, dass die in diesem Artikel vorgestellten Verfahren die erforderlichen Konfigurationsschritte zur Einrichtung der Citrix XenServer SEP sesam Integration sind. Details zu den wichtigsten Funktionen der Citrix XenServer-Integration und der Sicherungs-Konfiguration finden Sie unter [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]].<br />
<br />
=={{anchor|requirements}}Voraussetzungen==<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS und Datenbank Support Matrix]] für die Liste der unterstützten Citrix XenServer Versionen.<br />
* SEP sesam Server Version 4.4.3 oder höher. Der Citrix XenServer Sicherungs-Client ist bereits in allen SEP sesam Paketen enthalten.<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardwareanforderungen]] auf dem [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] oder [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]. <br />
*Jeder XenServer muss über eine eigene '''Management-Schnittstelle''' verfügen.<br />
*In einer Cluster-Konfiguration, in der mehrere XenServer in einem Pool organisiert sind, muss der '''Pool-Master''' XenServer als ''SEP sesam Client'' konfiguriert werden.<br />
{{Anmerkung| Der Sicherungsverkehr läuft immer über die Management-Schnittstelle des XenServers. Achten Sie auf eine gute Netzwerk-Performance, z.B. 2x 10 Gbit Netzwerkschnittstellen als Bond sowohl auf dem XenServer als auch auf dem Backup-Server.}}<br />
<br />
=== {{anchor|data_mover}}SEP sesam Data Mover für Citrix XenServer (SDM-CX)===<br />
{{:Template:Data mover Citrix XenServer/de}}<br />
<br />
=={{anchor|configuration}}XenServer als SEP sesam Client einrichten== <br />
Um Ihre virtuellen Maschinen zu schützen, müssen Sie Ihren XenServer als SEP sesam Client konfigurieren. Stellen Sie sicher, dass die [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#requirements|Voraussetzungen]] erfüllt sind, bevor Sie mit der Konfiguration beginnen. Die Optionen zur Konfiguration des XenServers können je nach SEP sesam Version leicht variieren.<br />
<ol><li>Wählen Sie unter '''Auswahl''' -> '''Komponenten''' -> '''Topologie''' den entsprechenden ''Standort'' und klicken Sie auf die Schaltfläche '''Neuer Client'''. Das Fenster ''Neuer Client'' wird geöffnet.</li><br />
<li>Geben Sie im Fenster ''Neuer Client'' den DNS-Namen der '''Management-Schnittstelle des Pool-Masters''' ein. Wenn Sie den korrekten DNS-Namen des Pool-Masters nicht eingeben, funktioniert das Surfen in der XenServer-Umgebung nicht.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Plattform'' das '''UNIX'''.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Betriebssystem'' den Eintrag '''Citrix XenServer'''.</li><br />
<li>Ab SEP sesam Version 4.4.3 wird nur noch der ''Zugriffsmodus'' '''PROXY''' unterstützt, der bei Auswahl des Betriebssystems Citrix XenServer standardmäßig eingestellt ist.</li><br />
{{Anmerkung|Wenn Sie eine SEP sesam Version ≥ 4.4.3 verwenden, stellen Sie sicher, dass der Zugriffsmodus '''PROXY''' ausgewählt ist. Wird der Zugriffsmodus ''CTRL'' verwendet, tritt ein Fehler auf, wenn der SEP sesam Server die Verbindung zum SEP sesam XenServer Client prüft.}}<br />
[[image:Add_client_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf den Reiter '''Citrix XenServer''' und geben Sie die Anmeldeinformationen ''root/admin'' für den XenServer ein.</li><br />
<li>Wählen Sie einen '''Data Mover'''. Der Data Mover muss der Hostname des SEP sesam Servers oder eines RDS sein. Details zu den Anforderungen finden Sie im obigen Abschnitt [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam DataMover für den Citrix XenServer (SDM-CX)]].</li><br />
[[image:Add_client-account_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf '''OK''', um den neuen Client hinzuzufügen.</li></ol><br />
<br />
==={{anchor|https}}Auswahl von '''https''' statt '''http''' Verbindung===<br />
<br />
SEP sesam verwendet das ''http'' Protokoll als Standardverbindung, um eine bessere Performance bei der Datenübertragung vom XenServer zum SEP sesam Server zu gewährleisten. Sicherungen über ''https'' können bis zu 98% CPU-Last auf dem XenServer verursachen. <br />
<br />
Sie können das Protokoll jedoch auf die sichere ''https'' (sicher mit SSL) Verbindung umstellen, indem Sie das ''https'' Protokoll unter '''Sicherungsauftrag''' -> '''Eigenschaften''' -> '''Optionen''' im Feld '''Sicherungsoptionen''' wie folgt angeben:<br />
<br />
-a http=https<br />
<br />
<br />
==={{anchor|NBD}} NBD auf Netzwerkinterfaces für CBT konfigurieren===<br />
Ab der Version 4.4.3.84SP3 aktiviert SEP sesam NBD nicht mehr automatisch auf allen verfügbaren Netzwerkinterfaces. NBD wird für den Transport von CBT-Sicherungen benötigt.<br />
<br />
Um NBD auf allen Netzwerkinterfaces zu aktivieren, verbinden Sie sich über SSH mit dem Poolmaster und führen Sie den folgenden Befehl aus<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
Diese Konfiguration kann zu Problemen führen, wenn es Netzwerke gibt, die der SEP sesam Datamover nicht erreichen kann. Beispiele für solche Konstellationen sind Speichernetzwerke oder eine DMZ.<br />
<br />
In diesem Fall ist eine weitere Konfuration erforderlich.<br />
<br />
Dazu können die folgenden Befehle verwendet werden:<br />
<br />
* um eine Liste der verfügbaren Interfaces zu erhalten<br />
xe netzwerk-liste<br />
* um die Eigenschaften eines Netzwerks zu erfahren.<br />
xe network-param-list uuid=<Netzwerk-uuid><br />
* um NBD für eine bestimmtes Interface zu aktivieren<br />
xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* um NBD für eine bestimmtes Interface zu deaktivieren<br />
xe network-param-remove uuid=<Netzwerk-uuid> param-name=purpose param-key=nbd<br />
* um NBD für alle Interfaces zu deaktivieren<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
Weitere Informationen finden Sie in der [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Dokumentation].<br />
<br />
==Bekannte Themen==<br />
Wenn Sie Probleme mit dem Citrix XenServer haben, überprüfen Sie den [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].<br />
<br />
<div class="noprint"><br />
=={{anchor|see also}}Siehe auch==<br />
[[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]</div></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:4_4_3:Citrix_XenServer_Requirements_and_Configuration/46/de&diff=176861Translations:4 4 3:Citrix XenServer Requirements and Configuration/46/de2021-02-11T11:25:22Z<p>Fho: Created page with "Weitere Informationen finden Sie in der [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Dokumentation]."</p>
<hr />
<div>Weitere Informationen finden Sie in der [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Dokumentation].</div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3:Citrix_XenServer_Requirements_and_Configuration/de&diff=1768604 4 3:Citrix XenServer Requirements and Configuration/de2021-02-11T11:24:40Z<p>Fho: Created page with "* um eine Liste der verfügbaren Interfaces zu erhalten xe netzwerk-liste * um die Eigenschaften eines Netzwerks zu erfahren. xe network-param-list uuid=<Netzwerk-uuid> * um..."</p>
<hr />
<div><div class="noprint"><languages /><br />
<br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]]}}</div><br />
<br />
<br />
=={{anchor|overview}}Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Weitere Quellen</b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=4_4_3_Grolar:Citrix_XenServer_Backup]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#Citrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Wenn Sie ein Problem mit Ihrem ''Citrix XenServer'' haben, überprüfen Sie bitte das [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Citrix XenServer Troubleshooting]].<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Falls Sie eine ältere SEP sesam Version verwenden, schauen Sie bitte ins [[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]].<br />
|}</div><br />
Dieser Artikel beschreibt Anforderungen und Konfigurationsschritte für die SEP sesam Integration im Zusammenhang mit dem Citrix XenServer. Beachten Sie, dass die in diesem Artikel vorgestellten Verfahren die erforderlichen Konfigurationsschritte zur Einrichtung der Citrix XenServer SEP sesam Integration sind. Details zu den wichtigsten Funktionen der Citrix XenServer-Integration und der Sicherungs-Konfiguration finden Sie unter [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]].<br />
<br />
=={{anchor|requirements}}Voraussetzungen==<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS und Datenbank Support Matrix]] für die Liste der unterstützten Citrix XenServer Versionen.<br />
* SEP sesam Server Version 4.4.3 oder höher. Der Citrix XenServer Sicherungs-Client ist bereits in allen SEP sesam Paketen enthalten.<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardwareanforderungen]] auf dem [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] oder [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]. <br />
*Jeder XenServer muss über eine eigene '''Management-Schnittstelle''' verfügen.<br />
*In einer Cluster-Konfiguration, in der mehrere XenServer in einem Pool organisiert sind, muss der '''Pool-Master''' XenServer als ''SEP sesam Client'' konfiguriert werden.<br />
{{Anmerkung| Der Sicherungsverkehr läuft immer über die Management-Schnittstelle des XenServers. Achten Sie auf eine gute Netzwerk-Performance, z.B. 2x 10 Gbit Netzwerkschnittstellen als Bond sowohl auf dem XenServer als auch auf dem Backup-Server.}}<br />
<br />
=== {{anchor|data_mover}}SEP sesam Data Mover für Citrix XenServer (SDM-CX)===<br />
{{:Template:Data mover Citrix XenServer/de}}<br />
<br />
=={{anchor|configuration}}XenServer als SEP sesam Client einrichten== <br />
Um Ihre virtuellen Maschinen zu schützen, müssen Sie Ihren XenServer als SEP sesam Client konfigurieren. Stellen Sie sicher, dass die [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#requirements|Voraussetzungen]] erfüllt sind, bevor Sie mit der Konfiguration beginnen. Die Optionen zur Konfiguration des XenServers können je nach SEP sesam Version leicht variieren.<br />
<ol><li>Wählen Sie unter '''Auswahl''' -> '''Komponenten''' -> '''Topologie''' den entsprechenden ''Standort'' und klicken Sie auf die Schaltfläche '''Neuer Client'''. Das Fenster ''Neuer Client'' wird geöffnet.</li><br />
<li>Geben Sie im Fenster ''Neuer Client'' den DNS-Namen der '''Management-Schnittstelle des Pool-Masters''' ein. Wenn Sie den korrekten DNS-Namen des Pool-Masters nicht eingeben, funktioniert das Surfen in der XenServer-Umgebung nicht.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Plattform'' das '''UNIX'''.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Betriebssystem'' den Eintrag '''Citrix XenServer'''.</li><br />
<li>Ab SEP sesam Version 4.4.3 wird nur noch der ''Zugriffsmodus'' '''PROXY''' unterstützt, der bei Auswahl des Betriebssystems Citrix XenServer standardmäßig eingestellt ist.</li><br />
{{Anmerkung|Wenn Sie eine SEP sesam Version ≥ 4.4.3 verwenden, stellen Sie sicher, dass der Zugriffsmodus '''PROXY''' ausgewählt ist. Wird der Zugriffsmodus ''CTRL'' verwendet, tritt ein Fehler auf, wenn der SEP sesam Server die Verbindung zum SEP sesam XenServer Client prüft.}}<br />
[[image:Add_client_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf den Reiter '''Citrix XenServer''' und geben Sie die Anmeldeinformationen ''root/admin'' für den XenServer ein.</li><br />
<li>Wählen Sie einen '''Data Mover'''. Der Data Mover muss der Hostname des SEP sesam Servers oder eines RDS sein. Details zu den Anforderungen finden Sie im obigen Abschnitt [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam DataMover für den Citrix XenServer (SDM-CX)]].</li><br />
[[image:Add_client-account_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf '''OK''', um den neuen Client hinzuzufügen.</li></ol><br />
<br />
==={{anchor|https}}Auswahl von '''https''' statt '''http''' Verbindung===<br />
<br />
SEP sesam verwendet das ''http'' Protokoll als Standardverbindung, um eine bessere Performance bei der Datenübertragung vom XenServer zum SEP sesam Server zu gewährleisten. Sicherungen über ''https'' können bis zu 98% CPU-Last auf dem XenServer verursachen. <br />
<br />
Sie können das Protokoll jedoch auf die sichere ''https'' (sicher mit SSL) Verbindung umstellen, indem Sie das ''https'' Protokoll unter '''Sicherungsauftrag''' -> '''Eigenschaften''' -> '''Optionen''' im Feld '''Sicherungsoptionen''' wie folgt angeben:<br />
<br />
-a http=https<br />
<br />
<br />
==={{anchor|NBD}} NBD auf Netzwerkinterfaces für CBT konfigurieren===<br />
Ab der Version 4.4.3.84SP3 aktiviert SEP sesam NBD nicht mehr automatisch auf allen verfügbaren Netzwerkinterfaces. NBD wird für den Transport von CBT-Sicherungen benötigt.<br />
<br />
Um NBD auf allen Netzwerkinterfaces zu aktivieren, verbinden Sie sich über SSH mit dem Poolmaster und führen Sie den folgenden Befehl aus<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
Diese Konfiguration kann zu Problemen führen, wenn es Netzwerke gibt, die der SEP sesam Datamover nicht erreichen kann. Beispiele für solche Konstellationen sind Speichernetzwerke oder eine DMZ.<br />
<br />
In diesem Fall ist eine weitere Konfuration erforderlich.<br />
<br />
Dazu können die folgenden Befehle verwendet werden:<br />
<br />
* um eine Liste der verfügbaren Interfaces zu erhalten<br />
xe netzwerk-liste<br />
* um die Eigenschaften eines Netzwerks zu erfahren.<br />
xe network-param-list uuid=<Netzwerk-uuid><br />
* um NBD für eine bestimmtes Interface zu aktivieren<br />
xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* um NBD für eine bestimmtes Interface zu deaktivieren<br />
xe network-param-remove uuid=<Netzwerk-uuid> param-name=purpose param-key=nbd<br />
* um NBD für alle Interfaces zu deaktivieren<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
For further information consult the [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Documentation]<br />
<br />
==Bekannte Themen==<br />
Wenn Sie Probleme mit dem Citrix XenServer haben, überprüfen Sie den [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].<br />
<br />
<div class="noprint"><br />
=={{anchor|see also}}Siehe auch==<br />
[[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]</div></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:4_4_3:Citrix_XenServer_Requirements_and_Configuration/45/de&diff=176859Translations:4 4 3:Citrix XenServer Requirements and Configuration/45/de2021-02-11T11:24:40Z<p>Fho: Created page with "* um eine Liste der verfügbaren Interfaces zu erhalten xe netzwerk-liste * um die Eigenschaften eines Netzwerks zu erfahren. xe network-param-list uuid=<Netzwerk-uuid> * um..."</p>
<hr />
<div>* um eine Liste der verfügbaren Interfaces zu erhalten<br />
xe netzwerk-liste<br />
* um die Eigenschaften eines Netzwerks zu erfahren.<br />
xe network-param-list uuid=<Netzwerk-uuid><br />
* um NBD für eine bestimmtes Interface zu aktivieren<br />
xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* um NBD für eine bestimmtes Interface zu deaktivieren<br />
xe network-param-remove uuid=<Netzwerk-uuid> param-name=purpose param-key=nbd<br />
* um NBD für alle Interfaces zu deaktivieren<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done</div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3:Citrix_XenServer_Requirements_and_Configuration/de&diff=1768584 4 3:Citrix XenServer Requirements and Configuration/de2021-02-11T11:22:30Z<p>Fho: Created page with "Dazu können die folgenden Befehle verwendet werden:"</p>
<hr />
<div><div class="noprint"><languages /><br />
<br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]]}}</div><br />
<br />
<br />
=={{anchor|overview}}Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Weitere Quellen</b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=4_4_3_Grolar:Citrix_XenServer_Backup]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#Citrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Wenn Sie ein Problem mit Ihrem ''Citrix XenServer'' haben, überprüfen Sie bitte das [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Citrix XenServer Troubleshooting]].<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Falls Sie eine ältere SEP sesam Version verwenden, schauen Sie bitte ins [[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]].<br />
|}</div><br />
Dieser Artikel beschreibt Anforderungen und Konfigurationsschritte für die SEP sesam Integration im Zusammenhang mit dem Citrix XenServer. Beachten Sie, dass die in diesem Artikel vorgestellten Verfahren die erforderlichen Konfigurationsschritte zur Einrichtung der Citrix XenServer SEP sesam Integration sind. Details zu den wichtigsten Funktionen der Citrix XenServer-Integration und der Sicherungs-Konfiguration finden Sie unter [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]].<br />
<br />
=={{anchor|requirements}}Voraussetzungen==<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS und Datenbank Support Matrix]] für die Liste der unterstützten Citrix XenServer Versionen.<br />
* SEP sesam Server Version 4.4.3 oder höher. Der Citrix XenServer Sicherungs-Client ist bereits in allen SEP sesam Paketen enthalten.<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardwareanforderungen]] auf dem [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] oder [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]. <br />
*Jeder XenServer muss über eine eigene '''Management-Schnittstelle''' verfügen.<br />
*In einer Cluster-Konfiguration, in der mehrere XenServer in einem Pool organisiert sind, muss der '''Pool-Master''' XenServer als ''SEP sesam Client'' konfiguriert werden.<br />
{{Anmerkung| Der Sicherungsverkehr läuft immer über die Management-Schnittstelle des XenServers. Achten Sie auf eine gute Netzwerk-Performance, z.B. 2x 10 Gbit Netzwerkschnittstellen als Bond sowohl auf dem XenServer als auch auf dem Backup-Server.}}<br />
<br />
=== {{anchor|data_mover}}SEP sesam Data Mover für Citrix XenServer (SDM-CX)===<br />
{{:Template:Data mover Citrix XenServer/de}}<br />
<br />
=={{anchor|configuration}}XenServer als SEP sesam Client einrichten== <br />
Um Ihre virtuellen Maschinen zu schützen, müssen Sie Ihren XenServer als SEP sesam Client konfigurieren. Stellen Sie sicher, dass die [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#requirements|Voraussetzungen]] erfüllt sind, bevor Sie mit der Konfiguration beginnen. Die Optionen zur Konfiguration des XenServers können je nach SEP sesam Version leicht variieren.<br />
<ol><li>Wählen Sie unter '''Auswahl''' -> '''Komponenten''' -> '''Topologie''' den entsprechenden ''Standort'' und klicken Sie auf die Schaltfläche '''Neuer Client'''. Das Fenster ''Neuer Client'' wird geöffnet.</li><br />
<li>Geben Sie im Fenster ''Neuer Client'' den DNS-Namen der '''Management-Schnittstelle des Pool-Masters''' ein. Wenn Sie den korrekten DNS-Namen des Pool-Masters nicht eingeben, funktioniert das Surfen in der XenServer-Umgebung nicht.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Plattform'' das '''UNIX'''.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Betriebssystem'' den Eintrag '''Citrix XenServer'''.</li><br />
<li>Ab SEP sesam Version 4.4.3 wird nur noch der ''Zugriffsmodus'' '''PROXY''' unterstützt, der bei Auswahl des Betriebssystems Citrix XenServer standardmäßig eingestellt ist.</li><br />
{{Anmerkung|Wenn Sie eine SEP sesam Version ≥ 4.4.3 verwenden, stellen Sie sicher, dass der Zugriffsmodus '''PROXY''' ausgewählt ist. Wird der Zugriffsmodus ''CTRL'' verwendet, tritt ein Fehler auf, wenn der SEP sesam Server die Verbindung zum SEP sesam XenServer Client prüft.}}<br />
[[image:Add_client_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf den Reiter '''Citrix XenServer''' und geben Sie die Anmeldeinformationen ''root/admin'' für den XenServer ein.</li><br />
<li>Wählen Sie einen '''Data Mover'''. Der Data Mover muss der Hostname des SEP sesam Servers oder eines RDS sein. Details zu den Anforderungen finden Sie im obigen Abschnitt [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam DataMover für den Citrix XenServer (SDM-CX)]].</li><br />
[[image:Add_client-account_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf '''OK''', um den neuen Client hinzuzufügen.</li></ol><br />
<br />
==={{anchor|https}}Auswahl von '''https''' statt '''http''' Verbindung===<br />
<br />
SEP sesam verwendet das ''http'' Protokoll als Standardverbindung, um eine bessere Performance bei der Datenübertragung vom XenServer zum SEP sesam Server zu gewährleisten. Sicherungen über ''https'' können bis zu 98% CPU-Last auf dem XenServer verursachen. <br />
<br />
Sie können das Protokoll jedoch auf die sichere ''https'' (sicher mit SSL) Verbindung umstellen, indem Sie das ''https'' Protokoll unter '''Sicherungsauftrag''' -> '''Eigenschaften''' -> '''Optionen''' im Feld '''Sicherungsoptionen''' wie folgt angeben:<br />
<br />
-a http=https<br />
<br />
<br />
==={{anchor|NBD}} NBD auf Netzwerkinterfaces für CBT konfigurieren===<br />
Ab der Version 4.4.3.84SP3 aktiviert SEP sesam NBD nicht mehr automatisch auf allen verfügbaren Netzwerkinterfaces. NBD wird für den Transport von CBT-Sicherungen benötigt.<br />
<br />
Um NBD auf allen Netzwerkinterfaces zu aktivieren, verbinden Sie sich über SSH mit dem Poolmaster und führen Sie den folgenden Befehl aus<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
Diese Konfiguration kann zu Problemen führen, wenn es Netzwerke gibt, die der SEP sesam Datamover nicht erreichen kann. Beispiele für solche Konstellationen sind Speichernetzwerke oder eine DMZ.<br />
<br />
In diesem Fall ist eine weitere Konfuration erforderlich.<br />
<br />
Dazu können die folgenden Befehle verwendet werden:<br />
<br />
* to get a list of available interfaces<br />
xe network-list<br />
* to get the properties of a network<br />
xe network-param-list uuid=<network-uuid><br />
* to enable NBD for a specific interface<br />
xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to disable NBD for a specific interface<br />
xe network-param-remove uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to deactivate NBD for all interfaces<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
For further information consult the [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Documentation]<br />
<br />
==Bekannte Themen==<br />
Wenn Sie Probleme mit dem Citrix XenServer haben, überprüfen Sie den [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].<br />
<br />
<div class="noprint"><br />
=={{anchor|see also}}Siehe auch==<br />
[[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]</div></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:4_4_3:Citrix_XenServer_Requirements_and_Configuration/44/de&diff=176857Translations:4 4 3:Citrix XenServer Requirements and Configuration/44/de2021-02-11T11:22:30Z<p>Fho: Created page with "Dazu können die folgenden Befehle verwendet werden:"</p>
<hr />
<div>Dazu können die folgenden Befehle verwendet werden:</div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3:Citrix_XenServer_Requirements_and_Configuration/de&diff=1768564 4 3:Citrix XenServer Requirements and Configuration/de2021-02-11T11:22:19Z<p>Fho: Created page with "In diesem Fall ist eine weitere Konfuration erforderlich."</p>
<hr />
<div><div class="noprint"><languages /><br />
<br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]]}}</div><br />
<br />
<br />
=={{anchor|overview}}Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Weitere Quellen</b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=4_4_3_Grolar:Citrix_XenServer_Backup]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#Citrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Wenn Sie ein Problem mit Ihrem ''Citrix XenServer'' haben, überprüfen Sie bitte das [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Citrix XenServer Troubleshooting]].<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Falls Sie eine ältere SEP sesam Version verwenden, schauen Sie bitte ins [[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]].<br />
|}</div><br />
Dieser Artikel beschreibt Anforderungen und Konfigurationsschritte für die SEP sesam Integration im Zusammenhang mit dem Citrix XenServer. Beachten Sie, dass die in diesem Artikel vorgestellten Verfahren die erforderlichen Konfigurationsschritte zur Einrichtung der Citrix XenServer SEP sesam Integration sind. Details zu den wichtigsten Funktionen der Citrix XenServer-Integration und der Sicherungs-Konfiguration finden Sie unter [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]].<br />
<br />
=={{anchor|requirements}}Voraussetzungen==<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS und Datenbank Support Matrix]] für die Liste der unterstützten Citrix XenServer Versionen.<br />
* SEP sesam Server Version 4.4.3 oder höher. Der Citrix XenServer Sicherungs-Client ist bereits in allen SEP sesam Paketen enthalten.<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardwareanforderungen]] auf dem [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] oder [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]. <br />
*Jeder XenServer muss über eine eigene '''Management-Schnittstelle''' verfügen.<br />
*In einer Cluster-Konfiguration, in der mehrere XenServer in einem Pool organisiert sind, muss der '''Pool-Master''' XenServer als ''SEP sesam Client'' konfiguriert werden.<br />
{{Anmerkung| Der Sicherungsverkehr läuft immer über die Management-Schnittstelle des XenServers. Achten Sie auf eine gute Netzwerk-Performance, z.B. 2x 10 Gbit Netzwerkschnittstellen als Bond sowohl auf dem XenServer als auch auf dem Backup-Server.}}<br />
<br />
=== {{anchor|data_mover}}SEP sesam Data Mover für Citrix XenServer (SDM-CX)===<br />
{{:Template:Data mover Citrix XenServer/de}}<br />
<br />
=={{anchor|configuration}}XenServer als SEP sesam Client einrichten== <br />
Um Ihre virtuellen Maschinen zu schützen, müssen Sie Ihren XenServer als SEP sesam Client konfigurieren. Stellen Sie sicher, dass die [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#requirements|Voraussetzungen]] erfüllt sind, bevor Sie mit der Konfiguration beginnen. Die Optionen zur Konfiguration des XenServers können je nach SEP sesam Version leicht variieren.<br />
<ol><li>Wählen Sie unter '''Auswahl''' -> '''Komponenten''' -> '''Topologie''' den entsprechenden ''Standort'' und klicken Sie auf die Schaltfläche '''Neuer Client'''. Das Fenster ''Neuer Client'' wird geöffnet.</li><br />
<li>Geben Sie im Fenster ''Neuer Client'' den DNS-Namen der '''Management-Schnittstelle des Pool-Masters''' ein. Wenn Sie den korrekten DNS-Namen des Pool-Masters nicht eingeben, funktioniert das Surfen in der XenServer-Umgebung nicht.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Plattform'' das '''UNIX'''.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Betriebssystem'' den Eintrag '''Citrix XenServer'''.</li><br />
<li>Ab SEP sesam Version 4.4.3 wird nur noch der ''Zugriffsmodus'' '''PROXY''' unterstützt, der bei Auswahl des Betriebssystems Citrix XenServer standardmäßig eingestellt ist.</li><br />
{{Anmerkung|Wenn Sie eine SEP sesam Version ≥ 4.4.3 verwenden, stellen Sie sicher, dass der Zugriffsmodus '''PROXY''' ausgewählt ist. Wird der Zugriffsmodus ''CTRL'' verwendet, tritt ein Fehler auf, wenn der SEP sesam Server die Verbindung zum SEP sesam XenServer Client prüft.}}<br />
[[image:Add_client_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf den Reiter '''Citrix XenServer''' und geben Sie die Anmeldeinformationen ''root/admin'' für den XenServer ein.</li><br />
<li>Wählen Sie einen '''Data Mover'''. Der Data Mover muss der Hostname des SEP sesam Servers oder eines RDS sein. Details zu den Anforderungen finden Sie im obigen Abschnitt [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam DataMover für den Citrix XenServer (SDM-CX)]].</li><br />
[[image:Add_client-account_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf '''OK''', um den neuen Client hinzuzufügen.</li></ol><br />
<br />
==={{anchor|https}}Auswahl von '''https''' statt '''http''' Verbindung===<br />
<br />
SEP sesam verwendet das ''http'' Protokoll als Standardverbindung, um eine bessere Performance bei der Datenübertragung vom XenServer zum SEP sesam Server zu gewährleisten. Sicherungen über ''https'' können bis zu 98% CPU-Last auf dem XenServer verursachen. <br />
<br />
Sie können das Protokoll jedoch auf die sichere ''https'' (sicher mit SSL) Verbindung umstellen, indem Sie das ''https'' Protokoll unter '''Sicherungsauftrag''' -> '''Eigenschaften''' -> '''Optionen''' im Feld '''Sicherungsoptionen''' wie folgt angeben:<br />
<br />
-a http=https<br />
<br />
<br />
==={{anchor|NBD}} NBD auf Netzwerkinterfaces für CBT konfigurieren===<br />
Ab der Version 4.4.3.84SP3 aktiviert SEP sesam NBD nicht mehr automatisch auf allen verfügbaren Netzwerkinterfaces. NBD wird für den Transport von CBT-Sicherungen benötigt.<br />
<br />
Um NBD auf allen Netzwerkinterfaces zu aktivieren, verbinden Sie sich über SSH mit dem Poolmaster und führen Sie den folgenden Befehl aus<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
Diese Konfiguration kann zu Problemen führen, wenn es Netzwerke gibt, die der SEP sesam Datamover nicht erreichen kann. Beispiele für solche Konstellationen sind Speichernetzwerke oder eine DMZ.<br />
<br />
In diesem Fall ist eine weitere Konfuration erforderlich.<br />
<br />
The following commands can be used to accomplish this:<br />
<br />
* to get a list of available interfaces<br />
xe network-list<br />
* to get the properties of a network<br />
xe network-param-list uuid=<network-uuid><br />
* to enable NBD for a specific interface<br />
xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to disable NBD for a specific interface<br />
xe network-param-remove uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to deactivate NBD for all interfaces<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
For further information consult the [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Documentation]<br />
<br />
==Bekannte Themen==<br />
Wenn Sie Probleme mit dem Citrix XenServer haben, überprüfen Sie den [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].<br />
<br />
<div class="noprint"><br />
=={{anchor|see also}}Siehe auch==<br />
[[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]</div></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:4_4_3:Citrix_XenServer_Requirements_and_Configuration/43/de&diff=176855Translations:4 4 3:Citrix XenServer Requirements and Configuration/43/de2021-02-11T11:22:19Z<p>Fho: Created page with "In diesem Fall ist eine weitere Konfuration erforderlich."</p>
<hr />
<div>In diesem Fall ist eine weitere Konfuration erforderlich.</div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3:Citrix_XenServer_Requirements_and_Configuration/de&diff=1768544 4 3:Citrix XenServer Requirements and Configuration/de2021-02-11T11:22:07Z<p>Fho: Created page with "Diese Konfiguration kann zu Problemen führen, wenn es Netzwerke gibt, die der SEP sesam Datamover nicht erreichen kann. Beispiele für solche Konstellationen sind Speichernet..."</p>
<hr />
<div><div class="noprint"><languages /><br />
<br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]]}}</div><br />
<br />
<br />
=={{anchor|overview}}Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Weitere Quellen</b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=4_4_3_Grolar:Citrix_XenServer_Backup]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#Citrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Wenn Sie ein Problem mit Ihrem ''Citrix XenServer'' haben, überprüfen Sie bitte das [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Citrix XenServer Troubleshooting]].<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Falls Sie eine ältere SEP sesam Version verwenden, schauen Sie bitte ins [[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]].<br />
|}</div><br />
Dieser Artikel beschreibt Anforderungen und Konfigurationsschritte für die SEP sesam Integration im Zusammenhang mit dem Citrix XenServer. Beachten Sie, dass die in diesem Artikel vorgestellten Verfahren die erforderlichen Konfigurationsschritte zur Einrichtung der Citrix XenServer SEP sesam Integration sind. Details zu den wichtigsten Funktionen der Citrix XenServer-Integration und der Sicherungs-Konfiguration finden Sie unter [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]].<br />
<br />
=={{anchor|requirements}}Voraussetzungen==<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS und Datenbank Support Matrix]] für die Liste der unterstützten Citrix XenServer Versionen.<br />
* SEP sesam Server Version 4.4.3 oder höher. Der Citrix XenServer Sicherungs-Client ist bereits in allen SEP sesam Paketen enthalten.<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardwareanforderungen]] auf dem [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] oder [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]. <br />
*Jeder XenServer muss über eine eigene '''Management-Schnittstelle''' verfügen.<br />
*In einer Cluster-Konfiguration, in der mehrere XenServer in einem Pool organisiert sind, muss der '''Pool-Master''' XenServer als ''SEP sesam Client'' konfiguriert werden.<br />
{{Anmerkung| Der Sicherungsverkehr läuft immer über die Management-Schnittstelle des XenServers. Achten Sie auf eine gute Netzwerk-Performance, z.B. 2x 10 Gbit Netzwerkschnittstellen als Bond sowohl auf dem XenServer als auch auf dem Backup-Server.}}<br />
<br />
=== {{anchor|data_mover}}SEP sesam Data Mover für Citrix XenServer (SDM-CX)===<br />
{{:Template:Data mover Citrix XenServer/de}}<br />
<br />
=={{anchor|configuration}}XenServer als SEP sesam Client einrichten== <br />
Um Ihre virtuellen Maschinen zu schützen, müssen Sie Ihren XenServer als SEP sesam Client konfigurieren. Stellen Sie sicher, dass die [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#requirements|Voraussetzungen]] erfüllt sind, bevor Sie mit der Konfiguration beginnen. Die Optionen zur Konfiguration des XenServers können je nach SEP sesam Version leicht variieren.<br />
<ol><li>Wählen Sie unter '''Auswahl''' -> '''Komponenten''' -> '''Topologie''' den entsprechenden ''Standort'' und klicken Sie auf die Schaltfläche '''Neuer Client'''. Das Fenster ''Neuer Client'' wird geöffnet.</li><br />
<li>Geben Sie im Fenster ''Neuer Client'' den DNS-Namen der '''Management-Schnittstelle des Pool-Masters''' ein. Wenn Sie den korrekten DNS-Namen des Pool-Masters nicht eingeben, funktioniert das Surfen in der XenServer-Umgebung nicht.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Plattform'' das '''UNIX'''.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Betriebssystem'' den Eintrag '''Citrix XenServer'''.</li><br />
<li>Ab SEP sesam Version 4.4.3 wird nur noch der ''Zugriffsmodus'' '''PROXY''' unterstützt, der bei Auswahl des Betriebssystems Citrix XenServer standardmäßig eingestellt ist.</li><br />
{{Anmerkung|Wenn Sie eine SEP sesam Version ≥ 4.4.3 verwenden, stellen Sie sicher, dass der Zugriffsmodus '''PROXY''' ausgewählt ist. Wird der Zugriffsmodus ''CTRL'' verwendet, tritt ein Fehler auf, wenn der SEP sesam Server die Verbindung zum SEP sesam XenServer Client prüft.}}<br />
[[image:Add_client_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf den Reiter '''Citrix XenServer''' und geben Sie die Anmeldeinformationen ''root/admin'' für den XenServer ein.</li><br />
<li>Wählen Sie einen '''Data Mover'''. Der Data Mover muss der Hostname des SEP sesam Servers oder eines RDS sein. Details zu den Anforderungen finden Sie im obigen Abschnitt [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam DataMover für den Citrix XenServer (SDM-CX)]].</li><br />
[[image:Add_client-account_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf '''OK''', um den neuen Client hinzuzufügen.</li></ol><br />
<br />
==={{anchor|https}}Auswahl von '''https''' statt '''http''' Verbindung===<br />
<br />
SEP sesam verwendet das ''http'' Protokoll als Standardverbindung, um eine bessere Performance bei der Datenübertragung vom XenServer zum SEP sesam Server zu gewährleisten. Sicherungen über ''https'' können bis zu 98% CPU-Last auf dem XenServer verursachen. <br />
<br />
Sie können das Protokoll jedoch auf die sichere ''https'' (sicher mit SSL) Verbindung umstellen, indem Sie das ''https'' Protokoll unter '''Sicherungsauftrag''' -> '''Eigenschaften''' -> '''Optionen''' im Feld '''Sicherungsoptionen''' wie folgt angeben:<br />
<br />
-a http=https<br />
<br />
<br />
==={{anchor|NBD}} NBD auf Netzwerkinterfaces für CBT konfigurieren===<br />
Ab der Version 4.4.3.84SP3 aktiviert SEP sesam NBD nicht mehr automatisch auf allen verfügbaren Netzwerkinterfaces. NBD wird für den Transport von CBT-Sicherungen benötigt.<br />
<br />
Um NBD auf allen Netzwerkinterfaces zu aktivieren, verbinden Sie sich über SSH mit dem Poolmaster und führen Sie den folgenden Befehl aus<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
Diese Konfiguration kann zu Problemen führen, wenn es Netzwerke gibt, die der SEP sesam Datamover nicht erreichen kann. Beispiele für solche Konstellationen sind Speichernetzwerke oder eine DMZ.<br />
<br />
In that case further confuration is needed.<br />
<br />
The following commands can be used to accomplish this:<br />
<br />
* to get a list of available interfaces<br />
xe network-list<br />
* to get the properties of a network<br />
xe network-param-list uuid=<network-uuid><br />
* to enable NBD for a specific interface<br />
xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to disable NBD for a specific interface<br />
xe network-param-remove uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to deactivate NBD for all interfaces<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
For further information consult the [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Documentation]<br />
<br />
==Bekannte Themen==<br />
Wenn Sie Probleme mit dem Citrix XenServer haben, überprüfen Sie den [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].<br />
<br />
<div class="noprint"><br />
=={{anchor|see also}}Siehe auch==<br />
[[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]</div></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:4_4_3:Citrix_XenServer_Requirements_and_Configuration/42/de&diff=176853Translations:4 4 3:Citrix XenServer Requirements and Configuration/42/de2021-02-11T11:22:07Z<p>Fho: Created page with "Diese Konfiguration kann zu Problemen führen, wenn es Netzwerke gibt, die der SEP sesam Datamover nicht erreichen kann. Beispiele für solche Konstellationen sind Speichernet..."</p>
<hr />
<div>Diese Konfiguration kann zu Problemen führen, wenn es Netzwerke gibt, die der SEP sesam Datamover nicht erreichen kann. Beispiele für solche Konstellationen sind Speichernetzwerke oder eine DMZ.</div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3:Citrix_XenServer_Requirements_and_Configuration/de&diff=1768524 4 3:Citrix XenServer Requirements and Configuration/de2021-02-11T11:21:37Z<p>Fho: Created page with "Um NBD auf allen Netzwerkinterfaces zu aktivieren, verbinden Sie sich über SSH mit dem Poolmaster und führen Sie den folgenden Befehl aus for uuid in $(xe network-list | gr..."</p>
<hr />
<div><div class="noprint"><languages /><br />
<br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]]}}</div><br />
<br />
<br />
=={{anchor|overview}}Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Weitere Quellen</b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=4_4_3_Grolar:Citrix_XenServer_Backup]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#Citrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Wenn Sie ein Problem mit Ihrem ''Citrix XenServer'' haben, überprüfen Sie bitte das [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Citrix XenServer Troubleshooting]].<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Falls Sie eine ältere SEP sesam Version verwenden, schauen Sie bitte ins [[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]].<br />
|}</div><br />
Dieser Artikel beschreibt Anforderungen und Konfigurationsschritte für die SEP sesam Integration im Zusammenhang mit dem Citrix XenServer. Beachten Sie, dass die in diesem Artikel vorgestellten Verfahren die erforderlichen Konfigurationsschritte zur Einrichtung der Citrix XenServer SEP sesam Integration sind. Details zu den wichtigsten Funktionen der Citrix XenServer-Integration und der Sicherungs-Konfiguration finden Sie unter [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]].<br />
<br />
=={{anchor|requirements}}Voraussetzungen==<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS und Datenbank Support Matrix]] für die Liste der unterstützten Citrix XenServer Versionen.<br />
* SEP sesam Server Version 4.4.3 oder höher. Der Citrix XenServer Sicherungs-Client ist bereits in allen SEP sesam Paketen enthalten.<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardwareanforderungen]] auf dem [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] oder [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]. <br />
*Jeder XenServer muss über eine eigene '''Management-Schnittstelle''' verfügen.<br />
*In einer Cluster-Konfiguration, in der mehrere XenServer in einem Pool organisiert sind, muss der '''Pool-Master''' XenServer als ''SEP sesam Client'' konfiguriert werden.<br />
{{Anmerkung| Der Sicherungsverkehr läuft immer über die Management-Schnittstelle des XenServers. Achten Sie auf eine gute Netzwerk-Performance, z.B. 2x 10 Gbit Netzwerkschnittstellen als Bond sowohl auf dem XenServer als auch auf dem Backup-Server.}}<br />
<br />
=== {{anchor|data_mover}}SEP sesam Data Mover für Citrix XenServer (SDM-CX)===<br />
{{:Template:Data mover Citrix XenServer/de}}<br />
<br />
=={{anchor|configuration}}XenServer als SEP sesam Client einrichten== <br />
Um Ihre virtuellen Maschinen zu schützen, müssen Sie Ihren XenServer als SEP sesam Client konfigurieren. Stellen Sie sicher, dass die [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#requirements|Voraussetzungen]] erfüllt sind, bevor Sie mit der Konfiguration beginnen. Die Optionen zur Konfiguration des XenServers können je nach SEP sesam Version leicht variieren.<br />
<ol><li>Wählen Sie unter '''Auswahl''' -> '''Komponenten''' -> '''Topologie''' den entsprechenden ''Standort'' und klicken Sie auf die Schaltfläche '''Neuer Client'''. Das Fenster ''Neuer Client'' wird geöffnet.</li><br />
<li>Geben Sie im Fenster ''Neuer Client'' den DNS-Namen der '''Management-Schnittstelle des Pool-Masters''' ein. Wenn Sie den korrekten DNS-Namen des Pool-Masters nicht eingeben, funktioniert das Surfen in der XenServer-Umgebung nicht.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Plattform'' das '''UNIX'''.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Betriebssystem'' den Eintrag '''Citrix XenServer'''.</li><br />
<li>Ab SEP sesam Version 4.4.3 wird nur noch der ''Zugriffsmodus'' '''PROXY''' unterstützt, der bei Auswahl des Betriebssystems Citrix XenServer standardmäßig eingestellt ist.</li><br />
{{Anmerkung|Wenn Sie eine SEP sesam Version ≥ 4.4.3 verwenden, stellen Sie sicher, dass der Zugriffsmodus '''PROXY''' ausgewählt ist. Wird der Zugriffsmodus ''CTRL'' verwendet, tritt ein Fehler auf, wenn der SEP sesam Server die Verbindung zum SEP sesam XenServer Client prüft.}}<br />
[[image:Add_client_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf den Reiter '''Citrix XenServer''' und geben Sie die Anmeldeinformationen ''root/admin'' für den XenServer ein.</li><br />
<li>Wählen Sie einen '''Data Mover'''. Der Data Mover muss der Hostname des SEP sesam Servers oder eines RDS sein. Details zu den Anforderungen finden Sie im obigen Abschnitt [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam DataMover für den Citrix XenServer (SDM-CX)]].</li><br />
[[image:Add_client-account_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf '''OK''', um den neuen Client hinzuzufügen.</li></ol><br />
<br />
==={{anchor|https}}Auswahl von '''https''' statt '''http''' Verbindung===<br />
<br />
SEP sesam verwendet das ''http'' Protokoll als Standardverbindung, um eine bessere Performance bei der Datenübertragung vom XenServer zum SEP sesam Server zu gewährleisten. Sicherungen über ''https'' können bis zu 98% CPU-Last auf dem XenServer verursachen. <br />
<br />
Sie können das Protokoll jedoch auf die sichere ''https'' (sicher mit SSL) Verbindung umstellen, indem Sie das ''https'' Protokoll unter '''Sicherungsauftrag''' -> '''Eigenschaften''' -> '''Optionen''' im Feld '''Sicherungsoptionen''' wie folgt angeben:<br />
<br />
-a http=https<br />
<br />
<br />
==={{anchor|NBD}} NBD auf Netzwerkinterfaces für CBT konfigurieren===<br />
Ab der Version 4.4.3.84SP3 aktiviert SEP sesam NBD nicht mehr automatisch auf allen verfügbaren Netzwerkinterfaces. NBD wird für den Transport von CBT-Sicherungen benötigt.<br />
<br />
Um NBD auf allen Netzwerkinterfaces zu aktivieren, verbinden Sie sich über SSH mit dem Poolmaster und führen Sie den folgenden Befehl aus<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
This configuration may cause problems, when there are networks the SEP sesam Datamover cannot reach. Examples for such constellations are storage networks or a DMZ.<br />
<br />
In that case further confuration is needed.<br />
<br />
The following commands can be used to accomplish this:<br />
<br />
* to get a list of available interfaces<br />
xe network-list<br />
* to get the properties of a network<br />
xe network-param-list uuid=<network-uuid><br />
* to enable NBD for a specific interface<br />
xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to disable NBD for a specific interface<br />
xe network-param-remove uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to deactivate NBD for all interfaces<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
For further information consult the [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Documentation]<br />
<br />
==Bekannte Themen==<br />
Wenn Sie Probleme mit dem Citrix XenServer haben, überprüfen Sie den [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].<br />
<br />
<div class="noprint"><br />
=={{anchor|see also}}Siehe auch==<br />
[[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]</div></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:4_4_3:Citrix_XenServer_Requirements_and_Configuration/41/de&diff=176851Translations:4 4 3:Citrix XenServer Requirements and Configuration/41/de2021-02-11T11:21:37Z<p>Fho: Created page with "Um NBD auf allen Netzwerkinterfaces zu aktivieren, verbinden Sie sich über SSH mit dem Poolmaster und führen Sie den folgenden Befehl aus for uuid in $(xe network-list | gr..."</p>
<hr />
<div>Um NBD auf allen Netzwerkinterfaces zu aktivieren, verbinden Sie sich über SSH mit dem Poolmaster und führen Sie den folgenden Befehl aus<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done</div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3:Citrix_XenServer_Requirements_and_Configuration/de&diff=1768504 4 3:Citrix XenServer Requirements and Configuration/de2021-02-11T11:20:49Z<p>Fho: Created page with "==={{anchor|NBD}} NBD auf Netzwerkinterfaces für CBT konfigurieren=== Ab der Version 4.4.3.84SP3 aktiviert SEP sesam NBD nicht mehr automatisch auf allen verfügbaren Netzwer..."</p>
<hr />
<div><div class="noprint"><languages /><br />
<br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]]}}</div><br />
<br />
<br />
=={{anchor|overview}}Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Weitere Quellen</b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=4_4_3_Grolar:Citrix_XenServer_Backup]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#Citrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Wenn Sie ein Problem mit Ihrem ''Citrix XenServer'' haben, überprüfen Sie bitte das [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Citrix XenServer Troubleshooting]].<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Falls Sie eine ältere SEP sesam Version verwenden, schauen Sie bitte ins [[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer Archiv]].<br />
|}</div><br />
Dieser Artikel beschreibt Anforderungen und Konfigurationsschritte für die SEP sesam Integration im Zusammenhang mit dem Citrix XenServer. Beachten Sie, dass die in diesem Artikel vorgestellten Verfahren die erforderlichen Konfigurationsschritte zur Einrichtung der Citrix XenServer SEP sesam Integration sind. Details zu den wichtigsten Funktionen der Citrix XenServer-Integration und der Sicherungs-Konfiguration finden Sie unter [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]].<br />
<br />
=={{anchor|requirements}}Voraussetzungen==<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS und Datenbank Support Matrix]] für die Liste der unterstützten Citrix XenServer Versionen.<br />
* SEP sesam Server Version 4.4.3 oder höher. Der Citrix XenServer Sicherungs-Client ist bereits in allen SEP sesam Paketen enthalten.<br />
* Überprüfen Sie die [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardwareanforderungen]] auf dem [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] oder [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]. <br />
*Jeder XenServer muss über eine eigene '''Management-Schnittstelle''' verfügen.<br />
*In einer Cluster-Konfiguration, in der mehrere XenServer in einem Pool organisiert sind, muss der '''Pool-Master''' XenServer als ''SEP sesam Client'' konfiguriert werden.<br />
{{Anmerkung| Der Sicherungsverkehr läuft immer über die Management-Schnittstelle des XenServers. Achten Sie auf eine gute Netzwerk-Performance, z.B. 2x 10 Gbit Netzwerkschnittstellen als Bond sowohl auf dem XenServer als auch auf dem Backup-Server.}}<br />
<br />
=== {{anchor|data_mover}}SEP sesam Data Mover für Citrix XenServer (SDM-CX)===<br />
{{:Template:Data mover Citrix XenServer/de}}<br />
<br />
=={{anchor|configuration}}XenServer als SEP sesam Client einrichten== <br />
Um Ihre virtuellen Maschinen zu schützen, müssen Sie Ihren XenServer als SEP sesam Client konfigurieren. Stellen Sie sicher, dass die [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#requirements|Voraussetzungen]] erfüllt sind, bevor Sie mit der Konfiguration beginnen. Die Optionen zur Konfiguration des XenServers können je nach SEP sesam Version leicht variieren.<br />
<ol><li>Wählen Sie unter '''Auswahl''' -> '''Komponenten''' -> '''Topologie''' den entsprechenden ''Standort'' und klicken Sie auf die Schaltfläche '''Neuer Client'''. Das Fenster ''Neuer Client'' wird geöffnet.</li><br />
<li>Geben Sie im Fenster ''Neuer Client'' den DNS-Namen der '''Management-Schnittstelle des Pool-Masters''' ein. Wenn Sie den korrekten DNS-Namen des Pool-Masters nicht eingeben, funktioniert das Surfen in der XenServer-Umgebung nicht.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Plattform'' das '''UNIX'''.</li><br />
<li>Wählen Sie in der Dropdown-Liste ''Betriebssystem'' den Eintrag '''Citrix XenServer'''.</li><br />
<li>Ab SEP sesam Version 4.4.3 wird nur noch der ''Zugriffsmodus'' '''PROXY''' unterstützt, der bei Auswahl des Betriebssystems Citrix XenServer standardmäßig eingestellt ist.</li><br />
{{Anmerkung|Wenn Sie eine SEP sesam Version ≥ 4.4.3 verwenden, stellen Sie sicher, dass der Zugriffsmodus '''PROXY''' ausgewählt ist. Wird der Zugriffsmodus ''CTRL'' verwendet, tritt ein Fehler auf, wenn der SEP sesam Server die Verbindung zum SEP sesam XenServer Client prüft.}}<br />
[[image:Add_client_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf den Reiter '''Citrix XenServer''' und geben Sie die Anmeldeinformationen ''root/admin'' für den XenServer ein.</li><br />
<li>Wählen Sie einen '''Data Mover'''. Der Data Mover muss der Hostname des SEP sesam Servers oder eines RDS sein. Details zu den Anforderungen finden Sie im obigen Abschnitt [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam DataMover für den Citrix XenServer (SDM-CX)]].</li><br />
[[image:Add_client-account_XenServer_Beefalo_V2_de.jpg|730px|link=]]<br />
<br clear=all><br />
<li>Klicken Sie auf '''OK''', um den neuen Client hinzuzufügen.</li></ol><br />
<br />
==={{anchor|https}}Auswahl von '''https''' statt '''http''' Verbindung===<br />
<br />
SEP sesam verwendet das ''http'' Protokoll als Standardverbindung, um eine bessere Performance bei der Datenübertragung vom XenServer zum SEP sesam Server zu gewährleisten. Sicherungen über ''https'' können bis zu 98% CPU-Last auf dem XenServer verursachen. <br />
<br />
Sie können das Protokoll jedoch auf die sichere ''https'' (sicher mit SSL) Verbindung umstellen, indem Sie das ''https'' Protokoll unter '''Sicherungsauftrag''' -> '''Eigenschaften''' -> '''Optionen''' im Feld '''Sicherungsoptionen''' wie folgt angeben:<br />
<br />
-a http=https<br />
<br />
<br />
==={{anchor|NBD}} NBD auf Netzwerkinterfaces für CBT konfigurieren===<br />
Ab der Version 4.4.3.84SP3 aktiviert SEP sesam NBD nicht mehr automatisch auf allen verfügbaren Netzwerkinterfaces. NBD wird für den Transport von CBT-Sicherungen benötigt.<br />
<br />
To activate NBD on all network interfaces, connect to the Poolmaster via SSH and execute the following command<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
This configuration may cause problems, when there are networks the SEP sesam Datamover cannot reach. Examples for such constellations are storage networks or a DMZ.<br />
<br />
In that case further confuration is needed.<br />
<br />
The following commands can be used to accomplish this:<br />
<br />
* to get a list of available interfaces<br />
xe network-list<br />
* to get the properties of a network<br />
xe network-param-list uuid=<network-uuid><br />
* to enable NBD for a specific interface<br />
xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to disable NBD for a specific interface<br />
xe network-param-remove uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to deactivate NBD for all interfaces<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
For further information consult the [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Documentation]<br />
<br />
==Bekannte Themen==<br />
Wenn Sie Probleme mit dem Citrix XenServer haben, überprüfen Sie den [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].<br />
<br />
<div class="noprint"><br />
=={{anchor|see also}}Siehe auch==<br />
[[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]</div></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:4_4_3:Citrix_XenServer_Requirements_and_Configuration/40/de&diff=176849Translations:4 4 3:Citrix XenServer Requirements and Configuration/40/de2021-02-11T11:20:49Z<p>Fho: Created page with "==={{anchor|NBD}} NBD auf Netzwerkinterfaces für CBT konfigurieren=== Ab der Version 4.4.3.84SP3 aktiviert SEP sesam NBD nicht mehr automatisch auf allen verfügbaren Netzwer..."</p>
<hr />
<div>==={{anchor|NBD}} NBD auf Netzwerkinterfaces für CBT konfigurieren===<br />
Ab der Version 4.4.3.84SP3 aktiviert SEP sesam NBD nicht mehr automatisch auf allen verfügbaren Netzwerkinterfaces. NBD wird für den Transport von CBT-Sicherungen benötigt.</div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3:Citrix_XenServer_Requirements_and_Configuration&diff=1768394 4 3:Citrix XenServer Requirements and Configuration2021-02-11T11:18:41Z<p>Fho: Marked this version for translation</p>
<hr />
<div><translate><!--T:1--><br />
<div class="noprint"><languages /><br />
<br />
<!--T:38--><br />
{{Copyright SEP AG|en}}<br />
<br />
<!--T:2--><br />
{{Navigation_latest|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer archive]]}}</div></translate><br />
<br />
<br />
<translate>=={{anchor|overview}}Overview== <!--T:3--></translate><br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><translate><!--T:4--><br />
Additional resources</translate></b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--><br />
[[File:SEP_next.png|45px|link=4_4_3_Grolar:Citrix_XenServer_Backup]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--><br />
See also: [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Restore]]</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:7--><br />
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#Citrix]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:8--><br />
If you have a problem with your ''Citrix XenServer'', check [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Citrix XenServer troubleshooting]].</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:9--><br />
[[File:icon_archived_docs.png|45px|link=Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:10--><br />
If you are using an older SEP sesam version, refer to [[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer archive]].</translate><br />
|}</div><br />
<translate><!--T:11--><br />
This article describes requirements and configuration steps for SEP sesam integration with Citrix XenServer. Note that the procedures introduced in this article are the required configuration steps to set up Citrix XenServer SEP sesam integration. For details on Citrix XenServer integration key features and backup configuration, see [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]].<br />
<br />
=={{anchor|requirements}}Requirements== <!--T:12--></translate><br />
* <translate><!--T:13--><br />
Check the [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS and Database Support Matrix]] for the list of supported Citrix XenServer versions.</translate><br />
* <translate><!--T:14--><br />
SEP sesam Server v. 4.4.3 or higher. Citrix XenServer backup client is already included in all SEP sesam packages.</translate><br />
* <translate><!--T:15--><br />
Check [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] or [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]].</translate> <br />
*<translate><!--T:16--><br />
Each XenServer must have a dedicated '''management interface'''.</translate><br />
*<translate><!--T:17--><br />
In a cluster configuration where more XenServers are organized in a pool, the '''pool master''' XenServer must be configured as a ''SEP sesam Client''.</translate><br />
{{<translate><!--T:18--><br />
note</translate>| <translate><!--T:19--><br />
The backup traffic always goes over the management interface of the XenServer. Make sure you get good network performance, for example 2x 10 Gbit network interfaces as a bond on the XenServer as well as on the backup server.</translate>}}<br />
<br />
<translate>=== {{anchor|data_mover}}SEP sesam data mover for Citrix XenServer (SDM-CX)=== <!--T:20--><br />
{{:Template:Data mover Citrix XenServer/en}}<br />
<br />
== {{anchor|configuration}}Configuring XenServer as a SEP sesam Client == <!--T:21--><br />
To protect your virtual machines, you must configure your XenServer as a SEP sesam Client. Make sure that the [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#requirements|prerequisites]] are met before starting with configuration. The options for configuring XenServer may differ slightly depending on your SEP sesam version.</translate><br />
<ol><li><translate><!--T:22--><br />
From '''Main Selection''' -> '''Components''' -> '''Topology''', select the relevant ''location'' and click the '''New Client''' button. The ''New Client'' window opens.</translate></li><br />
<li><translate><!--T:23--><br />
In the ''New Client'' window, enter the '''management interface DNS name of the pool master'''. If you fail to enter the correct DNS name of the pool master, browsing XenServer environment will not work.</translate></li><br />
<li><translate><br />
<!--T:39--><br />
Under ''Platform'' drop-down list, select the '''UNIX'''.</translate></li><br />
<li><translate><!--T:24--><br />
Under ''Operating system'' drop-down list, select the '''Citrix XenServer'''.</translate></li><br />
<li><translate><!--T:25--><br />
As of SEP sesam v. 4.4.3, the only supported ''access mode'' is '''PROXY''', which is set by default when the Citrix XenServer operating system is selected.</translate></li><br />
{{<translate><!--T:26--><br />
note</translate>|<translate><!--T:27--><br />
If you are using SEP sesam version ≥ 4.4.3, make sure that the '''PROXY''' access mode is selected. If the access mode ''CTRL'' is used, an error occurs when SEP sesam Server checks the connection to the SEP sesam XenServer client.</translate>}}<br />
<translate><!--T:28--><br />
[[image:Add_client_XenServer_Beefalo_V2.jpg|730px|link=]]</translate><br />
<br clear=all><br />
<li><translate><!--T:29--><br />
Click the tab '''Citrix XenServer''' and enter ''root/admin'' credentials for XenServer.</translate></li><br />
<li><translate><!--T:30--><br />
Select a '''Data mover'''. The data mover must be the host name of the SEP sesam Server or RDS. For details on requirements, see the above section [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam data mover for Citrix XenServer (SDM-CX)]].</translate></li><br />
<translate><!--T:31--><br />
[[image:Add_client-account_XenServer_Beefalo_V2.jpg|730px|link=]]</translate><br />
<br clear=all><br />
<li><translate><!--T:32--><br />
Click '''OK''' to add the new client.</translate></li></ol><br />
<br />
<translate>=== {{anchor|https}}Selecting ''https'' instead of ''http'' connection === <!--T:33--><br />
<br />
<!--T:34--><br />
SEP sesam uses the ''http'' protocol as a default connection to ensure better performance when transferring data from XenServer to SEP sesam Server. Backups over ''https'' can cause up to 98% CPU load on XenServer. <br />
<br />
<!--T:35--><br />
However, you can change the protocol to the secure ''https'' (secure with SSL) connection by specifying the ''https'' protocol under '''Backup task''' -> '''Properties''' -> '''Options''' tab -> '''Backup options''' as follows:</translate><br />
<br />
-a http=https<br />
<br />
<br />
<translate>==={{anchor|NBD}} Configure NBD on network interfaces for CBT=== <!--T:40--><br />
Starting from Version 4.4.3.84SP3, SEP sesam will no longer automatically enable NBD on all available network interfaces. NBD is required for the transport of CBT backups.<br />
<br />
<!--T:41--><br />
To activate NBD on all network interfaces, connect to the Poolmaster via SSH and execute the following command<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
<!--T:42--><br />
This configuration may cause problems, when there are networks the SEP sesam Datamover cannot reach. Examples for such constellations are storage networks or a DMZ.<br />
<br />
<!--T:43--><br />
In that case further confuration is needed.<br />
<br />
<!--T:44--><br />
The following commands can be used to accomplish this:<br />
<br />
<!--T:45--><br />
* to get a list of available interfaces<br />
xe network-list<br />
* to get the properties of a network<br />
xe network-param-list uuid=<network-uuid><br />
* to enable NBD for a specific interface<br />
xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to disable NBD for a specific interface<br />
xe network-param-remove uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to deactivate NBD for all interfaces<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
<!--T:46--><br />
For further information consult the [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Documentation]<br />
<br />
</translate><br />
<translate>==Known issues== <!--T:36--><br />
If you have problems with Citrix XenServer, check the [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].<br />
<br />
<div class="noprint"><br />
=={{anchor|see also}}See also== <!--T:37--><br />
[[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Restore]]</div></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3:Citrix_XenServer_Requirements_and_Configuration&diff=1768384 4 3:Citrix XenServer Requirements and Configuration2021-02-11T10:58:19Z<p>Fho: </p>
<hr />
<div><translate><!--T:1--><br />
<div class="noprint"><languages /><br />
<br />
<!--T:38--><br />
{{Copyright SEP AG|en}}<br />
<br />
<!--T:2--><br />
{{Navigation_latest|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer archive]]}}</div></translate><br />
<br />
<br />
<translate>=={{anchor|overview}}Overview== <!--T:3--></translate><br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><translate><!--T:4--><br />
Additional resources</translate></b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--><br />
[[File:SEP_next.png|45px|link=4_4_3_Grolar:Citrix_XenServer_Backup]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--><br />
See also: [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Restore]]</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:7--><br />
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#Citrix]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:8--><br />
If you have a problem with your ''Citrix XenServer'', check [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Citrix XenServer troubleshooting]].</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:9--><br />
[[File:icon_archived_docs.png|45px|link=Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:10--><br />
If you are using an older SEP sesam version, refer to [[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer archive]].</translate><br />
|}</div><br />
<translate><!--T:11--><br />
This article describes requirements and configuration steps for SEP sesam integration with Citrix XenServer. Note that the procedures introduced in this article are the required configuration steps to set up Citrix XenServer SEP sesam integration. For details on Citrix XenServer integration key features and backup configuration, see [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]].<br />
<br />
=={{anchor|requirements}}Requirements== <!--T:12--></translate><br />
* <translate><!--T:13--><br />
Check the [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS and Database Support Matrix]] for the list of supported Citrix XenServer versions.</translate><br />
* <translate><!--T:14--><br />
SEP sesam Server v. 4.4.3 or higher. Citrix XenServer backup client is already included in all SEP sesam packages.</translate><br />
* <translate><!--T:15--><br />
Check [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] or [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]].</translate> <br />
*<translate><!--T:16--><br />
Each XenServer must have a dedicated '''management interface'''.</translate><br />
*<translate><!--T:17--><br />
In a cluster configuration where more XenServers are organized in a pool, the '''pool master''' XenServer must be configured as a ''SEP sesam Client''.</translate><br />
{{<translate><!--T:18--><br />
note</translate>| <translate><!--T:19--><br />
The backup traffic always goes over the management interface of the XenServer. Make sure you get good network performance, for example 2x 10 Gbit network interfaces as a bond on the XenServer as well as on the backup server.</translate>}}<br />
<br />
<translate>=== {{anchor|data_mover}}SEP sesam data mover for Citrix XenServer (SDM-CX)=== <!--T:20--><br />
{{:Template:Data mover Citrix XenServer/en}}<br />
<br />
== {{anchor|configuration}}Configuring XenServer as a SEP sesam Client == <!--T:21--><br />
To protect your virtual machines, you must configure your XenServer as a SEP sesam Client. Make sure that the [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#requirements|prerequisites]] are met before starting with configuration. The options for configuring XenServer may differ slightly depending on your SEP sesam version.</translate><br />
<ol><li><translate><!--T:22--><br />
From '''Main Selection''' -> '''Components''' -> '''Topology''', select the relevant ''location'' and click the '''New Client''' button. The ''New Client'' window opens.</translate></li><br />
<li><translate><!--T:23--><br />
In the ''New Client'' window, enter the '''management interface DNS name of the pool master'''. If you fail to enter the correct DNS name of the pool master, browsing XenServer environment will not work.</translate></li><br />
<li><translate><br />
<!--T:39--><br />
Under ''Platform'' drop-down list, select the '''UNIX'''.</translate></li><br />
<li><translate><!--T:24--><br />
Under ''Operating system'' drop-down list, select the '''Citrix XenServer'''.</translate></li><br />
<li><translate><!--T:25--><br />
As of SEP sesam v. 4.4.3, the only supported ''access mode'' is '''PROXY''', which is set by default when the Citrix XenServer operating system is selected.</translate></li><br />
{{<translate><!--T:26--><br />
note</translate>|<translate><!--T:27--><br />
If you are using SEP sesam version ≥ 4.4.3, make sure that the '''PROXY''' access mode is selected. If the access mode ''CTRL'' is used, an error occurs when SEP sesam Server checks the connection to the SEP sesam XenServer client.</translate>}}<br />
<translate><!--T:28--><br />
[[image:Add_client_XenServer_Beefalo_V2.jpg|730px|link=]]</translate><br />
<br clear=all><br />
<li><translate><!--T:29--><br />
Click the tab '''Citrix XenServer''' and enter ''root/admin'' credentials for XenServer.</translate></li><br />
<li><translate><!--T:30--><br />
Select a '''Data mover'''. The data mover must be the host name of the SEP sesam Server or RDS. For details on requirements, see the above section [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam data mover for Citrix XenServer (SDM-CX)]].</translate></li><br />
<translate><!--T:31--><br />
[[image:Add_client-account_XenServer_Beefalo_V2.jpg|730px|link=]]</translate><br />
<br clear=all><br />
<li><translate><!--T:32--><br />
Click '''OK''' to add the new client.</translate></li></ol><br />
<br />
<translate>=== {{anchor|https}}Selecting ''https'' instead of ''http'' connection === <!--T:33--><br />
<br />
<!--T:34--><br />
SEP sesam uses the ''http'' protocol as a default connection to ensure better performance when transferring data from XenServer to SEP sesam Server. Backups over ''https'' can cause up to 98% CPU load on XenServer. <br />
<br />
<!--T:35--><br />
However, you can change the protocol to the secure ''https'' (secure with SSL) connection by specifying the ''https'' protocol under '''Backup task''' -> '''Properties''' -> '''Options''' tab -> '''Backup options''' as follows:</translate><br />
<br />
-a http=https<br />
<br />
<br />
<translate>==={{anchor|NBD}} Configure NBD on network interfaces for CBT===<br />
Starting from Version 4.4.3.84SP3, SEP sesam will no longer automatically enable NBD on all available network interfaces. NBD is required for the transport of CBT backups.<br />
<br />
To activate NBD on all network interfaces, connect to the Poolmaster via SSH and execute the following command<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
This configuration may cause problems, when there are networks the SEP sesam Datamover cannot reach. Examples for such constellations are storage networks or a DMZ.<br />
<br />
In that case further confuration is needed.<br />
<br />
The following commands can be used to accomplish this:<br />
<br />
* to get a list of available interfaces<br />
xe network-list<br />
* to get the properties of a network<br />
xe network-param-list uuid=<network-uuid><br />
* to enable NBD for a specific interface<br />
xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to disable NBD for a specific interface<br />
xe network-param-remove uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to deactivate NBD for all interfaces<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
For further information consult the [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Documentation]<br />
<br />
</translate><br />
<translate>==Known issues== <!--T:36--><br />
If you have problems with Citrix XenServer, check the [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].<br />
<br />
<div class="noprint"><br />
=={{anchor|see also}}See also== <!--T:37--><br />
[[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Restore]]</div></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3:Citrix_XenServer_Requirements_and_Configuration&diff=1768374 4 3:Citrix XenServer Requirements and Configuration2021-02-11T10:57:43Z<p>Fho: </p>
<hr />
<div><translate><!--T:1--><br />
<div class="noprint"><languages /><br />
<br />
<!--T:38--><br />
{{Copyright SEP AG|en}}<br />
<br />
<!--T:2--><br />
{{Navigation_latest|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer archive]]}}</div></translate><br />
<br />
<br />
<translate>=={{anchor|overview}}Overview== <!--T:3--></translate><br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><translate><!--T:4--><br />
Additional resources</translate></b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--><br />
[[File:SEP_next.png|45px|link=4_4_3_Grolar:Citrix_XenServer_Backup]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--><br />
See also: [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Restore]]</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:7--><br />
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide#Citrix]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:8--><br />
If you have a problem with your ''Citrix XenServer'', check [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Citrix XenServer troubleshooting]].</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:9--><br />
[[File:icon_archived_docs.png|45px|link=Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:10--><br />
If you are using an older SEP sesam version, refer to [[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer archive]].</translate><br />
|}</div><br />
<translate><!--T:11--><br />
This article describes requirements and configuration steps for SEP sesam integration with Citrix XenServer. Note that the procedures introduced in this article are the required configuration steps to set up Citrix XenServer SEP sesam integration. For details on Citrix XenServer integration key features and backup configuration, see [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]].<br />
<br />
=={{anchor|requirements}}Requirements== <!--T:12--></translate><br />
* <translate><!--T:13--><br />
Check the [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS and Database Support Matrix]] for the list of supported Citrix XenServer versions.</translate><br />
* <translate><!--T:14--><br />
SEP sesam Server v. 4.4.3 or higher. Citrix XenServer backup client is already included in all SEP sesam packages.</translate><br />
* <translate><!--T:15--><br />
Check [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] or [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]].</translate> <br />
*<translate><!--T:16--><br />
Each XenServer must have a dedicated '''management interface'''.</translate><br />
*<translate><!--T:17--><br />
In a cluster configuration where more XenServers are organized in a pool, the '''pool master''' XenServer must be configured as a ''SEP sesam Client''.</translate><br />
{{<translate><!--T:18--><br />
note</translate>| <translate><!--T:19--><br />
The backup traffic always goes over the management interface of the XenServer. Make sure you get good network performance, for example 2x 10 Gbit network interfaces as a bond on the XenServer as well as on the backup server.</translate>}}<br />
<br />
<translate>=== {{anchor|data_mover}}SEP sesam data mover for Citrix XenServer (SDM-CX)=== <!--T:20--><br />
{{:Template:Data mover Citrix XenServer/en}}<br />
<br />
== {{anchor|configuration}}Configuring XenServer as a SEP sesam Client == <!--T:21--><br />
To protect your virtual machines, you must configure your XenServer as a SEP sesam Client. Make sure that the [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#requirements|prerequisites]] are met before starting with configuration. The options for configuring XenServer may differ slightly depending on your SEP sesam version.</translate><br />
<ol><li><translate><!--T:22--><br />
From '''Main Selection''' -> '''Components''' -> '''Topology''', select the relevant ''location'' and click the '''New Client''' button. The ''New Client'' window opens.</translate></li><br />
<li><translate><!--T:23--><br />
In the ''New Client'' window, enter the '''management interface DNS name of the pool master'''. If you fail to enter the correct DNS name of the pool master, browsing XenServer environment will not work.</translate></li><br />
<li><translate><br />
<!--T:39--><br />
Under ''Platform'' drop-down list, select the '''UNIX'''.</translate></li><br />
<li><translate><!--T:24--><br />
Under ''Operating system'' drop-down list, select the '''Citrix XenServer'''.</translate></li><br />
<li><translate><!--T:25--><br />
As of SEP sesam v. 4.4.3, the only supported ''access mode'' is '''PROXY''', which is set by default when the Citrix XenServer operating system is selected.</translate></li><br />
{{<translate><!--T:26--><br />
note</translate>|<translate><!--T:27--><br />
If you are using SEP sesam version ≥ 4.4.3, make sure that the '''PROXY''' access mode is selected. If the access mode ''CTRL'' is used, an error occurs when SEP sesam Server checks the connection to the SEP sesam XenServer client.</translate>}}<br />
<translate><!--T:28--><br />
[[image:Add_client_XenServer_Beefalo_V2.jpg|730px|link=]]</translate><br />
<br clear=all><br />
<li><translate><!--T:29--><br />
Click the tab '''Citrix XenServer''' and enter ''root/admin'' credentials for XenServer.</translate></li><br />
<li><translate><!--T:30--><br />
Select a '''Data mover'''. The data mover must be the host name of the SEP sesam Server or RDS. For details on requirements, see the above section [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam data mover for Citrix XenServer (SDM-CX)]].</translate></li><br />
<translate><!--T:31--><br />
[[image:Add_client-account_XenServer_Beefalo_V2.jpg|730px|link=]]</translate><br />
<br clear=all><br />
<li><translate><!--T:32--><br />
Click '''OK''' to add the new client.</translate></li></ol><br />
<br />
<translate>=== {{anchor|https}}Selecting ''https'' instead of ''http'' connection === <!--T:33--><br />
<br />
<!--T:34--><br />
SEP sesam uses the ''http'' protocol as a default connection to ensure better performance when transferring data from XenServer to SEP sesam Server. Backups over ''https'' can cause up to 98% CPU load on XenServer. <br />
<br />
<!--T:35--><br />
However, you can change the protocol to the secure ''https'' (secure with SSL) connection by specifying the ''https'' protocol under '''Backup task''' -> '''Properties''' -> '''Options''' tab -> '''Backup options''' as follows:</translate><br />
<br />
-a http=https<br />
<br />
<br />
<translate>==={{anchor|NBD}} Configure NBD on network interfaces for CBT===<br />
Starting from SEP sesam Version 4.4.3.84SP3 SEP sesam will no longer automatically enable NBD on all available network interfaces. NBD is required for the transport of CBT backups.<br />
<br />
To activate NBD on all network interfaces, connect to the Poolmaster via SSH and execute the following command<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
This configuration may cause problems, when there are networks the SEP sesam Datamover cannot reach. Examples for such constellations are storage networks or a DMZ.<br />
<br />
In that case further confuration is needed.<br />
<br />
The following commands can be used to accomplish this:<br />
<br />
* to get a list of available interfaces<br />
xe network-list<br />
* to get the properties of a network<br />
xe network-param-list uuid=<network-uuid><br />
* to enable NBD for a specific interface<br />
xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to disable NBD for a specific interface<br />
xe network-param-remove uuid=<network-uuid> param-name=purpose param-key=nbd<br />
* to deactivate NBD for all interfaces<br />
for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done<br />
<br />
For further information consult the [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Documentation]<br />
<br />
</translate><br />
<translate>==Known issues== <!--T:36--><br />
If you have problems with Citrix XenServer, check the [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].<br />
<br />
<div class="noprint"><br />
=={{anchor|see also}}See also== <!--T:37--><br />
[[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Restore]]</div></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Troubleshooting_Citrix_XEN_Server&diff=176659Source:Troubleshooting Citrix XEN Server2021-02-08T13:12:40Z<p>Fho: </p>
<hr />
<div>__FORCETOC__<br />
<br />
<noinclude>{{Copyright SEP AG en}}<br />
<br />
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/SEP_sesam_Documentation#previous|documentation archive]]}}<br /></noinclude><br />
==Citrix XEN Server==<br />
<noinclude><div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><br />
Additional resources</b></center><br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <br />
[[File:SEP_next.png|45px|link=Special:MyLanguage/Citrix_XEN_Server]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <br />
See also: [[Special:MyLanguage/Citrix_XEN_Server|Citrix XEN Server]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <br />
[[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <br />
Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions.<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <br />
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <br />
Other problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].<br />
|}<br />
</div></noinclude><br />
<br />
=== Error when using quiesced snapshots===<br />
<br />
'''Problem'''<br />
*Using ''VM.snapshot_with_quiesce'' method fails in Citrix Hypervisor ≥ 8.1 or in the version ≥ 9.0.x.x drivers. <br />
<br />
'''Cause'''<br />
*VSS and quiesced snapshots of Windows VMs capability have been removed in Citrix Hypervisor ≥ 8.1 and in the version ≥ 9.0.x.x drivers. They are only supported in Citrix Hypervisor ≤ 8.0. For more information, see [https://docs.citrix.com/en-us/citrix-hypervisor/whats-new/removed-features.html Citrix Hypervisor 8.1 Deprecations and removals].<br />
<br />
&rArr; '''Solution'''<br />
*If you want to continue using the quiesced snapshot feature with Windows VMs hosted on Citrix Hypervisor 8.0 and earlier, do not update to the 9.0.x.x drivers. <br />
<br />
===CBT Backup fails because Xen Server TLS certificate contains wrong ip address===<br />
<br />
'''Problem'''<br />
* CBT Backup fails with Error: Failed to get NBD client for device '******: NBD client connection error: hostname '****' doesn't match u'******''<br />
<br />
'''Cause'''<br />
The TLS certificate of a Xen Server contains a wrong ip address. Therefore no NBD session can be established.<br />
<br />
&rArr; '''Solution'''<br />
* Check all Xen Servers in the Pool whether the ip address in the certificate matches<br />
* On the Xen Server where it does not match execute the following commands<br />
*# Create a backup of the existing certificate <code> mv /etc/xensource/xapi-ssl.pem /etc/xensource/xapi-ssl.pem.$(date -u +%Y%m%d) </code><br />
*# Create a new certificate <code> /opt/xensource/libexec/generate_ssl_cert /etc/xensource/xapi-ssl.pem <ip-address or FQDN> </code><br />
*# Restart XenAPI service <code> systemctl restart xapi </code><br />
*# Restart NBD Service <code> systemctl restart xapi-nbd </code><br />
<br />
=== Message "Upload to URL ... failed" appears during restore, "insufficient space" error occurs during backup===<br />
<br />
'''Problems'''<br />
*Restore fails with an error: "Upload to URL ... failed."<br />
*SR_BACKEND_FAILURE_44: : There is insufficient space to create snapshot on Storage Repository. <br />
<br />
'''Possible cause'''<br />
*There is not enough space available on the default storage.<br />
*If the "insufficient space" error occurs during the backup, it might be related to the snapshot process. XenServer was unable to create a snapshot for the VM because there was not enough space in your Storage Repository.<br />
<br />
&rArr; '''Solution'''<br />
*Use XenCenter to select another default storage that has enough free disk capacity to store the virtual disk(s).<br />
<br />
'''Other issues'''<br />
<ul><li>Some errors are not reported in detail by XEN API. More information can be found in XenServer in ''/var/log'' directory.</li><br />
<li>In some pool configurations all pool members must have their management interface listed in DNS.</li><br />
<li>If the settings below don't agree on asynchronous routing and connection drops and/or 3 second or 80 second delays, opening sockets may occour. This is very similar to having 2 network cards configured with ipv4 to the same subnet and connected to the same switch.</li><br />
<li>If you use Cisco switches and you have configured (Citrix unsupported) ''lacp bonding 802.3ad'', ensureit is very important that both sides agree on the balancing type. The Linux default is ''layer2'' and the Cisco default is ''layer3+4''.</li> <br />
<li>Check the bonding mode on the host with <tt>cat /proc/net/bond/bond*</tt> for bonding mode:</li> <br />
IEEE 802.3ad Dynamic link aggregation<br /><br />
Transmit Hash Policy: layer2 (0) or Transmit Hash Policy: layer3+4 (1).<br />
<li>Users have reported that this command and a reboot solves the problem, but this cannot be formally recommended due to its untested and unsupported status:</li><br />
xe pif-param-set uuid=${UUID_OF_BOND_PIF} other-config:bond-xmit_hash_policy=1 <br />
<li>In the common situation where 802.1ad with xmit_hash_policy=1 and STP are in use, multiple settings need to be adjusted on the Cisco side according to the article [http://support.citrix.com/article/CTX123158 Considerations for Connecting XenServer to the Switch Ports].</li><br />
<li>Most other network related performance and reliability issues can be resolved with [http://support.citrix.com/article/CTX123158 Considerations for Connecting XenServer to the Switch Ports].</li><br />
<li>In some situations when using thin storage repositories, an sr rescan is necessary to re-detect free space before a backup or restore.</li><br />
</ul><br />
<noinclude>== See also ==<br />
[[Special:MyLanguage/Citrix_XEN_Server|Citrix XEN Server]]</noinclude></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Troubleshooting_Citrix_XEN_Server&diff=176658Source:Troubleshooting Citrix XEN Server2021-02-08T11:52:31Z<p>Fho: </p>
<hr />
<div>__FORCETOC__<br />
<br />
<noinclude>{{Copyright SEP AG en}}<br />
<br />
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/SEP_sesam_Documentation#previous|documentation archive]]}}<br /></noinclude><br />
==Citrix XEN Server==<br />
<noinclude><div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><br />
Additional resources</b></center><br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <br />
[[File:SEP_next.png|45px|link=Special:MyLanguage/Citrix_XEN_Server]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <br />
See also: [[Special:MyLanguage/Citrix_XEN_Server|Citrix XEN Server]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <br />
[[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <br />
Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions.<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <br />
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <br />
Other problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].<br />
|}<br />
</div></noinclude><br />
<br />
=== Error when using quiesced snapshots===<br />
<br />
'''Problem'''<br />
*Using ''VM.snapshot_with_quiesce'' method fails in Citrix Hypervisor ≥ 8.1 or in the version ≥ 9.0.x.x drivers. <br />
<br />
'''Cause'''<br />
*VSS and quiesced snapshots of Windows VMs capability have been removed in Citrix Hypervisor ≥ 8.1 and in the version ≥ 9.0.x.x drivers. They are only supported in Citrix Hypervisor ≤ 8.0. For more information, see [https://docs.citrix.com/en-us/citrix-hypervisor/whats-new/removed-features.html Citrix Hypervisor 8.1 Deprecations and removals].<br />
<br />
&rArr; '''Solution'''<br />
*If you want to continue using the quiesced snapshot feature with Windows VMs hosted on Citrix Hypervisor 8.0 and earlier, do not update to the 9.0.x.x drivers. <br />
<br />
===CBT Backup fails because Xen Server TLS certificate contains wrong ip address===<br />
<br />
'''Problem'''<br />
* CBT Backup fails with Error: Failed to get NBD client for device '******: NBD client connection error: hostname '****' doesn't match u'******''<br />
<br />
'''Cause'''<br />
The TLS certificate of a Xen Server contains a wrong ip address. Therefore no NBD session can be established.<br />
<br />
&rArr; '''Solution'''<br />
* Check all Xen Servers in the Pool whether the ip address in the certificate matches<br />
* On the Xen Server where it does not match execute the following commands<br />
*# Create a backup of the existing certificate <code> mv /etc/xensource/xapi-ssl.pem /etc/xensource/xapi-ssl.pem.$(date -u +%Y%m%d) </code><br />
*# Create a new certificate <code> /opt/xensource/libexec/generate_ssl_cert /etc/xensource/xapi-ssl.pem <ip-address or FQDN> </code><br />
*# Restart XenAPI service <code> service xapi restart </code><br />
<br />
=== Message "Upload to URL ... failed" appears during restore, "insufficient space" error occurs during backup===<br />
<br />
'''Problems'''<br />
*Restore fails with an error: "Upload to URL ... failed."<br />
*SR_BACKEND_FAILURE_44: : There is insufficient space to create snapshot on Storage Repository. <br />
<br />
'''Possible cause'''<br />
*There is not enough space available on the default storage.<br />
*If the "insufficient space" error occurs during the backup, it might be related to the snapshot process. XenServer was unable to create a snapshot for the VM because there was not enough space in your Storage Repository.<br />
<br />
&rArr; '''Solution'''<br />
*Use XenCenter to select another default storage that has enough free disk capacity to store the virtual disk(s).<br />
<br />
'''Other issues'''<br />
<ul><li>Some errors are not reported in detail by XEN API. More information can be found in XenServer in ''/var/log'' directory.</li><br />
<li>In some pool configurations all pool members must have their management interface listed in DNS.</li><br />
<li>If the settings below don't agree on asynchronous routing and connection drops and/or 3 second or 80 second delays, opening sockets may occour. This is very similar to having 2 network cards configured with ipv4 to the same subnet and connected to the same switch.</li><br />
<li>If you use Cisco switches and you have configured (Citrix unsupported) ''lacp bonding 802.3ad'', ensureit is very important that both sides agree on the balancing type. The Linux default is ''layer2'' and the Cisco default is ''layer3+4''.</li> <br />
<li>Check the bonding mode on the host with <tt>cat /proc/net/bond/bond*</tt> for bonding mode:</li> <br />
IEEE 802.3ad Dynamic link aggregation<br /><br />
Transmit Hash Policy: layer2 (0) or Transmit Hash Policy: layer3+4 (1).<br />
<li>Users have reported that this command and a reboot solves the problem, but this cannot be formally recommended due to its untested and unsupported status:</li><br />
xe pif-param-set uuid=${UUID_OF_BOND_PIF} other-config:bond-xmit_hash_policy=1 <br />
<li>In the common situation where 802.1ad with xmit_hash_policy=1 and STP are in use, multiple settings need to be adjusted on the Cisco side according to the article [http://support.citrix.com/article/CTX123158 Considerations for Connecting XenServer to the Switch Ports].</li><br />
<li>Most other network related performance and reliability issues can be resolved with [http://support.citrix.com/article/CTX123158 Considerations for Connecting XenServer to the Switch Ports].</li><br />
<li>In some situations when using thin storage repositories, an sr rescan is necessary to re-detect free space before a backup or restore.</li><br />
</ul><br />
<noinclude>== See also ==<br />
[[Special:MyLanguage/Citrix_XEN_Server|Citrix XEN Server]]</noinclude></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Troubleshooting_Citrix_XEN_Server&diff=176657Source:Troubleshooting Citrix XEN Server2021-02-08T11:19:24Z<p>Fho: /* Citrix XEN Server */</p>
<hr />
<div>__FORCETOC__<br />
<br />
<noinclude>{{Copyright SEP AG en}}<br />
<br />
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/SEP_sesam_Documentation#previous|documentation archive]]}}<br /></noinclude><br />
==Citrix XEN Server==<br />
<noinclude><div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><br />
Additional resources</b></center><br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <br />
[[File:SEP_next.png|45px|link=Special:MyLanguage/Citrix_XEN_Server]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <br />
See also: [[Special:MyLanguage/Citrix_XEN_Server|Citrix XEN Server]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <br />
[[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <br />
Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions.<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <br />
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <br />
Other problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].<br />
|}<br />
</div></noinclude><br />
<br />
=== Error when using quiesced snapshots===<br />
<br />
'''Problem'''<br />
*Using ''VM.snapshot_with_quiesce'' method fails in Citrix Hypervisor ≥ 8.1 or in the version ≥ 9.0.x.x drivers. <br />
<br />
'''Cause'''<br />
*VSS and quiesced snapshots of Windows VMs capability have been removed in Citrix Hypervisor ≥ 8.1 and in the version ≥ 9.0.x.x drivers. They are only supported in Citrix Hypervisor ≤ 8.0. For more information, see [https://docs.citrix.com/en-us/citrix-hypervisor/whats-new/removed-features.html Citrix Hypervisor 8.1 Deprecations and removals].<br />
<br />
&rArr; '''Solution'''<br />
*If you want to continue using the quiesced snapshot feature with Windows VMs hosted on Citrix Hypervisor 8.0 and earlier, do not update to the 9.0.x.x drivers. <br />
<br />
===CBT Backup fails because Xen Server TLS certificate contains wrong ip address===<br />
<br />
'''Problem'''<br />
* CBT Backup fails with Error: Failed to get NBD client for device '******: NBD client connection error: hostname '****' doesn't match u'******''<br />
<br />
'''Cause'''<br />
The TLS certificate of a Xen Server contains a wrong ip address. Therefore no NBD session can be established.<br />
<br />
&rArr; '''Solution'''<br />
* Check all Xen Servers in the Pool whether the ip address in the certificate matches<br />
* On the Xen Server where it does not match execute <br />
/opt/xensource/libexec/generate_ssl_cert<br />
to generate a new certificate<br />
<br />
=== Message "Upload to URL ... failed" appears during restore, "insufficient space" error occurs during backup===<br />
<br />
'''Problems'''<br />
*Restore fails with an error: "Upload to URL ... failed."<br />
*SR_BACKEND_FAILURE_44: : There is insufficient space to create snapshot on Storage Repository. <br />
<br />
'''Possible cause'''<br />
*There is not enough space available on the default storage.<br />
*If the "insufficient space" error occurs during the backup, it might be related to the snapshot process. XenServer was unable to create a snapshot for the VM because there was not enough space in your Storage Repository.<br />
<br />
&rArr; '''Solution'''<br />
*Use XenCenter to select another default storage that has enough free disk capacity to store the virtual disk(s).<br />
<br />
'''Other issues'''<br />
<ul><li>Some errors are not reported in detail by XEN API. More information can be found in XenServer in ''/var/log'' directory.</li><br />
<li>In some pool configurations all pool members must have their management interface listed in DNS.</li><br />
<li>If the settings below don't agree on asynchronous routing and connection drops and/or 3 second or 80 second delays, opening sockets may occour. This is very similar to having 2 network cards configured with ipv4 to the same subnet and connected to the same switch.</li><br />
<li>If you use Cisco switches and you have configured (Citrix unsupported) ''lacp bonding 802.3ad'', ensureit is very important that both sides agree on the balancing type. The Linux default is ''layer2'' and the Cisco default is ''layer3+4''.</li> <br />
<li>Check the bonding mode on the host with <tt>cat /proc/net/bond/bond*</tt> for bonding mode:</li> <br />
IEEE 802.3ad Dynamic link aggregation<br /><br />
Transmit Hash Policy: layer2 (0) or Transmit Hash Policy: layer3+4 (1).<br />
<li>Users have reported that this command and a reboot solves the problem, but this cannot be formally recommended due to its untested and unsupported status:</li><br />
xe pif-param-set uuid=${UUID_OF_BOND_PIF} other-config:bond-xmit_hash_policy=1 <br />
<li>In the common situation where 802.1ad with xmit_hash_policy=1 and STP are in use, multiple settings need to be adjusted on the Cisco side according to the article [http://support.citrix.com/article/CTX123158 Considerations for Connecting XenServer to the Switch Ports].</li><br />
<li>Most other network related performance and reliability issues can be resolved with [http://support.citrix.com/article/CTX123158 Considerations for Connecting XenServer to the Switch Ports].</li><br />
<li>In some situations when using thin storage repositories, an sr rescan is necessary to re-detect free space before a backup or restore.</li><br />
</ul><br />
<noinclude>== See also ==<br />
[[Special:MyLanguage/Citrix_XEN_Server|Citrix XEN Server]]</noinclude></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Changed_Block_Tracking_(CBT)/de&diff=171914Source:Changed Block Tracking (CBT)/de2020-11-19T14:45:56Z<p>Fho: Created page with "=={{anchor|VMware}}CBT auf VMware=="</p>
<hr />
<div><languages/><br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Tigon''/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/SEP_sesam_Documentation|Dokumentationsarchiv]]}}<br /><br />
==Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge#cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Weitere Quellen</b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:VMware_Backup|VMware Backup]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3:VMware Requirements & Restrictions|VMware Anforderungen & Beschränkungen]] – [[Special:MyLanguage/4_4_3_Tigon:VMware_Backup|VMware Sicherung]] – [[Special:MyLanguage/4_4_3:VMware_Restore|VMware Rücksicherung]] – [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:VMware_Instant_Recovery|VMware Instant Recovery]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Im Problemfall nutzen Sie den [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]. <br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=Special:MyLanguage/SEP_sesam_Documentation]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Falls Sie eine ältere SEP sesam Version verwenden, schauen Sie bitte ins [[Special:MyLanguage/SEP_sesam_Documentation|Dokumentationsarchiv]].<br />
|}</div><br />
<br />
The Changed Block Tracking (CBT) feature is an incremental backup technology for VMware and Citrix XenServer that identifies changes on block level and backs up only disk blocks of a VM’s virtual disk that have changed since the last backup; in case of VMware it also backs up the blocks that are in use (on VMFS partitions). SEP sesam uses CBT to perform block level incremental ([[Special:MyLanguage/SEP_sesam_Glossary#INCR|INC]]) and differential ([[Special:MyLanguage/SEP_sesam_Glossary#DIFF|DIFF]]) backups of [[Special:MyLanguage/SEP_sesam_Glossary#VMDK|VMDKs]] (VMware) or VDIs (Citrix XenServer) after a full ([[Special:MyLanguage/SEP_sesam_Glossary#FULL|FULL]]) backup has been successfully executed.<br />
<br />
SEP sesam enables CBT automatically by default to optimize backups of VMs. This way the amount of copied data is reduced, which results in reduced amount of time for the backups, reduced network bandwidth required for transferring data, and reduced required storage capacity.<br />
<br />
CBT tracks changes of the corresponding VMDK/VDI file in special log file (CTK on VMware, log file on Citrix XenServer). These files are permanent and must not be deleted after the backups.<br />
<br />
> [[Special:MyLanguage/Changed_Block_Tracking_(CBT)#VMware|CBT mit VMware]]<br />
<br />
> [[Special:MyLanguage/Changed_Block_Tracking_(CBT)#Citrix|CBT on Citrix XenServer]]<br />
<br />
=={{anchor|VMware}}CBT auf VMware==<br />
SEP sesam provides efficient data protection for virtual machines (VMs) running on VMware ESXi servers by using [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1021175 ''VMware vSphere Storage APIs – Data Protection''] (VADP). Part of the VADP is also Changed Block Tracking (CBT). CBT can identify the disk sectors altered between two change set IDs on many file systems and, on VMFS partitions, can also identify all the disk sectors that are in use.<br />
<br />
===Prerequisites for using CBT===<br />
SEP sesam enables CBT globally by default if the following prerequisites are met:<br />
*The host must be ESX/ESXi 4.0 or later.<br />
*VMs must be using hardware version 7 or newer.<br />
*I/O operations must go through the ESX/ESXi storage stack. NFS is supported, RDM is also supported in virtual compatibility mode, but not in physical compatibility mode (''rdmp''). VMFS is supported, backed by SAN, iSCSI, or local disk.<br />
*Virtual machine storage must not be (persistent or non-persistent) independent disk – unaffected by snapshots.<br />
*If there are any existing snapshots of VM, CBT cannot be enabled.<br />
<br />
===CBT restrictions===<br />
SEP sesam uses CBT for performing incremental backups and calls VMware ''QueryChangedDiskAreas("*")'' for the list of changed areas from the last given snapshot that should be included in backup. ''QueryChangedDiskAreas("*")'' is done in full backups; it returns information about areas of a virtual disk that are in use (allocated). The first time ''QueryChangedDiskAreas("*")'' is called, it returns allocated areas of virtual disk. All subsequent calls then return changed areas rather than allocated areas. Note that what CBT does depends on the disk type; it would return used space only for thin and thick lazy zeroed disks.<br />
<br />
VMware states the following restriction: Be aware that entire disks are allocated, and are therefore returned when ''QueryChangedDiskAreas("*")'' is used in the following scenarios:<br />
*When a cloned <tt>thick</tt> disk is created.<br />
*Disks are formatted by using the ''long format'' setting.<br />
*Disks are created with ''vmkfstools'' using the <tt>eagerZeroedThick</tt> format option – eager zeroed thick disks.<br />
*VMDK is stored on the storage which does not support VMFS, such as NFS or iSCSI devices.<br />
<br />
Additionally, the following restrictions apply for CBT:<br />
*VMware does not support enabling CBT on a VM that already has some existing snapshots. As specified by VMware, for CBT to work "the virtual machine must have zero (0) snapshots when CBT is enabled, for a clean start".<br />
*Prior to vSphere 6.5, the ''QueryChangedDiskAreas("*")'' returns an error if the CBT data is corrupt. This would lead to an inflated (but correct) incremental/differential backup. However, as of vSphere 6.5, the ''QueryChangedDiskAreas("*")'' no longer returns an error for corrupt CBT data, which may lead to corrupt or incomplete incremental/differential backup.<br />
<br />
For more details on CBT, see the VMware article [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1020128 Changed Block Tracking (CBT) on virtual machines].<br />
<br />
==={{anchor|globally}}Disabling and enabling CBT for VMware globally===<br />
<br />
By default, SEP sesam enables the CBT functionality globally. CBT is enabled per virtual disk. In SEP sesam v. ≤ [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Grolar'']], it was possible to disable/enable CBT in the backup task properties, as described in the section below [[Special:MyLanguage/Changed_Block_Tracking_(CBT)#bck_task|Disabling and enabling CBT in backup task]]. This is no longer supported in v. ≥ 4.4.3 ''Beefalo''.<br />
<br />
{{Anmerkung|Typically, there is no need to disable CBT. By disabling CBT, the respective VM's FULL/DIFF/INC backup chain is aborted without the possibility to perform subsequent DIFF and INC backups. Only COPY backups are possible which means that the whole VMDK including empty blocks (provisioned size means that the size of a backup and the size of VMDK equals) will be backed up each time.}}<br />
<br />
<ol><li>In the SEP sesam GUI, from the ''menu bar'' select '''Configuration''' -> '''Defaults''', and then switch to tab '''Extras'''.</li> <br />
<li>Under the ''Extras'' options, select or deselect the check box '''Globally activate changed block tracking (CBT)'''.</li><br />
[[File:CBT_global_Beefalo_V2_de.jpg|600px|link=]]<br />
<br clear=all><br />
</ol><br />
<br />
==={{anchor|bck_task}}Disabling and enabling CBT in backup task (v. ≤ ''Grolar'') ===<br />
<br />
In v. ≤ [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Grolar'']], you can also disable/enable the CBT functionality in the backup tasks properties. This change takes effect when the next backup is run and is applied to all backup tasks related to the respective VM. <br />
<br />
{{Anmerkung|Typically, there is no need to disable CBT. By disabling CBT, the respective VM's FULL/DIFF/INC backup chain is aborted without the possibility to perform subsequent DIFF and INC backups. Only COPY backups are possible which means that the whole VMDK including empty blocks (provisioned size means that the size of a backup and the size of VMDK equals) will be backed up each time.}}<br />
<br />
<ol><li>From '''Main Selection -> Tasks -> By Clients''', select the ''vCenter'' client and click '''New Backup Task''', or double-click an already existing backup task.</li><br />
<li>If you are creating a new backup task, specify the '''Source'''. Browse for the VM that you want to include in the backup and select it. Note that you can only configure one VM per backup task. By selecting the source, the ''[[Special:MyLanguage/SEP_sesam_Glossary#task_type|task type]]'' and ''task name'' are set automatically.</li><br />
If you are changing only the CBT option, move to the next step.<br />
<li>Use the following options carefully.</li><br />
[[image:Backup_as_image-CBT_default_de.jpg|link=]]<br />
<br clear=all><br />
<ul><li>By default, '''Backup as Image''' option is enabled and performs a FULL raw backup of VMDK without CBT, even though the CBT is selected. However, CBT is applied for subsequent differential and incremental backups. If ''Backup as image'' option is deselected while the CBT stays enabled, the CBT is fully utilized. For details on how the combination of these options affects the size of your backed up data, check [[Special:MyLanguage/4_4_3 Tigon:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|VMware single file restore & instant recovery support matrix]].</li><br />
<li>If you want to exclude a dedicated virtual disk (VMDK) from snapshot operations and backup only VM configuration, select the '''Backup only the VM configuration''' check box. In this case, only Open Virtualization Format (OVF) file and VM configuration are backed up.</li><br />
<li>{{anchor|CBT}}By default, '''Changed Block Tracking''' option is enabled. Disabling it will break a CBT backup chain (full, differential, incremental) for all backup tasks related to the same VM! If enabled again, you must run a full backup to start a new backup chain.<br />
{{note|Resetting CBT requires administrator privileges.}}<br />
</ul><br />
<li>Click '''OK''' to save the task.</li></ol><br />
<br />
=={{anchor|Citrix}}CBT on Citrix XenServer==<br />
<br />
CBT support for for Citrix XenServer ≥ 7.3 was introduced with v. 4.4.3 [[Special:MyLanguage/SEP_sesam_Release_Versions|''Grolar'']]. It is available for clients with XenServer Enterprise Edition by default.<br />
<br />
CBT provides incremental backup capabilities; hence, all backup levels (FULL, INC and DIFF) can be used for Citrix XenServer backups. Since CBT for Citrix XenServer ≥ 7.3 is enabled by default, it can be skipped only by performing a copy backup. For details, see [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]].<br />
<br />
There are some considerations to take into account when restoring a differential or incremental backup from Citrix Xen VM. For details, see [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore#CBT|Citrix XenServer Restore]]. <br />
<br />
==Siehe auch==<br />
[[Special:MyLanguage/4_4_3:VMware Requirements & Restrictions|VMware Anforderungen & Beschränkungen]] – [[Special:MyLanguage/4_4_3_Tigon:VMware_Backup|VMware Sicherung]] – [[Special:MyLanguage/4_4_3:VMware_Restore|VMware Rücksicherung]] – [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:VMware_Instant_Recovery|VMware Instant Recovery]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]</div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:Source:Changed_Block_Tracking_(CBT)/40/de&diff=171913Translations:Source:Changed Block Tracking (CBT)/40/de2020-11-19T14:45:56Z<p>Fho: Created page with "=={{anchor|VMware}}CBT auf VMware=="</p>
<hr />
<div>=={{anchor|VMware}}CBT auf VMware==</div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Changed_Block_Tracking_(CBT)/de&diff=171912Source:Changed Block Tracking (CBT)/de2020-11-19T14:45:43Z<p>Fho: Created page with "CBT mit VMware"</p>
<hr />
<div><languages/><br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Tigon''/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/SEP_sesam_Documentation|Dokumentationsarchiv]]}}<br /><br />
==Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge#cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Weitere Quellen</b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:VMware_Backup|VMware Backup]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3:VMware Requirements & Restrictions|VMware Anforderungen & Beschränkungen]] – [[Special:MyLanguage/4_4_3_Tigon:VMware_Backup|VMware Sicherung]] – [[Special:MyLanguage/4_4_3:VMware_Restore|VMware Rücksicherung]] – [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:VMware_Instant_Recovery|VMware Instant Recovery]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Im Problemfall nutzen Sie den [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]. <br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=Special:MyLanguage/SEP_sesam_Documentation]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Falls Sie eine ältere SEP sesam Version verwenden, schauen Sie bitte ins [[Special:MyLanguage/SEP_sesam_Documentation|Dokumentationsarchiv]].<br />
|}</div><br />
<br />
The Changed Block Tracking (CBT) feature is an incremental backup technology for VMware and Citrix XenServer that identifies changes on block level and backs up only disk blocks of a VM’s virtual disk that have changed since the last backup; in case of VMware it also backs up the blocks that are in use (on VMFS partitions). SEP sesam uses CBT to perform block level incremental ([[Special:MyLanguage/SEP_sesam_Glossary#INCR|INC]]) and differential ([[Special:MyLanguage/SEP_sesam_Glossary#DIFF|DIFF]]) backups of [[Special:MyLanguage/SEP_sesam_Glossary#VMDK|VMDKs]] (VMware) or VDIs (Citrix XenServer) after a full ([[Special:MyLanguage/SEP_sesam_Glossary#FULL|FULL]]) backup has been successfully executed.<br />
<br />
SEP sesam enables CBT automatically by default to optimize backups of VMs. This way the amount of copied data is reduced, which results in reduced amount of time for the backups, reduced network bandwidth required for transferring data, and reduced required storage capacity.<br />
<br />
CBT tracks changes of the corresponding VMDK/VDI file in special log file (CTK on VMware, log file on Citrix XenServer). These files are permanent and must not be deleted after the backups.<br />
<br />
> [[Special:MyLanguage/Changed_Block_Tracking_(CBT)#VMware|CBT mit VMware]]<br />
<br />
> [[Special:MyLanguage/Changed_Block_Tracking_(CBT)#Citrix|CBT on Citrix XenServer]]<br />
<br />
=={{anchor|VMware}}CBT on VMware==<br />
SEP sesam provides efficient data protection for virtual machines (VMs) running on VMware ESXi servers by using [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1021175 ''VMware vSphere Storage APIs – Data Protection''] (VADP). Part of the VADP is also Changed Block Tracking (CBT). CBT can identify the disk sectors altered between two change set IDs on many file systems and, on VMFS partitions, can also identify all the disk sectors that are in use.<br />
<br />
===Prerequisites for using CBT===<br />
SEP sesam enables CBT globally by default if the following prerequisites are met:<br />
*The host must be ESX/ESXi 4.0 or later.<br />
*VMs must be using hardware version 7 or newer.<br />
*I/O operations must go through the ESX/ESXi storage stack. NFS is supported, RDM is also supported in virtual compatibility mode, but not in physical compatibility mode (''rdmp''). VMFS is supported, backed by SAN, iSCSI, or local disk.<br />
*Virtual machine storage must not be (persistent or non-persistent) independent disk – unaffected by snapshots.<br />
*If there are any existing snapshots of VM, CBT cannot be enabled.<br />
<br />
===CBT restrictions===<br />
SEP sesam uses CBT for performing incremental backups and calls VMware ''QueryChangedDiskAreas("*")'' for the list of changed areas from the last given snapshot that should be included in backup. ''QueryChangedDiskAreas("*")'' is done in full backups; it returns information about areas of a virtual disk that are in use (allocated). The first time ''QueryChangedDiskAreas("*")'' is called, it returns allocated areas of virtual disk. All subsequent calls then return changed areas rather than allocated areas. Note that what CBT does depends on the disk type; it would return used space only for thin and thick lazy zeroed disks.<br />
<br />
VMware states the following restriction: Be aware that entire disks are allocated, and are therefore returned when ''QueryChangedDiskAreas("*")'' is used in the following scenarios:<br />
*When a cloned <tt>thick</tt> disk is created.<br />
*Disks are formatted by using the ''long format'' setting.<br />
*Disks are created with ''vmkfstools'' using the <tt>eagerZeroedThick</tt> format option – eager zeroed thick disks.<br />
*VMDK is stored on the storage which does not support VMFS, such as NFS or iSCSI devices.<br />
<br />
Additionally, the following restrictions apply for CBT:<br />
*VMware does not support enabling CBT on a VM that already has some existing snapshots. As specified by VMware, for CBT to work "the virtual machine must have zero (0) snapshots when CBT is enabled, for a clean start".<br />
*Prior to vSphere 6.5, the ''QueryChangedDiskAreas("*")'' returns an error if the CBT data is corrupt. This would lead to an inflated (but correct) incremental/differential backup. However, as of vSphere 6.5, the ''QueryChangedDiskAreas("*")'' no longer returns an error for corrupt CBT data, which may lead to corrupt or incomplete incremental/differential backup.<br />
<br />
For more details on CBT, see the VMware article [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1020128 Changed Block Tracking (CBT) on virtual machines].<br />
<br />
==={{anchor|globally}}Disabling and enabling CBT for VMware globally===<br />
<br />
By default, SEP sesam enables the CBT functionality globally. CBT is enabled per virtual disk. In SEP sesam v. ≤ [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Grolar'']], it was possible to disable/enable CBT in the backup task properties, as described in the section below [[Special:MyLanguage/Changed_Block_Tracking_(CBT)#bck_task|Disabling and enabling CBT in backup task]]. This is no longer supported in v. ≥ 4.4.3 ''Beefalo''.<br />
<br />
{{Anmerkung|Typically, there is no need to disable CBT. By disabling CBT, the respective VM's FULL/DIFF/INC backup chain is aborted without the possibility to perform subsequent DIFF and INC backups. Only COPY backups are possible which means that the whole VMDK including empty blocks (provisioned size means that the size of a backup and the size of VMDK equals) will be backed up each time.}}<br />
<br />
<ol><li>In the SEP sesam GUI, from the ''menu bar'' select '''Configuration''' -> '''Defaults''', and then switch to tab '''Extras'''.</li> <br />
<li>Under the ''Extras'' options, select or deselect the check box '''Globally activate changed block tracking (CBT)'''.</li><br />
[[File:CBT_global_Beefalo_V2_de.jpg|600px|link=]]<br />
<br clear=all><br />
</ol><br />
<br />
==={{anchor|bck_task}}Disabling and enabling CBT in backup task (v. ≤ ''Grolar'') ===<br />
<br />
In v. ≤ [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Grolar'']], you can also disable/enable the CBT functionality in the backup tasks properties. This change takes effect when the next backup is run and is applied to all backup tasks related to the respective VM. <br />
<br />
{{Anmerkung|Typically, there is no need to disable CBT. By disabling CBT, the respective VM's FULL/DIFF/INC backup chain is aborted without the possibility to perform subsequent DIFF and INC backups. Only COPY backups are possible which means that the whole VMDK including empty blocks (provisioned size means that the size of a backup and the size of VMDK equals) will be backed up each time.}}<br />
<br />
<ol><li>From '''Main Selection -> Tasks -> By Clients''', select the ''vCenter'' client and click '''New Backup Task''', or double-click an already existing backup task.</li><br />
<li>If you are creating a new backup task, specify the '''Source'''. Browse for the VM that you want to include in the backup and select it. Note that you can only configure one VM per backup task. By selecting the source, the ''[[Special:MyLanguage/SEP_sesam_Glossary#task_type|task type]]'' and ''task name'' are set automatically.</li><br />
If you are changing only the CBT option, move to the next step.<br />
<li>Use the following options carefully.</li><br />
[[image:Backup_as_image-CBT_default_de.jpg|link=]]<br />
<br clear=all><br />
<ul><li>By default, '''Backup as Image''' option is enabled and performs a FULL raw backup of VMDK without CBT, even though the CBT is selected. However, CBT is applied for subsequent differential and incremental backups. If ''Backup as image'' option is deselected while the CBT stays enabled, the CBT is fully utilized. For details on how the combination of these options affects the size of your backed up data, check [[Special:MyLanguage/4_4_3 Tigon:VMware_Single_File_Restore_and_Instant_Recovery_Support_Matrix|VMware single file restore & instant recovery support matrix]].</li><br />
<li>If you want to exclude a dedicated virtual disk (VMDK) from snapshot operations and backup only VM configuration, select the '''Backup only the VM configuration''' check box. In this case, only Open Virtualization Format (OVF) file and VM configuration are backed up.</li><br />
<li>{{anchor|CBT}}By default, '''Changed Block Tracking''' option is enabled. Disabling it will break a CBT backup chain (full, differential, incremental) for all backup tasks related to the same VM! If enabled again, you must run a full backup to start a new backup chain.<br />
{{note|Resetting CBT requires administrator privileges.}}<br />
</ul><br />
<li>Click '''OK''' to save the task.</li></ol><br />
<br />
=={{anchor|Citrix}}CBT on Citrix XenServer==<br />
<br />
CBT support for for Citrix XenServer ≥ 7.3 was introduced with v. 4.4.3 [[Special:MyLanguage/SEP_sesam_Release_Versions|''Grolar'']]. It is available for clients with XenServer Enterprise Edition by default.<br />
<br />
CBT provides incremental backup capabilities; hence, all backup levels (FULL, INC and DIFF) can be used for Citrix XenServer backups. Since CBT for Citrix XenServer ≥ 7.3 is enabled by default, it can be skipped only by performing a copy backup. For details, see [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]].<br />
<br />
There are some considerations to take into account when restoring a differential or incremental backup from Citrix Xen VM. For details, see [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore#CBT|Citrix XenServer Restore]]. <br />
<br />
==Siehe auch==<br />
[[Special:MyLanguage/4_4_3:VMware Requirements & Restrictions|VMware Anforderungen & Beschränkungen]] – [[Special:MyLanguage/4_4_3_Tigon:VMware_Backup|VMware Sicherung]] – [[Special:MyLanguage/4_4_3:VMware_Restore|VMware Rücksicherung]] – [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:VMware_Instant_Recovery|VMware Instant Recovery]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Sicherung]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Rücksicherung]]</div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:Source:Changed_Block_Tracking_(CBT)/38/de&diff=171911Translations:Source:Changed Block Tracking (CBT)/38/de2020-11-19T14:45:43Z<p>Fho: Created page with "CBT mit VMware"</p>
<hr />
<div>[[Special:MyLanguage/Changed_Block_Tracking_(CBT)#VMware|CBT mit VMware]]</div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3_Beefalo:SEP_sesam_OS_and_Database_Support_Matrix&diff=1719104 4 3 Beefalo:SEP sesam OS and Database Support Matrix2020-11-19T14:29:12Z<p>Fho: /* {{anchor|VMware}}VMware */</p>
<hr />
<div>{{Copyright SEP AG en}}<br />
<br />
== Overview ==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><br />
Additional resources</b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" |<br />
[[File:SEP_next.png|45px|link=Special:MyLanguage/SEP_sesam_Storage_Hardware_Support_Matrix|SEP sesam Storage Hardware Support Matrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |<br />
See also: [[Special:MyLanguage/SEP_sesam_Storage_Hardware_Support_Matrix|SEP sesam Storage Hardware Support Matrix]] – [[Special:MyLanguage/Java_Compatibility_Matrix|Java Compatibility Matrix]]<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" |<br />
[[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |<br />
Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions.<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" |<br />
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |<br />
Problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].<br />
|}<br />
</div><br />
The support matrix lists all the configurations and versions currently supported by SEP sesam and SEP IT-Save. SEP sesam automatically detects your environment's hardware configuration. Note that SEP sesam only recognizes storage devices known or listed by the operating system, such as OS where the Master Server/Remote Device Server will be installed. For details, see [[SEP_sesam_Storage_Hardware_Support_Matrix|Storage Hardware page]].<br /><br />
See also new [[Release_Notes_4.4.3_Beefalo|release notes v. 4.4.3 ''Beefalo'']].<br />
<br />
== SEP sesam Backup Servers and Clients ==<br />
<br />
;Versions older than 4.4: For each operating system the latest SEP sesam version is listed, thus ensuring that the listed version works with 4.4 SEP sesam Server. For example, a SLES7 running version 3.4 of a SEP sesam Client will be backed up by a SEP sesam Server version 4.4.2. There will be no development for versions prior to 4.4; however the support and bug fixes are still available. <br />
<br />
''It is recommended to upgrade the SEP sesam server and client components to the latest version during the regular upgrade process (check the list of [[SEP_sesam_Release_Versions|SEP sesam release versions]]). This ensures the highest possible protection of the SEP sesam Clients. Customers with a valid [[Licensing|license]] are eligible for a free SEP sesam upgrade for any new release until the end of the license term. Before upgrading your SEP sesam environment, check the support matrix and [[4_4_3_Beefalo:SEP_sesam_OS_and_Database_Support_Matrix#compatibility|compatibility]].''<br />
<br />
{{Note|<br />
<ul><li>'''Tar (.tgz) installation no longer available'''</li><br />
Since SEP sesam V4.4 tar files are no longer available. For earlier SEP sesam versions, SEP provides generic tar (<tt>.tgz</tt>) installation kits of SEP sesam for Linux based on glibc 2.0-2.4 on i386/x86-64. They can be used for almost all Linux distributions, but SEP provides no guarantees of their usability. Support is available on a best effort basis.<br /><br />
'''''Attention:''''' No support is offered for tar installations on systems, where native packages are available.<br />
<li>{{anchor|compatibility}}'''SEP sesam Server 4.2 or lower compatibility issue'''</li> <br />
SEP sesam GUI version 4.4 does not support downgrading to SEP sesam Server version 4.2 or lower. Installing SEP sesam GUI 4.4 in the environment with a lower SEP sesam Server version causes errors due to incompatibility of SEP sesam GUI version 4.4 with older SEP sesam Server versions. Since there is no GUI backward compatibility and the GUI cannot be downgraded to version 4.2, you should download and install SEP sesam GUI version 4.2 from {{download}} to preserve compatibility with SEP sesam 4.2 or lower.</ul>}}<br />
<br />
; '''''Click for version'''''<br />
:{| cellpadding="5" cellspacing="0" style="width:100%" <br />
| &rarr;[[#Linux|'''''Linux''''']] || &rarr;[[#Windows|'''''Windows''''']] || &rarr;[[#Solaris|'''''Solaris''''']] || &rarr;[[#AIX|'''''AIX''''']] || &rarr;[[#MacOS|'''''MacOS''''']] || &rarr;[[#BSD|'''''BSD''''']] || &rarr;[[#HP-UX|'''''HP-UX''''']] || &rarr;[[#NetApp_ONTAP|'''''NetApp ONTAP''''']]|| &rarr;[[#NetWare|'''''NetWare''''']] || &rarr;[[#NDMP|'''''NDMP''''']] || &rarr;[[#Other|'''''Other''''']]<br />
|}<br />
<br />
==={{anchor|Linux}}Linux===<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#73BA25; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" | {{anchor|SUSE}}SUSE<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|-<br />
|[https://download.sep.de/linux/SuSE SLES15] (ppc)|| 4.4.3.84 || 4.4.3.84 ||4.4.3.84 ||4.4.3.84<br />
|-<br />
|[https://download.sep.de/linux/SuSE SLES15] (x86-64) || 4.4.3 || 4.4.3 ||4.4.3 ||4.4.3 <br />
|-<br />
|[https://download.sep.de/linux/SuSE SLES12] (x86-64) || 4.4 || 4.4 ||4.4 ||4.4<br />
|-<br />
|[https://download.sep.de/linux/SuSE SLES12] (Power, IBM z Systems, IBM LinuxONE) || 4.4 || 4.4 || 4.4 ||4.4<br />
|-<br />
|[https://download.sep.de/linux/SuSE SLES11] (i386, x86-64) || 4.4 || 4.4. ||4.4 ||4.4<br />
|-<br />
|[https://download.sep.de/linux/SuSE SLES11] (Power) || 4.4 ||4.4 || 4.4 ||4.4<br />
|-<br />
<!-- Comment <br />
* SLES11 (Power) will be built if customer request comes up!<br />
|[https://download.sep.de/linux/SuSE SLES11] (i386, x86-64) || 4.4 ||style="color: grey; font-style: italic;" | {{H:title|This is the last supported SEP sesam Server version for SLES11|4.4.3.64}}||4.4 ||4.4<br />
|-<br />
|[https://download.sep.de/linux/SuSE SLES11] (Power) || 4.4 ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for SLES11|4.4.3.64}} || 4.4 ||4.4<br />
|-<br />
--><br />
|[https://download.sep.de/linux/SuSE SLES10] (i386, x86-64) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for SLES10|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for SLES10|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for SLES10|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for SLES10|4.2}}<br />
|-<br />
|[https://download.sep.de/linux/SuSE SLES9] (i386, x86-64, Power) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for SLES9|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for SLES9|4.2.1.34}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for SLES9|4.2.1.34}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for SLES9|4.2.1.34}}<br />
|-<br />
|[https://download.sep.de/linux/SuSE/i386/ SLES8] (i386) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for SLES8|4.0}} || || ||<br />
|-<br />
|[https://download.sep.de/linux/other/i386/ SLES7] (i386) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for SLES7|4.0}} || || || <br />
|- <br />
|[https://download.sep.de/linux/SuSE OES 2018] (x86-64) <sup>[[#notea|'''Note<sup>a</sup>''']]</sup> || 4.4 || 4.4 || 4.4 ||4.4 <br />
|- <br />
|[https://download.sep.de/linux/SuSE OES 2015] (x86-64) <sup>[[#noteb|'''Note<sup>b</sup>''']]</sup> || 4.4 || 4.4 || 4.4 ||4.4 <br />
|-<br />
|[https://download.sep.de/linux/SuSE OES11 SP2 or higher] (x86-64) <sup>[[#noteb|'''Note<sup>b</sup>''']]</sup> || 4.4 || 4.4 || 4.4 ||4.4 <br />
|- <br />
|[https://download.sep.de/linux/SuSE OES11] (x86-64) || 4.4 || 4.4 || 4.4 ||4.4 <br />
|-<br />
|[https://download.sep.de/linux/SuSE OES2] (x86-64) || 4.4 || 4.4 || 4.4 ||4.4 <br />
|-<br />
|[https://download.sep.de/linux/SuSE OES2] (i386) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for SuSE OES2|4.2}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for SuSE OES2|4.2}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for SuSE OES2|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for SuSE OES2|4.2}}<br />
|-<br />
|[https://download.sep.de/linux/SuSE OES1] (i386, x86-64) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for SuSE OES1|4.2.1.34}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for SuSE OES1|4.2.1.34}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for SuSE OES1|4.2.1.34}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for SuSE OES1|4.2.1.34}} <br />
|-<br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
<div id="notea"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>a</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">The SEP sesam Micro Focus (Novell) OES module is already a part of the SLES 12 packages. It is not required to download and install any separate sesam-novell-client package.</span><br />
<div id="noteb"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>b</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; ">OES11 SP2 eDirectory (NetIQ Directory) is supported by SEP sesam since version 4.2.2-40 and with SEP Sesam Novell Client 4.2.2-35. For additional information, see [[OES11Sp2_eDir_en |OES11Sp2 eDir]].</span><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|} <br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background: #FC0203; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" | {{anchor|Red_Hat}}Red Hat<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|[https://download.sep.de/linux/RedHat RHEL8] (x86-64) || [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']] || [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']] || [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']]||[[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']]<br />
|-<br />
|[https://download.sep.de/linux/RedHat RHEL7] (x86-64) || 4.4 || 4.4 || 4.4 ||4.4 <br />
|-<br />
|[https://download.sep.de/linux/RedHat RHEL7] (Power, IBM z Systems, IBM LinuxONE) || 4.4 || 4.4 || 4.4 ||4.4 <br />
|- <br />
|[https://download.sep.de/linux/RedHat RHEL6] (x86-64) || 4.4 || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for RHEL6|4.4.3.64}} || 4.4 ||4.4<br />
|- <br />
|[https://download.sep.de/linux/RedHat RHEL6] (Power) || 4.4 ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for RHEL6|4.4.3.64}} || 4.4 ||4.4<br />
|-<br />
|[https://download.sep.de/linux/RedHat RHEL6] (i386) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for RHEL6|4.2}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for RHEL6|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for RHEL6|4.2.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for RHEL6|4.2}}<br />
|- <br />
|[https://download.sep.de/linux/RedHat RHEL5] (i386, x86-64) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for RHEL5|4.2}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for RHEL5|4.2}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for RHEL5|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for RHEL5|4.2}} <br />
|-<br />
|[https://download.sep.de/linux/RedHat/i386/RHEL4/ RHEL4] (i386) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for RHEL4|4.2.1.34 }} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for RHEL4|4.2.1.34 }}|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for RHEL4|4.2.1.34 }} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for RHEL4|4.2.1.34 }} <br />
|-<br />
|[https://download.sep.de/linux/RedHat/x86_64/RHEL8/ CentOS 8] (x86-64) || [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']] || [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']] || [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']]||[[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']]<br />
|-<br />
|[https://download.sep.de/linux/RedHat/x86_64/RHEL7/ CentOS 7] (x86-64) || 4.4 || 4.4 ||4.4 ||4.4<br />
|-<br />
|[https://download.sep.de/linux/RedHat/i386/RHEL6/ CentOS 6] (i386) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for CentOS 6 (i386)|4.2}}|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for CentOS 6 (i386)|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for CentOS 6 (i386)|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for CentOS 6 (i386)|4.2}}<br />
|-<br />
|[https://download.sep.de/linux/RedHat/x86_64/RHEL6/ CentOS 6] (x86-64) || 4.4 || 4.4 ||4.4 ||4.4<br />
|-<br />
|[https://download.sep.de/linux/RedHat/i386/RHEL5/ CentOS 5] (i386) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for CentOS 5 (i386)|4.2}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for CentOS 5 (i386)|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for CentOS 5 (i386)|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for CentOS 5 (i386)|4.2}}<br />
|-<br />
|[https://download.sep.de/linux/RedHat/x86_64/RHEL5/ CentOS 5] (x86-64) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for CentOS 5 (x86-64)|4.2}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for CentOS 5 (x86-64)|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for CentOS 5 (x86-64)|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for CentOS 5 (x86-64)|4.2}}<br />
|-<br />
|[https://download.sep.de/linux/RedHat/i386/RHEL4/ CentOS 4] (i386) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for CentOS 4 (i386)|4.2.1.34}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for CentOS 4 (i386)|4.2.1.34}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for CentOS 4 (i386)|4.2.1.34}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for CentOS 4 (i386)|4.2.1.34}}<br />
|-<br />
|}<br />
<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|} <br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background: #9D0000; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" | Oracle<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|[https://download.sep.de/linux/RedHat Oracle Linux 8] (x86-64) <sup>[[#note6a|'''Note<sup>a</sup>''']]</sup> || 4.4.3 ''Beefalo'' || 4.4.3 ''Beefalo''|| 4.4.3 ''Beefalo'' || 4.4.3 ''Beefalo''<br />
|- <br />
|[https://download.sep.de/linux/RedHat Oracle Linux 7] (x86-64) || 4.4 || 4.4 || 4.4 ||4.4 <br />
|- <br />
|[https://download.sep.de/linux/RedHat Oracle Linux 6] (x86-64) || 4.4 || 4.4 || 4.4 ||4.4 <br />
|-<br />
|[https://download.sep.de/linux/RedHat Oracle Linux 6] (i386) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Oracle Linux 6 (i386)|4.2}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Oracle Linux 6 (i386)|4.2}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Oracle Linux 6 (i386)|4.2.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Oracle Linux 6 (i386)|4.2}}<br />
|-<br />
|[https://download.sep.de/linux/RedHat Oracle Linux 7 - Unbreakable Enterprise Linux Kernel (UEK)] (x86-64) || 4.4 || 4.4 || 4.4 ||4.4 <br />
|-<br />
|[https://download.sep.de/linux/RedHat Oracle Linux 6 - Unbreakable Enterprise Linux Kernel (UEK)] (x86-64) || 4.4 || 4.4 || 4.4 ||4.4 <br />
|-<br />
|[https://download.sep.de/linux/RedHat Oracle Linux 6 - Unbreakable Enterprise Linux Kernel (UEK)] (i386) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Oracle Linux 6 - UEK (i386)|4.2}} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Oracle Linux 6 - UEK (i386)|4.2}}|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Oracle Linux 6 - UEK (i386)|4.2.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Oracle Linux 6 - UEK (i386)|4.2}}<br />
|-<br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
<div id="note6a"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>a</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">Oracle Linux 8 requires at least SEP sesam version 4.4.3.71 ''Beefalo'' for Server, RDS and GUI.</span><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|} <br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#D70751; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" |{{anchor|Debian}}Debian<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|[http://download.sep.de/linux/repositories/debian/ Debian 10 Buster] (x86-64) ||4.4.3 ''Beefalo'' ||4.4.3 ''Beefalo'' ||4.4.3 ''Beefalo'' ||4.4.3 ''Beefalo'' <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Debian 9 Stretch] (x86-64) ||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Debian 8 Jessie] (x86-64) ||4.4 ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Debian 8 Jessie|4.4.3.64}}||4.4 ||4.4<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Debian 7 Wheezy] (x86-64)||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Debian 7 Wheezy (x86-64)|4.4.3.64}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Debian 7 Wheezy (x86-64)|4.4.3.48}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Debian 7 Wheezy (x86-64)|4.4.3.48}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Debian 7 Wheezy (x86-64)|4.4.3.48}}<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Debian 7 Wheezy] (i386) ||4.4.3 ''Tigon''||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Debian 7 Wheezy (i386)|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Debian 7 Wheezy (i386)|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Debian 7 Wheezy (i386)|4.2}}<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Debian 6 Squeeze] (i386, x86-64) ||4.4 ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Debian 6 Squeeze|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Debian 6 Squeeze|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Debian 6 Squeeze|4.2}} <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Debian 5 Lenny] (i386, x86-64) ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Debian 5 Lenny|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Debian 5 Lenny|4.2.1.34}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Debian 5 Lenny|4.2.1.34}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Debian 5 Lenny|4.2.1.34}}<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Debian 4 Etch] (i386, x86-64) ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Debian 4 Etch|4.0}} || ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Debian 4 Etch|3.6}}||<br />
|-<br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|} <br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#DE4815; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" |{{anchor|Ubuntu}}Ubuntu<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 20.04 LTS] (x86-64) ||4.4.3.84 ''Beefalo V2'' ||4.4.3.84 ''Beefalo V2'' ||4.4.3.84 ''Beefalo V2'' ||4.4.3.84 ''Beefalo V2''<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 18.04 LTS] (x86-64) ||4.4.3 ||4.4.3 ||4.4.3 ||4.4.3 <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 16.04 LTS] (x86-64, IBM z Systems, IBM LinuxONE) ||4.4 ||4.4 ||4.4 ||4.4 <br />
|- <br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 14.04 LTS] (x86-64) ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Ubuntu 14.04 LTS (x86-64)|4.4.3 ''Grolar''}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Ubuntu 14.04 LTS (x86-64)|4.4.3 ''Tigon V2''}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Ubuntu 14.04 LTS (x86-64)|4.4.3 ''Tigon V2''}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Ubuntu 14.04 LTS (x86-64)|4.4.3 ''Tigon V2''}}<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 14.04 LTS] (i386) ||4.4.3 ''Tigon'' ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Ubuntu 14.04 LTS (i386)|4.4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Ubuntu 14.04 LTS (i386)|4.4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Ubuntu 14.04 LTS (i386)|4.4.2}}<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 12.04 LTS] (x86-64, i386) ||4.4 ||4.4 ||4.4 ||4.4 <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 11.04] (i386) ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Ubuntu 11.04 (i386)|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Ubuntu 11.04 (i386)|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Ubuntu 11.04 (i386)|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Ubuntu 11.04 (i386)|4.2}}<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 11.04] (x86-64) ||4.4 ||4.4 ||4.4 ||4.4 <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 10.04 LTS] (x86-64) ||4.4 ||4.4 ||4.4 ||4.4<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 10.04 LTS] (i386) ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Ubuntu 10.04 LTS (i386)|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Ubuntu 10.04 LTS (i386)|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Ubuntu 10.04 LTS (i386)|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Ubuntu 10.04 LTS (i386)|4.2}}<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 08.10] (i386, x86-64) ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Ubuntu 08.10|4.2.1.34 }} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Ubuntu 08.10|4.2.1.34 }} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Ubuntu 08.10|4.2.1.34 }} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Ubuntu 08.10|4.2.1.34 }} <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 08.04 LTS] (i386, x86-64) ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Ubuntu 08.04 LTS|4.2.1.34 }} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Ubuntu 08.04 LTS|4.2.1.34 }} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Ubuntu 08.04 LTS|4.2.1.34 }} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Ubuntu 08.04 LTS|4.2.1.34 }} <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Ubuntu 07.10] (i386) ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Ubuntu 07.10|4.0}} || || || <br />
|-<br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|} <br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background: #D0002D; color: #FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" | {{anchor|UCS}}Univention<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 4.4] (x86-64)||4.4.3 ''Grolar''||4.4.3 ''Grolar'' ||4.4.3 ''Grolar''||4.4.3 ''Grolar''<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 4.3] (x86-64)||4.4.3 ''Tigon V2'' ||4.4.3 ''Tigon V2'' ||4.4.3 ''Tigon V2'' ||4.4.3 ''Tigon V2''<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 4.2] (x86-64)||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 4.1] (x86-64)||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 4.0] (x86-64)||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' ||4.4.3 ''Tigon'' <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 4.0] (x86-64)||4.4 ||4.4 ||4.4 ||4.4<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 3.2] (i386, x86-64)||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Univention UCS 3.2|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Univention UCS 3.2|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Univention UCS 3.2|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Univention UCS 3.2|4.2}}<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 3.1] (i386, x86-64)||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Univention UCS 3.1|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Univention UCS 3.1|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Univention UCS 3.1|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Univention UCS 3.1|4.2}}<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 3.0] (i386, x86-64)||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Univention UCS 3.0|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Univention UCS 3.0|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Univention UCS 3.0|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Univention UCS 3.0|4.2}} <br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 2.4] (i386, x86-64)||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Univention UCS 2.4|4.2.1.34 }}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Univention UCS 2.4|4.2.1.34 }}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Univention UCS 2.4|4.2.1.34 }}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Univention UCS 2.4|4.2.1.34 }}<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 2.3] (i386, x86-64)||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Univention UCS 2.3|4.2.1.34 }}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Univention UCS 2.3|4.2.1.34 }}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Univention UCS 2.3|4.2.1.34 }}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Univention UCS 2.3|4.2.1.34 }}<br />
|-<br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 2.2] (i386, x86-64)||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Univention UCS 2.2|4.2.1.34 }}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Univention UCS 2.2|4.2.1.34 }}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Univention UCS 2.2|4.2.1.34 }}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Univention UCS 2.2|4.2.1.34 }}<br />
|- <br />
|[https://download.sep.de/linux/repositories/debian/pool/main/s/ Univention UCS 2.0] (i386, x86-64)||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Univention UCS 2.0|4.0 }}|| || ||<br />
|-<br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
{| cellspacing="0" align="right"<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#A2A2A2; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" |{{anchor|Linux_other}}Other<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|-<br />
|[https://download.sep.de/linux/other Other (unsupported)] ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version|4.2}} <br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
{| cellspacing="0" align="right"<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
==={{anchor|Windows}}Windows===<br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#2b5797; color:#FFFFFF"<br />
! scope="col" style="width: 250px; text-align:left;" | Version<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows Server 2019 Core] (x64) <sup>[[#note1a|'''Note<sup>a</sup>''']]</sup> || 4.4.3 ''Grolar'' || || ||<br />
|- <br />
|[https://download.sep.de/windows/x64/ Windows Server 2019] (x64) <sup>[[#note1a|'''Note<sup>a</sup>''']]</sup> || 4.4.3 ''Grolar'' || 4.4.3 ''Grolar'' ||4.4.3 ''Grolar'' ||4.4.3 ''Grolar''<br />
|- <br />
|[https://download.sep.de/windows/x64/ Windows Server 2016 Core] (x64) <sup>[[#note1b|'''Note<sup>b</sup>''']]</sup> || 4.4.3 ''Grolar'' || || ||<br />
|- <br />
|[https://download.sep.de/windows/x64/ Windows Server 2016] (x64) <sup>[[#note1b|'''Note<sup>b</sup>''']]</sup> || 4.4.3 ''Grolar'' || 4.4.3 ''Grolar'' || 4.4.3 ''Grolar'' || 4.4.3 ''Grolar''<br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows Server 2012 R2] (x64) <sup>[[#note1b|'''Note<sup>b</sup>''']]</sup> || 4.4.3 ''Grolar'' || 4.4.3 ''Grolar'' || 4.4.3 ''Grolar'' || 4.4.3 ''Grolar''<br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows Server 2012 R2 Core] (x64) <sup>[[#note1b|'''Note<sup>b</sup>''']]</sup>|| 4.4.3 ''Grolar'' || || ||<br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows Server 2012] (x64) <sup>[[#note1b|'''Note<sup>b</sup>''']]</sup> || 4.4.3 ''Grolar'' || 4.4.3 ''Grolar'' || 4.4.3 ''Grolar'' || 4.4.3 ''Grolar''<br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows Server 2012 Core] (x64) <sup>[[#note1b|'''Note<sup>b</sup>''']]</sup>|| 4.4.3 ''Grolar'' || || ||<br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows Small Business Server 2011] (x64) <sup>[[#note1c|'''Note<sup>c</sup>''']]</sup> || 4.4.3 ''Tigon V2'' || 4.4.3 ''Tigon V2'' || 4.4.3 ''Tigon V2'' || 4.4.3 ''Tigon V2''<br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows Server 2008 R2] (x64) || 4.4.3 ''Tigon V2'' || 4.4.3 ''Tigon V2''|| 4.4.3 ''Tigon V2'' || 4.4.3 ''Tigon V2''<br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows Server 2008 R2 Core] (x64) || 4.4.3 ''Tigon V2'' || || ||<br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows Server 2008 SP2] (x64) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows Server 2008 SP2 (x64)|4.4.3 ''Grolar'' }} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Windows Server 2008 SP2 (x64)|4.4.3 ''Tigon V2'' }} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Windows Server 2008 SP2 (x64)|4.4.3 ''Tigon V2'' }} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Windows Server 2008 SP2 (x64)|4.4.3 ''Grolar'' }} <br />
|-<br />
|[https://download.sep.de/windows/x86/ Windows Server 2008 SP2] (x86 ≤ 3GB RAM) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows Server 2008 SP2 (x86 ≤ 3GB RAM)|4.4.3 ''Grolar'' }} || || || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Windows Server 2008 SP2 (x86 ≤ 3GB RAM)|4.4.3 ''Grolar'' }}<br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows Small Business Server 2008] (x64) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows Small Business Server 2008 (x64)|4.4.3 ''Grolar'' }} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Windows Small Business Server 2008 (x64)|4.4.3 ''Tigon V2'' }} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Windows Small Business Server 2008 (x64)|4.4.3 ''Tigon V2'' }} || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Windows Small Business Server 2008 (x64)|4.4.3 ''Grolar'' }} <br />
|-<br />
|[https://download.sep.de/archive/4.2/windows/ Windows Server 2003 R2] (x86 ≤ 3GB RAM, x64) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows Server 2003 R2|4.2}}|| || ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Windows Server 2003 R2|4.2}}<br />
|- <br />
|[https://download.sep.de/archive/4.2/windows/ Windows Server 2003 ≥ SP2] (x86 ≤ 3GB RAM, x64) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows Server 2003 SP2|4.2}}|| || || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Windows Server 2003 SP2|4.2}}<br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows 10] (x64) || 4.4.3 ''Tigon'' || 4.4.3 ''Tigon'' || 4.4.3 ''Tigon'' || 4.4.3 ''Tigon''<br />
|-<br />
|[https://download.sep.de/windows/x86/ Windows 10] (x86) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows 10 (x86)|4.4.3 ''Grolar'' }} || || || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Windows 10 (x86)|4.4.3 ''Grolar'' }}<br />
|-<br />
|[https://download.sep.de/windows/x64/ Windows 8] (x64) || 4.4.3 ''Tigon'' || 4.4.3 ''Tigon'' || 4.4.3 ''Tigon'' || 4.4.3 ''Tigon''<br />
|-<br />
|[https://download.sep.de/windows/x86/ Windows 8] (x86 ≤ 3GB RAM) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows 8 (x86 ≤ 3GB RAM)|4.4.3 ''Grolar'' }} || || || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Windows 8 (x86 ≤ 3GB RAM)|4.4.3 ''Grolar'' }}<br />
|- <br />
|[https://download.sep.de/windows/x64/ Windows 7] (x64) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows 7 (x64)|4.4.3 ''Grolar'' }} || || || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Windows 7 (x64)|4.4.3 ''Grolar'' }} <br />
|- <br />
|[https://download.sep.de/windows/x86/ Windows 7] (x86 ≤ 3GB RAM) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows 7 (x86 ≤ 3GB RAM)|4.4.3 ''Grolar'' }} || || || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Windows 7 (x86 ≤ 3GB RAM)|4.4.3 ''Grolar'' }}<br />
|-<br />
|[https://download.sep.de/archive/4.2/windows/ Windows Vista] (x86 ≤ 3GB RAM, x64) ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows Vista|4.2}} || || ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Windows Vista|4.2}} <br />
|-<br />
|[https://download.sep.de/archive/4.2/windows/ Windows XP ≥ SP2] (x86 ≤ 3GB RAM, x64) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows XP|4.2}} || || || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Windows XP|4.2}} <br />
|-<br />
|[https://download.sep.de/archive/3.6/windows/x86/ Windows 2000] || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows 2000|3.6}} || || ||<br />
|-<br />
|[https://download.sep.de/archive/3.2/windows/x86/win-nt4.0/win32_cli.3.2.1.9_winnt.exe Windows NT]|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Windows NT|3.2}} || || ||<br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<div id="note1a"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>a</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">Windows Server 2019 is supported with v. [[SEP_sesam_Release_Versions|4.4.3 ''Grolar'']], however, it is recognized as Windows Server 2016. With v. 4.4.3 ''Beefalo'' the Windows Server 2019 is normally recognized</span><br />
<div id="note1b"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>b</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">Microsoft Data Deduplication Enabled Volumes are only supported since version 4.4. For details, see [[Archive:Release_Notes_4.4.1#Microsoft_Data_Deduplication_Enabled_Volumes |Release Notes]].</span><br />
<div id="note1c"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>c</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">The only supported edition is Windows SBS standard edition. Essentials edition is not supported!</span><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
==={{anchor|Solaris}}Solaris===<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background: #9D0000; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" | <div id="Solaris">Version</div><br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|[https://download.sep.de/solaris/x86 Solaris 11] (i386, x86-64)|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Solaris 11 (i386, x86-64)|4.2}}|| || ||<br />
|-<br />
|[https://download.sep.de/solaris/sparc9 Solaris 11] (sparc)|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Solaris 11 (sparc)|4.2}} || || ||<br />
|-<br />
|[https://download.sep.de/solaris/sparc9 Solaris 10] (sparc, i386) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Solaris 10|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Solaris 10|4.2}}|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Solaris 10|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Solaris 10|4.2}}<br />
|-<br />
|[https://download.sep.de/solaris/sparc9 Solaris 9] (sparc)|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Solaris 9|4.2}}|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for Solaris 9|4.2}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for Solaris 9|4.2}} ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for Solaris 9|4.2}} <br />
|-<br />
|[https://download.sep.de/solaris/sparc9 Solaris 8] (sparc)|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Solaris 8|3.0}} || || || <br />
|-<br />
|[https://download.sep.de/solaris/sparc7 Solaris 7] (sparc)|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for Solaris 7|3.0}} || || || <br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
==={{anchor|AIX}}AIX===<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#66cc00; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" | Version<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|[https://download.sep.de/aix/ AIX 7] || 4.4 || || 4.4 || <br />
|- <br />
|[https://download.sep.de/aix/ AIX 6] || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for AIX 6|4.0}} || || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for AIX 6|4.0}} || <br />
|-<br />
|[https://download.sep.de/aix/ AIX 5.x]||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for AIX 5.x|4.0}} || ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for AIX 5.x|4.0}}|| <br />
|-<br />
|[https://download.sep.de/aix/ AIX 4.3]||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for AIX 4.3|3.0}}|| || || <br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
==={{anchor|MacOS}}[[SEP_sesam_for_MacOS|MacOS]]===<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#00ccff; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" |Version<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|[https://download.sep.de/discontinued/macos_x/ MacOS X 10.8] (Intel) || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for MacOS X 10.8|4.2}} || || ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for MacOS X 10.8|4.2}} <br />
|-<br />
|[https://download.sep.de/discontinued/macos_x/ MacOS X 10.6] (Intel)|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for MacOS X 10.6|4.2.2}} || || || style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam GUI version for MacOS X 10.6|4.2.2}}<br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
==={{anchor|BSD}}BSD===<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#cc3333; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" |Version<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|[https://download.sep.de/bsd/freebsd/ FreeBSD 8] (i386, x86_64)|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for FreeBSD 8|4.0}}|| style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Server version for FreeBSD 8|4.0}}||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam RDS version for FreeBSD 8|4.0}} || <br />
|-<br />
|[https://download.sep.de/bsd/freebsd/ OpenBSD 4.6]||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for OpenBSD 4.6|4.0}} || || || <br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
==={{anchor|HP-UX}}HP-UX===<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#006699; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" | Version<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|- <br />
|[https://download.sep.de/unix/hp-ux/ HP-UX 11 ia64]||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for HP-UX 11 ia64|4.0}} || || ||<br />
|- <br />
|[https://download.sep.de/unix/hp-ux/ HP-UX 11 risc]||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for HP-UX 11 risc|3.0}}|| || || <br />
|-<br />
|[https://download.sep.de/unix/hp-ux/ HP-UX 10 risc]||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for HP-UX 10 risc|3.0}} || || || <br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
==={{anchor|NetApp_ONTAP}}[[Special:MyLanguage/NetApp|NetApp ONTAP]]===<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#0066cc; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" |Version<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px;"| GUI <br />
|-<br />
|≥ ONTAP 9.x|| || ≥ 4.4.3.69 ''Beefalo''|| || <br />
|-<br />
|≥ ONTAP 8.x (7-Mode and clustered data)|| || ≥ 4.4.3.69 ''Beefalo'' || || <br />
|-<br />
|ONTAP 7.x.x–8.2.x (7-Mode and clustered data)|| || 4.4.3.64 ''Grolar''|| || <br />
|-<br />
|ONTAP 7.x.x - 8.2.x (7-Mode only)|| || 4.4.2.x–4.4.3.64 || || <br />
|}<br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
==={{anchor|NetWare}}NetWare===<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#cc3333; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" |Version<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px;"| GUI <br />
|-<br />
|NetWare 6.x ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for NetWare 6.x |4.0}} || || || <br />
|-<br />
|NetWare 5.1 ||style="color: grey; font-style: italic;"|{{H:title|This is the last supported SEP sesam Client version for NetWare 5.1 |4.0}}|| || || <br />
|}<br />
'''Legend'''<br /><br />
<p>&#9632; Currently supported SEP sesam version. For example, version 4.4 means that all [[SEP_sesam_Release_Versions|4.4.x releases]] are supported.</p><br />
<p><span style="font-size:100%; line-height: 1.3em; color:grey;font-style: italic;">&#9632; The last supported SEP sesam version for the respective component (e.g., Server).</span></p><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
==={{anchor|NDMP}}[[NDMP|NDMP]]===<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#000000; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" |Version<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|NetApp ||4.4 || || || <br />
|-<br />
|Oracle ZFS ||4.4 || || || <br />
|-<br />
|EMC VNX ||4.4 || || || <br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
==={{anchor|Other}}Other===<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#A2A2A2; color:#FFFFFF"<br />
! scope="col" style="width: 170px; text-align:left;" |Supported<br />
! scope="col" style="width: 40px; text-align:left;" | Client<br />
! scope="col" style="width: 40px; text-align:left;"| Server<br />
! scope="col" style="width: 40px; text-align:left;" | RDS<br />
! scope="col" style="width: 40px; text-align:left;"| GUI <br />
|-<br />
|Tru64 5.x ||alpha || || || <br />
|-<br />
|SINIX 5.44 || mips || || || <br />
|-<br />
|FreeBSD 5 || i386 || || || <br />
|-<br />
|SCO-UX || i386 ||i386|| ||<br />
|- <br />
|VMS || alpha || || || <br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
== {{anchor|BSR_Linux}}[[Bare_Metal_Recovery_Linux|SEP sesam Bare Metal Recovery Linux]] ==<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- <br />
|- style="background:#FFCC01; color:#FFFFFF"<br />
! scope="col" style="width: 90px; text-align:left;" | Linux BSR based on REAR<br />
! scope="col" style="width: 20px; text-align:left;" | Platform <br />
! scope="col" style="width: 20px; text-align:left;" | Version <br />
|-<br />
|SLES 15 || x86-64 || 4.4.3 ''Beefalo''<br />
|-<br />
|SLES 12 || x86-64, Power* IBM Linux ONE*||<br />
|-<br />
|SLES 11 ||i386, x86-64, Power* || [[SEP_sesam_Release_Versions|4.4.3.64 ''Grolar'']] ONLY if ''UEFI BIOS'' is used. Version ''4.4.3.64'' is the '''last version with integrated REAR 2.4'''; later REAR versions (≥ REAR 2.5) no longer support SLES11 (with UEFI).<br /><br />
To continue using BSR SLES11, you '''should not upgrade''' to a later version of SEP sesam.<br />
|-<br />
|SLES 10 ≥ SP2 ||i386, x86-64 || <br />
|-<br />
|RHEL 8 || x86-64 || 4.4.3 ''Beefalo''<br />
|-<br />
|RHEL 7 ||x86-64, Power*||<br />
|-<br />
|RHEL 6 ||i386, x86-64, Power* || <br />
|-<br />
|CentOS 6 ||i386, x86-64|| <br />
|-<br />
|Debian 10 Buster ||x86-64 || 4.4.3 ''Beefalo''<br />
|-<br />
|Debian 8 Jessie ||i386, x86-64 ||<br />
|-<br />
|Debian 7 Wheezy ||i386, x86-64 ||<br />
|}<br />
<br />
{{Note|<br />
<ul><li>'''Systems using UEFI as boot loader are currently only supported on SLES'''</li><br />
On SLES creating a UEFI bootable recovery image is only possible with additional packages. For details, see [[Disaster_Recovery_for_Linux_3.0_en#UEFI|UEFI]].<br />
<li>'''Virtual Machines running on XEN cannot be backed up by SEP sesam BSR solution'''</li><br />
The resulting ISO image with a paravirtualized kernel included will not be bootable. Please use the SEP Sesam Citrix XEN module for Citrix XEN Server to create a consistent and relevant backup for a disaster recovery.<br />
<li>'''Power PC'''</li><br />
''For PowerPC and Linux One Systems please get in touch with sales@sep.de!''<br /><br />
These architectures may not work out of the box or may need special configuration. Consulting for these is available according to the price list.</li></ul>}}<br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
<!-- Wird nicht mehr unterstützt (auch nicht mit Diskinfo!)<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- <br />
|- style="background:#FFCC01; color:#002F55"<br />
! scope="col" style="width: 90px; text-align:left;" | <div id="Linux BSR">Linux BSR</div><br />
! scope="col" style="width: 20px; text-align:left;" | Platform <br />
|-<br />
|SLES10 ||i386, x86-64<br />
|-<br />
|SLES9 ||i386, x86-64 <br />
|-<br />
|SLES8 ||i386 <br />
|-<br />
|RHEL5 ||i386, x86-64 <br />
|-<br />
|RHEL4 ||i386 <br />
|-<br />
|Ubuntu 08/04 ||i386, x86-64 <br />
|-<br />
|Debian Etch ||i386, x86-64 <br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
--><br />
<br />
== {{anchor|Windows_BSR_Pro}}[[SEP_sesam_BSR_Pro_for_Windows|SEP sesam Bare Metal Recovery Windows]]==<br />
<br />
<!-- *** Supported OS see: http://www.oo-software.com/de/download/current/oodiskimagesrv *** <br />
Unterstützte Betriebssysteme: Windows® 10, 8.1, 8, 7 , Server 2008 R2, Server 2008, Vista, Server 2003, Server 2012, Server 2012 R2 --><br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- <br />
|- style="background:#2b5797; color:#FFFFFF"<br />
! scope="col" style="width: 90px; text-align:left;" | Windows BSR Pro<br />
! scope="col" style="width: 20px; text-align:left;" | Platform <br />
! scope="col" style="width: 20px; text-align:left;" | Version <br />
|-<br />
|Windows Server 2019 || x64 || 4.4.3 ''Beefalo''<br />
|-<br />
|Windows Server 2016 || x64 || 4.4.3 ''Tigon''<br />
|-<br />
|Windows Server 2012 [R2] || x64 || 4.4<br />
|- <br />
|Windows Server 2008 R2 || x64 || 4.4<br />
|-<br />
|Windows Server 2008 || x86, x64 || 4.4<br />
|-<br />
<!-- für BSR Pro brauchen wir eine 4.4.2.er Version - der neuere SBC läuft nicht auf 2003. - also keine Installation vom Sesam (4.4.2.x) und damit kein BSR Pro<br />
|Windows Server 2003 || x86, x64|| 4.4.2<br />
|---><br />
|Windows 10 ||x86, x64|| 4.4<br />
|-<br />
|Windows 8[.1] ||x86, x64 || 4.4<br />
|-<br />
|Windows 7 ||x86, x64 || 4.4<br />
|-<br />
|}<br />
<br />
{{Note|<br />
*SEP sesam BSR Pro is supported on platform x86 (32 bit) only from version 4.4.2.88. For details, see [[Special:MyLanguage/SEP_sesam_BSR_Pro_for_Windows|SEP sesam BSR Pro for Windows]].<br />
*SEP sesam BSR Pro does not support Windows Server Core.}}<br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
== SEP sesam VM extensions ==<br />
'''''Click for version'''''<br />
:{| cellpadding="5" cellspacing="0" style="width:70%" <br />
| &rarr; [[#VMware|'''''VMware''''']] || [[#Citrix|&rarr; '''''Citrix''''']] || [[#XCP|&rarr; '''''XCP-ng''''']] || [[#Hyper-V|&rarr; '''''Hyper-V''''']] <br />
|}<br />
<br />
:{| cellpadding="5" cellspacing="0" style="width:70%"<br />
|| [[#RHV|&rarr; '''''RHV''''']] || [[#OLVM|&rarr; '''''OLVM''''']] || [[#KVM|&rarr; '''''KVM''''']] || [[#Proxmox|&rarr;'''''Proxmox''''']]||[[#OpenNebula|&rarr;'''''OpenNebula''''']] <br />
|}<br />
<br />
=== {{anchor|VMware}}[[VMware|VMware]] ===<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#669933; color:#FFFFFF"<br />
! scope="col" style="width: 120px; text-align:left;" | VMware version <sup>[[#note2a|'''Note<sup>a</sup>''']]</sup><br />
! scope="col" style="width: 60px; text-align:left;" | VDDK <sup>[[#note2b|'''Note<sup>b</sup>''']]</sup><br />
! scope="col" style="width: 60px; text-align:left;" | VADP<br />
! scope="col" style="width: 60px; text-align:left;"| Limitations <br />
|-<br />
|vSphere 7.0 ||[https://code.vmware.com/web/sdk/65/vddk VDDK 6.5.2] (manual update required) || [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']] || <br />
*Check [https://code.vmware.com/web/sdk/7.0/vddk Release Notes] for compatibility and issues. <br />
|-<br />
|vSphere 6.7 ||[https://code.vmware.com/web/sdk/65/vddk VDDK 6.5.2] (manual update required) <br / > [https://code.vmware.com/web/sdk/6.0/vddk VDDK 6.0.3] (manual update required) || [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Grolar'']] || <br />
*Check [https://code.vmware.com/web/sdk/67/vddk Release Notes] for compatibility and issues. <br />
|-<br />
|vSphere 6.5 ||[https://code.vmware.com/web/sdk/65/vddk VDDK 6.5.2] (manual update required)<br /> [https://www.vmware.com/support/developer/vddk/vddk-603-releasenotes.html#whatsnew VDDK 6.0.3] (included in SEP sesam Windows client ≥ 4.4.3.48) <br /> [https://www.vmware.com/support/developer/vddk/vddk-602-releasenotes.html#whatsnew VDDK 6.0.2] (included in SEP sesam Windows client ≤ 4.4.3.42) || [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Tigon'' and ''Tigon V2'']] (4.4.3.42-.48) <br /> || <br />
*VDDK 6.5 or higher is required for backup of VMs residing on VMFS-6 datastores using SAN transport mode<br />
*Not supported: Backing up encrypted VMDKs <br />
* VDDK 6.5 only supports ESXi 5.5, ESXi 6.0, and ESXi 6.5. <br />
|-<br />
|vSphere 6.0 || [https://www.vmware.com/support/developer/vddk/vddk-602-releasenotes.html#whatsnew VDDK 6.0.2] || [[Special:MyLanguage/SEP_sesam_Release_Versions|≤ 4.4.2.66]] || <br />
|-<br />
|vSphere 5.5 || [https://code.vmware.com/web/sdk/55/vddk VDDK 5.5 – 5.5.5] || [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.2]] || <br />
|-<br />
|vSphere 5.1 || VDDK 5.1 || [[Special:MyLanguage/SEP_sesam_Release_Versions|≤ 4.4.1]] || <br />
|-<br />
|vSphere 5.0 || VDDK 5.0 || [[Special:MyLanguage/SEP_sesam_Release_Versions|≤ 4.4.1]] || <br />
|-<br />
|}<br />
<div id="note2a"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>a</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">As of VMware vSphere 5, backup with SEP sesam is only supported with a licensed ESXi hypervisor. Backup of ESXi 5.5 hypervisors is supported as of [[SEP_sesam_Release_Versions|SEP sesam version 4.2.2.40]].</span><br />
<div id="note2b"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>b</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">The VMware policy concerning backward and forward compatibility is for VDDK to support N-2 and N+1 releases. For example, VDDK 6.0 and all of its update releases support vSphere 5.1, 5.5, and 6.5 (except new features).</span><br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|Citrix}}[[Citrix_XEN_Server|Citrix]] ===<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#000000; color:#FFFFFF"<br />
! scope="col" style="width: 120px; text-align:left;" | Citrix version<br />
! scope="col" style="width: 30px; text-align:left;"| Version <br />
! scope="col" style="width: 30px; text-align:left;"| CBT support <br />
! scope="col" style="width: 60px; text-align:left;"| VSS and quiesced snapshots <br />
|-<br />
|Citrix Hypervisor 8.2 || 4.4.3.84 ''Beefalo V2'' ||Available for Premium Edition (previously Enterprise Edition). <sup>[[#note_quiesce_c|'''Note<sup>c</sup>''']]</sup> ||No longer supported. <sup>[[#note_quiesce_a|'''Note<sup>a</sup>''']]</sup><br />
|-<br />
|Citrix Hypervisor 8.1 || 4.4.3 ''Beefalo'' ||Available for Premium Edition (previously Enterprise Edition). <sup>[[#note_quiesce_c|'''Note<sup>c</sup>''']]</sup> ||No longer supported. <sup>[[#note_quiesce_a|'''Note<sup>a</sup>''']]</sup><br />
|-<br />
|Citrix Hypervisor 8.0 || 4.4.3 ''Beefalo'' ||Available for Premium Edition (previously Enterprise Edition). <sup>[[#note_quiesce_c|'''Note<sup>c</sup>''']]</sup> ||Supported. <sup>[[#note_quiesce_b|'''Note<sup>b</sup>''']]</sup><br />
|-<br />
|XenServer 7.6 || 4.4.3 ''Grolar'' ||Available for XenServer Enterprise Edition. ||Supported. <sup>[[#note_quiesce_b|'''Note<sup>b</sup>''']]</sup><br />
|-<br />
|XenServer 7.3 || 4.4.3 ''Grolar'' ||Available for XenServer Enterprise Edition. ||Supported. <sup>[[#note_quiesce_b|'''Note<sup>b</sup>''']]</sup><br />
|-<br />
|XenServer 7.2 || ||X ||Supported. <sup>[[#note_quiesce_b|'''Note<sup>b</sup>''']]</sup><br />
|-<br />
<br />
|XenServer 7.1 || ||X||Supported. <sup>[[#note_quiesce_b|'''Note<sup>b</sup>''']]</sup><br />
<br />
|-<br />
|XenServer 6.5 || ||X ||Supported. <sup>[[#note_quiesce_b|'''Note<sup>b</sup>''']]</sup><br />
|-<br />
|XenServer 6.2 || ||X ||Supported. <sup>[[#note_quiesce_b|'''Note<sup>b</sup>''']]</sup><br />
|-<br />
|XenServer 6.0 || ||X ||Supported. <sup>[[#note_quiesce_b|'''Note<sup>b</sup>''']]</sup><br />
|-<br />
|XenServer 5.6 || ||X ||Supported. <sup>[[#note_quiesce_b|'''Note<sup>b</sup>''']]</sup><br />
|-<br />
|}<br />
<div id="note_quiesce_a"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>a</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">VSS and quiesced snapshots of Windows VMs are only ''supported in Citrix Hypervisor 8.0 and earlier versions''; they have been ''removed in Citrix Hypervisor ≥ 8.1 and in the version ≥ 9.0.x.x drivers''. For more information, see [https://docs.citrix.com/en-us/citrix-hypervisor/whats-new/removed-features.html Citrix Hypervisor 8.1 Deprecations and removals]. </span><br />
<div id="note_quiesce_b"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>b</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">To continue using the quiesced snapshot feature with Windows VMs hosted on Citrix Hypervisor 8.0 and earlier, retain your current 8.2.x.x version of the Windows I/O drivers and do not update to the 9.0.x.x drivers.</span><br />
<div id="note_quiesce_c"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>c</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">Citrix Hypervisor (XenServer) ''Changed Block Tracking'' (CBT) is required for ''single file restore''. </span><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|XCP}} XCP-ng ===<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#cc6666; color:#FFFFFF"<br />
! scope="col" style="width: 120px; text-align:left;" | XCP-ng version<br />
! scope="col" style="width: 30px; text-align:left;"| Version <br />
! scope="col" style="width: 30px; text-align:left;"| CBT support<br />
! scope="col" style="width: 60px; text-align:left;"| VSS and quiesced snapshots <br />
<!-- <br />
|-<br />
|XCP-ng 8.1|| 4.4.3 ''Beefalo'' ||XCP-ng CBT is available. ||No longer supported. <sup>[[#note_xcp_quiesce_a|'''Note<sup>a</sup>''']]</sup> --><br />
|-<br />
|XCP-ng 8.0|| 4.4.3 ''Grolar'' ||XCP-ng CBT is available. ||Supported. <sup>[[#note_xcp_quiesce|'''Note<sup></sup>''']]</sup><br />
|-<br />
|XCP-ng 7.6|| 4.4.3 ''Grolar'' ||XCP-ng CBT is available. ||Supported. <sup>[[#note_xcp_quiesce|'''Note<sup></sup>''']]</sup><br />
|-<br />
|}<br />
<!-- <div id="note_xcp_quiesce_a"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>a</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">As XCP-ng 8.1 is based on Citrix Hypervisor 8.1 that has removed support for VSS and quiesced snapshots in ''Citrix Hypervisor ≥ 8.1 and in the version ≥ 9.0.x.x drivers'', the following applies: VSS and quiesced snapshots support is removed in XCP-ng 8.1. Windows guest tools version 9 (the default for recent versions of Windows if you install Citrix drivers) already removed VSS support, even for older versions ofCH/XCP-ng. For more information, see [https://github.com/xcp-ng/xcp/wiki/XCP-ng-8.1-Release-Notes XCP ng 8.1 Release Notes]. </span> --><br />
<div id="note_xcp_quiesce"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;"> As XCP-ng is based on Citrix Hypervisor that has removed support for VSS and quiesced snapshots in ''Citrix Hypervisor ≥ 8.1 and in the version ≥ 9.0.x.x drivers'', the following applies: To continue using the quiesced snapshot feature with Windows VMs hosted on XCP-ng 8.0 and earlier, retain your current 8.2.x.x version of the Windows I/O drivers and do not update to the 9.0.x.x drivers. For more information, see [https://github.com/xcp-ng/xcp/wiki/XCP-ng-8.1-Release-Notes XCP ng 8.1 Release Notes] and [https://docs.citrix.com/en-us/citrix-hypervisor/whats-new/removed-features.html Citrix Hypervisor 8.1 Deprecations and removals].</span><br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|Hyper-V}}[[Hyper-V|Hyper-V]]===<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#0099ff; color:#FFFFFF"<br />
! scope="col" style="width: 120px; text-align:left;" | Hyper-V version <br />
! scope="col" style="width: 30px; text-align:left;"| Version <br />
|-<br />
|Hyper-V Server 2019 || 4.4.3 ''Beefalo'' <br />
|-<br />
|Hyper-V Server 2016 || 4.4.3 ''Tigon'' <br />
|-<br />
|Hyper-V 3.0 Server 2012 R2 - with/without CSV || 4.4.3 <br />
|-<br />
|Hyper-V 3.0 Server 2012 - only without CSV || 4.4.2 <br />
|-<br />
|Hyper-V 2.0 Server 2008 R2 - only without CSV || 4.4.1 <br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|RHV}}[[RHV|Red Hat Virtualization (RHV/RHEV)]] ===<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#FC0203; color:#FFFFFF"<br />
! scope="col" style="width: 120px; text-align:left;" | RHV/RHEV version <br />
! scope="col" style="width: 30px; text-align:left;"| Version <br />
|-<br />
|RHV 4.4 || 4.4<br />
|-<br />
|RHV 4.3 || 4.4<br />
|-<br />
|RHV 4.2 || 4.4<br />
|-<br />
|RHV 4.1 || 4.4.3 <br />
|-<br />
|RHV 4.0 || 4.4.3 <br />
|-<br />
|RHEV 3.6 || 4.4.2<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|OLVM}}[[RHV|Oracle Linux Virtualization Manager (OLVM)]] ===<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#FC0203; color:#FFFFFF"<br />
! scope="col" style="width: 120px; text-align:left;" | OHV version <br />
! scope="col" style="width: 30px; text-align:left;"| Version <br />
|-<br />
|OLVM 4.2 || 4.4.3, 4.4<br />
|-<br />
|}<br />
<br />
{{Note|As of v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']], the RHV module also supports <tt>oVirt</tt>-based platforms within Oracle Linux Virtualization Manager (OLVM). For details, see [[Special:MyLanguage/RHV|RHV documentation]].}}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|KVM}}[[KVM_QEMU|KVM/QEMU]]===<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#ff6600; color:#FFFFFF"<br />
! scope="col" style="width: 120px; text-align:left;" | Supported OS (with KVM/libvirt) <br />
! scope="col" style="width: 30px; text-align:left;"| Version <br />
|-<br />
|Debian, RHEL, SLES, IBM z Systems, IBM LinuxONE, Oracle Linux (for other OS please contact [mailto:sales@sep.de sales@sep.de]) || 4.4.3 ''Tigon''<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|Proxmox}}[[Proxmox_VE|Proxmox VE]] ===<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#FC0203; color:#FFFFFF"<br />
! scope="col" style="width: 120px; text-align:left;" | Version <br />
! scope="col" style="width: 30px; text-align:left;"| Version <br />
|-<br />
|Proxmox 5.4 || 4.4<br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|OpenNebula}}[[OpenNebula|OpenNebula]] ===<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#0099cc; color:#FFFFFF"<br />
! scope="col" style="width: 30px; text-align:left;"| Version <br />
! scope="col" style="width: 120px; text-align:left;" | Supported OS <br />
! scope="col" style="width: 30px; text-align:left;"| SEP sesam version <br />
|-<br />
|OpenNebula 5.8||Ubuntu (for other OS please contact [mailto:sales@sep.de sales@sep.de]) || 4.4.3 ''Grolar''<br />
|-<br />
|OpenNebula 5.2.1||Ubuntu (for other OS please contact [mailto:sales@sep.de sales@sep.de]) || 4.4.3 ''Tigon''<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
== SEP sesam database and groupware online backup modules ==<br />
<br />
; '''''Click for version'''''<br />
:{| cellpadding="5" cellspacing="0" style="width:70%" <br />
| &rarr;[[#Oracle|'''''Oracle''''']] || [[#SAP_ASE|&rarr;'''''SAP ASE''''']] || [[#SAP_HANA|&rarr;'''''SAP HANA''''']] || [[#SAP_NetWeaver|&rarr;'''''SAP NetWeaver''''']] || [[#MAX_DB|&rarr;'''''MAX-DB''''']]<br />
|}<br />
:{| cellpadding="5" cellspacing="0" style="width:70%" <br />
|[[#Informix|&rarr;'''''Informix''''']] || [[#IBM_DB2|&rarr;'''''IBM DB2''''']] || [[#MS_SQL|&rarr;'''''Microsoft SQL Server''''']] || [[#MySQL|&rarr;'''''MySQL/MariaDB''''']] || [[#PostgreSQL|&rarr;'''''PostgreSQL''''']]<br />
|}<br />
<br />
=== {{anchor|Oracle}}[[Oracle|Oracle]] ===<br />
Since SEP sesam [[SEP_sesam_Release_Versions|4.4.1.14]], all components for setting up the Oracle extension are already included in the SEP sesam installation packages.<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background: #9D0000; color:#FFFFFF"<br />
! scope="col" style="width: 90px; text-align:left;" | Version<br />
! scope="col" style="width: 40px; text-align:left;" | Oracle 9i<br />
! scope="col" style="width: 40px; text-align:left;"| Oracle 10g<br />
! scope="col" style="width: 40px; text-align:left;" | Oracle 11g<br />
! scope="col" style="width: 40px; text-align:left;" | Oracle 12c/18c/19c <sup>[[#note7a|'''Note<sup>a</sup>''']]</sup><br />
|-<br />
|SLES12 || || || x86-64, Power, IBM LinuxONE || x86-64, Power, IBM LinuxONE<br />
|-<br />
|SLES11 || i386, x86-64 || i386, x86-64 ||i386, x86-64, Power || X86-64, Power<br />
|-<br />
|SLES10 || i386, x86-64 || i386, x86-64 ||i386, x86-64 ||<br />
|-<br />
|SLES9 || i386, x86-64 || i386, x86-64 || ||<br />
|-<br />
|SLES8 || i386 || || ||<br />
|-<br />
|RHEL7 || || || x86-64, Power, IBM LinuxONE || x86-64, Power, IBM LinuxONE<br />
|-<br />
|RHEL6 || i386, x86-64 || i386, x86-64 || i386, x86-64, Power || x86-64, Power<br />
|-<br />
|RHEL5 || i386, x86-64 || i386, x86-64 || i386, x86-64 ||<br />
|-<br />
|RHEL4 || i386 || || ||<br />
|-<br />
|Solaris 11 || || || i386, x86-64 || i386, x86-64<br />
|-<br />
|Solaris 10 || sparc || sparc || i386, x86-64 ||<br />
|-<br />
|Solaris 9 || sparc || sparc || ||<br />
|-<br />
|AIX 7 || Power || Power || Power || Power<br />
|-<br />
|AIX 6.x || Power || Power || Power ||<br />
|-<br />
|AIX 5.x || Power || Power || Power ||<br />
|- <br />
|Windows Server 2019 || || || || x64<br />
|- <br />
|Windows Server 2016 || || || || x64<br />
|- <br />
|Windows Server 2012 [R2] || || x64 || x64 || x64<br />
|- <br />
|Windows Server 2008 [R2] || x86, x64 || x86, x64 || x86, x64 || x64<br />
|-<br />
|Windows Server 2003 [R2] || x86, x64 || x86, x64 || x86, x64 ||<br />
|-<br />
|Windows 7 || || || x86, x64 ||<br />
|-<br />
|Windows 2000 || x86 || x86 || ||<br />
|-<br />
|}<br />
<br />
<div id="note7a"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>a</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">With Oracle databases v. ≥ ''12c'', multitenant architecture is supported to allow for backup and restore of multitenant container databases (CDBs) and pluggable databases (PDBs) in a similar way as for traditional Oracle databases (non-CDBs). For details, see [[Special:MyLanguage/4_4_3:Oracle_Backup#CDB|Backing up CDBs and PDBs]].</span><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
==={{anchor|SAP_ASE}} [[SAP| SAP ASE]] ===<br />
Since SEP sesam [[SEP_sesam_Release_Versions|4.4.3.39 ''Tigon'']], all components for setting up the SAP Adaptive Server Enterprise (ASE) 16.0 (formerly SAP Sybase ASE) extension are already included in the SEP sesam installation packages.<br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#ff9900; color:#FFFFFF"<br />
! scope="col" style="width: 40px; text-align:left;" | Version<br />
! scope="col" style="width: 20px; text-align:left;" | SAP ASE 16.0<br />
|-<br />
|SLES12 || x86-64, Power<br />
|-<br />
|SLES11 || x86-64, Power<br />
|-<br />
|RHEL7 || i386, x86-64<br />
|-<br />
|RHEL6 || i386, x86-64<br />
|-<br />
|Windows Server 2016 || x64 <br />
|-<br />
|Windows Server 2012 || x64 <br />
|-<br />
|Windows Server 2008 [R2] || x64 <br />
|- |}<br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|SAP_HANA}}[[SAP|SAP HANA]] ===<br />
Since SEP sesam [[SEP_sesam_Release_Versions|4.4.1.14]], all components for setting up the SAP HANA extension are already included in the SEP sesam installation packages. For details on SAP by SEP sesam, see [https://www.sep.de/solutions/sap/ SAP solutions].<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#3399ff; color:#FFFFFF"<br />
! scope="col" style="width: 20px; text-align:left;" | Version<br />
! scope="col" style="width: 20px; text-align:left;" | SAP HANA<br />
! scope="col" style="width: 20px; text-align:left;" | SAP HANA 2.0<br />
|- <br />
|SLES15 || x86-64, Power || x86-64, Power <br />
|- <br />
|SLES15 for SAP || x86-64, Power || x86-64, Power <br />
|-<br />
|SLES12 || x86-64, Power || x86-64, Power <br />
|-<br />
|SLES12 for SAP || x86-64, Power || x86-64, Power <br />
|-<br />
|SLES11 || x86-64, Power || x86-64, Power <br />
|-<br />
|SLES11 for SAP || x86-64, Power || x86-64, Power<br />
|-<br />
|RHEL7 || x86-64, Power || x86-64, Power<br />
|-<br />
|RHEL7 for SAP HANA || x86-64, Power || x86-64, Power <br />
|-<br />
|RHEL6 || x86-64, Power || x86-64, Power<br />
|-<br />
|RHEL6 for SAP HANA || x86-64, Power || x86-64, Power<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|SAP_NetWeaver}}[[SAP|SAP NetWeaver]] ===<br />
Since SEP sesam [[SEP_sesam_Release_Versions|4.4.1.14]], all components for setting up the SAP NetWeaver extension are already included in the SEP sesam installation packages. For details on SAP by SEP sesam, see [https://www.sep.de/solutions/sap/ SAP solutions].<br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#000000; color:#FFFFFF"<br />
! scope="col" style="width: 90px; text-align:left;" | Version<br />
! scope="col" style="width: 20px; text-align:left;" | SAP Oracle<br />
! scope="col" style="width: 20px; text-align:left;"| SAP MaxDB 7.6 - 7.9<br />
|-<br />
|SLES12 || x86-64 || x86-64, Power<br />
|-<br />
|SLES11 || x86-64 || x86-64, Power<br />
|-<br />
|SLES10 || i386, x86-64 || i386, x86-64 <br />
|-<br />
|RHEL7 || i386, x86-64 || i386, x86-64<br />
|-<br />
|RHEL6 || i386, x86-64 || i386, x86-64<br />
|-<br />
|RHEL5 || i386, x86-64 || i386, x86-64 <br />
|-<br />
|AIX 7 || Power || <br />
|-<br />
|Windows Server 2016 || x64 || x64 <br />
|-<br />
|Windows Server 2012 || x64 || x64 <br />
|-<br />
|Windows Server 2008 [R2] || x64 || x64 <br />
|- |}<br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|MAX_DB}}[[SAP|MAX-DB]] ===<br />
Since SEP sesam [[SEP_sesam_Release_Versions|4.4.1.14]], all components for setting up the MAX-DB extension are already included in the SEP sesam installation packages.<br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#3399ff; color:#FFFFFF"<br />
! scope="col" style="width: 20px; text-align:left;" | Version<br />
! scope="col" style="width: 20px; text-align:left;" | MaxDB 7.2 - 7.9 <br />
|-<br />
|SLES12 || x86-64, Power <br />
<br />
|-<br />
|SLES11 || x86-64, Power <br />
|-<br />
|SLES10 || i386, x86-64 <br />
|-<br />
|SLES9 || i386, x86-64 <br />
|-<br />
|SLES8 || i386 <br />
|-<br />
|RHEL7 || x86-64, Power <br />
|-<br />
|RHEL6 || x86-64, Power <br />
|-<br />
|RHEL5 || i386, x86-64 <br />
|-<br />
|RHEL4 || i386 <br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|Informix}}[[Informix|Informix]] ===<br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#000066; color:#FFFFFF"<br />
! scope="col" style="width: 50px; text-align:left;" | Version<br />
! scope="col" style="width: 20px; text-align:left;" | Informix 7<br />
! scope="col" style="width: 20px; text-align:left;"| Informix 9<br />
! scope="col" style="width: 20px; text-align:left;" | Informix 10<br />
! scope="col" style="width: 20px; text-align:left;" | Informix 11<br />
! scope="col" style="width: 20px; text-align:left;" | Informix 12<br />
|-<br />
|SLES12 || i386 || i386 || i386 || i386/x64 || i386/x64 <br />
|-<br />
|SLES11 || i386 || i386 || i386 || i386/x64 || i386/x64 <br />
|-<br />
|SLES10 || i386 || i386 || i386 || i386/x64 ||<br />
|-<br />
|SLES9 || i386 || i386 || i386 || i386/x64 ||<br />
|-<br />
|RHEL7 || i386 || i386 || i386 || i386/x64 || i386/x64 <br />
|-<br />
|RHEL6 || i386 || i386 || i386 || i386/x64 || i386/x64 <br />
|-<br />
|RHEL5 || i386 || i386 || i386 || i386/x64 ||<br />
|-<br />
|RHEL4 || i386 || i386 || i386 || i386/x64 ||<br />
|-<br />
|Windows Server 2012 [R2]||x86, x64 ||x86, x64 ||x86, x64 || x64 || x64<br />
|-<br />
|Windows Server 2008 [R2]||x86, x64 ||x86, x64 ||x86, x64 || x64 || x64<br />
|-<br />
|Windows Server 2003 ||x86, x64 ||x86, x64 ||x86, x64 || x64 ||<br />
|-<br />
|Windows 7 ||x86, x64 ||x86, x64 ||x86, x64 || x64 ||<br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|IBM_DB2}}[[IBM_DB2|IBM DB2]] ===<br />
All required components for IBM DB2 may already be included in the SEP sesam Client package. If not, you can download the extension from [https://download.sep.de/extensions/databases/db2/ SEP Download Center]. <br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#009900; color:#FFFFFF"<br />
! scope="col" style="width: 90px; text-align:left;" |Version<br />
! scope="col" style="width: 40px; text-align:left;" | DB2 8<br />
! scope="col" style="width: 40px; text-align:left;"| DB2 9<br />
! scope="col" style="width: 40px; text-align:left;"| DB2 10<br />
! scope="col" style="width: 40px; text-align:left;"| DB2 11<br />
|-<br />
|SLES12 || || x86-64, Power, IBM LinuxONE || x86-64, Power, IBM LinuxONE || x86-64, Power, IBM LinuxONE<br />
|-<br />
|SLES11 || i386, x86-64, Power || i386, x86-64, Power || i386, x86-64, Power || i386, x86-64, Power<br />
|-<br />
|SLES10 || i386, x86-64 || i386, x86-64 || i386, x86-64 || i386, x86-64<br />
|-<br />
|SLES9 || i386 || i386 || ||<br />
|-<br />
|RHEL7 || || x86-64, Power, IBM LinuxONE || x86-64, Power, IBM LinuxONE || x86-64, Power, IBM LinuxONE<br />
|-<br />
|RHEL6 || i386, x86-64 || i386, x86-64 || i386, x86-64 || i386, x86-64<br />
|-<br />
|RHEL5 || i386, x86-64 || i386, x86-64 || i386, x86-64 || i386, x86-64<br />
|-<br />
|RHEL4 || i386 || i386 || ||<br />
|-<br />
|Windows Server 2008 [R2] || x86, x64 || x86, x64 || x86, x64 || x86, x64<br />
|-<br />
|Windows Server 2003 || x86, x64 || x86, x64 || ||<br />
|-<br />
|AIX 7 || || Power || Power || Power<br />
|-<br />
|AIX 6 || || Power || Power ||<br />
|-<br />
|AIX 5 || || Power || Power ||<br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|MS_SQL}}[[MS_SQL|Microsoft SQL Server]] ===<br />
<br />
All required programs are included in the SEP sesam Client package.<br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#990000; color:#FFFFFF"<br />
! scope="col" style="width: 150px; text-align:left;" | Version<br />
! scope="col" style="width: 150px; text-align:left;" | SQL Server 2000<br />
! scope="col" style="width: 10px; text-align:left;" | SQL Server 2005 (Express)<br />
! scope="col" style="width: 10px; text-align:left;" | SQL Server 2008 (Express)<br />
! scope="col" style="width: 10px; text-align:left;" | SQL Server 2008 R2 (Express)<br />
! scope="col" style="width: 10px; text-align:left;" | SQL Server 2012 (Express)<br />
! scope="col" style="width: 10px; text-align:left;" | SQL Server 2014 (Express)<br />
! scope="col" style="width: 20px; text-align:left;" | SQL Server 2016 (Express)<br />
! scope="col" style="width: 20px; text-align:left;" | SQL Server 2017 (Express)<br />
! scope="col" style="width: 20px; text-align:left;" | SQL Server 2019 (Express)<br />
|-<br />
|Windows Server 2019 || || || || || || x64 || x64 || x64 || x64<br />
|-<br />
|Windows Server 2016 || || || || || || x64 || x64|| x64 || x64<br />
|-<br />
|Windows Server 2012 R2 || || || || x64 || x64 || x64 || x64|| x64 || x64<br />
|-<br />
|Windows Server 2012 || || || || x64 || x64 || x64 || x64|| ||<br />
|-<br />
|Windows Server 2008 R2 || ||x86, x64 || x86, x64 || x86, x64 || x86, x64 || x86, x64 || || ||<br />
|-<br />
|Windows Server 2008 || ||x86, x64 || x86, x64 || x86, x64 || x86, x64 || x86, x64 || || ||<br />
|-<br />
|Windows Server 2003 || x86 <sup>[[#note3a|'''Note<sup>a</sup>''']]</sup> ||x86, x64 || x86, x64 || x86, x64 || || || || ||<br />
|- <br />
|Windows XP || x86 <sup>[[#note3a|'''Note<sup>a</sup>''']]</sup> ||x86, x64 || x86, x64 || x86, x64 || || || || ||<br />
|-<br />
|Windows 2000 || x86 <sup>[[#note3a|'''Note<sup>a</sup>''']]</sup> ||x86 || || || || || || ||<br />
|-<br />
|}<br />
<div id="note3a"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>a</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">To support Microsoft SQL Server 2000, replace the <tt>sbcmsql.dll</tt> in <tt>{{sesamroot|bin\sesam}}</tt> directory on the SEP sesam Client with a specific version, which can be downloaded [https://download.sep.de/extensions/databases/MS-SQL/SQL2000/sbcmsql.zip here].</span><br />
<br />
{{Note|Microsoft SQL Cluster is supported; MS SQL Server on Windows Failover Cluster (active/passive) and also Always On Availability Groups.}}<br />
<br />
See also [http://support.microsoft.com/kb/321185 MS article ''How to determine the version, edition and update level of SQL Server''] to determine your SQL Server version and edition.<br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|MySQL}}[[MySQL|MySQL/MariaDB]] ===<br />
<br />
All required programs are included in the SEP sesam Client package. <br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#ff9900; color:#FFFFFF"<br />
! scope="col" style="width: 90px; text-align:left;" | Version<br />
! scope="col" style="width: 50px; text-align:left;" | MySQL 4<br />
! scope="col" style="width: 50px; text-align:left;"| MySQL 5<br />
! scope="col" style="width: 50px; text-align:left;"| MariaDB 5 <br />
! scope="col" style="width: 50px; text-align:left;"| MariaDB 10<br />
|-<br />
|SLES12 || || x86-64, Power, IBM z Systems, IBM LinuxONE || x86-64 || x86-64, Power, IBM z Systems, IBM LinuxONE<br />
|-<br />
|SLES11 || || i386, x86-64, Power, IBM z Systems, IBM LinuxONE || i386, x86-64 || i386, x86-64, Power, IBM z Systems, IBM LinuxONE <br />
|-<br />
|SLES10 || i386, x86-64 || i386, x86-64 || i386, x86-64 || i386, x86-64<br />
|-<br />
|SLES9 || i386, x86-64 || i386, x86-64 || ||<br />
|-<br />
|SLES8 || i386, x86-64 || i386, x86-64 || ||<br />
|-<br />
|RHEL7 || || x86-64, Power, IBM z Systems, IBM LinuxONE || x86-64 || x86-64, Power, IBM z Systems, IBM LinuxONE<br />
|-<br />
|RHEL6 || || i386, x86-64, Power, IBM z Systems, IBM LinuxONE || i386, x86-64 || i386, x86-64, Power, IBM z Systems, IBM LinuxONE <br />
|-<br />
|RHEL5 || i386, x86-64 || i386, x86-64 || i386, x86-64 || i386, x86-64<br />
|-<br />
|RHEL4 || i386, x86-64 || i386, x86-64 || ||<br />
|-<br />
|Debian Buster || || x86_64 || x86-64 || x86-64<br />
|-<br />
|Debian Strech || || x86_64 || x86-64 || x86-64<br />
|-<br />
|Debian Jessie || || i386,x86_64 || i386, x86-64 || i386, x86-64<br />
|-<br />
|Debian Wheezy || || i386,x86_64 || i386, x86-64 || i386, x86-64 <br />
|-<br />
|Debian Squeeze || || i386,x86_64 || i386, x86-64 || i386, x86-64 <br />
|-<br />
|Debian Lenny || || i386,x86_64 || i386, x86-64 || i386, x86-64 <br />
|-<br />
|Debian Etch || i386 || i386 || ||<br />
|-<br />
|Ubuntu || i386,x86_64 || i386,x86_64 || i386, x86-64 || i386, x86-64<br />
|-<br />
|Univention UCS 4.0 || || i386, x86-64 || i386, x86-64 || i386, x86-64<br />
|-<br />
|Univention UCS 3.2 || || i386, x86-64 || i386, x86-64 || i386, x86-64<br />
|-<br />
|Univention UCS 3.0 || || i386, x86-64 || i386, x86-64 || i386, x86-64<br />
|-<br />
|Univention UCS 2.2 || i386, x86-64 || i386, x86-64 || i386, x86-64 || i386, x86-64<br />
|-<br />
|Windows 2008 and higher || || x86-64 || || <br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|PostgreSQL}}[[PostgreSQL|PostgreSQL / EnterpriseDB]]===<br />
<br />
All required programs are included in the SEP sesam Client package. Note that SEP sesam installation on '''RHEL changes permissions''' of <tt>/var/run/postgresql</tt> to grant Sesam user PostgreSQL access privileges.<br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#336699; color:#FFFFFF"<br />
! scope="col" style="width: 60px; text-align:left;" | Version<br />
! scope="col" style="width: 90px; text-align:left;" | PostgreSQL 7<br />
! scope="col" style="width: 90px; text-align:left;"| PostgreSQL 8<br />
! scope="col" style="width: 90px; text-align:left;"| Enterprise DB 8.3<br />
! scope="col" style="width: 90px; text-align:left;"| PostgreSQL 9<br />
! scope="col" style="width: 90px; text-align:left;"| Enterprise DB 9.5 <br />
! scope="col" style="width: 90px; text-align:left;"| PostgreSQL 10 <br />
|-<br />
|SLES12 || || x86-64, Power || x86-64, Power|| x86-64, Power, IBM z Systems, IBM LinuxONE || x86-64, Power, IBM z Systems, IBM LinuxONE || x86-64, Power, IBM z Systems, IBM LinuxONE<br />
|-<br />
|SLES11 || i386, x86-64 || i386, x86-64, Power || i386, x86-64, Power || i386, x86-64, Power, IBM z Systems, IBM LinuxONE || x86-64, Power, IBM z Systems, IBM LinuxONE||<br />
|-<br />
|SLES10 || i386, x86-64 || i386, x86-64 || i386, x86-64 || i386, x86-64 || || <br />
|-<br />
|SLES9 || i386, x86-64 || i386, x86-64 || i386, x86-64 || i386, x86-64 || || <br />
|-<br />
|SLES8 || i386 || i386 || || || ||<br />
|-<br />
|RHEL7 || || x86-64, Power || x86-64, Power || x86-64, Power, IBM z Systems, IBM LinuxONE || x86-64, Power, IBM z Systems, IBM LinuxONE ||<br />
|-<br />
|RHEL6 || i386, x86-64 || i386, x86-64, Power ||i386, x86-64, Power || i386, x86-64, Power || x86-64, Power ||<br />
|-<br />
|RHEL5 || i386, x86-64 || i386, x86-64 ||i386, x86-64 || i386, x86-64 || ||<br />
|-<br />
|RHEL4 || i386 || i386 || || || ||<br />
|-<br />
|Debian Stretch || || x86-64 || x86-64 || x86-64 || x86-64 ||<br />
|-<br />
|Debian Jessie || || x86-64 || x86-64 || x86-64 || x86-64 ||<br />
|- <br />
|Debian Wheezy || i386, x86-64 || i386, x86-64 ||i386, x86-64 || i386, x86-64 || i386, x86-64 ||<br />
|-<br />
|Debian Squeeze || i386, x86-64 || i386, x86-64 ||i386, x86-64 || i386, x86-64 || ||<br />
|-<br />
|Debian Lenny || i386, x86-64 || i386, x86-64 ||i386, x86-64 || i386, x86-64 || ||<br />
|-<br />
|Univention UCS || i386, x86-64 || i386, x86-64 || i386, x86-64 || i386, x86-64 || i386, x86-64 ||<br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
== {{anchor|Groupware}}Groupware and mail backup modules ==<br />
<br />
; '''''Click for version'''''<br />
:{| cellpadding="5" cellspacing="0" style="width:80%" <br />
| &rarr;[[#MS_Exchange|'''''Microsoft Exchange Server''''']] || [[#MS_SharePoint|&rarr;'''''Microsoft SharePoint''''']] || [[#GroupWise|&rarr;'''''GroupWise''''']] || [[#IBM_Domino|&rarr;'''''IBM Domino Server''''']] || [[#Kopano|&rarr;'''''Kopano''''']] <br />
|}<br />
:{| cellpadding="5" cellspacing="0" style="width:80%" <br />
| [[#Zarafa|&rarr;'''''Zarafa''''']] || [[#Scalix|&rarr;'''''Scalix''''']] || [[#JIRA|&rarr;'''''JIRA''''']] || [[#Dovecot_IMAP|&rarr;'''''Dovecot IMAP''''']] || [[#Cyrus_IMAP|&rarr;'''''Cyrus IMAP''''']] || [[#Courier_IMAP|&rarr;'''''Courier IMAP''''']] || [[#openLDAP|&rarr;'''''openLDAP''''']]<br />
|}<br />
<br />
=== {{anchor|MS_Exchange}}[[MS_Exchange|Microsoft Exchange Server]] ===<br />
<br />
All required programs are included in the SEP sesam Client package.<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#3366cc; color:#FFFFFF"<br />
! scope="col" style="width: 60px; text-align:left;"| Version<br />
! scope="col" style="width: 90px; text-align:left;" | MS Exchange 2007 <sup>[[#note4a|'''Note<sup>a</sup>''']]</sup><br />
! scope="col" style="width: 90px; text-align:left;" | MS Exchange 2010 <sup>[[#note4a|'''Note<sup>a</sup>''']]</sup><br />
! scope="col" style="width: 90px; text-align:left;" | MS Exchange 2013 CU3 <sup>[[#note4a|'''Note<sup>a</sup>''']]/[[#note4b|'''Note<sup>b</sup>''']]</sup><br />
! scope="col" style="width: 90px; text-align:left;" | MS Exchange 2013 <sup>[[#note4a|'''Note<sup>a</sup>''']]</sup><br />
! scope="col" style="width: 90px; text-align:left;" | MS Exchange 2016 <sup>[[#note4a|'''Note<sup>a</sup>''']]</sup><br />
! scope="col" style="width: 90px; text-align:left;" | MS Exchange 2019 <sup>[[#note4a|'''Note<sup>a</sup>''']]</sup><br />
|-<br />
|Windows Server 2019 || || || || || ||x64 (as of [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']])<br />
|-<br />
|Windows Server 2016 || || || || || x64 (as of [[SEP_sesam_Release_Versions|4.4.3 ''Tigon v.1'']]) || <br />
|-<br />
|Windows Server 2012 R2 || || x64 with Exchange 2010 SP3 || x64 || x64 || x64 ||<br />
|-<br />
|Windows Server 2012 || || x64 with Exchange 2010 SP3 || x64 ||x64 || || <br />
|-<br />
|Windows Server 2008 R2 || x64 || x64 || x64 ||x64 || || <br />
|-<br />
|Windows Server 2008 || x64 || x64 || || || || <br />
|-<br />
|}<br />
<div id="note4a"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>a</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">Since version 4.2.2.35, Microsoft .Net Framework 4 is required for Microsoft Exchange Server 2007/2010/2013/2016/2019.</span><br />
<div id="note4b"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>b</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">For Microsoft Exchange Server 2013, MS Exchange Server 2013 Cumulative Update 3 is required. For details, see [http://blogs.technet.com/b/exchange/archive/2013/11/25/released-exchange-server-2013-cumulative-update-3.aspx Released: Exchange Server 2013 Cumulative Update 3] and [http://support.microsoft.com/kb/2888315 KB2888315].</span><br />
<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|MS_SharePoint}}[[SharePoint|Microsoft SharePoint]] ===<br />
<br />
All required programs are included in the SEP sesam Client package to support SharePoint Server running on SQL Server 2012.<br />
<br />
The SEP sesam Client package must be installed on the SharePoint Server and on the SQL Server.<br />
<br />
If the SQL Server version is different to SQL Server 2012 (e.g. 2014) then the dynamic link library [https://download.sep.de/extensions/groupware/MS-SharePoint/ SQLMGR.DLL must be replaced] on the SQL Server (see [https://msdn.microsoft.com/de-de/library/gg492257.aspx Supported Combinations of SharePoint and Reporting Services Server and Add-in (SQL Server 2014)]). <br />
<br />
{{Note|<br />
*The SQLMGR.DLL is a .NET assembly build with platform ''Any CPU'' therefore it can run on x64 and on x86 architecture.<br />
*Single item restore (site, document, etc.) is supported for: SharePoint 2007, 2010, 2013 ad 2016 in combination with SQL Server 2005, 2008, 2008 R2, 2012 SP1 and 2014.}}<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#0066cc; color:#FFFFFF"<br />
! scope="col" style="width: 40px; text-align:left;" | Version<br />
! scope="col" style="width: 20px; text-align:left;" | SharePoint 2007<br />
! scope="col" style="width: 20px; text-align:left;" | SharePoint 2010 <br />
! scope="col" style="width: 20px; text-align:left;" | SharePoint 2013<br />
! scope="col" style="width: 20px; text-align:left;" | SharePoint 2016<br />
|-<br />
|Windows Server 2016 || || || || [https://download.sep.de/extensions/groupware/MS-SharePoint x64] <br />
|-<br />
|Windows Server 2012 R2 || || || [https://download.sep.de/extensions/groupware/MS-SharePoint x64] || [https://download.sep.de/extensions/groupware/MS-SharePoint x64] <br />
|-<br />
|Windows Server 2012 || || [https://download.sep.de/extensions/groupware/MS-SharePoint x64] || [https://download.sep.de/extensions/groupware/MS-SharePoint x64] ||<br />
|-<br />
|Windows Server 2008 R2 SP1|| [https://download.sep.de/extensions/groupware/MS-SharePoint x64] || [https://download.sep.de/extensions/groupware/MS-SharePoint x64] || [https://download.sep.de/extensions/groupware/MS-SharePoint x64] ||<br />
|-<br />
|Windows Server 2008 || [https://download.sep.de/extensions/groupware/MS-SharePoint x86, x64] || [https://download.sep.de/extensions/groupware/MS-SharePoint x64] || ||<br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|GorupWise}}[[GroupWise|GroupWise]] ===<br />
All required programs are included in the SEP sesam Novell client package.<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:90%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#000000; color:#FFFFFF"<br />
! scope="col" style="width: 120px; text-align:left;" | Version<br />
! scope="col" style="width: 60px; text-align:left;" | GW 5.x<br />
! scope="col" style="width: 60px; text-align:left;"| GW 6.x <br />
! scope="col" style="width: 60px; text-align:left;" | GW 7.x<br />
! scope="col" style="width: 60px; text-align:left;"| GW 8.x<br />
! scope="col" style="width: 60px; text-align:left;" | GW 2012 <br />
! scope="col" style="width: 60px; text-align:left;" | GW 2014 /2014R2<br />
! scope="col" style="width: 60px; text-align:left;" | GW 2018<br />
|-<br />
|Linux-OES2018 || || || || || || x86_64|| x86_64<br />
|-<br />
|Linux-OES2015 || || || || || x86_64 || x86_64 || x86_64 <br />
|-<br />
|Linux-OES11 <sup>[[#note5a|'''Note<sup>a</sup>''']]</sup> || || || || i386 || x86_64 || x86_64 || <br />
|-<br />
|Linux-OES2 || i386 || i386 || i386 || i386 || x86_64 || ||<br />
|-<br />
|Linux-OES1 || i386 || i386 || i386 || i386 || || ||<br />
|-<br />
|NetWare 6.5 || || || || || || ||<br />
|-<br />
|-<br />
|}<br />
<div id="note5a"><span style="font-size:92%; line-height: 1.3em; color:black;">'''Note<sup>a</sup>'''</span></div><br />
<span style="font-size:92%; line-height: 1.3em; color:black;">Since SEP sesam version 4.2.2-40, OES11 SP2 is supported with SEP Sesam Novell Client 4.2.2-35.</span><br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|IBM_Domino}}[[Lotus_Domino|IBM/HCL Domino Server]] ===<br />
<br />
All required components for IBM/HCL Domino Server (previously Lotus Domino Server) may already be included in the SEP sesam Client package. If not, you can download the extension from [https://download.sep.de/extensions/groupware/notes/ SEP Download Center]. <br />
<br />
{| class="sortable" border="2" cellpadding="6" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#ffcc33; color:#FFFFFF"<br />
! scope="col" style="width: 50px; text-align:left;" | OS minimum<br />
! scope="col" style="width: 20px; text-align:left;"| Domino 8.5<br />
! scope="col" style="width: 20px; text-align:left;"| Domino 9.0.1<br />
! scope="col" style="width: 20px; text-align:left;"| Domino 10<br />
! scope="col" style="width: 20px; text-align:left;"| Domino 11<br />
|-<br />
|SLES12 || x86_64 || x64 || x64 || x64<br />
|-<br />
|SLES11 SP1 || i386, x86_64 || x64 || ||<br />
|-<br />
|RHEL7 || || x64 || x64 || x64<br />
|-<br />
|RHEL6 U3 || i386, x86_64 || x64 || ||<br />
|-<br />
|Windows Server 2019 || || || x64 || x64<br />
|-<br />
|Windows Server 2016 || || x64 || x64 || x64<br />
|-<br />
|Windows Server 2012 [R2] || || x64 || ||<br />
|-<br />
|Windows Server 2008 [R2] || x64 || x64 || ||<br />
|-<br />
|Windows Server 2003 || i386, x64 || || ||<br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|Kopano}}[[Kopano|Kopano]] ===<br />
All required programs are included in the SEP sesam Client package.<br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#00ccff; color:#FFFFFF"<br />
! scope="col" style="width: 50px; text-align:left;" | Version<br />
! scope="col" style="width: 20px; text-align:left;" | Kopano 8.3<br />
! scope="col" style="width: 20px; text-align:left;"| Kopano 8.4 <br />
! scope="col" style="width: 20px; text-align:left;"| Kopano 8.7.12 <br />
|-<br />
|SLES12 || x86_64 || x86_64 || x86_64 <br />
|-<br />
|RHEL7 || x86_64 || x86_64 || x86_64<br />
|-<br />
|RHEL6 || i686, x86_64 || i686, x86_64 || x86_64<br />
|-<br />
|Wheezy (Debian 7.x) || i386, x86_64 || i386, x86_64 || x86_64 <br />
|-<br />
|Jessie (Debian 8.x) || i386, x86_64 || i386, x86_64 || x86_64 <br />
|-<br />
|Ubuntu 16.04 || x86_64 || x86_64 || x86_64 <br />
|-<br />
|Ubuntu 14.04 || x86_64 || x86_64 || x86_64<br />
|- <br />
|Univention UCS 4.x || i386 (only for updates), x86_64 || i386 (only for updates), x86_64 || x86_64 <br />
|- <br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|Zarafa}}[[Kopano|Zarafa]] ===<br />
All required programs are included in the SEP sesam Client package. Supported are '''Zarafa Standard''', '''Professional''' and '''Enterprise Edition'''.<br />
<br />
{{Note|Single mailbox backup for ''Zarafa Community Edition'' is not supported because of the Zarafa license restrictions.}}<br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#006699; color:#FFFFFF"<br />
! scope="col" style="width: 50px; text-align:left;" | Version<br />
! scope="col" style="width: 20px; text-align:left;" | Zarafa 5.20<br />
! scope="col" style="width: 20px; text-align:left;"| Zarafa 6.40<br />
! scope="col" style="width: 20px; text-align:left;"| Zarafa 7 <br />
|-<br />
|SLES12 || || || x86_64 <br />
|-<br />
|SLES11 || i386 || i386 || i386,x86_64 <br />
|-<br />
|SLES10 || i386 || i386 || i386,x86_64<br />
|-<br />
|SLES9 || i386 || i386 || <br />
|-<br />
|RHEL7 || || || x86_64<br />
|-<br />
|RHEL6 || i386 || i386 || i386,x86_64<br />
|-<br />
|RHEL5 || i386 || i386 || i386,x86_64<br />
|- <br />
|RHEL4 || i386 || i386 ||<br />
|-<br />
|Etch || i386 || i386 || <br />
|-<br />
|Lenny || i386 || i386 || i386,x86_64 <br />
|-<br />
|Squeeze || i386 || i386 || i386,x86_64 <br />
|-<br />
|Wheezy || || || i386,x86_64 <br />
|-<br />
|Jessie || || || x86_64 <br />
|-<br />
|Ubuntu 16.04 || || || x86_64 <br />
|-<br />
|Ubuntu 12.04 || || i386 || i386,x86_64<br />
|-<br />
|Ubuntu 10.04 || i386 || i386 || i386,x86_64<br />
|-<br />
|Ubuntu 08.04 || i386 || i386 || <br />
|- <br />
|Univention UCS 3.0 || || || i386, x86_64<br />
|- <br />
|Univention UCS 2.4 || || || i386, x86_64<br />
|-<br />
|Univention UCS 2.2 || i386 || i386 ||<br />
|- <br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|Scalix}}Scalix ===<br />
{{note|SEP AG has discontinued support for Scalix as of [[SEP sesam Release Versions|SEP sesam 4.4.3 ''Tigon V2'']].}}<br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#cc0033; color:#FFFFFF"<br />
! scope="col" style="width: 50px; text-align:left;" | Version<br />
! scope="col" style="width: 20px; text-align:left;" | Scalix 12<br />
|-<br />
|SLES12 || x86_64, Power <br />
|-<br />
|SLES11 || i386, x86_64, Power <br />
|-<br />
|RHEL7 || x86_64, Power <br />
|-<br />
|RHEL6 || i386, x86_64, Power <br />
|-<br />
|Debian || i386, x86_64 <br />
|-<br />
|Ubuntu || i386, x86_64 <br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
<br />
=== {{anchor|JIRA}}[[JIRA|JIRA]] ===<br />
<br />
SEP sesam has developed a reliable backup and restore solution for JIRA in cooperation with [https://www.catworkx.com/en ''catWorkX'']. This add-on is available on [https://marketplace.atlassian.com/plugins/de.catworkx.jira.plugins.sep-sesam-integration/versions Atlassian Marketplace]. The following versions are available:<br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- <br />
|- style="background:#3399ff; color:#FFFFFF"<br />
! scope="col" style="width: 20px; text-align:left;" | Version<br />
! scope="col" style="width: 40px; text-align:left;" | JIRA Server <br />
! scope="col" style="width: 40px; text-align:left;" | SEP sesam Server<br />
|-<br />
|7.0.1.2 ||JIRA Server 7.0.0 - 7.1.9 || SEP sesam version ≥ 4.4.2<br />
|-<br />
|6.4.1.2 ||JIRA Server 6.4.1 - 6.4.14 || SEP sesam version ≥ 4.4.2 <br />
|}<br />
<br />
=== {{anchor|Dovecot_IMAP}}Dovecot IMAP ===<br />
<br />
<div id="Dovecot IMAP">All required programs are included in the SEP sesam Client package.</div><br />
<br />
=== {{anchor|Cyrus_IMAP}}Cyrus IMAP ===<br />
<br />
<div id="Cyrus IMAP">All required programs are included in the SEP sesam Client package.</div><br />
<br />
=== {{anchor|Courier_IMAP}}Courier IMAP ===<br />
<br />
<div id="Courier IMAP">All required programs are included in the SEP sesam Client package.</div><br />
<br />
=== {{anchor|openLDAP}}openLDAP ===<br />
<br />
All required programs are included in the SEP sesam Client package. <br />
<br />
{| class="sortable" border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#996666; color:#000000"<br />
! scope="col" style="width: 50px; text-align:left;" | Version<br />
! scope="col" style="width: 20px; text-align:left;" | openLDAP 2.3.<br />
! scope="col" style="width: 20px; text-align:left;"| openLDAP 2.4. <br />
|-<br />
|SLES12 || x86_64 || x86_64 <br />
|-<br />
|SLES11 || i386, x86_64 || i386, x86_64 <br />
|-<br />
|SLES10 || i386, x86_64 || i386, x86_64 <br />
|-<br />
|SLES9 || i386, x86_64 || i386, x86_64<br />
|-<br />
|RHEL7 || x86_64 || x86_64 <br />
|-<br />
|RHEL6 || i386, x86_64 || i386, x86_64 <br />
|-<br />
|RHEL5 || i386, x86_64 || i386, x86_64 <br />
|-<br />
|RHEL4 || i386 || i386<br />
|-<br />
|Debian || i386, x86_64 || i386, x86_64 <br />
|-<br />
|Ubuntu || i386, x86_64 || i386, x86_64 <br />
|-<br />
|Univention UCS 3.0 || i386, x86_64 || i386, x86_64<br />
|-<br />
|Univention UCS 2.4 || i386, x86_64 || i386, x86_64 <br />
|- <br />
|Univention UCS 2.2 || i386, x86_64 || i386, x86_64 <br />
|-<br />
|}<br />
{| style="margin-left: auto; margin-right: 0px;" cellspacing="0""<br />
| [[#top|Back to top of page]]<br />
|}<br />
==Unsupported OS==<br />
{{:Unsupported OS}}<br />
==See also==<br />
[[Special:MyLanguage/Java_Compatibility_Matrix|Java Compatibility Matrix]] – [[Special:MyLanguage/SEP_sesam_Storage_Hardware_Support_Matrix|SEP sesam Storage Hardware Support Matrix]]<br />
<br />
[[Category:Support Matrices]]</div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Installing_guestfs-tools_on_Linux&diff=171909Source:Installing guestfs-tools on Linux2020-11-19T10:06:43Z<p>Fho: /* Checking guestmount capabilities on your system */</p>
<hr />
<div> __FORCETOC__<br />
<translate><br />
<!--T:1--><br />
<div class="noprint"><languages /><br />
{{Copyright SEP AG en}}<br />
<br />
<!--T:2--><br />
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/VMware|VMware archive]]}}</div></translate><br /><br />
<translate>==Overview== <!--T:3--></translate><br />
<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 25%; "><center><b><translate><!--T:4--><br />
Additional resources</translate></b></center><br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--><br />
[[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--><br />
See also: [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images] </translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:7--><br />
[[File:support-matrix.png|45px|link=Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:8--><br />
Check all supported [[SEP_sesam_OS_and_Database_Support_Matrix|OS, database configurations and versions]].</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:11--><br />
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:12--><br />
Problems with VMware? Check [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware troubleshooting]].</translate> <br />
|}<br />
</div><br />
<translate><!--T:13--><br />
On Linux, SEP sesam single file restore from virtualization platform backups, e.g., ''VMware vSphere'', requires the <tt>guestfs-tools</tt> package to be installed to be able to access and mount the file system of an image on Linux. If the package is not installed on your SEP sesam Server or RDS Linux server, you will not be able to mount VMDK and consequently, perform a single file restore.<br />
<br />
<!--T:14--><br />
To learn more about the guestfs-tools, see [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]. <br />
<br />
==Installing <tt>guestfs-tools</tt> package== <!--T:15--> <br />
<br />
<!--T:16--><br />
Use the command line to install the guestfs-tools package according to your specific Linux distributions, i.e., ''SLES'', ''Debian'', ''Ubuntu'', ''RHEL'', or ''CentOS''. For details on Linux installation, see [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]]. <br />
<br />
<!--T:17--><br />
Depending on your Linux distribution, specify the relevant command:</translate><br />
<br />
<ul><li><translate><!--T:18--> On SLES (SUSE Linux Enterprise Server)</translate></li><br />
zypper install guestfs-tools<br />
<li><translate><!--T:19--> On Debian and Ubuntu</translate></li><br />
apt-get install libguestfs-tools<br />
<li><translate><!--T:20--> On RHEL and CentOS</translate></li><br />
yum install libguestfs-tools<br />
</ul><br />
<br />
==Restrictions and extra steps required on RHEL/CentOS==<br />
Due to restrictions on RHEL mounting Windows VMs will not work. Take a look at [https://libguestfs.org/guestfs-faq.1.html#mount:-unsupported-filesystem-type-with-ntfs-in-rhel-7.2 libguestfs FAQ] for more information.<br />
<br />
On RHEL and its Derivates there are additional steps required to get the single file restore working:<br />
<br />
1. Open /etc/libvirt/qemu.conf and change the variable user from qemu to root<br />
<br />
2. Restart the service libvirtd, by using <br />
systemctl restart libvirtd<br />
<br />
3. Add a new line to /usr/lib64/guestfs/supermin.d/packages containing libgpg-error<br />
<br />
4. Remove old guestmount appliances <br />
rm -rf /var/tmp/.guestfs-*<br />
5. Test if the guestmount appliance builds without errors, by executing <br />
libguestfs-test-tool <br />
This has to exit with<br />
===== TEST FINISHED OK =====<br />
<br />
6. If selinux is set to enforcing, guestfs-tools will not be able to access the Virtual Harddisks provided by SEP sesam, so mounting still fails.<br />
<br />
==Restrictions and extra steps required on SUSE==<br />
<br />
1. install augeas augeas-lenses e2fsprogs on your SEP sesam Server or RDS Linux server<br />
<br />
2. Add new lines to /usr/lib64/guestfs/supermin.d/packages containing <br />
libaugeas0<br />
augeas<br />
augeas-lenses<br />
<br />
== Checking guestmount capabilities on your system ==<br />
<br />
To check whether guestmount works on your system run<br />
libguestfs-test-tool<br />
If the last line is<br />
===== TEST FINISHED OK =====<br />
guestmount works correctly.<br />
<br />
<br />
You can check which things guestmount supports on your system currently, by running <br />
<br />
guestfish -a /dev/null run : supported<br />
<br />
on your SEP sesam Server or the SEP sesam RDS, where the savesets you want to mount are located.<br />
<br />
This will show you whether vms with filesystems like btrfs or ntfs can be mounted. You may add this functionality by installing the required packages on your system.<br />
Also you have to add lines for those package names to<br />
/usr/lib64/guestfs/supermin.d/packages<br />
on the system.<br />
<br />
<translate><br />
<div class="noprint"><br />
<br />
==Known issues== <!--T:21--><br />
If you have problems with VMware single file restore, check the [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware troubleshooting]].<br />
<br />
==See also== <!--T:22--><br />
[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]</div></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Installing_guestfs-tools_on_Linux&diff=171908Source:Installing guestfs-tools on Linux2020-11-19T10:06:00Z<p>Fho: </p>
<hr />
<div> __FORCETOC__<br />
<translate><br />
<!--T:1--><br />
<div class="noprint"><languages /><br />
{{Copyright SEP AG en}}<br />
<br />
<!--T:2--><br />
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/VMware|VMware archive]]}}</div></translate><br /><br />
<translate>==Overview== <!--T:3--></translate><br />
<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 25%; "><center><b><translate><!--T:4--><br />
Additional resources</translate></b></center><br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--><br />
[[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--><br />
See also: [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images] </translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:7--><br />
[[File:support-matrix.png|45px|link=Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:8--><br />
Check all supported [[SEP_sesam_OS_and_Database_Support_Matrix|OS, database configurations and versions]].</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:11--><br />
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:12--><br />
Problems with VMware? Check [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware troubleshooting]].</translate> <br />
|}<br />
</div><br />
<translate><!--T:13--><br />
On Linux, SEP sesam single file restore from virtualization platform backups, e.g., ''VMware vSphere'', requires the <tt>guestfs-tools</tt> package to be installed to be able to access and mount the file system of an image on Linux. If the package is not installed on your SEP sesam Server or RDS Linux server, you will not be able to mount VMDK and consequently, perform a single file restore.<br />
<br />
<!--T:14--><br />
To learn more about the guestfs-tools, see [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]. <br />
<br />
==Installing <tt>guestfs-tools</tt> package== <!--T:15--> <br />
<br />
<!--T:16--><br />
Use the command line to install the guestfs-tools package according to your specific Linux distributions, i.e., ''SLES'', ''Debian'', ''Ubuntu'', ''RHEL'', or ''CentOS''. For details on Linux installation, see [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]]. <br />
<br />
<!--T:17--><br />
Depending on your Linux distribution, specify the relevant command:</translate><br />
<br />
<ul><li><translate><!--T:18--> On SLES (SUSE Linux Enterprise Server)</translate></li><br />
zypper install guestfs-tools<br />
<li><translate><!--T:19--> On Debian and Ubuntu</translate></li><br />
apt-get install libguestfs-tools<br />
<li><translate><!--T:20--> On RHEL and CentOS</translate></li><br />
yum install libguestfs-tools<br />
</ul><br />
<br />
==Restrictions and extra steps required on RHEL/CentOS==<br />
Due to restrictions on RHEL mounting Windows VMs will not work. Take a look at [https://libguestfs.org/guestfs-faq.1.html#mount:-unsupported-filesystem-type-with-ntfs-in-rhel-7.2 libguestfs FAQ] for more information.<br />
<br />
On RHEL and its Derivates there are additional steps required to get the single file restore working:<br />
<br />
1. Open /etc/libvirt/qemu.conf and change the variable user from qemu to root<br />
<br />
2. Restart the service libvirtd, by using <br />
systemctl restart libvirtd<br />
<br />
3. Add a new line to /usr/lib64/guestfs/supermin.d/packages containing libgpg-error<br />
<br />
4. Remove old guestmount appliances <br />
rm -rf /var/tmp/.guestfs-*<br />
5. Test if the guestmount appliance builds without errors, by executing <br />
libguestfs-test-tool <br />
This has to exit with<br />
===== TEST FINISHED OK =====<br />
<br />
6. If selinux is set to enforcing, guestfs-tools will not be able to access the Virtual Harddisks provided by SEP sesam, so mounting still fails.<br />
<br />
==Restrictions and extra steps required on SUSE==<br />
<br />
1. install augeas augeas-lenses e2fsprogs on your SEP sesam Server or RDS Linux server<br />
<br />
2. Add new lines to /usr/lib64/guestfs/supermin.d/packages containing <br />
libaugeas0<br />
augeas<br />
augeas-lenses<br />
<br />
== Checking guestmount capabilities on your system ==<br />
<br />
To check whether guestmount works on your system run<br />
libguestfs-test-tool<br />
If the last line is<br />
===== TEST FINISHED OK =====<br />
<br />
<br />
You can check which things guestmount supports on your system currently, by running <br />
<br />
guestfish -a /dev/null run : supported<br />
<br />
on your SEP sesam Server or the SEP sesam RDS, where the savesets you want to mount are located.<br />
<br />
This will show you whether vms with filesystems like btrfs or ntfs can be mounted. You may add this functionality by installing the required packages on your system.<br />
Also you have to add lines for those package names to<br />
/usr/lib64/guestfs/supermin.d/packages<br />
on the system.<br />
<br />
<translate><br />
<div class="noprint"><br />
==Known issues== <!--T:21--><br />
If you have problems with VMware single file restore, check the [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware troubleshooting]].<br />
<br />
==See also== <!--T:22--><br />
[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]</div></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Installing_guestfs-tools_on_Linux/de&diff=170858Source:Installing guestfs-tools on Linux/de2020-10-20T15:00:20Z<p>Fho: Created page with "==Installieren des <tt>guestfs-tools</tt> Pakets=="</p>
<hr />
<div> __FORCETOC__<br />
<div class="noprint"><languages /><br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/VMware|VMware Archiv]]}}</div><br /><br />
==Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 25%; "><center><b>Weitere Quellen</b></center><br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Einzeldateirücksicherung]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Installation - Kurzanleitung]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images] <br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:support-matrix.png|45px|link=Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Überprüfen Sie die unterstützten [[SEP_sesam_OS_and_Database_Support_Matrix|OS, Datenbank-Konfigurationen und Versionen]].<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Im Falle von Problemen mit ''VMware'' bitte hier schauen: [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware Troubleshooting]]. <br />
|}<br />
</div><br />
On Linux, SEP sesam single file restore from virtualization platform backups, e.g., ''VMware vSphere'', requires the <tt>guestfs-tools</tt> package to be installed to be able to access and mount the file system of an image on Linux. If the package is not installed on your SEP sesam Server or RDS Linux server, you will not be able to mount VMDK and consequently, perform a single file restore.<br />
<br />
To learn more about the guestfs-tools, see [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]. <br />
<br />
==Installieren des <tt>guestfs-tools</tt> Pakets== <br />
<br />
Use the command line to install the guestfs-tools package according to your specific Linux distributions, i.e., ''SLES'', ''Debian'', ''Ubuntu'', ''RHEL'', or ''CentOS''. For details on Linux installation, see [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]]. <br />
<br />
Depending on your Linux distribution, specify the relevant command:<br />
<br />
<ul><li>Auf SLES (SUSE Linux Enterprise Server)</li><br />
zypper install guestfs-tools<br />
<li>Auf Debian und Ubuntu</li><br />
apt-get install libguestfs-tools<br />
<li>Auf RHEL und CentOS</li><br />
yum install libguestfs-tools<br />
</ul><br />
<br />
==Restrictions and extra steps required on RHEL/CentOS==<br />
Due to restrictions on RHEL mounting Windows VMs will not work. Take a look at [https://libguestfs.org/guestfs-faq.1.html#mount:-unsupported-filesystem-type-with-ntfs-in-rhel-7.2 libguestfs FAQ] for more information.<br />
<br />
On RHEL and its Derivates there are additional steps required to get the single file restore working:<br />
<br />
1. Open /etc/libvirt/qemu.conf and change the variable user from qemu to root<br />
<br />
2. Restart the service libvirtd, by using <br />
systemctl restart libvirtd<br />
<br />
3. Add a new line to /usr/lib64/guestfs/supermin.d/packages containing libgpg-error<br />
<br />
4. Remove old guestmount appliances <br />
rm -rf /var/tmp/.guestfs-*<br />
5. Test if the guestmount appliance builds without errors, by executing <br />
libguestfs-test-tool <br />
This has to exit with<br />
===== TEST FINISHED OK =====<br />
<br />
6. If selinux is set to enforcing, guestfs-tools will not be able to access the Virtual Harddisks provided bu SEP sesam, so mounting still fails.<br />
<br />
== Checking guestmount capabilities on your system ==<br />
<br />
You can check which things guestmount supports on your system currently, by running <br />
<br />
guestfish -a /dev/null run : supported<br />
<br />
on your SEP sesam Server or the SEP sesam RDS, where the savesets you want to mount are located.<br />
<br />
This will show you whether vms with filesystems like btrfs or ntfs can be mounted. You may add this functionality by installing the required packages on your system.<br />
Also you have to add lines for those package names to<br />
/usr/lib64/guestfs/supermin.d/packages<br />
on the system.<br />
<br />
<div class="noprint"><br />
==Bekannte Themen==<br />
Wenn Sie Probleme mit VMware Einzeldateirücksicherung (Single File Restore) haben, überprüfen Sie den [[Special:MyLanguage/Troubleshooting_Guide#VMware|Troubleshooting Guide]].<br />
<br />
==Siehe auch== <br />
[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Einzeldateirücksicherung]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Installation - Kurzanleitung]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]</div></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:Source:Installing_guestfs-tools_on_Linux/15/de&diff=170857Translations:Source:Installing guestfs-tools on Linux/15/de2020-10-20T15:00:20Z<p>Fho: Created page with "==Installieren des <tt>guestfs-tools</tt> Pakets=="</p>
<hr />
<div>==Installieren des <tt>guestfs-tools</tt> Pakets==</div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Installing_guestfs-tools_on_Linux/de&diff=170856Source:Installing guestfs-tools on Linux/de2020-10-20T14:58:09Z<p>Fho: Created page with "Auf SLES (SUSE Linux Enterprise Server)"</p>
<hr />
<div> __FORCETOC__<br />
<div class="noprint"><languages /><br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/VMware|VMware Archiv]]}}</div><br /><br />
==Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 25%; "><center><b>Weitere Quellen</b></center><br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Einzeldateirücksicherung]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Installation - Kurzanleitung]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images] <br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:support-matrix.png|45px|link=Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Überprüfen Sie die unterstützten [[SEP_sesam_OS_and_Database_Support_Matrix|OS, Datenbank-Konfigurationen und Versionen]].<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Im Falle von Problemen mit ''VMware'' bitte hier schauen: [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware Troubleshooting]]. <br />
|}<br />
</div><br />
On Linux, SEP sesam single file restore from virtualization platform backups, e.g., ''VMware vSphere'', requires the <tt>guestfs-tools</tt> package to be installed to be able to access and mount the file system of an image on Linux. If the package is not installed on your SEP sesam Server or RDS Linux server, you will not be able to mount VMDK and consequently, perform a single file restore.<br />
<br />
To learn more about the guestfs-tools, see [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]. <br />
<br />
==Installing <tt>guestfs-tools</tt> package== <br />
<br />
Use the command line to install the guestfs-tools package according to your specific Linux distributions, i.e., ''SLES'', ''Debian'', ''Ubuntu'', ''RHEL'', or ''CentOS''. For details on Linux installation, see [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]]. <br />
<br />
Depending on your Linux distribution, specify the relevant command:<br />
<br />
<ul><li>Auf SLES (SUSE Linux Enterprise Server)</li><br />
zypper install guestfs-tools<br />
<li>Auf Debian und Ubuntu</li><br />
apt-get install libguestfs-tools<br />
<li>Auf RHEL und CentOS</li><br />
yum install libguestfs-tools<br />
</ul><br />
<br />
==Restrictions and extra steps required on RHEL/CentOS==<br />
Due to restrictions on RHEL mounting Windows VMs will not work. Take a look at [https://libguestfs.org/guestfs-faq.1.html#mount:-unsupported-filesystem-type-with-ntfs-in-rhel-7.2 libguestfs FAQ] for more information.<br />
<br />
On RHEL and its Derivates there are additional steps required to get the single file restore working:<br />
<br />
1. Open /etc/libvirt/qemu.conf and change the variable user from qemu to root<br />
<br />
2. Restart the service libvirtd, by using <br />
systemctl restart libvirtd<br />
<br />
3. Add a new line to /usr/lib64/guestfs/supermin.d/packages containing libgpg-error<br />
<br />
4. Remove old guestmount appliances <br />
rm -rf /var/tmp/.guestfs-*<br />
5. Test if the guestmount appliance builds without errors, by executing <br />
libguestfs-test-tool <br />
This has to exit with<br />
===== TEST FINISHED OK =====<br />
<br />
6. If selinux is set to enforcing, guestfs-tools will not be able to access the Virtual Harddisks provided bu SEP sesam, so mounting still fails.<br />
<br />
== Checking guestmount capabilities on your system ==<br />
<br />
You can check which things guestmount supports on your system currently, by running <br />
<br />
guestfish -a /dev/null run : supported<br />
<br />
on your SEP sesam Server or the SEP sesam RDS, where the savesets you want to mount are located.<br />
<br />
This will show you whether vms with filesystems like btrfs or ntfs can be mounted. You may add this functionality by installing the required packages on your system.<br />
Also you have to add lines for those package names to<br />
/usr/lib64/guestfs/supermin.d/packages<br />
on the system.<br />
<br />
<div class="noprint"><br />
==Bekannte Themen==<br />
Wenn Sie Probleme mit VMware Einzeldateirücksicherung (Single File Restore) haben, überprüfen Sie den [[Special:MyLanguage/Troubleshooting_Guide#VMware|Troubleshooting Guide]].<br />
<br />
==Siehe auch== <br />
[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Einzeldateirücksicherung]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Installation - Kurzanleitung]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]</div></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:Source:Installing_guestfs-tools_on_Linux/18/de&diff=170855Translations:Source:Installing guestfs-tools on Linux/18/de2020-10-20T14:58:09Z<p>Fho: Created page with "Auf SLES (SUSE Linux Enterprise Server)"</p>
<hr />
<div>Auf SLES (SUSE Linux Enterprise Server)</div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Installing_guestfs-tools_on_Linux/de&diff=170854Source:Installing guestfs-tools on Linux/de2020-10-20T14:57:59Z<p>Fho: Created page with "Auf RHEL und CentOS"</p>
<hr />
<div> __FORCETOC__<br />
<div class="noprint"><languages /><br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/VMware|VMware Archiv]]}}</div><br /><br />
==Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 25%; "><center><b>Weitere Quellen</b></center><br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Einzeldateirücksicherung]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Installation - Kurzanleitung]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images] <br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:support-matrix.png|45px|link=Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Überprüfen Sie die unterstützten [[SEP_sesam_OS_and_Database_Support_Matrix|OS, Datenbank-Konfigurationen und Versionen]].<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Im Falle von Problemen mit ''VMware'' bitte hier schauen: [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware Troubleshooting]]. <br />
|}<br />
</div><br />
On Linux, SEP sesam single file restore from virtualization platform backups, e.g., ''VMware vSphere'', requires the <tt>guestfs-tools</tt> package to be installed to be able to access and mount the file system of an image on Linux. If the package is not installed on your SEP sesam Server or RDS Linux server, you will not be able to mount VMDK and consequently, perform a single file restore.<br />
<br />
To learn more about the guestfs-tools, see [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]. <br />
<br />
==Installing <tt>guestfs-tools</tt> package== <br />
<br />
Use the command line to install the guestfs-tools package according to your specific Linux distributions, i.e., ''SLES'', ''Debian'', ''Ubuntu'', ''RHEL'', or ''CentOS''. For details on Linux installation, see [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]]. <br />
<br />
Depending on your Linux distribution, specify the relevant command:<br />
<br />
<ul><li>On SLES (SUSE Linux Enterprise Server)</li><br />
zypper install guestfs-tools<br />
<li>Auf Debian und Ubuntu</li><br />
apt-get install libguestfs-tools<br />
<li>Auf RHEL und CentOS</li><br />
yum install libguestfs-tools<br />
</ul><br />
<br />
==Restrictions and extra steps required on RHEL/CentOS==<br />
Due to restrictions on RHEL mounting Windows VMs will not work. Take a look at [https://libguestfs.org/guestfs-faq.1.html#mount:-unsupported-filesystem-type-with-ntfs-in-rhel-7.2 libguestfs FAQ] for more information.<br />
<br />
On RHEL and its Derivates there are additional steps required to get the single file restore working:<br />
<br />
1. Open /etc/libvirt/qemu.conf and change the variable user from qemu to root<br />
<br />
2. Restart the service libvirtd, by using <br />
systemctl restart libvirtd<br />
<br />
3. Add a new line to /usr/lib64/guestfs/supermin.d/packages containing libgpg-error<br />
<br />
4. Remove old guestmount appliances <br />
rm -rf /var/tmp/.guestfs-*<br />
5. Test if the guestmount appliance builds without errors, by executing <br />
libguestfs-test-tool <br />
This has to exit with<br />
===== TEST FINISHED OK =====<br />
<br />
6. If selinux is set to enforcing, guestfs-tools will not be able to access the Virtual Harddisks provided bu SEP sesam, so mounting still fails.<br />
<br />
== Checking guestmount capabilities on your system ==<br />
<br />
You can check which things guestmount supports on your system currently, by running <br />
<br />
guestfish -a /dev/null run : supported<br />
<br />
on your SEP sesam Server or the SEP sesam RDS, where the savesets you want to mount are located.<br />
<br />
This will show you whether vms with filesystems like btrfs or ntfs can be mounted. You may add this functionality by installing the required packages on your system.<br />
Also you have to add lines for those package names to<br />
/usr/lib64/guestfs/supermin.d/packages<br />
on the system.<br />
<br />
<div class="noprint"><br />
==Bekannte Themen==<br />
Wenn Sie Probleme mit VMware Einzeldateirücksicherung (Single File Restore) haben, überprüfen Sie den [[Special:MyLanguage/Troubleshooting_Guide#VMware|Troubleshooting Guide]].<br />
<br />
==Siehe auch== <br />
[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Einzeldateirücksicherung]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Installation - Kurzanleitung]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]</div></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:Source:Installing_guestfs-tools_on_Linux/20/de&diff=170853Translations:Source:Installing guestfs-tools on Linux/20/de2020-10-20T14:57:59Z<p>Fho: Created page with "Auf RHEL und CentOS"</p>
<hr />
<div>Auf RHEL und CentOS</div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Installing_guestfs-tools_on_Linux/de&diff=170852Source:Installing guestfs-tools on Linux/de2020-10-20T14:57:48Z<p>Fho: Created page with "Auf Debian und Ubuntu"</p>
<hr />
<div> __FORCETOC__<br />
<div class="noprint"><languages /><br />
{{Copyright SEP AG|de}}<br />
<br />
{{Navigation_latest_de|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/VMware|VMware Archiv]]}}</div><br /><br />
==Übersicht==<br />
<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 25%; "><center><b>Weitere Quellen</b></center><br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Siehe auch: [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Einzeldateirücksicherung]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Installation - Kurzanleitung]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images] <br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:support-matrix.png|45px|link=Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Überprüfen Sie die unterstützten [[SEP_sesam_OS_and_Database_Support_Matrix|OS, Datenbank-Konfigurationen und Versionen]].<br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide]]<br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Im Falle von Problemen mit ''VMware'' bitte hier schauen: [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware Troubleshooting]]. <br />
|}<br />
</div><br />
On Linux, SEP sesam single file restore from virtualization platform backups, e.g., ''VMware vSphere'', requires the <tt>guestfs-tools</tt> package to be installed to be able to access and mount the file system of an image on Linux. If the package is not installed on your SEP sesam Server or RDS Linux server, you will not be able to mount VMDK and consequently, perform a single file restore.<br />
<br />
To learn more about the guestfs-tools, see [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]. <br />
<br />
==Installing <tt>guestfs-tools</tt> package== <br />
<br />
Use the command line to install the guestfs-tools package according to your specific Linux distributions, i.e., ''SLES'', ''Debian'', ''Ubuntu'', ''RHEL'', or ''CentOS''. For details on Linux installation, see [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]]. <br />
<br />
Depending on your Linux distribution, specify the relevant command:<br />
<br />
<ul><li>On SLES (SUSE Linux Enterprise Server)</li><br />
zypper install guestfs-tools<br />
<li>Auf Debian und Ubuntu</li><br />
apt-get install libguestfs-tools<br />
<li>On RHEL and CentOS</li><br />
yum install libguestfs-tools<br />
</ul><br />
<br />
==Restrictions and extra steps required on RHEL/CentOS==<br />
Due to restrictions on RHEL mounting Windows VMs will not work. Take a look at [https://libguestfs.org/guestfs-faq.1.html#mount:-unsupported-filesystem-type-with-ntfs-in-rhel-7.2 libguestfs FAQ] for more information.<br />
<br />
On RHEL and its Derivates there are additional steps required to get the single file restore working:<br />
<br />
1. Open /etc/libvirt/qemu.conf and change the variable user from qemu to root<br />
<br />
2. Restart the service libvirtd, by using <br />
systemctl restart libvirtd<br />
<br />
3. Add a new line to /usr/lib64/guestfs/supermin.d/packages containing libgpg-error<br />
<br />
4. Remove old guestmount appliances <br />
rm -rf /var/tmp/.guestfs-*<br />
5. Test if the guestmount appliance builds without errors, by executing <br />
libguestfs-test-tool <br />
This has to exit with<br />
===== TEST FINISHED OK =====<br />
<br />
6. If selinux is set to enforcing, guestfs-tools will not be able to access the Virtual Harddisks provided bu SEP sesam, so mounting still fails.<br />
<br />
== Checking guestmount capabilities on your system ==<br />
<br />
You can check which things guestmount supports on your system currently, by running <br />
<br />
guestfish -a /dev/null run : supported<br />
<br />
on your SEP sesam Server or the SEP sesam RDS, where the savesets you want to mount are located.<br />
<br />
This will show you whether vms with filesystems like btrfs or ntfs can be mounted. You may add this functionality by installing the required packages on your system.<br />
Also you have to add lines for those package names to<br />
/usr/lib64/guestfs/supermin.d/packages<br />
on the system.<br />
<br />
<div class="noprint"><br />
==Bekannte Themen==<br />
Wenn Sie Probleme mit VMware Einzeldateirücksicherung (Single File Restore) haben, überprüfen Sie den [[Special:MyLanguage/Troubleshooting_Guide#VMware|Troubleshooting Guide]].<br />
<br />
==Siehe auch== <br />
[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Einzeldateirücksicherung]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Installation - Kurzanleitung]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]</div></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Translations:Source:Installing_guestfs-tools_on_Linux/19/de&diff=170851Translations:Source:Installing guestfs-tools on Linux/19/de2020-10-20T14:57:48Z<p>Fho: Created page with "Auf Debian und Ubuntu"</p>
<hr />
<div>Auf Debian und Ubuntu</div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Installing_guestfs-tools_on_Linux&diff=170394Source:Installing guestfs-tools on Linux2020-10-02T13:38:14Z<p>Fho: </p>
<hr />
<div> __FORCETOC__<br />
<translate><br />
<!--T:1--><br />
<div class="noprint"><languages /><br />
{{Copyright SEP AG en}}<br />
<br />
<!--T:2--><br />
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/VMware|VMware archive]]}}</div></translate><br /><br />
<translate>==Overview== <!--T:3--></translate><br />
<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 25%; "><center><b><translate><!--T:4--><br />
Additional resources</translate></b></center><br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--><br />
[[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--><br />
See also: [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images] </translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:7--><br />
[[File:support-matrix.png|45px|link=Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:8--><br />
Check all supported [[SEP_sesam_OS_and_Database_Support_Matrix|OS, database configurations and versions]].</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:11--><br />
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:12--><br />
Problems with VMware? Check [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware troubleshooting]].</translate> <br />
|}<br />
</div><br />
<translate><!--T:13--><br />
On Linux, SEP sesam single file restore from virtualization platform backups, e.g., ''VMware vSphere'', requires the <tt>guestfs-tools</tt> package to be installed to be able to access and mount the file system of an image on Linux. If the package is not installed on your SEP sesam Server or RDS Linux server, you will not be able to mount VMDK and consequently, perform a single file restore.<br />
<br />
<!--T:14--><br />
To learn more about the guestfs-tools, see [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]. <br />
<br />
==Installing <tt>guestfs-tools</tt> package== <!--T:15--> <br />
<br />
<!--T:16--><br />
Use the command line to install the guestfs-tools package according to your specific Linux distributions, i.e., ''SLES'', ''Debian'', ''Ubuntu'', ''RHEL'', or ''CentOS''. For details on Linux installation, see [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]]. <br />
<br />
<!--T:17--><br />
Depending on your Linux distribution, specify the relevant command:</translate><br />
<br />
<ul><li><translate><!--T:18--> On SLES (SUSE Linux Enterprise Server)</translate></li><br />
zypper install guestfs-tools<br />
<li><translate><!--T:19--> On Debian and Ubuntu</translate></li><br />
apt-get install libguestfs-tools<br />
<li><translate><!--T:20--> On RHEL and CentOS</translate></li><br />
yum install libguestfs-tools<br />
</ul><br />
<br />
==Restrictions and extra steps required on RHEL/CentOS==<br />
Due to restrictions on RHEL mounting Windows VMs will not work. Take a look at [https://libguestfs.org/guestfs-faq.1.html#mount:-unsupported-filesystem-type-with-ntfs-in-rhel-7.2 libguestfs FAQ] for more information.<br />
<br />
On RHEL and its Derivates there are additional steps required to get the single file restore working:<br />
<br />
1. Open /etc/libvirt/qemu.conf and change the variable user from qemu to root<br />
<br />
2. Restart the service libvirtd, by using <br />
systemctl restart libvirtd<br />
<br />
3. Add a new line to /usr/lib64/guestfs/supermin.d/packages containing libgpg-error<br />
<br />
4. Remove old guestmount appliances <br />
rm -rf /var/tmp/.guestfs-*<br />
5. Test if the guestmount appliance builds without errors, by executing <br />
libguestfs-test-tool <br />
This has to exit with<br />
===== TEST FINISHED OK =====<br />
<br />
6. If selinux is set to enforcing, guestfs-tools will not be able to access the Virtual Harddisks provided bu SEP sesam, so mounting still fails.<br />
<br />
== Checking guestmount capabilities on your system ==<br />
<br />
You can check which things guestmount supports on your system currently, by running <br />
<br />
guestfish -a /dev/null run : supported<br />
<br />
on your SEP sesam Server or the SEP sesam RDS, where the savesets you want to mount are located.<br />
<br />
This will show you whether vms with filesystems like btrfs or ntfs can be mounted. You may add this functionality by installing the required packages on your system.<br />
Also you have to add lines for those package names to<br />
/usr/lib64/guestfs/supermin.d/packages<br />
on the system.<br />
<br />
<translate><br />
<div class="noprint"><br />
==Known issues== <!--T:21--><br />
If you have problems with VMware single file restore, check the [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware troubleshooting]].<br />
<br />
==See also== <!--T:22--><br />
[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]</div></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Installing_guestfs-tools_on_Linux&diff=164236Source:Installing guestfs-tools on Linux2020-08-11T11:04:47Z<p>Fho: </p>
<hr />
<div> __FORCETOC__<br />
<translate><br />
<!--T:1--><br />
<div class="noprint"><languages /><br />
{{Copyright SEP AG en}}<br />
<br />
<!--T:2--><br />
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/VMware|VMware archive]]}}</div></translate><br /><br />
<translate>==Overview== <!--T:3--></translate><br />
<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 25%; "><center><b><translate><!--T:4--><br />
Additional resources</translate></b></center><br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--><br />
[[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--><br />
See also: [[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images] </translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:7--><br />
[[File:support-matrix.png|45px|link=Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:8--><br />
Check all supported [[SEP_sesam_OS_and_Database_Support_Matrix|OS, database configurations and versions]].</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:11--><br />
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:12--><br />
Problems with VMware? Check [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware troubleshooting]].</translate> <br />
|}<br />
</div><br />
<translate><!--T:13--><br />
On Linux, SEP sesam single file restore from virtualization platform backups, e.g., ''VMware vSphere'', requires the <tt>guestfs-tools</tt> package to be installed to be able to access and mount the file system of an image on Linux. If the package is not installed on your SEP sesam Server or RDS Linux server, you will not be able to mount VMDK and consequently, perform a single file restore.<br />
<br />
<!--T:14--><br />
To learn more about the guestfs-tools, see [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]. <br />
<br />
==Installing <tt>guestfs-tools</tt> package== <!--T:15--> <br />
<br />
<!--T:16--><br />
Use the command line to install the guestfs-tools package according to your specific Linux distributions, i.e., ''SLES'', ''Debian'', ''Ubuntu'', ''RHEL'', or ''CentOS''. For details on Linux installation, see [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]]. <br />
<br />
<!--T:17--><br />
Depending on your Linux distribution, specify the relevant command:</translate><br />
<br />
<ul><li><translate><!--T:18--> On SLES (SUSE Linux Enterprise Server)</translate></li><br />
zypper install guestfs-tools<br />
<li><translate><!--T:19--> On Debian and Ubuntu</translate></li><br />
apt-get install libguestfs-tools<br />
<li><translate><!--T:20--> On RHEL and CentOS</translate></li><br />
yum install libguestfs-tools<br />
</ul><br />
<br />
==Restrictions and extra steps required on RHEL/CentOS==<br />
Due to restrictions on RHEL mounting Windows VMs will not work. Take a look at [https://libguestfs.org/guestfs-faq.1.html#mount:-unsupported-filesystem-type-with-ntfs-in-rhel-7.2 libguestfs FAQ] for more information.<br />
<br />
On RHEL and its Derivates there are additional steps required to get the single file restore working:<br />
<br />
1. Open /etc/libvirt/qemu.conf and change the variable user from qemu to root<br />
<br />
2. Restart the service libvirtd, by using <br />
systemctl restart libvirtd<br />
<br />
3. Add a new line to /usr/lib64/guestfs/supermin.d/packages containing libgpg-error<br />
<br />
4. Remove old guestmount appliances <br />
rm -rf /var/tmp/.guestfs-*<br />
5. Test if the guestmount appliance builds without errors, by executing <br />
libguestfs-test-tool <br />
This has to exit with<br />
===== TEST FINISHED OK =====<br />
<br />
6. If selinux is set to enforcing, guestfs-tools will not be able to access the Virtual Harddisks provided bu SEP sesam, so mounting still fails.<br />
<br />
<translate><br />
<div class="noprint"><br />
==Known issues== <!--T:21--><br />
If you have problems with VMware single file restore, check the [[Special:MyLanguage/Troubleshooting_Guide#VMware|VMware troubleshooting]].<br />
<br />
==See also== <!--T:22--><br />
[[Special:MyLanguage/4_4_3:VMware_Single_File_Restore|VMware Single File Restore]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide#linux|SEP sesam Quick Install Guide]] – [http://libguestfs.org/ <tt>libguestfs</tt> tools for accessing and modifying virtual machine disk images]</div></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3_Beefalo:SEPuler_-_an_event_calendar&diff=1638584 4 3 Beefalo:SEPuler - an event calendar2020-08-10T11:42:41Z<p>Fho: </p>
<hr />
<div><translate><!--T:1--><br />
<noinclude><div class="noprint"><languages /><br />
{{Template:Navigator Beefalo/en|Media Strategy|Media Strategy|Backup|Backup}}</div></translate><br />
<br />
<br />
</noinclude><translate>==={{anchor|SEPuler}}SEPuler – an event calendar=== <!--T:2--><br />
<br />
<!--T:3--><br />
SEPuler is a process that controls the scheduling of all SEP sesam tasks, such as backup, migration, replication, restore and other tasks. It acts as an electronic calendar and assistant performing all SEP sesam data protection events.<br />
<br />
<!--T:4--><br />
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. <br />
<br />
<!--T:5--><br />
Once the event has started, SEPuler will determine the next execution event for a cyclical task and rewrite the event to the task calendar. For example, if SEPuler starts a weekly backup on January 1, it will schedule a new weekly backup to occur on January 8.<br />
<br />
<!--T:6--><br />
[[Special:MyLanguage/4_4_3_Beefalo:Backup#backup|Backup]], [[Special:MyLanguage/Configuring_Migration|migration]],</translate><br />
<translate><!--T:7--><br />
[[Special:MyLanguage/About_Replication|replication]], [[Special:MyLanguage/Creating_a_Media_Event|media event]], [[Special:MyLanguage/Creating_a_Command_Event|command event]],</translate><br />
<translate><!--T:8--><br />
[[Special:MyLanguage/4_4_3_Beefalo:Restore|restore]] and [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar#SEP_sesam_backup_day_–_NEWDAY|newday]] are all types of SEPuler events. <br />
<br />
<!--T:9--><br />
Events initiated with the '''Immediate start''' command from the GUI or command line are posted in the calendar as non-recurring events.<br />
<br />
<!--T:10--><br />
All events in SEP sesam start from the SEPuler schedule, even if they are unique, non-recurring tasks. An overview of scheduled as well as completed, expired events and their current status is provided by [[Special:MyLanguage/SEP_sesam_Glossary#calendar_sheet|''Calendar sheet'']] from the ''Main selection'' -> '''Scheduling''' -> '''Calendar Sheet'''.<br />
<br />
<!--T:11--><br />
[[image:GUI_schedules_Beefalo_V2.jpg|600px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate>===={{anchor|schedules}}Schedules==== <!--T:12--><br />
<br />
<!--T:13--><br />
Schedules are used for setting events to occur at a specific time. A schedule is a timetable that defines the cyclic behavior of an event, i.e., when the event is to take place and how frequently to repeat it. The fact that a schedule exists does not automatically mean that an event is executed. <br />
<br />
<!--T:14--><br />
Only when one or more events (backup, migration, command, etc.) are assigned to the schedule, it becomes active. The entries in the schedule are then picked up by the SEPuler. Modifying a schedule affects all the events assigned to that schedule.<br />
<br />
<!--T:15--><br />
Flexible scheduling features include the following:<br />
* Any number of events of the same type can be linked to one or more schedules.<br />
* A task (backup, migration, replication, media action, restore and command event) may have events in several schedules.</translate><br />
<translate><!--T:16--><br />
* Schedules provide '''User defined''' option that allows you to create a calendar which is customized according to your country or company specific requirements. You can use it to exclude scheduled jobs from running on specific dates, such as holidays, or to schedule additional jobs on selected dates. For details, see [[Special:MyLanguage/Creating_Custom_Calendar|Creating Custom Calendar]]. </translate><br />
<translate><!--T:17--><br />
* A schedule's execution can be deactivated: a schedule will remain displayed as shaded (gray) in the list of schedules, but the related jobs will not run.</translate><br />
<translate><br />
<!--T:68--><br />
*The option '''Without Schedule''' is available, if you set the value for <tt>enable_gui_events_without_schedule</tt> in the ''Defaults'' window (''Configuration'' -> ''Defaults'' -> ''Settings'' tab) to 1 manually. It shows all backup events which are not assigned to a schedule. Such events are typically created for external backups, where the external applications manage the backup scheduling. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Schedules#without|Schedules]].<br />
<br />
===={{anchor|event priority}}Event Priority==== <!--T:18--><br />
<br />
<!--T:19--><br />
For complex event strategies, event priority is used by SEPuler for resolving scheduling conflicts. Priorities can be assigned to events, from lowest (1, default) to highest (99). For each [[Special:MyLanguage/SEP_sesam_Glossary#backup_day|SEP sesam backup day]] all scheduled events are checked according to their type and priority to see whether the events of the same type (for example, a backup) with the same task name and higher priority have already expired or are still planned to run; in the latter case, SEP sesam suppresses execution of lower priority events of the same type. In other words, if there are more equal events (see [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar#equality|equality of events]]) of the same type scheduled on the same backup day, only the event with a higher priority is executed. This prevents the events that might be linked to several schedules, which overlap on certain days, to be executed except for the one with the highest priority. <br />
<br />
<!--T:63--><br />
If all equal events of the same type have the same priority (for example, the default – 1), then all of them are executed. Events with priority 0 are not checked for dependency of event priorities and are always executed.<br />
<br />
<!--T:64--><br />
Priorities can be used together with [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar#blocking_events|Blocking date]] option.<br />
<br />
<!--T:20--><br />
{{note|Event priority determines which job in a queue will first be executed regardless of the equality of events. If there are jobs in the queue and a new event with a higher priority is activated by SEPuler, this job will first access a busy device.}}<br />
<br />
====={{anchor|equality}}Equality of Events===== <!--T:21--><br />
<br />
<!--T:22--><br />
The equality of events is managed according to their type:<br />
*Backup events are equal if their task name is the same. The same is true for each individual event type: migration, replication, command and restore event.<br />
*Media events are equal if their drive number or drive group number is the same.<br />
<br />
<!--T:23--><br />
'''Example'''<br />
In the following example, backup of the directory <tt>/etc</tt> of the client ''stratum1'' with the task name ''stratum1_etc'' is started via three different schedules.</translate><br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:50%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#FFCC01; color:#002F55"<br />
! scope="col" |<translate><!--T:70--> Name</translate><br />
! scope="col" |<translate><!--T:71--> Time</translate> <br />
! scope="col" |<translate><!--T:72--> Priority</translate><br />
! scope="col" |<translate><!--T:73--> Task</translate> <br />
|-<br />
|<translate><!--T:74--> Daily</translate>||8 p.m.||1|| <translate><!--T:75--> daily incremental</translate> <br />
|-<br />
|<translate><!--T:76--> Weekly</translate>||6 p.m.||2|| <translate><!--T:77--> differential on the weekend</translate> <br />
|-<br />
|-<br />
|<translate><!--T:78--> Monthly</translate>||9 p.m.||3|| <translate><!--T:79--> full at the end of the month</translate> <br />
|}<br />
<br />
<translate><!--T:37--><br />
* On weekends, the ''weekend'' event is performed instead of the ''daily'' event (prio 2 overrides prio 1).<br />
* At the end of the month, the ''end of month'' event is performed instead of the ''daily'' event (prio 3 overrides prio 1).<br />
* If the end of the month and the weekend coincide, then the ''end of month'' event is performed instead the ''Weekend'' event (prio 3 overrides prio 2).<br />
<br />
<!--T:38--><br />
[[image:Event_priority_Beefalo_V2.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate>===={{anchor|blocking_events}}Blocking Events==== <!--T:39--><br />
<br />
<!--T:40--><br />
A blocking event is any type of event with a higher priority that obstructs another event and prevents it from moving to '''active''' backup status. It may be used to prevent the activation of certain events on specific days (e.g., end of year, end of fiscal year, holidays, etc).</translate><br />
<br />
<!--T:41--><br />
{{<translate><!--T:65--><br />
note</translate>|<br />
<translate><!--T:61--><br />
* A blocking event is created by selecting the '''Blocking date''' checkbox during the configuration of an event.<br />
* Switching off a schedule blocks the execution of all events using this schedule ('''Execution off''' option in the schedule).<br />
* A blocking event only affects other events with the same name when schedules are overlapping.<br />
*A blocking event suppresses any job with the same task name at respective ([[Special:MyLanguage/SEP_sesam_Glossary#backup day|SEP sesam backup day]]) day, regardless of whether it is scheduled to be run before, during or after the blocking event.</translate><br />
}}<br />
<br />
<!--T:42--><br />
<translate><!--T:66--><br />
'''Example'''<br />
<br />
<!--T:43--><br />
A backup event that executes the task ''stratum1_etc'' is configured to run daily with priority 2. A second backup event for the same task ''stratum1_etc'' is only scheduled for December 24th every year as a blocking event with priority 9. On December 24th, the priority check detects the ''stratum1_etc'' backup with higher priority and overrides the execution of the daily backup. The blocking event itself does not create an entry in the job status, but sends a notification that it was activated.<br />
<br />
<div class="noprint"><noinclude><br />
===={{anchor|SEP sesam backup day – NEWDAY}}SEP sesam backup day – NEWDAY==== <!--T:44--><br />
<br />
<!--T:62--><br />
{{:4 4 3 Beefalo:Newday Event/en|NEWDAY Event}}<br />
</noinclude></div></translate><br />
<br />
<!--T:59--><br />
<translate><br />
<noinclude>===See also===</noinclude> <!--T:60--><br />
<noinclude><div class="noprint">[[Special:MyLanguage/About_Scheduling|About Scheduling]] – [[Special:MyLanguage/4_4_3_Beefalo:Schedules|Schedules Overview]] – [[Special:MyLanguage/Creating_a_Schedule|Creating a Schedule]]</div></noinclude></translate><br />
<br />
<translate><!--T:80--> <noinclude>{{Footer/en}}</noinclude></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3_Beefalo:SEPuler_-_an_event_calendar&diff=1638534 4 3 Beefalo:SEPuler - an event calendar2020-08-10T11:35:16Z<p>Fho: </p>
<hr />
<div><translate><!--T:1--><br />
<noinclude><div class="noprint"><languages /><br />
{{Template:Navigator Beefalo/en|Media Strategy|Media Strategy|Backup|Backup}}</div></translate><br />
<br />
<br />
</noinclude><translate>==={{anchor|SEPuler}}SEPuler – an event calendar=== <!--T:2--><br />
<br />
<!--T:3--><br />
SEPuler is a process that controls the scheduling of all SEP sesam tasks, such as backup, migration, replication, restore and other tasks. It acts as an electronic calendar and assistant performing all SEP sesam data protection events.<br />
<br />
<!--T:4--><br />
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. <br />
<br />
<!--T:5--><br />
Once the event has started, SEPuler will determine the next execution event for a cyclical task and rewrite the event to the task calendar. For example, if SEPuler starts a weekly backup on January 1, it will schedule a new weekly backup to occur on January 8.<br />
<br />
<!--T:6--><br />
[[Special:MyLanguage/4_4_3_Beefalo:Backup#backup|Backup]], [[Special:MyLanguage/Configuring_Migration|migration]],</translate><br />
<translate><!--T:7--><br />
[[Special:MyLanguage/About_Replication|replication]], [[Special:MyLanguage/Creating_a_Media_Event|media event]], [[Special:MyLanguage/Creating_a_Command_Event|command event]],</translate><br />
<translate><!--T:8--><br />
[[Special:MyLanguage/4_4_3_Beefalo:Restore|restore]] and [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar#SEP_sesam_backup_day_–_NEWDAY|newday]] are all types of SEPuler events. <br />
<br />
<!--T:9--><br />
Events initiated with the '''Immediate start''' command from the GUI or command line are posted in the calendar as non-recurring events.<br />
<br />
<!--T:10--><br />
All events in SEP sesam start from the SEPuler schedule, even if they are unique, non-recurring tasks. An overview of scheduled as well as completed, expired events and their current status is provided by [[Special:MyLanguage/SEP_sesam_Glossary#calendar_sheet|''Calendar sheet'']] from the ''Main selection'' -> '''Scheduling''' -> '''Calendar Sheet'''.<br />
<br />
<!--T:11--><br />
[[image:GUI_schedules_Beefalo_V2.jpg|600px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate>===={{anchor|schedules}}Schedules==== <!--T:12--><br />
<br />
<!--T:13--><br />
Schedules are used for setting events to occur at a specific time. A schedule is a timetable that defines the cyclic behavior of an event, i.e., when the event is to take place and how frequently to repeat it. The fact that a schedule exists does not automatically mean that an event is executed. <br />
<br />
<!--T:14--><br />
Only when one or more events (backup, migration, command, etc.) are assigned to the schedule, it becomes active. The entries in the schedule are then picked up by the SEPuler. Modifying a schedule affects all the events assigned to that schedule.<br />
<br />
<!--T:15--><br />
Flexible scheduling features include the following:<br />
* Any number of events of the same type can be linked to one or more schedules.<br />
* A task (backup, migration, replication, media action, restore and command event) may have events in several schedules.</translate><br />
<translate><!--T:16--><br />
* Schedules provide '''User defined''' option that allows you to create a calendar which is customized according to your country or company specific requirements. You can use it to exclude scheduled jobs from running on specific dates, such as holidays, or to schedule additional jobs on selected dates. For details, see [[Special:MyLanguage/Creating_Custom_Calendar|Creating Custom Calendar]]. </translate><br />
<translate><!--T:17--><br />
* A schedule's execution can be deactivated: a schedule will remain displayed as shaded (gray) in the list of schedules, but the related jobs will not run.</translate><br />
<translate><br />
<!--T:68--><br />
*The option '''Without Schedule''' is available, if you set the value for <tt>enable_gui_events_without_schedule</tt> in the ''Defaults'' window (''Configuration'' -> ''Defaults'' -> ''Settings'' tab) to 1 manually. It shows all backup events which are not assigned to a schedule. Such events are typically created for external backups, where the external applications manage the backup scheduling. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Schedules#without|Schedules]].<br />
<br />
===={{anchor|event priority}}Event Priority==== <!--T:18--><br />
<br />
<!--T:19--><br />
For complex event strategies, event priority is used by SEPuler for resolving scheduling conflicts. Priorities can be assigned to events, from lowest (1, default) to highest (99). For each [[Special:MyLanguage/SEP_sesam_Glossary#backup_day|SEP sesam backup day]] all scheduled events are checked according to their type and priority to see whether the events of the same type (for example, a backup) with the same task name and higher priority have already expired or are still planned to run; in the latter case, SEP sesam suppresses execution of lower priority events of the same type. In other words, if there are more equal events (see [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar#equality|equality of events]]) of the same type scheduled on the same backup day, only the event with a higher priority is executed. This prevents the events that might be linked to several schedules, which overlap on certain days, to be executed except for the one with the highest priority. <br />
<br />
<!--T:63--><br />
If all equal events of the same type have the same priority (for example, the default – 1), then all of them are executed. Events with priority 0 are not checked for dependency of event priorities and are always executed.<br />
<br />
<!--T:64--><br />
Priorities can be used together with [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar#blocking_events|Blocking date]] option.<br />
<br />
<!--T:20--><br />
{{note|Event priority determines which job in a queue will first be executed regardless of the equality of events. If there are jobs in the queue and a new event with a higher priority is activated by SEPuler, this job will first access a busy device.}}<br />
<br />
====={{anchor|equality}}Equality of Events===== <!--T:21--><br />
<br />
<!--T:22--><br />
The equality of events is managed according to their type:<br />
*Backup events are equal if their task name is the same. The same is true for each individual event type: migration, replication, command and restore event.<br />
*Media events are equal if their drive number or drive group number is the same.<br />
<br />
<!--T:23--><br />
'''Example'''<br />
In the following example, backup of the directory <tt>/etc</tt> of the client ''stratum1'' with the task name ''stratum1_etc'' is started via three different schedules.</translate><br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:50%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#FFCC01; color:#002F55"<br />
! scope="col" |<translate><!--T:70--> Name</translate><br />
! scope="col" |<translate><!--T:71--> Time</translate> <br />
! scope="col" |<translate><!--T:72--> Priority</translate><br />
! scope="col" |<translate><!--T:73--> Task</translate> <br />
|-<br />
|<translate><!--T:74--> Daily</translate>||8 p.m.||1|| <translate><!--T:75--> daily incremental</translate> <br />
|-<br />
|<translate><!--T:76--> Weekly</translate>||6 p.m.||2|| <translate><!--T:77--> differential on the weekend</translate> <br />
|-<br />
|-<br />
|<translate><!--T:78--> Monthly</translate>||9 p.m.||3|| <translate><!--T:79--> full at the end of the month</translate> <br />
|}<br />
<br />
<translate><!--T:37--><br />
* On weekends, the ''weekend'' event is performed instead of the ''daily'' event (prio 2 overrides prio 1).<br />
* At the end of the month, the ''end of month'' event is performed instead of the ''daily'' event (prio 3 overrides prio 1).<br />
* If the end of the month and the weekend coincide, then the ''end of month'' event is performed instead the ''Weekend'' event (prio 3 overrides prio 2).<br />
<br />
<!--T:38--><br />
[[image:Event_priority_Beefalo_V2.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate>===={{anchor|blocking_events}}Blocking Events==== <!--T:39--><br />
<br />
<!--T:40--><br />
A blocking event is any type of event with a higher priority that obstructs another event and prevents it from moving to '''active''' backup status. It may be used to prevent the activation of certain events on specific days (e.g., end of year, end of fiscal year, holidays, etc).</translate><br />
<br />
<!--T:41--><br />
{{<translate><!--T:65--><br />
note</translate>|<br />
<translate><!--T:61--><br />
* A blocking event is created by selecting the '''Blocking date''' checkbox during the configuration of an event.<br />
* Switching off a schedule blocks the execution of all events using this schedule ('''Execution off''' option in the schedule).<br />
* A blocking event only affects other events with the same name when schedules are overlapping.<br />
*A blocking event suppresses any job with the same task name at respective ([[Special:MyLanguage/SEP_sesam_Glossary#backup day|SEP sesam backup day]]) day, regardless of whether it is scheduled to be run before, during or after the blocking event.</translate><br />
}}<br />
<br />
<!--T:42--><br />
<translate><!--T:66--><br />
'''Example'''<br />
<br />
<!--T:43--><br />
A backup event that executes the task ''stratum1_etc'' is configured to run daily with priority 2. A second backup event for the same task ''stratum1_etc'' is only scheduled for December 24th every year as a blocking event with priority 9. On December 24th, the priority check detects the ''stratum1_etc'' backup with higher priority and overrides the execution of the daily backup. The blocking event itself does not create an entry in the job status, but sends a notification that it was activated.<br />
<br />
<div class="noprint"><noinclude><br />
===={{anchor|SEP sesam backup day – NEWDAY}}SEP sesam backup day – NEWDAY==== <!--T:44--><br />
<br />
<!--T:62--><br />
{{:4 4 3 Beefalo:Newday Event/en|NEWDAY Event}}<br />
</noinclude></div></translate><br />
<br />
<!--T:59--><br />
<translate><br />
===See also=== <!--T:60--><br />
<noinclude><div class="noprint">[[Special:MyLanguage/About_Scheduling|About Scheduling]] – [[Special:MyLanguage/4_4_3_Beefalo:Schedules|Schedules Overview]] – [[Special:MyLanguage/Creating_a_Schedule|Creating a Schedule]]</div></noinclude></translate><br />
<br />
<translate><!--T:80--> <noinclude>{{Footer/en}}</noinclude></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3_Beefalo:SEPuler_-_an_event_calendar&diff=1638524 4 3 Beefalo:SEPuler - an event calendar2020-08-10T11:31:05Z<p>Fho: </p>
<hr />
<div><translate><!--T:1--><br />
<noinclude><div class="noprint"><languages /><br />
{{Template:Navigator Beefalo/en|Media Strategy|Media Strategy|Backup|Backup}}</div></translate><br />
<br />
<br />
</noinclude><translate>==={{anchor|SEPuler}}SEPuler – an event calendar=== <!--T:2--><br />
<br />
<!--T:3--><br />
SEPuler is a process that controls the scheduling of all SEP sesam tasks, such as backup, migration, replication, restore and other tasks. It acts as an electronic calendar and assistant performing all SEP sesam data protection events.<br />
<br />
<!--T:4--><br />
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. <br />
<br />
<!--T:5--><br />
Once the event has started, SEPuler will determine the next execution event for a cyclical task and rewrite the event to the task calendar. For example, if SEPuler starts a weekly backup on January 1, it will schedule a new weekly backup to occur on January 8.<br />
<br />
<!--T:6--><br />
[[Special:MyLanguage/4_4_3_Beefalo:Backup#backup|Backup]], [[Special:MyLanguage/Configuring_Migration|migration]],</translate><br />
<translate><!--T:7--><br />
[[Special:MyLanguage/About_Replication|replication]], [[Special:MyLanguage/Creating_a_Media_Event|media event]], [[Special:MyLanguage/Creating_a_Command_Event|command event]],</translate><br />
<translate><!--T:8--><br />
[[Special:MyLanguage/4_4_3_Beefalo:Restore|restore]] and [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar#SEP_sesam_backup_day_–_NEWDAY|newday]] are all types of SEPuler events. <br />
<br />
<!--T:9--><br />
Events initiated with the '''Immediate start''' command from the GUI or command line are posted in the calendar as non-recurring events.<br />
<br />
<!--T:10--><br />
All events in SEP sesam start from the SEPuler schedule, even if they are unique, non-recurring tasks. An overview of scheduled as well as completed, expired events and their current status is provided by [[Special:MyLanguage/SEP_sesam_Glossary#calendar_sheet|''Calendar sheet'']] from the ''Main selection'' -> '''Scheduling''' -> '''Calendar Sheet'''.<br />
<br />
<!--T:11--><br />
[[image:GUI_schedules_Beefalo_V2.jpg|600px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate>===={{anchor|schedules}}Schedules==== <!--T:12--><br />
<br />
<!--T:13--><br />
Schedules are used for setting events to occur at a specific time. A schedule is a timetable that defines the cyclic behavior of an event, i.e., when the event is to take place and how frequently to repeat it. The fact that a schedule exists does not automatically mean that an event is executed. <br />
<br />
<!--T:14--><br />
Only when one or more events (backup, migration, command, etc.) are assigned to the schedule, it becomes active. The entries in the schedule are then picked up by the SEPuler. Modifying a schedule affects all the events assigned to that schedule.<br />
<br />
<!--T:15--><br />
Flexible scheduling features include the following:<br />
* Any number of events of the same type can be linked to one or more schedules.<br />
* A task (backup, migration, replication, media action, restore and command event) may have events in several schedules.</translate><br />
<translate><!--T:16--><br />
* Schedules provide '''User defined''' option that allows you to create a calendar which is customized according to your country or company specific requirements. You can use it to exclude scheduled jobs from running on specific dates, such as holidays, or to schedule additional jobs on selected dates. For details, see [[Special:MyLanguage/Creating_Custom_Calendar|Creating Custom Calendar]]. </translate><br />
<translate><!--T:17--><br />
* A schedule's execution can be deactivated: a schedule will remain displayed as shaded (gray) in the list of schedules, but the related jobs will not run.</translate><br />
<translate><br />
<!--T:68--><br />
*The option '''Without Schedule''' is available, if you set the value for <tt>enable_gui_events_without_schedule</tt> in the ''Defaults'' window (''Configuration'' -> ''Defaults'' -> ''Settings'' tab) to 1 manually. It shows all backup events which are not assigned to a schedule. Such events are typically created for external backups, where the external applications manage the backup scheduling. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Schedules#without|Schedules]].<br />
<br />
===={{anchor|event priority}}Event Priority==== <!--T:18--><br />
<br />
<!--T:19--><br />
For complex event strategies, event priority is used by SEPuler for resolving scheduling conflicts. Priorities can be assigned to events, from lowest (1, default) to highest (99). For each [[Special:MyLanguage/SEP_sesam_Glossary#backup_day|SEP sesam backup day]] all scheduled events are checked according to their type and priority to see whether the events of the same type (for example, a backup) with the same task name and higher priority have already expired or are still planned to run; in the latter case, SEP sesam suppresses execution of lower priority events of the same type. In other words, if there are more equal events (see [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar#equality|equality of events]]) of the same type scheduled on the same backup day, only the event with a higher priority is executed. This prevents the events that might be linked to several schedules, which overlap on certain days, to be executed except for the one with the highest priority. <br />
<br />
<!--T:63--><br />
If all equal events of the same type have the same priority (for example, the default – 1), then all of them are executed. Events with priority 0 are not checked for dependency of event priorities and are always executed.<br />
<br />
<!--T:64--><br />
Priorities can be used together with [[Special:MyLanguage/4_4_3_Beefalo:SEPuler_-_an_event_calendar#blocking_events|Blocking date]] option.<br />
<br />
<!--T:20--><br />
{{note|Event priority determines which job in a queue will first be executed regardless of the equality of events. If there are jobs in the queue and a new event with a higher priority is activated by SEPuler, this job will first access a busy device.}}<br />
<br />
====={{anchor|equality}}Equality of Events===== <!--T:21--><br />
<br />
<!--T:22--><br />
The equality of events is managed according to their type:<br />
*Backup events are equal if their task name is the same. The same is true for each individual event type: migration, replication, command and restore event.<br />
*Media events are equal if their drive number or drive group number is the same.<br />
<br />
<!--T:23--><br />
'''Example'''<br />
In the following example, backup of the directory <tt>/etc</tt> of the client ''stratum1'' with the task name ''stratum1_etc'' is started via three different schedules.</translate><br />
<br />
{| border="2" cellpadding="4" cellspacing="0" style="width:50%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"<br />
|- style="background:#FFCC01; color:#002F55"<br />
! scope="col" |<translate><!--T:70--> Name</translate><br />
! scope="col" |<translate><!--T:71--> Time</translate> <br />
! scope="col" |<translate><!--T:72--> Priority</translate><br />
! scope="col" |<translate><!--T:73--> Task</translate> <br />
|-<br />
|<translate><!--T:74--> Daily</translate>||8 p.m.||1|| <translate><!--T:75--> daily incremental</translate> <br />
|-<br />
|<translate><!--T:76--> Weekly</translate>||6 p.m.||2|| <translate><!--T:77--> differential on the weekend</translate> <br />
|-<br />
|-<br />
|<translate><!--T:78--> Monthly</translate>||9 p.m.||3|| <translate><!--T:79--> full at the end of the month</translate> <br />
|}<br />
<br />
<translate><!--T:37--><br />
* On weekends, the ''weekend'' event is performed instead of the ''daily'' event (prio 2 overrides prio 1).<br />
* At the end of the month, the ''end of month'' event is performed instead of the ''daily'' event (prio 3 overrides prio 1).<br />
* If the end of the month and the weekend coincide, then the ''end of month'' event is performed instead the ''Weekend'' event (prio 3 overrides prio 2).<br />
<br />
<!--T:38--><br />
[[image:Event_priority_Beefalo_V2.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate>===={{anchor|blocking_events}}Blocking Events==== <!--T:39--><br />
<br />
<!--T:40--><br />
A blocking event is any type of event with a higher priority that obstructs another event and prevents it from moving to '''active''' backup status. It may be used to prevent the activation of certain events on specific days (e.g., end of year, end of fiscal year, holidays, etc).</translate><br />
<br />
<!--T:41--><br />
{{<translate><!--T:65--><br />
note</translate>|<br />
<translate><!--T:61--><br />
* A blocking event is created by selecting the '''Blocking date''' checkbox during the configuration of an event.<br />
* Switching off a schedule blocks the execution of all events using this schedule ('''Execution off''' option in the schedule).<br />
* A blocking event only affects other events with the same name when schedules are overlapping.<br />
*A blocking event suppresses any job with the same task name at respective ([[Special:MyLanguage/SEP_sesam_Glossary#backup day|SEP sesam backup day]]) day, regardless of whether it is scheduled to be run before, during or after the blocking event.</translate><br />
}}<br />
<br />
<!--T:42--><br />
<translate><!--T:66--><br />
'''Example'''<br />
<br />
<!--T:43--><br />
A backup event that executes the task ''stratum1_etc'' is configured to run daily with priority 2. A second backup event for the same task ''stratum1_etc'' is only scheduled for December 24th every year as a blocking event with priority 9. On December 24th, the priority check detects the ''stratum1_etc'' backup with higher priority and overrides the execution of the daily backup. The blocking event itself does not create an entry in the job status, but sends a notification that it was activated.<br />
<br />
<div class="noprint"><noinclude><br />
===={{anchor|SEP sesam backup day – NEWDAY}}SEP sesam backup day – NEWDAY==== <!--T:44--><br />
<br />
<!--T:62--><br />
{{:4 4 3 Beefalo:Newday Event/en|NEWDAY Event}}<br />
</noinclude></div></translate><br />
<br />
<!--T:59--><br />
<translate><noinclude><div class="noprint"><br />
===See also=== <!--T:60--><br />
[[Special:MyLanguage/About_Scheduling|About Scheduling]] – [[Special:MyLanguage/4_4_3_Beefalo:Schedules|Schedules Overview]] – [[Special:MyLanguage/Creating_a_Schedule|Creating a Schedule]]</div></noinclude></translate><br />
<br />
<translate><!--T:80--> <noinclude>{{Footer/en}}</noinclude></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=Source:Creating_Exclude_List&diff=163845Source:Creating Exclude List2020-08-10T11:23:02Z<p>Fho: </p>
<hr />
<div><languages /><translate><!--T:1--><br />
<noinclude><br />
<div class="noprint"><br />
{{Copyright SEP AG|en}}<br />
<br />
<!--T:2--><br />
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/SEP_sesam_Documentation#previous|Documentation archive]]}}</div><br />
</noinclude><br />
<br />
===Overview=== <!--T:3--></translate><br />
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><translate><!--T:4--><br />
Additional resources</translate></b></center><br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--><br />
[[File:SEP_next.png|45px|link=Special:MyLanguage/SBC_CLI#exclude_lists|SBC CLI exclude]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--><br />
See also: [[Special:MyLanguage/SBC_CLI#exclude_lists|SBC CLI exclude]] – [[Special:MyLanguage/4_4_3_Beefalo:Exclude_with_Regular_Expressions|Exclude with regular expressions]] – [[Special:MyLanguage/RegExp:_Examples_for_Excluding_Matched_Patterns|Examples for Excluding Matched Patterns]] – [[Special:MyLanguage/4_4_3_Beefalo:Exclude_with_File_Patterns|Exclude with file patterns]] – [[Special:MyLanguage/SEP_sesam_Volume_Shadow_Copy_Service_(VSS)_for_Windows#exclude|Manually excluding a VSS writer from backup]] – [[Special:MyLanguage/FAQ#exclude_VSS_writers|How to exclude specific VSS writers from a backup?]]</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:7--><br />
[[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:8--><br />
Check [[Special:MyLanguage/FAQ#exclude_directory|FAQ]] for additional information on exclude lists.</translate><br />
|}<br />
<br />
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"<br />
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:9--><br />
[[File:icon_archived_docs.png|45px|link=Special:MyLanguage/SEP_sesam_Documentation#previous|Documentation archive]]</translate><br />
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:10--><br />
If you are using an older SEP sesam version, refer to [[Special:MyLanguage/SEP_sesam_Documentation#previous|Documentation archive]].</translate><br />
|}</div></noinclude><br />
<translate><!--T:11--><br />
For each backup you can back up only selected files, [[Special:MyLanguage/FAQ#incl-excl_files|files that match a specific pattern]] and exclude specific files, file types or directories from backups.</translate><!-- What if include and exclude lists are specifying the same files/directories? Which list has a higher priority then? For example, if one specifies the same file in the include and exclude list/field, will the file be included or excluded from backup?--> <br />
<br />
<translate><!--T:12--><br />
Some files are only temporary while others are permanently in use. These files should be either excluded from the ordinary backup or be backed up in a special way. For example, you may not want to back up any temporary (''.tmp'') files, read-only files, or files from specific directories (e.g., ''download directory''). SEP sesam provides a number of ways for setting up exclusion:</translate><br />
<br />
*<translate><br />
<!--T:69--><br />
[[Special:MyLanguage/Creating_Exclude_List#GUI|Specifying ''Exclude list'']] in GUI.</translate><br />
*<translate><!--T:14--><br />
[[Special:MyLanguage/Creating_Exclude_List#custom|Creating a custom exclude list]] on the [[Special:MyLanguage/SBC_CLI#exclude_lists|SEP sesam Client (SBC CLI)]] to exclude a larger number of files</translate><br />
*<translate><!--T:15--><br />
[[Special:MyLanguage/Creating_Exclude_List#nosbc|Creating a special file ''nosbc'' in the directory]] itself to permanently mark the directory for exclusion.</translate><br />
*<translate><!--T:16--><br />
[[Special:MyLanguage/Creating_Exclude_List#sm.ini|Using SEP sesam configuration file ''sm.ini'']] to exclude files from all backups on the client. </translate><br />
<br />
<translate>==={{anchor|GUI}}Exclude list in GUI=== <!--T:70--> <br />
<br />
<!--T:71--><br />
When creating a backup task, you specify the source for your backup as well as define any files or patterns you want to exclude from backup. Note that when the number of files to be excluded for backup exceeds allowed length for the exclude list, you should set up exclusion as described in section [[Special:MyLanguage/Creating_Exclude_List#custom|Create a custom exclude list on client]]. Such custom exclude list (e.g., -X C:/sesam/exclude_list.txt) takes precedence over any exclude list specified in GUI.</translate> <br />
<ol><li><translate><!--T:72--><br />
From ''Main Selection'' -> '''Tasks''' -> '''By Clients''', select your client and click '''New Backup Task'''. The ''New Backup Task'' window opens.</translate><br />
<li><translate><!--T:73--><br />
Specify the '''Source'''. If you want to back up individual files, you can either browse for directories and files that you want to include in the backup or enter their names followed by a comma (''C:/Program Files/SEPsesam/var/db,C:\Users\AA\Documents\references''). If you want to back up the whole file system, set the source as ''all''. If you want to back up only files that match a specific pattern, use the [[Special:MyLanguage/FAQ#incl-excl_files|include list]] instead. Note that if you select the source by browsing, the ''task type'' and ''task name'' are set automatically. If you enter the source manually, you have to enter the ''task name'' and select relevant [[Special:MyLanguage/SEP_sesam_Glossary#task_type|''task type'']].</translate></li><br />
<li><translate><!--T:74--><br />
In the '''Exclude list''', specify the files or folders which you do not want to back up in one of the following ways:</translate><br /><br />
<translate><!--T:75--><br />
{{anchor|browse_button}}'''Exclude by using the browse button'''</translate><br /><translate><!--T:76--><br />
The simplest way to exclude the specific files or folders from the backup is by using the big browse button (next to the fields ''Source'' and ''Exclude list'') and selecting your source for exclude in the ''Client File View'' window. In our example we have excluded ''logs'' and ''program files'' from the backup, as shown in the screenshot below.</translate><br /><br />
<translate><!--T:77--><br />
[[image:Basic_exclude_list_Beefalo_V2.jpg|700px|link=]]</translate><br />
<br clear=all><br />
<translate><!--T:78--><br />
{{anchor|editor}}'''Add files, file types or regular expressions in the ''Exclude list editor'''''</translate><br /><br />
<translate><!--T:79--><br />
In the '''Exclude list editor''', specify the exclusions by using regular expressions. On Windows, you can also use the option ''Pattern exclude'', however on Linux it is only possible to exclude by using regular expressions (''RegExp exclude'').</translate><br />
<br /><translate><!--T:80--><br />
Add the exclusion patterns one by one followed by a comma. For example, if you want to back up source ''/usr'' but skip ''*.tmp'' and ''old*.c'' files and all old* directories, add the following pattern to the editor: {{path|\.tmp$, /old.*\.c$, /old.*/$}} </translate><br /><br />
<translate><br />
<!--T:81--><br />
[[image:Exclude_list_Beefalo_V2.jpg|700px|link=]]</translate><br />
<br clear=all><br />
<translate><!--T:82--><br />
Click '''OK'''.</translate></li></ol><br />
<translate><br />
<!--T:83--><br />
For more examples on excludes using regular expression patterns, see [[Special:MyLanguage/RegExp:_Examples_for_Excluding_Matched_Patterns|Examples for Excluding Matched Patterns]].</translate><br />
{{<translate><!--T:66--><br />
note</translate>|<translate><!--T:26--><br />
Exclude by using regular expressions is the default setting, but you can change it to use the file pattern (?,*) instead of regexp by modifying the configuration file <tt><SESAM_VAR>/var/ini/sm.ini</tt> on the [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]]. In the config file <tt>sm.ini</tt> change the entry</translate><br /> <translate><!--T:67--><br />
<nowiki>EXCLUDE_MATCH= REGEXP to EXCLUDE_MATCH= PATTERN</nowiki></translate>.}}<br />
<br />
<translate>==={{anchor|custom}}Create a custom exclude list on client=== <!--T:27--><br />
<br />
<!--T:28--><br />
You can specify a custom exclude list of items to be skipped during backup by creating a special file on SEP sesam Client. Typically, you would create a separate exclude file when the number of files or directories to be excluded for backup exceeds allowed length for exclude list (max. 1024 characters in SEP sesam version ≥ 4.4.3; max. 255 characters in version ≤ 4.4.2). Such custom exclude list takes precedence over any exclude list specified in GUI (the latter is ignored if both are specified).<br />
<br />
<!--T:29--><br />
A custom exclude list must be a text file that is created on the SEP sesam Client on which the backup will be executed. The syntax for exclude entries is platform/OS dependent, see:</translate><br />
*<translate><!--T:30--><br />
[[Special:MyLanguage/Creating_Exclude_List#linux|Exclude list on Linux]]</translate><br />
<br />
*<translate><!--T:31--><br />
[[Special:MyLanguage/Creating_Exclude_List#windows|Exclude list on Windows]]</translate><br />
<br />
*<translate><!--T:32--><br />
[[Special:MyLanguage/Creating_Exclude_List#novell|Exclude list for Micro Focus OES (formerly Novell OES)]]</translate><br />
<br />
<translate><!--T:33--><br />
Once you have created the exclude file, for example ''exclude_list.txt'', enter it in the backup task properties as follows:</translate><br /><br />
<br />
<translate><!--T:34--><br />
Create or open the '''backup task''', select the '''Options''' tab and under the ''Additional call arguments'' in the '''Backup options''' (previously ''Save options'') field, enter the specified file in the form:<br />
-X C:/sesam/exclude_list.txt</translate> <br />
<br />
<translate>===={{anchor|linux}}Exclude list on Linux==== <!--T:35--><br />
<br />
<!--T:36--><br />
Create the exclude file on the client in the directory {{path|/etc/sesam}}, for example {{path|/etc/sesam/exclude_list.txt}}. The following rules apply:</translate><br />
*<translate><!--T:37--><br />
Each file or directory that you want to exclude from backup must be specified in a separate line (one entry per line). </translate><br />
<br />
*<translate><!--T:38--><br />
Wildcards are not supported.</translate><br />
<br />
*<translate><!--T:39--><br />
The exclude entries have to be set up with a regular expressions syntax.</translate><br />
<br />
<translate><!--T:40--><br />
This is an example of the ''exclude_list.txt'' on Linux:</translate><br />
\./tmp$<br />
\./home/John Doe/videos.zip$<br />
\./home/John Doe/Business Documents/YearEnd Closing for business year 2006$<br />
<br />
{{<translate><br />
<!--T:64--><br />
note</translate>|<translate><br />
<!--T:65--><br />
In SEP sesam versions < 4.4.3.45, the exclude list, defined on Linux/UNIX in a Lotus Notes backup task, does not work if specified with {{path|\.}}. For versions < 4.4.3.45, specify the exclude list for Notes without the preceding backslash and a dot, e.g., use {{path|/srv/notesdata/help$}} instead of {{path|\./srv/notesdata/help$'}}. </translate>}}<br />
<br />
<translate>===={{anchor|windows}}Exclude list on Windows==== <!--T:41--><br />
<br />
<!--T:42--><br />
Create the exclude file on the client in the directory {{path|C:\Program Files\SEPsesam\var\ini}}, for example {{path|exclude_list.txt}}. The following rules apply:</translate><br />
* <translate><!--T:43--><br />
Use only {{path|/}} (slash) in the exclude file and NOT {{path|\}} (backslash).</translate><br />
<br />
* <translate><!--T:44--><br />
Each file or directory that you want to exclude from backup must be specified in a separate line (one entry per line). This also applies to paths that include spaces.</translate><br />
<br />
<br />
<translate><!--T:45--><br />
This is an example of the ''exclude_list.txt'' on Windows:</translate><br />
D:/DOWNLOAD<br />
D:/PREKITS<br />
D:/Dev<br />
D:/kit_2_3_1_7<br />
D:/kit_2_3_1_5<br />
D:/knoppix<br />
D:/ACHIM<br />
D:/gui<br />
<br />
<translate>===={{anchor|novell}}Exclude list for Micro Focus OES (formerly Novell OES)==== <!--T:46--><br />
<br />
<!--T:47--><br />
Create the exclude file on the client in the directory {{path|/etc/sesam}}, for example {{path|/etc/sesam/exclude_list.txt}}. The following rules apply:</translate><br />
*<translate><!--T:48--><br />
Each file or directory that you want to exclude from backup must be specified in a separate line (one entry per line). </translate><br />
<br />
*<translate><!--T:49--><br />
Use only the pattern format for exclude. </translate><br />
<br />
*<translate><!--T:50--><br />
Wildcards are allowed in the file or directory entries. </translate><br />
<br />
*<translate><!--T:51--><br />
An exclude folder must end with a {{path|/}} (slash).</translate><br />
<br />
<br />
<translate><!--T:52--><br />
This is an example of the ''exclude_list.txt'':</translate><br />
<br />
/media/nss/VOL1/tmp/<br />
/media/nss/VOL1/USR/*/Notes/Workspace/<br />
/media/nss/VOL1/data/do_not_backup.txt<br />
<br />
<translate><!--T:53--><br />
For example, ''/media/nss/VOL1'' is entered as source in the backup task. This means that the complete ''VOL1'' will be backed up, excluding the items in the exclude file that is specified by the following entry in the ''backup task properties'' -> '''Options''' tab -> '''Backup options''' (previously ''Save options'') field:</translate><br />
<br />
-X /etc/sesam/exclude_list.txt<br />
<br />
<translate><!--T:54--><br />
SEP sesam will exclude all the files and directories from the backup that are listed in the file.<br />
<br />
==={{anchor|nosbc}}Creating a special file ''nosbc'' to permanently exclude a directory=== <!--T:55--><br />
<br />
<!--T:56--><br />
You can permanently exclude a directory from all backups on the client by creating a special file in the directory itself – this file is <tt>.nosbc</tt> on Unix or <tt>nosbc</tt> on Windows. By creating such a file in the directory, the directory will not be backed up even though is might be included in the specified source. <br />
<br />
<!--T:57--><br />
The behavior can be switched off for a specific backup task by entering the ''-o noexcl'' switch under the '''backup task properties''', tab '''Options''' -> '''Backup options''' (previously ''Save options'').<br />
<br />
==={{anchor|sm.ini}}Using ''sm.ini'' to completely exclude files from backups on the client=== <!--T:58--><br />
<br />
<!--T:59--><br />
You can use the central SEP sesam config file <tt>sm.ini</tt> to specify the files on the client that should never be backed up. The advantage of using this method is that you can exclude files or directories from all backups performed on the respective client.</translate> <br />
<br />
<translate><!--T:60--><br />
The default location of the sm.ini file is <tt><SESAM_ROOT>\var\ini\sm.ini</tt>.<br />
<br />
<!--T:61--><br />
To define the excludes for the client, open the <tt>sm.ini</tt> file and under the parameter <tt>SBC_EXCLUDE</tt> enter one parameter per line. <br />
<ul><li>On Linux, use regular expressions to define the excludes in <tt>sm.ini</tt>. For example, to exclude the directories ''/dev'', ''/mnt'' and ''/media'' from the backup, specify the following:</li></translate><br />
[SBC_EXCLUDE]<br />
ExcludePattern1=\./mnt$<br />
ExcludePattern2=\./dev$<br />
ExcludePattern3=\./media$<br />
<br />
{{<translate><!--T:85--> Note</translate>|<translate><!--T:84--><br />
As of [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], the ''ExcludePattern900'' and higher exclude parameters are used for SEP sesam specific exclude patterns. In order to define your own exclude patterns, use parameters ''ExcludePattern1'' to ''ExcludePattern899''.</translate>}}<br />
<br />
<translate><!--T:62--><br />
<li>On Windows, use file patterns to define the excludes in <tt>sm.ini</tt>. You can use this to exclude files that match the specified names or paths (note that <file_name> can include wildcard characters, e.g., * and ?).</li></ul></translate><br />
<br />
<noinclude><translate><div class="noprint"><br />
===See also=== <!--T:63--><br />
[[Special:MyLanguage/SBC_CLI#exclude_lists|SBC CLI exclude]] – [[Special:MyLanguage/4_4_3_Beefalo:Exclude_with_Regular_Expressions|Exclude with regular expressions]] – [[Special:MyLanguage/RegExp:_Examples_for_Excluding_Matched_Patterns|Examples for Excluding Matched Patterns]] – [[Special:MyLanguage/4_4_3_Beefalo:Exclude_with_File_Patterns|Exclude with file patterns]] – [[Special:MyLanguage/SEP_sesam_Volume_Shadow_Copy_Service_(VSS)_for_Windows#exclude|Manually excluding a VSS writer from backup]] – [[Special:MyLanguage/FAQ#exclude_VSS_writers|How to exclude specific VSS writers from a backup?]]</div></translate></noinclude></div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3_Beefalo:Topology&diff=1638414 4 3 Beefalo:Topology2020-08-10T11:15:58Z<p>Fho: </p>
<hr />
<div><languages /><translate><br />
<!--T:1--><br />
<noinclude><div class="noprint"><br />
{{Template:Navigator Beefalo/en|User Manual#components|Components|Clients|Clients}}</div></noinclude></translate><br/><br />
<br />
<noinclude><br />
<translate>===Topology=== <!--T:131--> <br />
<br />
<!--T:7--><br />
</noinclude><br />
Topology represents the SEP sesam backup environment including the hardware, computers, backup devices, etc.<br />
<br />
<!--T:8--><br />
All interconnected computers – [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Clients]] and [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Servers]] – can be logically grouped into locations and sub-locations. You can use ''locations'' to group your clients according to their OS, data type, different geographical location, etc. <br />
<br />
<!--T:9--><br />
The menu item '''Topology''' shows all SEP sesam locations, clients, loaders and drives known to the Master Server as well as the media within the devices. By clicking the symbols they can be expanded into the subordinate structures via a function tree. Each client is assigned to a location and each loader and drive to a client. You can open their ''properties'' by double-clicking the relevant component (location, client or drive).<br />
<br />
<!--T:55--><br />
Such grouping enables large organizations at different locations to be managed and represented as a group with separate, centrally-managed units (using a tree view). Locations can be hierarchically organized - multiple sub-locations can be summarized under one Location. <br />
<br />
<!--T:10--><br />
A '''Master Sesam''' at the highest level presents all currently accessible ''regular'' SEP sesam computers. With a mouse click their individual data can be viewed.<br />
<br />
<!--T:11--><br />
A ''regular'' SEP sesam server shows one node only, namely itself.<br />
<br />
<!--T:12--><br />
[[Image:Topology_overview_Beefalo.jpg|750px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:56--><br />
With v. [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3. ''Beefalo'']], SEP sesam provides additional ''View Mode'' button that enables you to switch between the table view and the tree view with grouped objects.<br />
<br />
<!--T:57--><br />
*'''''Tree view''''': SEP sesam default view shows the status of individual locations grouped together in a hierarchical view.<br />
<br />
<!--T:58--><br />
*'''''Table view''''': A simple flat view that shows the status of individual locations one after another.<br />
<br />
<!--T:60--><br />
To create a new location independent of another location or a sub-location, click '''Topology''', and click the button '''New Location'''. A client is always assigned to and created within a location. For details, see [[Special:MyLanguage/Configuring_Location|Configuring Location]]. <br />
<br />
===={{anchor|client_update}}Updating client(s)==== <!--T:124--><br />
<br />
<!--T:125--><br />
As of v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], the <tt>sm_update_client</tt> command has been extended<!-- with automatic installation of service packs on the SEP sesam Server-->. Now you can check in the SEP sesam GUI if an update for your clients is available, see [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#check|Checking update status]]. If it is, the icon with the orange arrow is shown. For details on GUI icons, [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_Icons_Legend#client_status|Client status icons]]. <br />
<br />
<!--T:126--><br />
It is possible to check if the installed SEP sesam Client is up to date by right-clicking the location/client and selecting the ''Check Update State'' option. Use the ''Check Access State'' option to make sure that you have access to your SEP sesam client(s). Note that the availability of of the update/install options depends on your [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#mode|selected update mode]]. <br />
<br />
<!--T:127--><br />
You can update all clients within the location at once by right-clicking the location and selecting ''Update all clients''. You can also select to update only the clients running on Windows or Linux by using ''Update all Linux/Windows Clients''. This will update all Windows or Linux clients, respectively, within the selected location. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#mass_update|Performing mass update]]. <br />
<br />
<!--T:128--><br />
If you want to update an individual client rather than all clients within the location, right-click it and select ''Update Client''. You may want to exclude a particular client from being updated; in this case, double-click it to open its properties and select ''Do not update this client'' check box. Note that this setting applies in general for all possible updates. <br />
<br />
<!--T:129--><br />
If you have new Windows clients and would like to install either a SEP sesam Client, RDS (with GUI), GUI (with SEP sesam Client), or a SEP sesam Server on the selected client (with or without BSR), you only need to specify a user name and password (OS access) when selecting ''Install SEP sesam''. For the Exchange and Hyper-V clients, the selected package will be installed by providing the credentials used to connect to the host computer. You can also uninstall SEP sesam from the respective client by clicking ''Uninstall SEP sesam''.<br />
<br />
===={{anchor|location_properties}}Location properties==== <!--T:61--> <br />
<br />
<!--T:62--><br />
''Locations'' are defined as a group of clients and/or further sub-locations. This should help you to<br />
organize larger networks so that computers in a building, an external office, etc., can be managed and<br />
represented in the separate units. <br />
<br />
<!--T:63--><br />
You can configure new locations from a SEP sesam Server or from an existing location (sub-location). SEP sesam sets up a tree-structure for all locations (e.g., USA-Colorado-Boulder-SEP Software) offering greater visibility. For details, see [[Special:MyLanguage/Configuring_Location|Configuring Location]]. <br />
<br />
<!--T:64--><br />
You can also edit the existing location or sub-location settings by double-clicking a relevant location/sub-location to open its ''Properties''. <br />
<br />
<!--T:23--><br />
[[Image:Location_properties_Beefalo.jpg|450px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><br />
<!--T:65--><br />
'''''Location tab'''''<br />
<br />
<!--T:66--><br />
*'''''Name''''': Name of the location</translate><br />
<translate><!--T:67--> *'''''in''''': Superordinated location (relevant for sub-locations)</translate><br />
<translate><br />
<!--T:68--><br />
*'''''Description''''': More exact description of the location</translate><br />
<translate><!--T:69--> *'''''Contact''''': Contact person at this location</translate><br />
<translate><!--T:70--><br />
*'''''Note''''': Additional information<br />
<br />
<!--T:71--><br />
'''''OS Access tab'''''<br />
<br />
<!--T:72--><br />
When configuring a new location, you can enter the credentials that will apply to all clients within a location, instead of specifying it for each client individually. In this case, enter the credentials as an ''administrator'' to access the respective systems. You can edit your credentials in the ''location properties''. You have to use ''DOMAIN\USER'' format for the domain accounts or ''HOST\USER'' for the local accounts.<br />
<br />
<!--T:73--><br />
'''''Permissions tab'''''<br />
<br />
<!--T:74--><br />
Under the ''Permissions'' tab, you can configure permissions (ACLs) for your locations, if you have the ''admin'' rights. For details, see [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]].<br />
<br />
===={{anchor|client_properties}}Client properties==== <!--T:75--> <br />
<br />
<!--T:76--><br />
''Clients'' are the computers in the network (including the SEP sesam Server) that you want to back up and restore. <br />
<br />
<!--T:28--><br />
The following screenshot shows the input fields and functions of the clients.</translate><br />
<br />
{{<translate><!--T:77--> note</translate>|<translate><!--T:78--> The client properties are slightly different if you are configuring a new client or when the client is already added and configured and you edit its properties. The ''Platform'' is only available when configuring a new client, while tabs for specifying additional settings are only available for the already configured client in its properties.</translate>}}<br />
<br />
<translate><br />
<!--T:79--><br />
[[Image:Topology_client_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:80--> '''''Client tab'''''</translate><br />
<br />
<ul><li><translate><!--T:81--> '''''Name''''': Enter the name of the client – this has to be the network host name of the computer. The name has to be resolvable either by DNS or <tt>etc/hosts</tt> file.</translate></li><br />
<br />
<li><translate><!--T:82--> '''''Location''''': Predefined location. A client always has to be assigned to a location.</translate></li><br />
<br />
<li><translate><!--T:123--> '''''Platform''''': Select the relevant platform of the client (''Windows'', ''UNIX'', ''VMS'' or ''NETWARE''). Depending on the platform, tabs for special access parameters are displayed. The ''Platform'' is only available when configuring a new client.</translate></li><br />
<br />
<li><translate><!--T:83--> '''''Operating system''''': Select the operating system version of the computer you are adding as a client.</translate></li><br />
<br />
<li><translate><!--T:84--> '''''Access mode''''': Select the relevant access method for the server-client communication. {{:4 4 3 Beefalo:Access Modes/en}}</translate></li><br />
<li><translate><!--T:86--> '''''VM server type''''': If the client should be managed as a VM server, select the relevant type. This enables, for example, browsing the virtual environment when creating backup tasks.</translate></li><br />
<br />
<li><translate><!--T:87--> '''''Last SEP sesam message''''': The most recent system status message for the existing client.</translate></li><br />
<br />
<li><translate><!--T:88--> '''''Last successful access''''': The last successful access to the existing client.</translate></li><br />
<br />
<li><translate><!--T:89--> '''''Notes''''': Optional comment.</translate></li><br />
<br />
<li><translate><!--T:90--> '''''Interfaces''''':</translate></li> <br />
{{<translate><!--T:91--> Note</translate>|<translate><!--T:92--> Only edit this field if a client is a SEP sesam Server or Remote Device Server (RDS).</translate>}} <br />
<br />
<translate><!--T:93--><br />
If there is an additional network for backups available, the resolvable and changed DNS-name of a second network card of the SEP sesam Server can be entered into a new line. If several network cards are available, they need to be known to the DNS otherwise the connection to SEP sesam Server will fail. <br />
<br />
<!--T:94--><br />
The network protocols for data transfer can be set by using the common prefixes '''ftp://''' (default), '''http://''' or '''https://'''. For each protocol one interface has to be added in the interfaces box separated by single spaces. One interface for the HTTP protocol ''<nowiki>http://<hostname>:11000</nowiki>'' and one interface for the HTTPS protocol ''<nowiki>https://<hostname>:11088</nowiki>''.</translate><br />
<br />
<li><translate><!--T:95--> '''''SEP sesam version''''': This field shows the SBC (SEP sesam backup Client) version of the installation.</translate></li><br />
<br />
<li><translate><!--T:96--> '''''VM host and VM name''''': VM host and name are displayed, if you have specified them during the client creation.</translate></li><br />
<br />
<li><translate><!--T:97--> '''''Additional options'''''</translate></li> <br />
<br />
<translate><!--T:98--> There are two additional client-related options:</translate><br />
<br />
<ul><li><translate><!--T:99--> '''''Client is a virtual machine''''': Selecting this option allows you to edit the ''VM host'' (name of the VM Server) and the ''VM name''. These values are used to identify the backup client as a VM in a virtual environment.</translate></li><br />
<li><translate><!--T:130--> '''''Do not update this client''''' (≥ 4.4.3. ''Beefalo V2''): Checking this option allows you to exclude a particular client from being updated. This setting applies in general for all possible updates.</translate></li><br />
<li><translate><!--T:100--> '''''Execution off''''': If a client needs to be excluded from the backup for technical or other reasons, you can deactivate it by checking this option.</translate></li><br />
<br />
{{<translate><!--T:101--> Note</translate>|<translate><!--T:102--> If this option is set, the client will not be backed up until it is unlocked again even if it is scheduled for backup.</translate>}}<br />
</ul></ul><br />
<br />
<translate><!--T:103--><br />
'''''{{anchor|firewalls}}Options tab'''''<br />
<br />
<!--T:104--><br />
By default, SEP sesam uses random ports that are assigned by the operating system for its data connections. However, if you want to back up a client which is behind a firewall, you must manually define the ports. The available options depend on the client type. <br />
<br />
<!--T:105--><br />
[[image:Client__options_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
*<translate><!--T:106--> '''''Access options''''': The default communication port on the backup client is 11301. If a port other than 11301 is used, it must be configured in the client's <tt>sm.ini</tt> file. In this field, enter the port over which the client is reachable (e.g., <tt>-p 17301</tt>).</translate><br />
<translate><br />
<!--T:107--><br />
*'''''STPD options''''': The STPD options are used to define the backports from the clients to the SEP sesam Server, e.g. 11003-11006. These ports are then used to carry data during backups and restores. For each backup that runs parralel 2 ports of a client are needed.</translate><br />
<translate><br />
<!--T:108--><br />
*'''''Listen port''''': The default STPD-port for Remote Device Servers (incl. SEP sesam Server) is 11001.</translate><br />
*<translate><!--T:109--><br />
'''''Wake on LAN''''': For more information, see [[Special:MyLanguage/WOL_-_wake_on_LAN_of_a_SEP_sesam_client|How To]].<br />
<br />
<!--T:110--><br />
For details, see [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]].<br />
<br />
<!--T:111--><br />
'''''OS Access tab'''''<br />
<br />
<!--T:112--><br />
When configuring a new client, you have to enter the credentials as an administrator to access the respective systems. You can also edit your credentials in the ''client properties''. You have to use <tt>DOMAIN\USER</tt> format for domain accounts or <tt>HOST\USER</tt> for local accounts. <br />
<br />
<!--T:113--><br />
[[image:Client__access_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:114--><br />
'''''Additional tabs''''' <br />
<br />
<!--T:115--><br />
In the client properties two additional tabs are available for specifying additional settings. <br />
<br />
<!--T:116--><br />
Under the '''Permissions''' tab, you can add the relevant permissions (ACLs) for your client. For details, see [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]]. <br />
<br />
<!--T:117--><br />
[[image:Client__permissions_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:118--> If you are configuring clients that must be backed up by special [[Special:MyLanguage/SEP_sesam_Glossary#task_type|task types]], additional settings must be specified. A fifth tab is available for the following task types: ''Micro Focus Open Enterprise Server (formerly Novell OES)'', ''VMware'', ''Citrix XEN'', ''MySQL'', ''PostgreSQL'', ''NetApp'', ''RHV''. For example, for Micro Focus OES or NetWare server backup you have to specify the login data for the eDirectory and select the appropriate [[Special:MyLanguage/SEP_sesam_Glossary#data_mover|data mover]]. For Micro Focus, this is a SEP sesam Micro Focus (formerly Novell) Client which is installed on Linux computer with Micro Focus Storage Management Services (SMS).</translate><br /><br />
<translate><!--T:119--> [[image:Client__VMware_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<translate><!--T:120--><br />
For more information on specific task type, see the respective wiki articles under [[Special:MyLanguage/SEP_sesam_Documentation#extensions|Extensions]].<br />
<br />
<div class="noprint"><noinclude><br />
===See also=== <!--T:121--><br />
[[Special:MyLanguage/Configuring_Location|Configuring Location]] – [[Special:MyLanguage/Configuring_Clients|Configuring Clients]] – [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]] – [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]]<br />
<br />
<!--T:122--><br />
{{Footer/en}}</noinclude></div></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3_Beefalo:Topology&diff=1638374 4 3 Beefalo:Topology2020-08-10T10:58:50Z<p>Fho: </p>
<hr />
<div><languages /><translate><br />
<!--T:1--><br />
<div class="noprint"><noinclude><br />
{{Template:Navigator Beefalo/en|User Manual#components|Components|Clients|Clients}}</noinclude></div></translate><br/><br />
<br />
<noinclude><br />
<translate>===Topology=== <!--T:131--> <br />
<br />
<!--T:7--><br />
</noinclude><br />
Topology represents the SEP sesam backup environment including the hardware, computers, backup devices, etc.<br />
<br />
<!--T:8--><br />
All interconnected computers – [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Clients]] and [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Servers]] – can be logically grouped into locations and sub-locations. You can use ''locations'' to group your clients according to their OS, data type, different geographical location, etc. <br />
<br />
<!--T:9--><br />
The menu item '''Topology''' shows all SEP sesam locations, clients, loaders and drives known to the Master Server as well as the media within the devices. By clicking the symbols they can be expanded into the subordinate structures via a function tree. Each client is assigned to a location and each loader and drive to a client. You can open their ''properties'' by double-clicking the relevant component (location, client or drive).<br />
<br />
<!--T:55--><br />
Such grouping enables large organizations at different locations to be managed and represented as a group with separate, centrally-managed units (using a tree view). Locations can be hierarchically organized - multiple sub-locations can be summarized under one Location. <br />
<br />
<!--T:10--><br />
A '''Master Sesam''' at the highest level presents all currently accessible ''regular'' SEP sesam computers. With a mouse click their individual data can be viewed.<br />
<br />
<!--T:11--><br />
A ''regular'' SEP sesam server shows one node only, namely itself.<br />
<br />
<!--T:12--><br />
[[Image:Topology_overview_Beefalo.jpg|750px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:56--><br />
With v. [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3. ''Beefalo'']], SEP sesam provides additional ''View Mode'' button that enables you to switch between the table view and the tree view with grouped objects.<br />
<br />
<!--T:57--><br />
*'''''Tree view''''': SEP sesam default view shows the status of individual locations grouped together in a hierarchical view.<br />
<br />
<!--T:58--><br />
*'''''Table view''''': A simple flat view that shows the status of individual locations one after another.<br />
<br />
<!--T:60--><br />
To create a new location independent of another location or a sub-location, click '''Topology''', and click the button '''New Location'''. A client is always assigned to and created within a location. For details, see [[Special:MyLanguage/Configuring_Location|Configuring Location]]. <br />
<br />
===={{anchor|client_update}}Updating client(s)==== <!--T:124--><br />
<br />
<!--T:125--><br />
As of v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], the <tt>sm_update_client</tt> command has been extended<!-- with automatic installation of service packs on the SEP sesam Server-->. Now you can check in the SEP sesam GUI if an update for your clients is available, see [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#check|Checking update status]]. If it is, the icon with the orange arrow is shown. For details on GUI icons, [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_Icons_Legend#client_status|Client status icons]]. <br />
<br />
<!--T:126--><br />
It is possible to check if the installed SEP sesam Client is up to date by right-clicking the location/client and selecting the ''Check Update State'' option. Use the ''Check Access State'' option to make sure that you have access to your SEP sesam client(s). Note that the availability of of the update/install options depends on your [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#mode|selected update mode]]. <br />
<br />
<!--T:127--><br />
You can update all clients within the location at once by right-clicking the location and selecting ''Update all clients''. You can also select to update only the clients running on Windows or Linux by using ''Update all Linux/Windows Clients''. This will update all Windows or Linux clients, respectively, within the selected location. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#mass_update|Performing mass update]]. <br />
<br />
<!--T:128--><br />
If you want to update an individual client rather than all clients within the location, right-click it and select ''Update Client''. You may want to exclude a particular client from being updated; in this case, double-click it to open its properties and select ''Do not update this client'' check box. Note that this setting applies in general for all possible updates. <br />
<br />
<!--T:129--><br />
If you have new Windows clients and would like to install either a SEP sesam Client, RDS (with GUI), GUI (with SEP sesam Client), or a SEP sesam Server on the selected client (with or without BSR), you only need to specify a user name and password (OS access) when selecting ''Install SEP sesam''. For the Exchange and Hyper-V clients, the selected package will be installed by providing the credentials used to connect to the host computer. You can also uninstall SEP sesam from the respective client by clicking ''Uninstall SEP sesam''.<br />
<br />
===={{anchor|location_properties}}Location properties==== <!--T:61--> <br />
<br />
<!--T:62--><br />
''Locations'' are defined as a group of clients and/or further sub-locations. This should help you to<br />
organize larger networks so that computers in a building, an external office, etc., can be managed and<br />
represented in the separate units. <br />
<br />
<!--T:63--><br />
You can configure new locations from a SEP sesam Server or from an existing location (sub-location). SEP sesam sets up a tree-structure for all locations (e.g., USA-Colorado-Boulder-SEP Software) offering greater visibility. For details, see [[Special:MyLanguage/Configuring_Location|Configuring Location]]. <br />
<br />
<!--T:64--><br />
You can also edit the existing location or sub-location settings by double-clicking a relevant location/sub-location to open its ''Properties''. <br />
<br />
<!--T:23--><br />
[[Image:Location_properties_Beefalo.jpg|450px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><br />
<!--T:65--><br />
'''''Location tab'''''<br />
<br />
<!--T:66--><br />
*'''''Name''''': Name of the location</translate><br />
<translate><!--T:67--> *'''''in''''': Superordinated location (relevant for sub-locations)</translate><br />
<translate><br />
<!--T:68--><br />
*'''''Description''''': More exact description of the location</translate><br />
<translate><!--T:69--> *'''''Contact''''': Contact person at this location</translate><br />
<translate><!--T:70--><br />
*'''''Note''''': Additional information<br />
<br />
<!--T:71--><br />
'''''OS Access tab'''''<br />
<br />
<!--T:72--><br />
When configuring a new location, you can enter the credentials that will apply to all clients within a location, instead of specifying it for each client individually. In this case, enter the credentials as an ''administrator'' to access the respective systems. You can edit your credentials in the ''location properties''. You have to use ''DOMAIN\USER'' format for the domain accounts or ''HOST\USER'' for the local accounts.<br />
<br />
<!--T:73--><br />
'''''Permissions tab'''''<br />
<br />
<!--T:74--><br />
Under the ''Permissions'' tab, you can configure permissions (ACLs) for your locations, if you have the ''admin'' rights. For details, see [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]].<br />
<br />
===={{anchor|client_properties}}Client properties==== <!--T:75--> <br />
<br />
<!--T:76--><br />
''Clients'' are the computers in the network (including the SEP sesam Server) that you want to back up and restore. <br />
<br />
<!--T:28--><br />
The following screenshot shows the input fields and functions of the clients.</translate><br />
<br />
{{<translate><!--T:77--> note</translate>|<translate><!--T:78--> The client properties are slightly different if you are configuring a new client or when the client is already added and configured and you edit its properties. The ''Platform'' is only available when configuring a new client, while tabs for specifying additional settings are only available for the already configured client in its properties.</translate>}}<br />
<br />
<translate><br />
<!--T:79--><br />
[[Image:Topology_client_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:80--> '''''Client tab'''''</translate><br />
<br />
<ul><li><translate><!--T:81--> '''''Name''''': Enter the name of the client – this has to be the network host name of the computer. The name has to be resolvable either by DNS or <tt>etc/hosts</tt> file.</translate></li><br />
<br />
<li><translate><!--T:82--> '''''Location''''': Predefined location. A client always has to be assigned to a location.</translate></li><br />
<br />
<li><translate><!--T:123--> '''''Platform''''': Select the relevant platform of the client (''Windows'', ''UNIX'', ''VMS'' or ''NETWARE''). Depending on the platform, tabs for special access parameters are displayed. The ''Platform'' is only available when configuring a new client.</translate></li><br />
<br />
<li><translate><!--T:83--> '''''Operating system''''': Select the operating system version of the computer you are adding as a client.</translate></li><br />
<br />
<li><translate><!--T:84--> '''''Access mode''''': Select the relevant access method for the server-client communication. {{:4 4 3 Beefalo:Access Modes/en}}</translate></li><br />
<li><translate><!--T:86--> '''''VM server type''''': If the client should be managed as a VM server, select the relevant type. This enables, for example, browsing the virtual environment when creating backup tasks.</translate></li><br />
<br />
<li><translate><!--T:87--> '''''Last SEP sesam message''''': The most recent system status message for the existing client.</translate></li><br />
<br />
<li><translate><!--T:88--> '''''Last successful access''''': The last successful access to the existing client.</translate></li><br />
<br />
<li><translate><!--T:89--> '''''Notes''''': Optional comment.</translate></li><br />
<br />
<li><translate><!--T:90--> '''''Interfaces''''':</translate></li> <br />
{{<translate><!--T:91--> Note</translate>|<translate><!--T:92--> Only edit this field if a client is a SEP sesam Server or Remote Device Server (RDS).</translate>}} <br />
<br />
<translate><!--T:93--><br />
If there is an additional network for backups available, the resolvable and changed DNS-name of a second network card of the SEP sesam Server can be entered into a new line. If several network cards are available, they need to be known to the DNS otherwise the connection to SEP sesam Server will fail. <br />
<br />
<!--T:94--><br />
The network protocols for data transfer can be set by using the common prefixes '''ftp://''' (default), '''http://''' or '''https://'''. For each protocol one interface has to be added in the interfaces box separated by single spaces. One interface for the HTTP protocol ''<nowiki>http://<hostname>:11000</nowiki>'' and one interface for the HTTPS protocol ''<nowiki>https://<hostname>:11088</nowiki>''.</translate><br />
<br />
<li><translate><!--T:95--> '''''SEP sesam version''''': This field shows the SBC (SEP sesam backup Client) version of the installation.</translate></li><br />
<br />
<li><translate><!--T:96--> '''''VM host and VM name''''': VM host and name are displayed, if you have specified them during the client creation.</translate></li><br />
<br />
<li><translate><!--T:97--> '''''Additional options'''''</translate></li> <br />
<br />
<translate><!--T:98--> There are two additional client-related options:</translate><br />
<br />
<ul><li><translate><!--T:99--> '''''Client is a virtual machine''''': Selecting this option allows you to edit the ''VM host'' (name of the VM Server) and the ''VM name''. These values are used to identify the backup client as a VM in a virtual environment.</translate></li><br />
<li><translate><!--T:130--> '''''Do not update this client''''' (≥ 4.4.3. ''Beefalo V2''): Checking this option allows you to exclude a particular client from being updated. This setting applies in general for all possible updates.</translate></li><br />
<li><translate><!--T:100--> '''''Execution off''''': If a client needs to be excluded from the backup for technical or other reasons, you can deactivate it by checking this option.</translate></li><br />
<br />
{{<translate><!--T:101--> Note</translate>|<translate><!--T:102--> If this option is set, the client will not be backed up until it is unlocked again even if it is scheduled for backup.</translate>}}<br />
</ul></ul><br />
<br />
<translate><!--T:103--><br />
'''''{{anchor|firewalls}}Options tab'''''<br />
<br />
<!--T:104--><br />
By default, SEP sesam uses random ports that are assigned by the operating system for its data connections. However, if you want to back up a client which is behind a firewall, you must manually define the ports. The available options depend on the client type. <br />
<br />
<!--T:105--><br />
[[image:Client__options_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
*<translate><!--T:106--> '''''Access options''''': The default communication port on the backup client is 11301. If a port other than 11301 is used, it must be configured in the client's <tt>sm.ini</tt> file. In this field, enter the port over which the client is reachable (e.g., <tt>-p 17301</tt>).</translate><br />
<translate><br />
<!--T:107--><br />
*'''''STPD options''''': The STPD options are used to define the backports from the clients to the SEP sesam Server, e.g. 11003-11006. These ports are then used to carry data during backups and restores. For each backup that runs parralel 2 ports of a client are needed.</translate><br />
<translate><br />
<!--T:108--><br />
*'''''Listen port''''': The default STPD-port for Remote Device Servers (incl. SEP sesam Server) is 11001.</translate><br />
*<translate><!--T:109--><br />
'''''Wake on LAN''''': For more information, see [[Special:MyLanguage/WOL_-_wake_on_LAN_of_a_SEP_sesam_client|How To]].<br />
<br />
<!--T:110--><br />
For details, see [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]].<br />
<br />
<!--T:111--><br />
'''''OS Access tab'''''<br />
<br />
<!--T:112--><br />
When configuring a new client, you have to enter the credentials as an administrator to access the respective systems. You can also edit your credentials in the ''client properties''. You have to use <tt>DOMAIN\USER</tt> format for domain accounts or <tt>HOST\USER</tt> for local accounts. <br />
<br />
<!--T:113--><br />
[[image:Client__access_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:114--><br />
'''''Additional tabs''''' <br />
<br />
<!--T:115--><br />
In the client properties two additional tabs are available for specifying additional settings. <br />
<br />
<!--T:116--><br />
Under the '''Permissions''' tab, you can add the relevant permissions (ACLs) for your client. For details, see [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]]. <br />
<br />
<!--T:117--><br />
[[image:Client__permissions_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:118--> If you are configuring clients that must be backed up by special [[Special:MyLanguage/SEP_sesam_Glossary#task_type|task types]], additional settings must be specified. A fifth tab is available for the following task types: ''Micro Focus Open Enterprise Server (formerly Novell OES)'', ''VMware'', ''Citrix XEN'', ''MySQL'', ''PostgreSQL'', ''NetApp'', ''RHV''. For example, for Micro Focus OES or NetWare server backup you have to specify the login data for the eDirectory and select the appropriate [[Special:MyLanguage/SEP_sesam_Glossary#data_mover|data mover]]. For Micro Focus, this is a SEP sesam Micro Focus (formerly Novell) Client which is installed on Linux computer with Micro Focus Storage Management Services (SMS).</translate><br /><br />
<translate><!--T:119--> [[image:Client__VMware_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<translate><!--T:120--><br />
For more information on specific task type, see the respective wiki articles under [[Special:MyLanguage/SEP_sesam_Documentation#extensions|Extensions]].<br />
<br />
<div class="noprint"><noinclude><br />
===See also=== <!--T:121--><br />
[[Special:MyLanguage/Configuring_Location|Configuring Location]] – [[Special:MyLanguage/Configuring_Clients|Configuring Clients]] – [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]] – [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]]<br />
<br />
<!--T:122--><br />
{{Footer/en}}</noinclude></div></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3_Beefalo:Topology&diff=1638364 4 3 Beefalo:Topology2020-08-10T10:42:22Z<p>Fho: </p>
<hr />
<div><translate><br />
<!--T:1--><br />
<div class="noprint"><noinclude><languages/><br />
{{Template:Navigator Beefalo/en|User Manual#components|Components|Clients|Clients}}</div></translate><br/><br />
</noinclude><br />
<noinclude><br />
<translate>===Topology=== <!--T:131--> <br />
<br />
<!--T:7--><br />
</noinclude><br />
Topology represents the SEP sesam backup environment including the hardware, computers, backup devices, etc.<br />
<br />
<!--T:8--><br />
All interconnected computers – [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Clients]] and [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Servers]] – can be logically grouped into locations and sub-locations. You can use ''locations'' to group your clients according to their OS, data type, different geographical location, etc. <br />
<br />
<!--T:9--><br />
The menu item '''Topology''' shows all SEP sesam locations, clients, loaders and drives known to the Master Server as well as the media within the devices. By clicking the symbols they can be expanded into the subordinate structures via a function tree. Each client is assigned to a location and each loader and drive to a client. You can open their ''properties'' by double-clicking the relevant component (location, client or drive).<br />
<br />
<!--T:55--><br />
Such grouping enables large organizations at different locations to be managed and represented as a group with separate, centrally-managed units (using a tree view). Locations can be hierarchically organized - multiple sub-locations can be summarized under one Location. <br />
<br />
<!--T:10--><br />
A '''Master Sesam''' at the highest level presents all currently accessible ''regular'' SEP sesam computers. With a mouse click their individual data can be viewed.<br />
<br />
<!--T:11--><br />
A ''regular'' SEP sesam server shows one node only, namely itself.<br />
<br />
<!--T:12--><br />
[[Image:Topology_overview_Beefalo.jpg|750px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:56--><br />
With v. [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3. ''Beefalo'']], SEP sesam provides additional ''View Mode'' button that enables you to switch between the table view and the tree view with grouped objects.<br />
<br />
<!--T:57--><br />
*'''''Tree view''''': SEP sesam default view shows the status of individual locations grouped together in a hierarchical view.<br />
<br />
<!--T:58--><br />
*'''''Table view''''': A simple flat view that shows the status of individual locations one after another.<br />
<br />
<!--T:60--><br />
To create a new location independent of another location or a sub-location, click '''Topology''', and click the button '''New Location'''. A client is always assigned to and created within a location. For details, see [[Special:MyLanguage/Configuring_Location|Configuring Location]]. <br />
<br />
===={{anchor|client_update}}Updating client(s)==== <!--T:124--><br />
<br />
<!--T:125--><br />
As of v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], the <tt>sm_update_client</tt> command has been extended<!-- with automatic installation of service packs on the SEP sesam Server-->. Now you can check in the SEP sesam GUI if an update for your clients is available, see [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#check|Checking update status]]. If it is, the icon with the orange arrow is shown. For details on GUI icons, [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_Icons_Legend#client_status|Client status icons]]. <br />
<br />
<!--T:126--><br />
It is possible to check if the installed SEP sesam Client is up to date by right-clicking the location/client and selecting the ''Check Update State'' option. Use the ''Check Access State'' option to make sure that you have access to your SEP sesam client(s). Note that the availability of of the update/install options depends on your [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#mode|selected update mode]]. <br />
<br />
<!--T:127--><br />
You can update all clients within the location at once by right-clicking the location and selecting ''Update all clients''. You can also select to update only the clients running on Windows or Linux by using ''Update all Linux/Windows Clients''. This will update all Windows or Linux clients, respectively, within the selected location. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#mass_update|Performing mass update]]. <br />
<br />
<!--T:128--><br />
If you want to update an individual client rather than all clients within the location, right-click it and select ''Update Client''. You may want to exclude a particular client from being updated; in this case, double-click it to open its properties and select ''Do not update this client'' check box. Note that this setting applies in general for all possible updates. <br />
<br />
<!--T:129--><br />
If you have new Windows clients and would like to install either a SEP sesam Client, RDS (with GUI), GUI (with SEP sesam Client), or a SEP sesam Server on the selected client (with or without BSR), you only need to specify a user name and password (OS access) when selecting ''Install SEP sesam''. For the Exchange and Hyper-V clients, the selected package will be installed by providing the credentials used to connect to the host computer. You can also uninstall SEP sesam from the respective client by clicking ''Uninstall SEP sesam''.<br />
<br />
===={{anchor|location_properties}}Location properties==== <!--T:61--> <br />
<br />
<!--T:62--><br />
''Locations'' are defined as a group of clients and/or further sub-locations. This should help you to<br />
organize larger networks so that computers in a building, an external office, etc., can be managed and<br />
represented in the separate units. <br />
<br />
<!--T:63--><br />
You can configure new locations from a SEP sesam Server or from an existing location (sub-location). SEP sesam sets up a tree-structure for all locations (e.g., USA-Colorado-Boulder-SEP Software) offering greater visibility. For details, see [[Special:MyLanguage/Configuring_Location|Configuring Location]]. <br />
<br />
<!--T:64--><br />
You can also edit the existing location or sub-location settings by double-clicking a relevant location/sub-location to open its ''Properties''. <br />
<br />
<!--T:23--><br />
[[Image:Location_properties_Beefalo.jpg|450px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><br />
<!--T:65--><br />
'''''Location tab'''''<br />
<br />
<!--T:66--><br />
*'''''Name''''': Name of the location</translate><br />
<translate><!--T:67--> *'''''in''''': Superordinated location (relevant for sub-locations)</translate><br />
<translate><br />
<!--T:68--><br />
*'''''Description''''': More exact description of the location</translate><br />
<translate><!--T:69--> *'''''Contact''''': Contact person at this location</translate><br />
<translate><!--T:70--><br />
*'''''Note''''': Additional information<br />
<br />
<!--T:71--><br />
'''''OS Access tab'''''<br />
<br />
<!--T:72--><br />
When configuring a new location, you can enter the credentials that will apply to all clients within a location, instead of specifying it for each client individually. In this case, enter the credentials as an ''administrator'' to access the respective systems. You can edit your credentials in the ''location properties''. You have to use ''DOMAIN\USER'' format for the domain accounts or ''HOST\USER'' for the local accounts.<br />
<br />
<!--T:73--><br />
'''''Permissions tab'''''<br />
<br />
<!--T:74--><br />
Under the ''Permissions'' tab, you can configure permissions (ACLs) for your locations, if you have the ''admin'' rights. For details, see [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]].<br />
<br />
===={{anchor|client_properties}}Client properties==== <!--T:75--> <br />
<br />
<!--T:76--><br />
''Clients'' are the computers in the network (including the SEP sesam Server) that you want to back up and restore. <br />
<br />
<!--T:28--><br />
The following screenshot shows the input fields and functions of the clients.</translate><br />
<br />
{{<translate><!--T:77--> note</translate>|<translate><!--T:78--> The client properties are slightly different if you are configuring a new client or when the client is already added and configured and you edit its properties. The ''Platform'' is only available when configuring a new client, while tabs for specifying additional settings are only available for the already configured client in its properties.</translate>}}<br />
<br />
<translate><br />
<!--T:79--><br />
[[Image:Topology_client_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:80--> '''''Client tab'''''</translate><br />
<br />
<ul><li><translate><!--T:81--> '''''Name''''': Enter the name of the client – this has to be the network host name of the computer. The name has to be resolvable either by DNS or <tt>etc/hosts</tt> file.</translate></li><br />
<br />
<li><translate><!--T:82--> '''''Location''''': Predefined location. A client always has to be assigned to a location.</translate></li><br />
<br />
<li><translate><!--T:123--> '''''Platform''''': Select the relevant platform of the client (''Windows'', ''UNIX'', ''VMS'' or ''NETWARE''). Depending on the platform, tabs for special access parameters are displayed. The ''Platform'' is only available when configuring a new client.</translate></li><br />
<br />
<li><translate><!--T:83--> '''''Operating system''''': Select the operating system version of the computer you are adding as a client.</translate></li><br />
<br />
<li><translate><!--T:84--> '''''Access mode''''': Select the relevant access method for the server-client communication. {{:4 4 3 Beefalo:Access Modes/en}}</translate></li><br />
<li><translate><!--T:86--> '''''VM server type''''': If the client should be managed as a VM server, select the relevant type. This enables, for example, browsing the virtual environment when creating backup tasks.</translate></li><br />
<br />
<li><translate><!--T:87--> '''''Last SEP sesam message''''': The most recent system status message for the existing client.</translate></li><br />
<br />
<li><translate><!--T:88--> '''''Last successful access''''': The last successful access to the existing client.</translate></li><br />
<br />
<li><translate><!--T:89--> '''''Notes''''': Optional comment.</translate></li><br />
<br />
<li><translate><!--T:90--> '''''Interfaces''''':</translate></li> <br />
{{<translate><!--T:91--> Note</translate>|<translate><!--T:92--> Only edit this field if a client is a SEP sesam Server or Remote Device Server (RDS).</translate>}} <br />
<br />
<translate><!--T:93--><br />
If there is an additional network for backups available, the resolvable and changed DNS-name of a second network card of the SEP sesam Server can be entered into a new line. If several network cards are available, they need to be known to the DNS otherwise the connection to SEP sesam Server will fail. <br />
<br />
<!--T:94--><br />
The network protocols for data transfer can be set by using the common prefixes '''ftp://''' (default), '''http://''' or '''https://'''. For each protocol one interface has to be added in the interfaces box separated by single spaces. One interface for the HTTP protocol ''<nowiki>http://<hostname>:11000</nowiki>'' and one interface for the HTTPS protocol ''<nowiki>https://<hostname>:11088</nowiki>''.</translate><br />
<br />
<li><translate><!--T:95--> '''''SEP sesam version''''': This field shows the SBC (SEP sesam backup Client) version of the installation.</translate></li><br />
<br />
<li><translate><!--T:96--> '''''VM host and VM name''''': VM host and name are displayed, if you have specified them during the client creation.</translate></li><br />
<br />
<li><translate><!--T:97--> '''''Additional options'''''</translate></li> <br />
<br />
<translate><!--T:98--> There are two additional client-related options:</translate><br />
<br />
<ul><li><translate><!--T:99--> '''''Client is a virtual machine''''': Selecting this option allows you to edit the ''VM host'' (name of the VM Server) and the ''VM name''. These values are used to identify the backup client as a VM in a virtual environment.</translate></li><br />
<li><translate><!--T:130--> '''''Do not update this client''''' (≥ 4.4.3. ''Beefalo V2''): Checking this option allows you to exclude a particular client from being updated. This setting applies in general for all possible updates.</translate></li><br />
<li><translate><!--T:100--> '''''Execution off''''': If a client needs to be excluded from the backup for technical or other reasons, you can deactivate it by checking this option.</translate></li><br />
<br />
{{<translate><!--T:101--> Note</translate>|<translate><!--T:102--> If this option is set, the client will not be backed up until it is unlocked again even if it is scheduled for backup.</translate>}}<br />
</ul></ul><br />
<br />
<translate><!--T:103--><br />
'''''{{anchor|firewalls}}Options tab'''''<br />
<br />
<!--T:104--><br />
By default, SEP sesam uses random ports that are assigned by the operating system for its data connections. However, if you want to back up a client which is behind a firewall, you must manually define the ports. The available options depend on the client type. <br />
<br />
<!--T:105--><br />
[[image:Client__options_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
*<translate><!--T:106--> '''''Access options''''': The default communication port on the backup client is 11301. If a port other than 11301 is used, it must be configured in the client's <tt>sm.ini</tt> file. In this field, enter the port over which the client is reachable (e.g., <tt>-p 17301</tt>).</translate><br />
<translate><br />
<!--T:107--><br />
*'''''STPD options''''': The STPD options are used to define the backports from the clients to the SEP sesam Server, e.g. 11003-11006. These ports are then used to carry data during backups and restores. For each backup that runs parralel 2 ports of a client are needed.</translate><br />
<translate><br />
<!--T:108--><br />
*'''''Listen port''''': The default STPD-port for Remote Device Servers (incl. SEP sesam Server) is 11001.</translate><br />
*<translate><!--T:109--><br />
'''''Wake on LAN''''': For more information, see [[Special:MyLanguage/WOL_-_wake_on_LAN_of_a_SEP_sesam_client|How To]].<br />
<br />
<!--T:110--><br />
For details, see [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]].<br />
<br />
<!--T:111--><br />
'''''OS Access tab'''''<br />
<br />
<!--T:112--><br />
When configuring a new client, you have to enter the credentials as an administrator to access the respective systems. You can also edit your credentials in the ''client properties''. You have to use <tt>DOMAIN\USER</tt> format for domain accounts or <tt>HOST\USER</tt> for local accounts. <br />
<br />
<!--T:113--><br />
[[image:Client__access_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:114--><br />
'''''Additional tabs''''' <br />
<br />
<!--T:115--><br />
In the client properties two additional tabs are available for specifying additional settings. <br />
<br />
<!--T:116--><br />
Under the '''Permissions''' tab, you can add the relevant permissions (ACLs) for your client. For details, see [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]]. <br />
<br />
<!--T:117--><br />
[[image:Client__permissions_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:118--> If you are configuring clients that must be backed up by special [[Special:MyLanguage/SEP_sesam_Glossary#task_type|task types]], additional settings must be specified. A fifth tab is available for the following task types: ''Micro Focus Open Enterprise Server (formerly Novell OES)'', ''VMware'', ''Citrix XEN'', ''MySQL'', ''PostgreSQL'', ''NetApp'', ''RHV''. For example, for Micro Focus OES or NetWare server backup you have to specify the login data for the eDirectory and select the appropriate [[Special:MyLanguage/SEP_sesam_Glossary#data_mover|data mover]]. For Micro Focus, this is a SEP sesam Micro Focus (formerly Novell) Client which is installed on Linux computer with Micro Focus Storage Management Services (SMS).</translate><br /><br />
<translate><!--T:119--> [[image:Client__VMware_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<translate><!--T:120--><br />
For more information on specific task type, see the respective wiki articles under [[Special:MyLanguage/SEP_sesam_Documentation#extensions|Extensions]].<br />
<br />
<div class="noprint"><noinclude><br />
===See also=== <!--T:121--><br />
[[Special:MyLanguage/Configuring_Location|Configuring Location]] – [[Special:MyLanguage/Configuring_Clients|Configuring Clients]] – [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]] – [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]]<br />
<br />
<!--T:122--><br />
{{Footer/en}}</noinclude></div></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=4_4_3_Beefalo:Topology&diff=1638354 4 3 Beefalo:Topology2020-08-10T10:36:42Z<p>Fho: </p>
<hr />
<div><translate><br />
<!--T:1--><br />
<div class="noprint"><noinclude><languages/><br />
{{Template:Navigator Beefalo/en|User Manual#components|Components|Clients|Clients}}</div></translate><br/><br />
<br />
<br />
<translate>===Topology=== <!--T:131--> <br />
<br />
<!--T:7--><br />
</noinclude><br />
Topology represents the SEP sesam backup environment including the hardware, computers, backup devices, etc.<br />
<br />
<!--T:8--><br />
All interconnected computers – [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Clients]] and [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Servers]] – can be logically grouped into locations and sub-locations. You can use ''locations'' to group your clients according to their OS, data type, different geographical location, etc. <br />
<br />
<!--T:9--><br />
The menu item '''Topology''' shows all SEP sesam locations, clients, loaders and drives known to the Master Server as well as the media within the devices. By clicking the symbols they can be expanded into the subordinate structures via a function tree. Each client is assigned to a location and each loader and drive to a client. You can open their ''properties'' by double-clicking the relevant component (location, client or drive).<br />
<br />
<!--T:55--><br />
Such grouping enables large organizations at different locations to be managed and represented as a group with separate, centrally-managed units (using a tree view). Locations can be hierarchically organized - multiple sub-locations can be summarized under one Location. <br />
<br />
<!--T:10--><br />
A '''Master Sesam''' at the highest level presents all currently accessible ''regular'' SEP sesam computers. With a mouse click their individual data can be viewed.<br />
<br />
<!--T:11--><br />
A ''regular'' SEP sesam server shows one node only, namely itself.<br />
<br />
<!--T:12--><br />
[[Image:Topology_overview_Beefalo.jpg|750px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:56--><br />
With v. [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3. ''Beefalo'']], SEP sesam provides additional ''View Mode'' button that enables you to switch between the table view and the tree view with grouped objects.<br />
<br />
<!--T:57--><br />
*'''''Tree view''''': SEP sesam default view shows the status of individual locations grouped together in a hierarchical view.<br />
<br />
<!--T:58--><br />
*'''''Table view''''': A simple flat view that shows the status of individual locations one after another.<br />
<br />
<!--T:60--><br />
To create a new location independent of another location or a sub-location, click '''Topology''', and click the button '''New Location'''. A client is always assigned to and created within a location. For details, see [[Special:MyLanguage/Configuring_Location|Configuring Location]]. <br />
<br />
===={{anchor|client_update}}Updating client(s)==== <!--T:124--><br />
<br />
<!--T:125--><br />
As of v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], the <tt>sm_update_client</tt> command has been extended<!-- with automatic installation of service packs on the SEP sesam Server-->. Now you can check in the SEP sesam GUI if an update for your clients is available, see [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#check|Checking update status]]. If it is, the icon with the orange arrow is shown. For details on GUI icons, [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_Icons_Legend#client_status|Client status icons]]. <br />
<br />
<!--T:126--><br />
It is possible to check if the installed SEP sesam Client is up to date by right-clicking the location/client and selecting the ''Check Update State'' option. Use the ''Check Access State'' option to make sure that you have access to your SEP sesam client(s). Note that the availability of of the update/install options depends on your [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#mode|selected update mode]]. <br />
<br />
<!--T:127--><br />
You can update all clients within the location at once by right-clicking the location and selecting ''Update all clients''. You can also select to update only the clients running on Windows or Linux by using ''Update all Linux/Windows Clients''. This will update all Windows or Linux clients, respectively, within the selected location. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam#mass_update|Performing mass update]]. <br />
<br />
<!--T:128--><br />
If you want to update an individual client rather than all clients within the location, right-click it and select ''Update Client''. You may want to exclude a particular client from being updated; in this case, double-click it to open its properties and select ''Do not update this client'' check box. Note that this setting applies in general for all possible updates. <br />
<br />
<!--T:129--><br />
If you have new Windows clients and would like to install either a SEP sesam Client, RDS (with GUI), GUI (with SEP sesam Client), or a SEP sesam Server on the selected client (with or without BSR), you only need to specify a user name and password (OS access) when selecting ''Install SEP sesam''. For the Exchange and Hyper-V clients, the selected package will be installed by providing the credentials used to connect to the host computer. You can also uninstall SEP sesam from the respective client by clicking ''Uninstall SEP sesam''.<br />
<br />
===={{anchor|location_properties}}Location properties==== <!--T:61--> <br />
<br />
<!--T:62--><br />
''Locations'' are defined as a group of clients and/or further sub-locations. This should help you to<br />
organize larger networks so that computers in a building, an external office, etc., can be managed and<br />
represented in the separate units. <br />
<br />
<!--T:63--><br />
You can configure new locations from a SEP sesam Server or from an existing location (sub-location). SEP sesam sets up a tree-structure for all locations (e.g., USA-Colorado-Boulder-SEP Software) offering greater visibility. For details, see [[Special:MyLanguage/Configuring_Location|Configuring Location]]. <br />
<br />
<!--T:64--><br />
You can also edit the existing location or sub-location settings by double-clicking a relevant location/sub-location to open its ''Properties''. <br />
<br />
<!--T:23--><br />
[[Image:Location_properties_Beefalo.jpg|450px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><br />
<!--T:65--><br />
'''''Location tab'''''<br />
<br />
<!--T:66--><br />
*'''''Name''''': Name of the location</translate><br />
<translate><!--T:67--> *'''''in''''': Superordinated location (relevant for sub-locations)</translate><br />
<translate><br />
<!--T:68--><br />
*'''''Description''''': More exact description of the location</translate><br />
<translate><!--T:69--> *'''''Contact''''': Contact person at this location</translate><br />
<translate><!--T:70--><br />
*'''''Note''''': Additional information<br />
<br />
<!--T:71--><br />
'''''OS Access tab'''''<br />
<br />
<!--T:72--><br />
When configuring a new location, you can enter the credentials that will apply to all clients within a location, instead of specifying it for each client individually. In this case, enter the credentials as an ''administrator'' to access the respective systems. You can edit your credentials in the ''location properties''. You have to use ''DOMAIN\USER'' format for the domain accounts or ''HOST\USER'' for the local accounts.<br />
<br />
<!--T:73--><br />
'''''Permissions tab'''''<br />
<br />
<!--T:74--><br />
Under the ''Permissions'' tab, you can configure permissions (ACLs) for your locations, if you have the ''admin'' rights. For details, see [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]].<br />
<br />
===={{anchor|client_properties}}Client properties==== <!--T:75--> <br />
<br />
<!--T:76--><br />
''Clients'' are the computers in the network (including the SEP sesam Server) that you want to back up and restore. <br />
<br />
<!--T:28--><br />
The following screenshot shows the input fields and functions of the clients.</translate><br />
<br />
{{<translate><!--T:77--> note</translate>|<translate><!--T:78--> The client properties are slightly different if you are configuring a new client or when the client is already added and configured and you edit its properties. The ''Platform'' is only available when configuring a new client, while tabs for specifying additional settings are only available for the already configured client in its properties.</translate>}}<br />
<br />
<translate><br />
<!--T:79--><br />
[[Image:Topology_client_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:80--> '''''Client tab'''''</translate><br />
<br />
<ul><li><translate><!--T:81--> '''''Name''''': Enter the name of the client – this has to be the network host name of the computer. The name has to be resolvable either by DNS or <tt>etc/hosts</tt> file.</translate></li><br />
<br />
<li><translate><!--T:82--> '''''Location''''': Predefined location. A client always has to be assigned to a location.</translate></li><br />
<br />
<li><translate><!--T:123--> '''''Platform''''': Select the relevant platform of the client (''Windows'', ''UNIX'', ''VMS'' or ''NETWARE''). Depending on the platform, tabs for special access parameters are displayed. The ''Platform'' is only available when configuring a new client.</translate></li><br />
<br />
<li><translate><!--T:83--> '''''Operating system''''': Select the operating system version of the computer you are adding as a client.</translate></li><br />
<br />
<li><translate><!--T:84--> '''''Access mode''''': Select the relevant access method for the server-client communication. {{:4 4 3 Beefalo:Access Modes/en}}</translate></li><br />
<li><translate><!--T:86--> '''''VM server type''''': If the client should be managed as a VM server, select the relevant type. This enables, for example, browsing the virtual environment when creating backup tasks.</translate></li><br />
<br />
<li><translate><!--T:87--> '''''Last SEP sesam message''''': The most recent system status message for the existing client.</translate></li><br />
<br />
<li><translate><!--T:88--> '''''Last successful access''''': The last successful access to the existing client.</translate></li><br />
<br />
<li><translate><!--T:89--> '''''Notes''''': Optional comment.</translate></li><br />
<br />
<li><translate><!--T:90--> '''''Interfaces''''':</translate></li> <br />
{{<translate><!--T:91--> Note</translate>|<translate><!--T:92--> Only edit this field if a client is a SEP sesam Server or Remote Device Server (RDS).</translate>}} <br />
<br />
<translate><!--T:93--><br />
If there is an additional network for backups available, the resolvable and changed DNS-name of a second network card of the SEP sesam Server can be entered into a new line. If several network cards are available, they need to be known to the DNS otherwise the connection to SEP sesam Server will fail. <br />
<br />
<!--T:94--><br />
The network protocols for data transfer can be set by using the common prefixes '''ftp://''' (default), '''http://''' or '''https://'''. For each protocol one interface has to be added in the interfaces box separated by single spaces. One interface for the HTTP protocol ''<nowiki>http://<hostname>:11000</nowiki>'' and one interface for the HTTPS protocol ''<nowiki>https://<hostname>:11088</nowiki>''.</translate><br />
<br />
<li><translate><!--T:95--> '''''SEP sesam version''''': This field shows the SBC (SEP sesam backup Client) version of the installation.</translate></li><br />
<br />
<li><translate><!--T:96--> '''''VM host and VM name''''': VM host and name are displayed, if you have specified them during the client creation.</translate></li><br />
<br />
<li><translate><!--T:97--> '''''Additional options'''''</translate></li> <br />
<br />
<translate><!--T:98--> There are two additional client-related options:</translate><br />
<br />
<ul><li><translate><!--T:99--> '''''Client is a virtual machine''''': Selecting this option allows you to edit the ''VM host'' (name of the VM Server) and the ''VM name''. These values are used to identify the backup client as a VM in a virtual environment.</translate></li><br />
<li><translate><!--T:130--> '''''Do not update this client''''' (≥ 4.4.3. ''Beefalo V2''): Checking this option allows you to exclude a particular client from being updated. This setting applies in general for all possible updates.</translate></li><br />
<li><translate><!--T:100--> '''''Execution off''''': If a client needs to be excluded from the backup for technical or other reasons, you can deactivate it by checking this option.</translate></li><br />
<br />
{{<translate><!--T:101--> Note</translate>|<translate><!--T:102--> If this option is set, the client will not be backed up until it is unlocked again even if it is scheduled for backup.</translate>}}<br />
</ul></ul><br />
<br />
<translate><!--T:103--><br />
'''''{{anchor|firewalls}}Options tab'''''<br />
<br />
<!--T:104--><br />
By default, SEP sesam uses random ports that are assigned by the operating system for its data connections. However, if you want to back up a client which is behind a firewall, you must manually define the ports. The available options depend on the client type. <br />
<br />
<!--T:105--><br />
[[image:Client__options_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
*<translate><!--T:106--> '''''Access options''''': The default communication port on the backup client is 11301. If a port other than 11301 is used, it must be configured in the client's <tt>sm.ini</tt> file. In this field, enter the port over which the client is reachable (e.g., <tt>-p 17301</tt>).</translate><br />
<translate><br />
<!--T:107--><br />
*'''''STPD options''''': The STPD options are used to define the backports from the clients to the SEP sesam Server, e.g. 11003-11006. These ports are then used to carry data during backups and restores. For each backup that runs parralel 2 ports of a client are needed.</translate><br />
<translate><br />
<!--T:108--><br />
*'''''Listen port''''': The default STPD-port for Remote Device Servers (incl. SEP sesam Server) is 11001.</translate><br />
*<translate><!--T:109--><br />
'''''Wake on LAN''''': For more information, see [[Special:MyLanguage/WOL_-_wake_on_LAN_of_a_SEP_sesam_client|How To]].<br />
<br />
<!--T:110--><br />
For details, see [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]].<br />
<br />
<!--T:111--><br />
'''''OS Access tab'''''<br />
<br />
<!--T:112--><br />
When configuring a new client, you have to enter the credentials as an administrator to access the respective systems. You can also edit your credentials in the ''client properties''. You have to use <tt>DOMAIN\USER</tt> format for domain accounts or <tt>HOST\USER</tt> for local accounts. <br />
<br />
<!--T:113--><br />
[[image:Client__access_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:114--><br />
'''''Additional tabs''''' <br />
<br />
<!--T:115--><br />
In the client properties two additional tabs are available for specifying additional settings. <br />
<br />
<!--T:116--><br />
Under the '''Permissions''' tab, you can add the relevant permissions (ACLs) for your client. For details, see [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]]. <br />
<br />
<!--T:117--><br />
[[image:Client__permissions_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<br />
<translate><!--T:118--> If you are configuring clients that must be backed up by special [[Special:MyLanguage/SEP_sesam_Glossary#task_type|task types]], additional settings must be specified. A fifth tab is available for the following task types: ''Micro Focus Open Enterprise Server (formerly Novell OES)'', ''VMware'', ''Citrix XEN'', ''MySQL'', ''PostgreSQL'', ''NetApp'', ''RHV''. For example, for Micro Focus OES or NetWare server backup you have to specify the login data for the eDirectory and select the appropriate [[Special:MyLanguage/SEP_sesam_Glossary#data_mover|data mover]]. For Micro Focus, this is a SEP sesam Micro Focus (formerly Novell) Client which is installed on Linux computer with Micro Focus Storage Management Services (SMS).</translate><br /><br />
<translate><!--T:119--> [[image:Client__VMware_Beefalo.jpg|650px|link=]]</translate><br />
<br clear=all><br />
<translate><!--T:120--><br />
For more information on specific task type, see the respective wiki articles under [[Special:MyLanguage/SEP_sesam_Documentation#extensions|Extensions]].<br />
<br />
<div class="noprint"><noinclude><br />
===See also=== <!--T:121--><br />
[[Special:MyLanguage/Configuring_Location|Configuring Location]] – [[Special:MyLanguage/Configuring_Clients|Configuring Clients]] – [[Special:MyLanguage/4_4_3_Beefalo:Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/4_4_3_Grolar:Using_Access_Control_Lists|Using Access Control Lists]] – [[Special:MyLanguage/4_4_3_Tigon:List_of_Ports_Used_by_SEP_sesam|List of Ports Used by SEP sesam]]<br />
<br />
<!--T:122--><br />
{{Footer/en}}</noinclude></div></translate></div>Fhohttps://wiki.sep.de/wiki/index.php?title=User:Fho&diff=163722User:Fho2020-08-10T09:29:10Z<p>Fho: Created page with "{{:4_4_3_Beefalo:Topology/en}}"</p>
<hr />
<div>{{:4_4_3_Beefalo:Topology/en}}</div>Fhohttps://wiki.sep.de/wiki/index.php?title=Imprint&diff=161666Imprint2020-07-31T13:45:59Z<p>Fho: </p>
<hr />
<div><noinclude><div class="noprint"><languages /></div><br />
<translate><!--T:1--><br />
'''Legal Notices'''<br />
<br />
<!--T:2--><br />
Copyright &copy; SEP AG 1999-2018. All rights reserved.</noinclude><br />
<br />
<!--T:3--><br />
Any form of reproduction, duplication or distribution of the contents, in part or in whole, 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, the information in SEP sesam user documentation is subject to change without notice due to continuous product development. SEP AG cannot guarantee the accuracy of the explanation and shall not be liable for the use of provided information and the product implementation.<br />
<br />
<!--T:4--><br />
SEP sesam and SEP-related modules are trademarks of SEP AG. All other trademarks used at this site are the property of their respective owners.<noinclude></translate></noinclude><br />
<noinclude><br />
<hr><br />
'''<translate><!--T:5--><br />
Contact</translate>'''<br />
{|<br />
! style="text-align:left;width:200px;"| ''<translate><!--T:6--><br />
Germany</translate>''<br />
! style="text-align:left;width:200px;"| ''<translate><!--T:7--><br />
USA</translate>''<br />
|-<br />
|'''SEP AG'''<br />
|'''SEP Software Corp.'''<br />
|-<br />
|Konrad-Zuse-Straße 5<br />
|1630 30th Street Suite A, #265<br />
|-<br />
|D-83607 Holzkirchen<br />
|Boulder CO, 80301<br />
|-<br />
|Tel +49 8024 46331-0<br />
|Tel +1.303.449.0100<br />
|-<br />
|Fax +49 8024 46331-666<br />
|-<br />
|E-mail: info@sep.de<br />
|Email: info@sepusa.com<br />
|}<translate><!--T:8--><br />
</noinclude><noinclude></translate></noinclude></div>Fhohttps://wiki.sep.de/wiki/index.php?title=SBA_Book&diff=161665SBA Book2020-07-31T13:43:40Z<p>Fho: Created page with "=Part I: Introduction= ==Imprint== {{4_4_3:Imprint }} =Part II: Architecture Overview= ==SEP sesam Requirements== {{:SEP_sesam_Requirements }} ==Licensing== {{:4_4_3:SEP_s..."</p>
<hr />
<div>=Part I: Introduction=<br />
<br />
==Imprint==<br />
{{4_4_3:Imprint }}<br />
<br />
=Part II: Architecture Overview=<br />
<br />
==SEP sesam Requirements==<br />
{{:SEP_sesam_Requirements }}<br />
<br />
==Licensing==<br />
{{:4_4_3:SEP_sesam_License_Comparison}}<br />
<br />
=Part III: SEP sesam GUI=<br />
<br />
==SEP sesam Graphical User Interface (GUI)==<br />
{{:4_4_3_Beefalo:SEP_sesam_Graphical_User_Interface_(GUI)}}<br />
<br />
==Customizing GUI==<br />
{{:Customizing_GUI}}<br />
<br />
<br />
=GUI: Components=<br />
<br />
==Topology==<br />
{{:4_4_3_Beefalo:Topology}}<br />
<br />
==Clients==<br />
{{:4_4_3_Beefalo:Clients}}<br />
<br />
==Data Store==<br />
{{:4_4_3_Beefalo:Data_Store}}<br />
==Loaders==<br />
{{:4_4_3_Beefalo:Loaders}}</div>Fhohttps://wiki.sep.de/wiki/index.php?title=Archive:Disaster_Recovery_for_Linux_3.0&diff=154046Archive:Disaster Recovery for Linux 3.02020-03-12T17:48:09Z<p>Fho: /* RHEL7 */</p>
<hr />
<div>{{Copyright SEP AG en}}<br />
<br />
<br />
== Introduction ==<br />
This document includes information about SEP Sesam BSR Linux with REAR integration. Relax-and-Recover (REAR) (http://relax-and-recover.org/) is a setup-and-forget Linux bare metal disaster recovery solution based on GPL licence. This solution has been integrated into a SEP sesam backup client installation.<br />
<br />
=== Requirements ===<br />
* SEP Sesam Client >= 4.2.2 <br />
* SEP Sesam Server >= 4.2.2. Check [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] or [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]].<br />
* Enough free space in '''/tmp/''', '''/boot/''' and '''/var/opt/sesam/''' to keep the temporary ISO image (ca. 100 MB, depending on the system)!<br />
<br />
=== Supported distributions ===<br />
<br />
See the following list in our support matrix:<br />
<br />
[[SEP_sesam_OS_and_Database_Support_Matrix#SEP_sesam_Bare_Metal_Recovery_Linux|SEP REAR Support Matrix]]<br />
<br />
==== Package requirements ====<br />
There are some requirements which packages have to be installed, that a ReaR-based backup can be performed successfully.<br />
<br />
* RHEL 6<br />
** <tt>syslinux</tt><br />
<br />
=== Limitations ===<br />
* Backup of Sesam Server and Sesam RDS is currently not supported<br />
* Backup of Systems running on Citrix XEN Virtual Machines is currently not supported<br />
* Backup of Systems using UEFI is currently not supported<br />
<br />
==== Dissimilar Hardware ====<br />
<br />
In case you want to provide dissimilar hardware scenarios in your environment, please make sure to test this behavior beforehand. As SEP Sesam for REAR is generally able to restore to dissimiliar hardware there can always be certain limitations. As SEP cannot guarantee the dissimiliar hardware restore to work on every platform we do not give general support for it. In case you want to restore to dissimilar hardware, please test the restore szenario carefully to see if there are any limitations.<br />
<br />
==== (Multipath-)SAN Volumes / SAP HANA ====<br />
<br />
By default no layout of (Multipath-)SAN volumes is saved, this means that during recovery there will be no way to recover partitions of this kind. If you are in need to backup in a multipath san setup, or SAP HANA installations, please get in touch with support@sep.de<br />
<br />
== Backup ==<br />
The SEP Sesam Disaster Recovery allways includes a special '''Linux BSR''' backup task and a complete file system backup of the clients. This documentation explains what is happening during the backup and how the backup tasks should be configured.<br />
<br />
=== Functionality ===<br />
<br />
<!-- [[File:rear2.jpg]] --><br />
[[File:BSR-Linux3-Funtionality.jpg|link=]]<br />
<br />
<br />
During backup the following steps are performed:<br />
<br />
# The backup task creates a bootable CDROM or DVD image from the running system, including the SEP Sesam client<br />
# The backup task creates a boot option in the systems bootloader which can be booted in case that the original boot config fails<br />
# The created iso image is transferred to the backup server and backed up by a regular file backup<br />
# A regular file backup is performed with a second task<br />
<br />
=== Creating the backup tasks ===<br />
<br />
==== Disaster Recovery Task ====<br />
First step is to create a backup task for the Linux BSR console, this happens by choosing the Linux BSR backup option while browsing the client. This backup task will create the bootable CD / DVD image and the appropriate new bootloader entries on the client. This backup task should always be performed before the regular file backup.<br />
<br />
<br />
[[File:rear_backup_1.jpg|link=]]<br />
<br />
<br />
[[File:rear_backup_2.jpg|link=]]<br />
<br />
==== Special task options ====<br />
<br />
The following special options can be passed to the backup job "additional save options":<br />
<br />
-a nodelete : do not delete generated iso image after backup <br />
-a raw : Do backup file in plain ISO Image format. This allows to burn image to bootable media directly from the backup file in the DataStore<br />
-v 3 : create REAR Logfile with debugging output (stored in: /var/opt/sesam/var/lib/rear/var/log/rear/)<br />
<br />
==== Filesystem backup ====<br />
The second backup task is needed to recover a system completely is a full backup of the clients filesystem ([[Special:MyLanguage/SEP_sesam_Glossary#task_type|Task type]]: ''Path Backup''; Source: ''all''):<br />
<br />
<br />
[[File:rear_backup_3.jpg|link=]]<br />
<br />
<br />
==== Creating the bootable restore disk image ====<br />
After the Disaster Recovery Task has completed, a restore of it has to be performed to gain the bootable .iso file containing the recovery environment. Therefor, a restore of the BSR task (rear-test_BSR in the pictured example) is done using the standard options.<br />
<br />
When the restore task has completed successfully, the iso file stored in '''/var/opt/sesam/var/lib/rear/var/lib/rear/output/rear-[hostname].iso''' on the client can now be used to create a bootable media for the restore.<br />
<br />
== Restore ==<br />
<br />
=== Functionality ===<br />
<br />
<!--[[File:rear_restore.jpg]]--><br />
[[File:BSR-Linux3-Recovery.jpg|link=]]<br />
<br />
<br />
During recovery the following steps are performed:<br />
<br />
# Restore the ISO image to a different Linux machine, mount it to the recovery host or create a CDROM and use it as boot medium<br />
# The administrator boots the recovery console either via the created CDROM Image (2.1) or - if possible - via the systems bootloader (2.2)<br />
# The administrator recovers the systems partitions and filesystem configuration via the recovery console<br />
# A restore of the complete filesystem backup of the client is performed to the newly created partition<br />
<br />
After the steps have been performed successfully the system is rebooted<br />
<br />
=== Performing a restore ===<br />
<br />
==== Restoring the CDROM Image to a filesystem ====<br />
In case the system is not bootable via the recovery console anymore (in case of a complete filesystem crash) the system must be booted via the recovery console CDROM. The first step is restoring the created ISO image to a random system and burning it to a media of your choice.<br />
<br />
==== Booting the System from external media like USB/CDROM (or on-disk recovery console) ====<br />
<br />
===== Bootmenu =====<br />
After the media has been inserted the following boot menu will appear:<br />
<br />
<br />
[[File:rear_restore_1.jpg|link=]]<br />
<br />
<br />
===== Networking =====<br />
<br />
During bootup the system will provide you with a selection of network interfaces. Choose the right network interface which is needed to ensure connectivity with your backup server. The IP configuration of the original system will be used:<br />
<br />
<br />
[[File:rear_restore_2.jpg|link=]]<br />
<br />
<br />
===== Login to the disaster recovery console =====<br />
After the system has finished booting you can login to the disaster recovery console with the username "root" and no password. The disaster recovery console is also reachable via SSH, in case you have to login remotely. The recovery process can be started with the command "rear recover" just as shown in this screenshot:<br />
<br />
<br />
[[File:rear_restore_3.jpg|link=]]<br />
<br />
<br />
===== Restoring disk information =====<br />
The disk restore wizard will suggest a local disk to be partitioned, select the appropriate disk to be used:<br />
<br />
<br />
[[File:rear_restore_4.jpg|link=]]<br />
<br />
<br />
Confirm the disk layout configuration:<br />
<br />
<br />
[[File:rear_restore_5.jpg|link=]]<br />
<br />
<br />
Start the recovery and let the recovery console create the filesystems and partitions:<br />
<br />
<br />
[[File:rear_restore_6.jpg|link=]]<br />
<br />
<br />
[[File:rear_restore_7.jpg|link=]]<br />
<br />
<br />
After the recovery check wether if all filesystem have been created, in the screenshot above you can see that there is an newly created mountpoint "/mnt/local". This will be the restore target for the next step: restoring the filesystem data.<br />
<br />
<br />
[[File:rear_restore_8.jpg|link=]]<br />
<br />
<br />
==== Restoring the filesystem backup ====<br />
After the partitions and filesystems have been created the next step is to restore the files of the system to the recovery console.<br />
<br />
<br />
[[File:rear_restore2_1.jpg|link=]]<br />
<br />
<br />
[[File:rear_restore2_2.jpg|link=]]<br />
<br />
<br />
{{Box Attention| Restore target must be set to /mnt/local/|<br />
The restore target must be changed from the default value "all" to the new target "/mnt/local/" on the recovery console<br />
}}<br />
<br />
<br />
[[File:rear_restore2_3.jpg|link=]]<br />
<br />
<br />
After the filesystem backup has been restored exit the disaster recovery console with the command "exit" and reboot the system.<br />
<br />
==== Remote login via SSH ====<br />
<br />
The recovery process can also be initiated remotely, means that the booted system image is reachable via SSH. Username for login is 'root' and the password is either empty or 'recover'. With version >= 4.4.3 the password can be configured via special backup option:<br />
<br />
-a SSH_ROOT_PASSWORD=<password><br />
<br />
in the backup task options.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Known Issues ===<br />
<br />
==== Error Executing REAR ====<br />
;Problem<br />
SEP sesam Client package was successfully installed and path backups are working. If you have problems executing a rear backup check the backup log if there are some missing dependencies.<br />
<pre><br />
There are binaries or libraries in the ReaR recovery system that need additional libraries<br />
/opt/sesam/bin/sesam/libvirtmod.so requires additional libraries (fatal error)<br />
libvirt.so.0 => not found<br />
</pre><br />
=> In this case the package ''libvirt-client'' is missing. <br />
* On RHEL/CentOS 7 install it with the following command: <tt>yum install libvirt-client</tt><br />
* On SLES 12/15 install it with the following command: <tt>zypper install libvirt-client</tt><br />
<br />
==== Error The workflow mkrescue is not supported in the ReaR rescue/recovery system ====<br />
<br />
Delete the file /etc/rear-release<br />
<br />
==== REAR image hangs during bootup ====<br />
<br />
In case the system hangs during bootup like shown in the following image:<br />
<br />
[[File: rear-hang.jpg|link=]]<br />
<br />
try booting the system with the ACPI=OFF option (this option can be specified on the command line in the boot menu prompt, after the options BACKUP=SESAM OUTPUT=ISO)<br />
<br />
==== RHEL6/CENTOS6 ====<br />
<br />
===== Client won't start in recovery image =====<br />
<br />
The Sesam client will not automatically start on RHEL6 based Recovery images as the file "/etc/init.d/functions" is missing within the recovery image. The client can be started manually via:<br />
<br />
/opt/sesam/bin/sesam/sm_main start<br />
<br />
===== Recovered system wont boot because of missing "libblkid.so.1" =====<br />
<br />
If the recovered system won't boot, this is most probably caused by SELinux which is activated by default. <br />
Especially on RedHat Enterprise Linux 6 or CentOS 6 systems, follow these steps after rebooting from the REAR recover:<br />
<br />
* Press a key when prompted by the boot loader (GRUB):<br />
[[File: rhelcentos_grub1.jpg|link=]]<br />
<br />
<br />
* Select the appropriate boot loader entry:<br />
[[File: rhelcentos_grub2.jpg|link=]]<br />
<br />
<br />
* Press 'e' to edit the commands for the selected entry:<br />
[[File: rhelcentos_grub3.jpg|link=]]<br />
<br />
<br />
* Add 'selinux=0' to the commands:<br />
[[File: rhelcentos_grub4.jpg|link=]]<br />
<br />
<br />
* Press 'Enter' to confirm the changes and 'b' to boot up the machine with SELinux disabled.<br />
<br />
When having access to the system, change the option SELINUX of ''/etc/selinux/config'' to the following:<br />
SELINUX=permissive<br />
<br />
Afterwards, reboot the system and feel free to set the SELINUX value back to 'enforcing' if needed.<br />
<br />
<br />
==== RHEL7 ====<br />
<br />
===== backup fails with ERROR: The LSB package is not installed =====<br />
<br />
If the backup fails with:<br />
<br />
ERROR: The LSB package is not installed.<br />
<br />
Please install the lsb package:<br />
<br />
yum install redhat-lsb-core mkisofs syslinux<br />
<br />
===== backup fails with: ERROR: Cannot find required programs: mingetty =====<br />
<br />
See the following documentation:<br />
<br />
https://github.com/rear/rear/issues/348<br />
<br />
Please edit:<br />
<br />
/var/opt/sesam/var/lib/rear/usr/share/rear/conf/default.conf<br />
<br />
in and in the line:<br />
<br />
# required programs. Same as above, but if they are missing, we abort.<br />
REQUIRED_PROGS=(<br />
"$SCRIPT_FILE"<br />
<br />
remove the line:<br />
<br />
mingetty<br />
<br />
and try the backup again.<br />
<br />
=====UEFI=====<br />
In order to be able to create an UEFI/EFI bootable iso image the additional tool "ebiso" has to be installed on the client system.<br />
<br />
======rear error occurred during grub2-mkimage of bootx64.efi======<br />
<br />
Please install the ''grub2-efi-x64-modules'' package to fix this<br />
<br />
==== Debian9 ====<br />
===== Client won't start in recovery image =====<br />
<br />
The Sesam client will not automatically start on Debian9 based Recovery images. The client can be started manually via:<br />
<br />
/opt/sesam/bin/sesam/sm_main start<br />
<br />
==== SLES ====<br />
===== SM_SSH not working on SLES11 recovery image=====<br />
<br />
execute <br />
mount -t tmpfs none /dev/shm/ -o rw,nosuid,nodev,noexec<br />
before starting the recovery process<br />
<br />
===== UEFI =====<br />
<br />
====== Install EBISO for creating UEFI aware ISO images ======<br />
<br />
In order to be able to create an UEFI/EFI bootable iso image the additional tool "ebiso" has to be installed on the client system. This Package is not part of a regular SLES12/SLES15 installation and can be downloaded at the following URL:<br />
<br />
http://download.opensuse.org/repositories/Archiving:/Backup:/Rear/SLE_12/x86_64/<br />
<br />
or:<br />
<br />
http://download.sep.de/utils/bsr-linux/<br />
<br />
For other Linux distributions please contact support@sep.de<br />
<br />
Installation via:<br />
<br />
rpm -i ebiso-<version>.rpm<br />
<br />
====== Additional configuration ======<br />
<br />
<br />
In some cases the generated ISO Image mount will be too small for storing all needed information and has to be adjusted, this is will be fixed in future REAR verisons (1.19):<br />
<br />
'''/var/opt/sesam/var/lib/rear/usr/share/rear/lib/uefi-functions.sh''' (line64):<br />
<br />
change:<br />
<br />
(shim.efi|elilo.efi) size=128000 ;;<br />
<br />
to:<br />
<br />
(shim.efi|elilo.efi) size=228000 ;;<br />
<br />
===== restore: client is unreachable =====<br />
<br />
after booting the rescue image the client is not reachable, please start the client manually using the following command on the rescue command line:<br />
<br />
sh /etc/scripts/system-setup.d/59-start-sesam-client.sh<br />
<br />
== Further documentation ==<br />
* For further information about ''Relax and Recover'' [http://relax-and-recover.org/ see here]</div>Fhohttps://wiki.sep.de/wiki/index.php?title=Archive:Disaster_Recovery_for_Linux_3.0&diff=154045Archive:Disaster Recovery for Linux 3.02020-03-12T17:44:27Z<p>Fho: /* RHEL7 */</p>
<hr />
<div>{{Copyright SEP AG en}}<br />
<br />
<br />
== Introduction ==<br />
This document includes information about SEP Sesam BSR Linux with REAR integration. Relax-and-Recover (REAR) (http://relax-and-recover.org/) is a setup-and-forget Linux bare metal disaster recovery solution based on GPL licence. This solution has been integrated into a SEP sesam backup client installation.<br />
<br />
=== Requirements ===<br />
* SEP Sesam Client >= 4.2.2 <br />
* SEP Sesam Server >= 4.2.2. Check [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] or [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]].<br />
* Enough free space in '''/tmp/''', '''/boot/''' and '''/var/opt/sesam/''' to keep the temporary ISO image (ca. 100 MB, depending on the system)!<br />
<br />
=== Supported distributions ===<br />
<br />
See the following list in our support matrix:<br />
<br />
[[SEP_sesam_OS_and_Database_Support_Matrix#SEP_sesam_Bare_Metal_Recovery_Linux|SEP REAR Support Matrix]]<br />
<br />
==== Package requirements ====<br />
There are some requirements which packages have to be installed, that a ReaR-based backup can be performed successfully.<br />
<br />
* RHEL 6<br />
** <tt>syslinux</tt><br />
<br />
=== Limitations ===<br />
* Backup of Sesam Server and Sesam RDS is currently not supported<br />
* Backup of Systems running on Citrix XEN Virtual Machines is currently not supported<br />
* Backup of Systems using UEFI is currently not supported<br />
<br />
==== Dissimilar Hardware ====<br />
<br />
In case you want to provide dissimilar hardware scenarios in your environment, please make sure to test this behavior beforehand. As SEP Sesam for REAR is generally able to restore to dissimiliar hardware there can always be certain limitations. As SEP cannot guarantee the dissimiliar hardware restore to work on every platform we do not give general support for it. In case you want to restore to dissimilar hardware, please test the restore szenario carefully to see if there are any limitations.<br />
<br />
==== (Multipath-)SAN Volumes / SAP HANA ====<br />
<br />
By default no layout of (Multipath-)SAN volumes is saved, this means that during recovery there will be no way to recover partitions of this kind. If you are in need to backup in a multipath san setup, or SAP HANA installations, please get in touch with support@sep.de<br />
<br />
== Backup ==<br />
The SEP Sesam Disaster Recovery allways includes a special '''Linux BSR''' backup task and a complete file system backup of the clients. This documentation explains what is happening during the backup and how the backup tasks should be configured.<br />
<br />
=== Functionality ===<br />
<br />
<!-- [[File:rear2.jpg]] --><br />
[[File:BSR-Linux3-Funtionality.jpg|link=]]<br />
<br />
<br />
During backup the following steps are performed:<br />
<br />
# The backup task creates a bootable CDROM or DVD image from the running system, including the SEP Sesam client<br />
# The backup task creates a boot option in the systems bootloader which can be booted in case that the original boot config fails<br />
# The created iso image is transferred to the backup server and backed up by a regular file backup<br />
# A regular file backup is performed with a second task<br />
<br />
=== Creating the backup tasks ===<br />
<br />
==== Disaster Recovery Task ====<br />
First step is to create a backup task for the Linux BSR console, this happens by choosing the Linux BSR backup option while browsing the client. This backup task will create the bootable CD / DVD image and the appropriate new bootloader entries on the client. This backup task should always be performed before the regular file backup.<br />
<br />
<br />
[[File:rear_backup_1.jpg|link=]]<br />
<br />
<br />
[[File:rear_backup_2.jpg|link=]]<br />
<br />
==== Special task options ====<br />
<br />
The following special options can be passed to the backup job "additional save options":<br />
<br />
-a nodelete : do not delete generated iso image after backup <br />
-a raw : Do backup file in plain ISO Image format. This allows to burn image to bootable media directly from the backup file in the DataStore<br />
-v 3 : create REAR Logfile with debugging output (stored in: /var/opt/sesam/var/lib/rear/var/log/rear/)<br />
<br />
==== Filesystem backup ====<br />
The second backup task is needed to recover a system completely is a full backup of the clients filesystem ([[Special:MyLanguage/SEP_sesam_Glossary#task_type|Task type]]: ''Path Backup''; Source: ''all''):<br />
<br />
<br />
[[File:rear_backup_3.jpg|link=]]<br />
<br />
<br />
==== Creating the bootable restore disk image ====<br />
After the Disaster Recovery Task has completed, a restore of it has to be performed to gain the bootable .iso file containing the recovery environment. Therefor, a restore of the BSR task (rear-test_BSR in the pictured example) is done using the standard options.<br />
<br />
When the restore task has completed successfully, the iso file stored in '''/var/opt/sesam/var/lib/rear/var/lib/rear/output/rear-[hostname].iso''' on the client can now be used to create a bootable media for the restore.<br />
<br />
== Restore ==<br />
<br />
=== Functionality ===<br />
<br />
<!--[[File:rear_restore.jpg]]--><br />
[[File:BSR-Linux3-Recovery.jpg|link=]]<br />
<br />
<br />
During recovery the following steps are performed:<br />
<br />
# Restore the ISO image to a different Linux machine, mount it to the recovery host or create a CDROM and use it as boot medium<br />
# The administrator boots the recovery console either via the created CDROM Image (2.1) or - if possible - via the systems bootloader (2.2)<br />
# The administrator recovers the systems partitions and filesystem configuration via the recovery console<br />
# A restore of the complete filesystem backup of the client is performed to the newly created partition<br />
<br />
After the steps have been performed successfully the system is rebooted<br />
<br />
=== Performing a restore ===<br />
<br />
==== Restoring the CDROM Image to a filesystem ====<br />
In case the system is not bootable via the recovery console anymore (in case of a complete filesystem crash) the system must be booted via the recovery console CDROM. The first step is restoring the created ISO image to a random system and burning it to a media of your choice.<br />
<br />
==== Booting the System from external media like USB/CDROM (or on-disk recovery console) ====<br />
<br />
===== Bootmenu =====<br />
After the media has been inserted the following boot menu will appear:<br />
<br />
<br />
[[File:rear_restore_1.jpg|link=]]<br />
<br />
<br />
===== Networking =====<br />
<br />
During bootup the system will provide you with a selection of network interfaces. Choose the right network interface which is needed to ensure connectivity with your backup server. The IP configuration of the original system will be used:<br />
<br />
<br />
[[File:rear_restore_2.jpg|link=]]<br />
<br />
<br />
===== Login to the disaster recovery console =====<br />
After the system has finished booting you can login to the disaster recovery console with the username "root" and no password. The disaster recovery console is also reachable via SSH, in case you have to login remotely. The recovery process can be started with the command "rear recover" just as shown in this screenshot:<br />
<br />
<br />
[[File:rear_restore_3.jpg|link=]]<br />
<br />
<br />
===== Restoring disk information =====<br />
The disk restore wizard will suggest a local disk to be partitioned, select the appropriate disk to be used:<br />
<br />
<br />
[[File:rear_restore_4.jpg|link=]]<br />
<br />
<br />
Confirm the disk layout configuration:<br />
<br />
<br />
[[File:rear_restore_5.jpg|link=]]<br />
<br />
<br />
Start the recovery and let the recovery console create the filesystems and partitions:<br />
<br />
<br />
[[File:rear_restore_6.jpg|link=]]<br />
<br />
<br />
[[File:rear_restore_7.jpg|link=]]<br />
<br />
<br />
After the recovery check wether if all filesystem have been created, in the screenshot above you can see that there is an newly created mountpoint "/mnt/local". This will be the restore target for the next step: restoring the filesystem data.<br />
<br />
<br />
[[File:rear_restore_8.jpg|link=]]<br />
<br />
<br />
==== Restoring the filesystem backup ====<br />
After the partitions and filesystems have been created the next step is to restore the files of the system to the recovery console.<br />
<br />
<br />
[[File:rear_restore2_1.jpg|link=]]<br />
<br />
<br />
[[File:rear_restore2_2.jpg|link=]]<br />
<br />
<br />
{{Box Attention| Restore target must be set to /mnt/local/|<br />
The restore target must be changed from the default value "all" to the new target "/mnt/local/" on the recovery console<br />
}}<br />
<br />
<br />
[[File:rear_restore2_3.jpg|link=]]<br />
<br />
<br />
After the filesystem backup has been restored exit the disaster recovery console with the command "exit" and reboot the system.<br />
<br />
==== Remote login via SSH ====<br />
<br />
The recovery process can also be initiated remotely, means that the booted system image is reachable via SSH. Username for login is 'root' and the password is either empty or 'recover'. With version >= 4.4.3 the password can be configured via special backup option:<br />
<br />
-a SSH_ROOT_PASSWORD=<password><br />
<br />
in the backup task options.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Known Issues ===<br />
<br />
==== Error Executing REAR ====<br />
;Problem<br />
SEP sesam Client package was successfully installed and path backups are working. If you have problems executing a rear backup check the backup log if there are some missing dependencies.<br />
<pre><br />
There are binaries or libraries in the ReaR recovery system that need additional libraries<br />
/opt/sesam/bin/sesam/libvirtmod.so requires additional libraries (fatal error)<br />
libvirt.so.0 => not found<br />
</pre><br />
=> In this case the package ''libvirt-client'' is missing. <br />
* On RHEL/CentOS 7 install it with the following command: <tt>yum install libvirt-client</tt><br />
* On SLES 12/15 install it with the following command: <tt>zypper install libvirt-client</tt><br />
<br />
==== Error The workflow mkrescue is not supported in the ReaR rescue/recovery system ====<br />
<br />
Delete the file /etc/rear-release<br />
<br />
==== REAR image hangs during bootup ====<br />
<br />
In case the system hangs during bootup like shown in the following image:<br />
<br />
[[File: rear-hang.jpg|link=]]<br />
<br />
try booting the system with the ACPI=OFF option (this option can be specified on the command line in the boot menu prompt, after the options BACKUP=SESAM OUTPUT=ISO)<br />
<br />
==== RHEL6/CENTOS6 ====<br />
<br />
===== Client won't start in recovery image =====<br />
<br />
The Sesam client will not automatically start on RHEL6 based Recovery images as the file "/etc/init.d/functions" is missing within the recovery image. The client can be started manually via:<br />
<br />
/opt/sesam/bin/sesam/sm_main start<br />
<br />
===== Recovered system wont boot because of missing "libblkid.so.1" =====<br />
<br />
If the recovered system won't boot, this is most probably caused by SELinux which is activated by default. <br />
Especially on RedHat Enterprise Linux 6 or CentOS 6 systems, follow these steps after rebooting from the REAR recover:<br />
<br />
* Press a key when prompted by the boot loader (GRUB):<br />
[[File: rhelcentos_grub1.jpg|link=]]<br />
<br />
<br />
* Select the appropriate boot loader entry:<br />
[[File: rhelcentos_grub2.jpg|link=]]<br />
<br />
<br />
* Press 'e' to edit the commands for the selected entry:<br />
[[File: rhelcentos_grub3.jpg|link=]]<br />
<br />
<br />
* Add 'selinux=0' to the commands:<br />
[[File: rhelcentos_grub4.jpg|link=]]<br />
<br />
<br />
* Press 'Enter' to confirm the changes and 'b' to boot up the machine with SELinux disabled.<br />
<br />
When having access to the system, change the option SELINUX of ''/etc/selinux/config'' to the following:<br />
SELINUX=permissive<br />
<br />
Afterwards, reboot the system and feel free to set the SELINUX value back to 'enforcing' if needed.<br />
<br />
<br />
==== RHEL7 ====<br />
<br />
===== backup fails with ERROR: The LSB package is not installed =====<br />
<br />
If the backup fails with:<br />
<br />
ERROR: The LSB package is not installed.<br />
<br />
Please install the lsb package:<br />
<br />
yum install redhat-lsb-core mkisofs syslinux<br />
<br />
===== backup fails with: ERROR: Cannot find required programs: mingetty =====<br />
<br />
See the following documentation:<br />
<br />
https://github.com/rear/rear/issues/348<br />
<br />
Please edit:<br />
<br />
/var/opt/sesam/var/lib/rear/usr/share/rear/conf/default.conf<br />
<br />
in and in the line:<br />
<br />
# required programs. Same as above, but if they are missing, we abort.<br />
REQUIRED_PROGS=(<br />
"$SCRIPT_FILE"<br />
<br />
remove the line:<br />
<br />
mingetty<br />
<br />
and try the backup again.<br />
<br />
=====UEFI=====<br />
<br />
=====rear error occurred during grub2-mkimage of bootx64.efi=====<br />
<br />
Please install the grub2-efi-x64-modules package to fix this<br />
<br />
==== Debian9 ====<br />
===== Client won't start in recovery image =====<br />
<br />
The Sesam client will not automatically start on Debian9 based Recovery images. The client can be started manually via:<br />
<br />
/opt/sesam/bin/sesam/sm_main start<br />
<br />
==== SLES ====<br />
===== SM_SSH not working on SLES11 recovery image=====<br />
<br />
execute <br />
mount -t tmpfs none /dev/shm/ -o rw,nosuid,nodev,noexec<br />
before starting the recovery process<br />
<br />
===== UEFI =====<br />
<br />
====== Install EBISO for creating UEFI aware ISO images ======<br />
<br />
In order to be able to create an UEFI/EFI bootable iso image the additional tool "ebiso" has to be installed on the client system. This Package is not part of a regular SLES12/SLES15 installation and can be downloaded at the following URL:<br />
<br />
http://download.opensuse.org/repositories/Archiving:/Backup:/Rear/SLE_12/x86_64/<br />
<br />
or:<br />
<br />
http://download.sep.de/utils/bsr-linux/<br />
<br />
For other Linux distributions please contact support@sep.de<br />
<br />
Installation via:<br />
<br />
rpm -i ebiso-<version>.rpm<br />
<br />
====== Additional configuration ======<br />
<br />
<br />
In some cases the generated ISO Image mount will be too small for storing all needed information and has to be adjusted, this is will be fixed in future REAR verisons (1.19):<br />
<br />
'''/var/opt/sesam/var/lib/rear/usr/share/rear/lib/uefi-functions.sh''' (line64):<br />
<br />
change:<br />
<br />
(shim.efi|elilo.efi) size=128000 ;;<br />
<br />
to:<br />
<br />
(shim.efi|elilo.efi) size=228000 ;;<br />
<br />
===== restore: client is unreachable =====<br />
<br />
after booting the rescue image the client is not reachable, please start the client manually using the following command on the rescue command line:<br />
<br />
sh /etc/scripts/system-setup.d/59-start-sesam-client.sh<br />
<br />
== Further documentation ==<br />
* For further information about ''Relax and Recover'' [http://relax-and-recover.org/ see here]</div>Fho