To cut a long story short, you can install the Data Protector agent quite happily (I pushed it from my Linux-based installation server which has OB2_SSH_ENABLED=1 by adding my ssh key to the server appliance's .ssh/authorized_keys). But then it can't be imported.
You will see lines like this appear in the appliance's /var/log/messages :
2015-01-19T01:25:06+00:00 app01 xinetd: libwrap refused connection to omni (libwrap=inet) from ::ffff:192.168.1.14
2015-01-19T01:25:06+00:00 app01 xinetd: FAIL: omni libwrap from=::ffff:192.168.1.14
It's been so long since I dealt with TCP wrappers that I spent ages remembering what to do. In the end, it's just a matter of putting the following into /etc/hosts.allow
inet: 192.168.1.0/255.255.255.0 : ALLOW
Adjust based on whatever IP ranges and subnets you need to allow. Or use "ALL" instead of 192.168.1.0/255.255.255.0 if you don't have any security concerns.
Greg Baker is an independent consultant who happens to do a lot of work on HP DataProtector. He is the author of the only published books on HP Data Protector (http://www.ifost.org.au/press/#dp). He works with HP and HP partner companies to solve the hardest big-data problems (especially around backup). See more at IFOST's DataProtector pages at http://www.ifost.org.au/dataprotector
Post a Comment