Data Protector with “systemd” on RHEL 7

Update 2017/01/09: After some discussions with colleagues… you need to know, that for Data Protector clients “systemd” is used and only on Cell Manager the legacy mode with “xinetd” is leveraged. Even with the legacy mode there is no need to change to “systemd”, as “xinetd” is supported on RHEL too.

There are Data Protector customers interested to use systemd on RHEL 7, instead of xinetd. A colleague (Michael S.) sent a short how to with the required steps.

• Modify file /etc/xinetd.d/omni and change the parameter disable: disable = yes. Optional: Move the file to another location or delete it.
• Create the file data-protector.socket in folder /etc/systemd/system and add the following entries:
  

  [Unit]
  Description=Data Protector Socket
  
  [Socket]
  ListenStream=5555
  Accept=yes
  BindIPv6Only=both
  
  [Install]
  WantedBy=sockets.target
  

• Create the file data-protector@.service in folder /etc/systemd/system and add the following entries:
  

  [Unit]
  Description=Data Protector Server
  
  [Service]
  ExecStart=/opt/omni/lbin/inet -log /var/opt/omni/log/inet.log
  User=root
  StandardInput=socket

• Restart daemon xinetd to deactivate port 5555: systemctl restart xinetd
• Enable the socket data-protector.socket using the command: systemctl enable data-protector.socket
• Start the socket data-protector.socket using the command: systemctl start data-protector.socket
• Verify port 5555 using the command: netstat –an | grep 5555 or ss –ln | grep 5555 or ss –l | grep omni
• If possible try to restart the server to verify the changes made are psersistent.
• As usual, you could leverage telnet for the verification:
  

  [root@rheldp908 ~]# telnet rheldp907 5555
  Trying 192.128.253.132...
  Connected to rheldp907.
  Escape character is '^]'.
  HP Data Protector A.09.00: INET, internal build 110, built on Thu Aug 11 12:37:31 2016
  Connection closed by foreign host.