{"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":3514,"url":"https:\/\/www.data-protector.org\/wordpress\/2017\/09\/data-protector-10-patch-bundle-a-10-01-build-307\/","url_meta":{"origin":3238,"position":0},"title":"Data Protector 10 \u2013 Patch Bundle A.10.01 (Build 307)","date":"28. September 2017","format":false,"excerpt":"{:en}The Patch Bundle A.10.01 (Build 307) for Data Protector 10 has been released on September 28, 2017. This first cumulative patch can be installed on top of A.10.00. It is recommended to install it on all Installation Servers (IS) and the Cell Managers (CM). Then push the new packages from\u2026","rel":"","context":"In &quot;DP A.10.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2262,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/01\/data-protector-9-02-features-explained\/","url_meta":{"origin":3238,"position":1},"title":"Data Protector 9.02 features explained","date":"27. January 2015","format":false,"excerpt":"{:en} In December HP released the new Data Protector version 9.02. With this release additional features were implemented. Some of the new features are explained in more detail below. New Data Protector features: Pausing and Resuming Backup Jobs Reporting for Capacity Based Licensing VMware GRE for 3PAR Snapshots StoreOnce CoFC\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4432,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/12\/data-protector-10-updated-release-a-10-20-build-115\/","url_meta":{"origin":3238,"position":2},"title":"Data Protector 10 \u2013 Updated Release A.10.20 (Build 115)","date":"10. December 2018","format":false,"excerpt":"{:en}Data Protector\u00a0A.10.20 (Build 115)\u00a0has been released on December 6, 2018. The new version is another full install to simplify the upgrade and installation process.This will continue to be the default for all future Data Protector versions. Data Protector 10.20 does not require any previous version to install the latest version\u2026","rel":"","context":"In &quot;DP A.10.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4032,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/05\/complex-schedules-data-protector-10-03\/","url_meta":{"origin":3238,"position":3},"title":"Complex Schedules in Data Protector","date":"9. May 2018","format":false,"excerpt":"{:en}Transitioning to the new Consolidated Scheduler, introduced with Data Protector A.10.00, can be a challenge. Especially when customized schedules have been used in the Legacy Scheduler to overcome former product limitations. A common example are manually modified schedule files to execute jobs at the last weekend of the month. Data\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"https:\/\/i2.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/04\/2018-04-28_13h04_46-450x305.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":3072,"url":"https:\/\/www.data-protector.org\/wordpress\/2016\/05\/script-distribute-omnirc-file\/","url_meta":{"origin":3238,"position":4},"title":"Script to distribute omnirc file","date":"18. May 2016","format":false,"excerpt":"{:en} Since Data Protector 8.11 version it is possible to distribute omnirc parameter for the Data Protector clients using a command. In a former article I informed about - please refer to https:\/\/www.data-protector.org\/wordpress\/2014\/05\/distribute-omnirc-file\/. Using omnirc settings you can control the client behavior and is important from performance point of view\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/05\/omnircsync.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":1393,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/05\/advisory-c03753986\/","url_meta":{"origin":3238,"position":5},"title":"Advisory c03753986","date":"25. May 2013","format":false,"excerpt":"{:en}With document ID c03753986 on 2013\/05\/06 an advisory for HP Data Protector 6.11, 6.20, 6.21, 7.0 and 7.01 was released, describing a problem for restores of SAP data files and the file size is different from the SAP data file. When the omnirc parameter OB2SAPALIGN was used on Unix a\u2026","rel":"","context":"In &quot;Advisory&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}]}}