{"id":3238,"date":"2017-01-09T07:00:47","date_gmt":"2017-01-09T06:00:47","guid":{"rendered":"https:\/\/www.data-protector.org\/wordpress\/?p=3238"},"modified":"2017-01-09T08:27:17","modified_gmt":"2017-01-09T07:27:17","slug":"data-protector-systemd-rhel-7","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2017\/01\/data-protector-systemd-rhel-7\/","title":{"rendered":"Data Protector with &#8220;systemd&#8221; on RHEL 7"},"content":{"rendered":"<p><b>Update 2017\/01\/09:<\/b> After some discussions with colleagues&#8230; you need to know, that for Data Protector clients &#8220;systemd&#8221; is used and only on Cell Manager the legacy mode with &#8220;xinetd&#8221; is leveraged. Even with the legacy mode there is no need to change to &#8220;systemd&#8221;, as &#8220;xinetd&#8221; is supported on RHEL too.<\/p>\n<\/p>\n<p>\nThere are Data Protector customers interested to use <code>systemd<\/code> on RHEL 7, instead of <code>xinetd<\/code>. A colleague (Michael S.) sent a short how to with the required steps.\n<\/p>\n<ul>\n<li>Modify file <code>\/etc\/xinetd.d\/omni<\/code> and change the parameter disable: <code>disable = yes<\/code>. Optional: Move the file to another location or delete it.<\/li>\n<li>Create the file <code>data-protector.socket<\/code> in folder <code>\/etc\/systemd\/system<\/code> and add the following entries:<br \/>\n<blockquote style=\"font: 12px Courier; background-color: #ffffff; border: 1px solid #ccc; border-radius: 6px; box-shadow: 1px 1px 1px #ccc;\">\n<pre style=\"border: 0px; background-color: #ffffff;\">\r\n[Unit]\r\nDescription=Data Protector Socket\r\n\r\n[Socket]\r\nListenStream=5555\r\nAccept=yes\r\nBindIPv6Only=both\r\n\r\n[Install]\r\nWantedBy=sockets.target\r\n<\/pre>\n<\/blockquote>\n<\/li>\n<li>Create the file <code>data-protector@.service<\/code> in folder <code>\/etc\/systemd\/system<\/code> and add the following entries:<br \/>\n<blockquote style=\"font: 12px Courier; background-color: #ffffff; border: 1px solid #ccc; border-radius: 6px; box-shadow: 1px 1px 1px #ccc;\">\n<pre style=\"border: 0px; background-color: #ffffff;\">\r\n[Unit]\r\nDescription=Data Protector Server\r\n\r\n[Service]\r\nExecStart=\/opt\/omni\/lbin\/inet -log \/var\/opt\/omni\/log\/inet.log\r\nUser=root\r\nStandardInput=socket<\/pre>\n<\/blockquote>\n<\/li>\n<li>Restart daemon <code>xinetd<\/code> to deactivate port 5555: <code>systemctl restart xinetd<\/code><\/li>\n<li>Enable the socket <code>data-protector.socket<\/code> using the command: <code>systemctl enable data-protector.socket<\/code><\/li>\n<li>Start the socket <code>data-protector.socket<\/code> using the command: <code>systemctl start data-protector.socket<\/code><\/li>\n<li>Verify port 5555 using the command: <code>netstat \u2013an | grep 5555<\/code> or <code>ss \u2013ln | grep 5555<\/code> or <code>ss \u2013l | grep omni<\/code><\/li>\n<li>If possible try to restart the server to verify the changes made are psersistent.<\/li>\n<li>As usual, you could leverage telnet for the verification:<br \/>\n<blockquote style=\"font: 12px Courier; background-color: #ffffff; border: 1px solid #ccc; border-radius: 6px; box-shadow: 1px 1px 1px #ccc;\">\n<pre style=\"border: 0px; background-color: #ffffff;\">\r\n[root@rheldp908 ~]# telnet rheldp907 5555\r\nTrying 192.128.253.132...\r\nConnected to rheldp907.\r\nEscape character is '^]'.\r\nHP Data Protector A.09.00: INET, internal build 110, built on Thu Aug 11 12:37:31 2016\r\nConnection closed by foreign host.\r\n<\/pre>\n<\/blockquote>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Update 2017\/01\/09: After some discussions with colleagues&#8230; you need to know, that for Data Protector clients &#8220;systemd&#8221; is used and only on Cell Manager the legacy mode with &#8220;xinetd&#8221; is leveraged. Even with the legacy mode there is no need to change to &#8220;systemd&#8221;, as &#8220;xinetd&#8221; is supported on RHEL too. There are Data Protector [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3239,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[11],"tags":[],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"en","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":false,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/12\/rhel72.png","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-Qe","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":694,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/07\/data-protector-migration-unix-to-other-os\/","url_meta":{"origin":3238,"position":0},"title":"Data Protector Migration Unix to other OS","date":"29. July 2011","format":false,"excerpt":"{:de}Ich kenne nicht viele gute Gr\u00fcnde warum man eine Data Protector Installation von HP-UX auf ein anderes Betriebssystem wechseln sollte,\u00a0dennoch gibt es viele Kunden die diesen Schritt gehen wollen und zum Beispiel auf Windows oder Linux wechseln;\u00a0meist noch verbunden mit einem Upgrade auf eine aktuelle Version von Data Protector.\u00a0Und hier\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1662,"url":"https:\/\/www.data-protector.org\/wordpress\/2016\/01\/data-protector-8-0-windows-change-user-account-dp-services\/","url_meta":{"origin":3238,"position":1},"title":"Data Protector 8.0 Windows &#8211; change user account for DP services","date":"30. January 2016","format":false,"excerpt":"{:en}In previous versions of Data Protector it was simple to change the user account for the Data Protector services. With Data Protector 8.0 and the new IDB some more steps are required to change the user. The steps below were verified in a test environment. Stop the Data Protector services\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1480,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/07\/data-protector-8-00-cifs-share-backup\/","url_meta":{"origin":3238,"position":2},"title":"Data Protector 8.00 and CIFS Share Backup","date":"5. July 2013","format":false,"excerpt":"{:en}When using Data Protector 8.00 to backup a CIFS share (Network Share Backup), no matter if it is a Windows share or NetApp Filer, it could happen that the job does not backup any data from the share. In more detail, when selecting to backup all folders for the share\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":313,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/01\/eadr-mit-windows-2008-r2\/","url_meta":{"origin":3238,"position":3},"title":"EADR with Windows 2008 R2","date":"21. January 2011","format":false,"excerpt":"{:de}In einen fr\u00fcheren Artikel hatte ich \u00fcber die Wiederherstellung eines Windows 2003 Servers mit Data Protector berichtet. Nachdem Windows 2008 auch immer mehr in Rechenzentren betrieben wird zeige ich nachfolgend die Wiederherstellung eines Windows 2008 R2 Servers mit Data Protector und der Enhanced Automated Disaster Recovery Funktion. Vorbereitung: In der\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":114,"url":"https:\/\/www.data-protector.org\/wordpress\/2010\/07\/614039-no-more-space-in-any-of-the-detail-catalog-directories\/","url_meta":{"origin":3238,"position":4},"title":"[61:4039] No more space in any of the Detail Catalog directories","date":"7. July 2010","format":false,"excerpt":"{:en}The error [61:4039] could occur when the limit of the detail catalog is reached. In Data Protector 6.11 the size limit for a DCBF directory was increased up to 16 GB, in former versions the limit was set to 4 GB. For my customers I usually add at least addidtional\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1987,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/05\/distribute-omnirc-file\/","url_meta":{"origin":3238,"position":5},"title":"Distribute omnirc File","date":"23. May 2014","format":false,"excerpt":"{:en} You know Data Protector? So you know that the modification of parameter for Data Protector is done in file global and in file omnirc. The file global is maintained on the Cell Server directly, but the file omnirc (Linux\/HP-UX: \/opt\/omni, Windows 2008 C:\\programdata\\omniback) has to be maintained on each\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3238"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=3238"}],"version-history":[{"count":8,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3238\/revisions"}],"predecessor-version":[{"id":3289,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3238\/revisions\/3289"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media\/3239"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=3238"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=3238"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=3238"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}